Command Guide
Every adapter you select gets all 27 skills — the groupings below exist purely to help you locate the one you want, not to describe separate install modes or configuration.
Examples show Claude Code’s slash syntax. Codex takes the matching $skill
form, and other adapters accept the same request in plain language.
Not sure which one to reach for?
Section titled “Not sure which one to reach for?”| You want to | Start here |
|---|---|
| “Create the app — I have nothing yet.” | /scaffold |
| “Would caching help this dashboard?” | /explore |
| “Explain feature 5 before we spec it.” | /brief 5 |
| “Build the next planned feature.” | /feature, approve, then /implement |
| “Something is broken and I don’t know why.” | /debug |
| “I know the bug or small change we need.” | /fix |
| “Show that this feature works.” | /check |
| “Tell me how to test it myself.” | /check guide |
| “Review the implementation for defects.” | /audit current |
| “What testing does this project need?” | /test-plan |
| “Write test cases for this feature.” | /test-cases |
| “Automate the regression suite.” | /automate |
| “Run a full regression cycle.” | /test-run |
| “Where did we leave off?” | /status |
| “Is Syntaxis set up correctly?” | /doctor |
| Command | Purpose |
|---|---|
/feature |
Turn one build-plan item into a spec for your approval |
/implement |
Build the approved spec, then offer a code walkthrough |
/check |
Verify real behaviour; /check guide for a manual walkthrough |
/complete |
Final gates, archive the work, request merge approval |
Understand and review
Section titled “Understand and review”| Command | Purpose |
|---|---|
/explore |
Investigate an idea without writing files or requiring plans |
/brief |
Explain a planned feature, its dependencies, and likely size |
/status |
Progress, drift, blockers, and the next action |
/debug |
Reproduce and isolate a failure without editing code |
/audit |
Review code and record findings |
/doctor |
Check installation and workflow health |
Plan and set up
Section titled “Plan and set up”| Command | Purpose |
|---|---|
/scaffold |
Create the application for one of nine stacks |
/onboard |
Tune a fresh installation to the real project |
/adopt |
Bring Syntaxis into a codebase that already ships |
/discovery |
Develop the two plans through conversation |
/overview |
Generate durable context from both plans |
/prototype |
Throwaway static mockups before implementation |
/tests |
Set up a unit, browser, or mobile harness |
/ci |
Align one Verify command with GitHub checks |
Quality assurance
Section titled “Quality assurance”| Command | Purpose |
|---|---|
/test-plan |
Master test strategy, environments, and exit criteria |
/test-cases |
Design cases with durable IDs and traceability |
/automate |
Turn stable cases into web or mobile specs |
/test-run |
Execute a cycle, record evidence, open findings |
Recover and release
Section titled “Recover and release”| Command | Purpose |
|---|---|
/fix |
Spec a small unplanned change or confirmed bug |
/rollback |
Plan a history-preserving reversal |
/release |
Local deployment readiness; deploying needs separate approval |
Automation
Section titled “Automation”| Command | Purpose |
|---|---|
/autopilot |
One bounded spec-and-build pass, stopping before completion |
/continuous |
Complete reviewed items serially, local Git only |