Spacewave Debug
Testing & Qualityspacewave-debugSpacewave Debug is an Agent Skill for testing & quality published in the s4wave/spacewave repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use the spacewave-debug CLI to inspect and interact with the running page.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/s4wave/spacewave/blob/HEAD/.claude/skills/spacewave-debug/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/spacewave-debug, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Spacewave Debug
Use the spacewave-debug CLI tool to inspect the running Spacewave Alpha page from the terminal.
Quick reference:
# Get page info
go run ./cmd/spacewave-debug/ info
# Evaluate JS expression (auto-returns single expressions)
go run ./cmd/spacewave-debug/ eval "document.title"
# Evaluate from file (avoids shell quoting issues)
go run ./cmd/spacewave-debug/ eval --file .tmp/script.js
# Evaluate TypeScript from file (bundles with the app aliases first)
go run ./cmd/spacewave-debug/ eval --file .tmp/script.ts
# Show exact visual line breaks
go run ./cmd/spacewave-debug/ linebreaks "h1"
# Detect typographic orphans
go run ./cmd/spacewave-debug/ orphans "p"
# Dump geometry and typography
go run ./cmd/spacewave-debug/ measure ".card"
# Check grid row height consistency
go run ./cmd/spacewave-debug/ grid-check ".grid"
# Preview text rendering (inject, measure, restore)
go run ./cmd/spacewave-debug/ preview-text "h1" "New heading"
# Watch: re-evaluate a JS file on interval
go run ./cmd/spacewave-debug/ watch --file .tmp/script.js
Notes
- Prefer
eval --file .tmp/script.jsoreval --file .tmp/script.tsfor anything more than a short expression. Inline shell quoting gets fragile fast. - Plain expression eval auto-returns the expression value. Multi-line JavaScript
should use an explicit
returnwhen a result is needed. - TypeScript eval files are bundled through Vite, so app aliases such as
@s4wave/...are available. - The page-side eval result is serialized with
JSON.stringify. Convertbigintvalues to strings in debug scripts before exporting or returning. - Use
window.__s4wave_debug.rootto access the SDK root from page context. When using resource handles in TypeScript eval scripts, dispose only actual resource instances. For example,mountSessionByIdxreturns a wrapper object; useconst mounted = await root.mountSessionByIdx(...)and thenusing session = mounted.session. - If TypeScript eval reports a module MIME/type error or fails to fetch a
dynamically imported module, check that the debug bridge is serving
/p/spacewave-debug/eval/*.jsand the emitted chunks in.bldr/debug/eval/out/.