Commands

Lamina exposes four slash commands. Each maps to a phase in the init → design → implement → verify loop. Lamina does not activate passively — run each command explicitly in agent chat.

Quick path


/lamina-init <domain>
/lamina-design <feature or flow>
# your agent implements from implement.md
/lamina-verify guest checkout at http://localhost:3000
# your agent fixes from fix.md, then re-verify
/lamina-verify guest checkout at http://localhost:3000

Command reference

Command	Phase	Purpose
`/lamina`	Router	Optional — route explicit `/lamina <request>` to design, verify, or direct Q&A
`/lamina-init`	Charter	Domain scope — required before design or verify
`/lamina-design`	Design	`run.json`, `run.md`, `implement.md` at `ready_to_build`
`/lamina-verify`	Verify	Updated `run.json` findings, `report.md`, `fix.md`, optional `walkthrough/`

Prerequisite gates

Command	Requires
`/lamina-init`	None
`/lamina-design`	Valid `.lamina/business-context.md` from init
`/lamina-verify`	Valid `.lamina/business-context.md` from init
`/lamina` (design/verify routes)	Same gates as the dispatched command

Advanced: The init gate cannot be bypassed. If business-context.md is missing or invalid, design and verify return a blocked response and stop.

Typical sequence


/lamina-init Boutique hotel booking marketplace
/lamina-design Guest checkout with payment hold and cancellation
# … your agent implements from implement.md …
/lamina-verify guest checkout at http://localhost:3000
# … your agent fixes from fix.md …
/lamina-verify guest checkout at http://localhost:3000

Optional routing

If you are unsure which command to run, use the optional router — still an explicit slash command, not passive invocation:


/lamina Design the onboarding flow for a team collaboration app

/lamina interprets your request and dispatches to the right workflow. It does not replace /lamina-init on a new project.

What Lamina does not do

Action	Who handles it
Write app source	Your coding agent
Implement fixes from `fix.md`	Your coding agent (normal coding session)
Pick your framework or database	You
Style UI (colors, typography)	UI skills or your agent

Next steps

/lamina router — optional routing via /lamina <request>
Quickstart — full walkthrough
The loop — design → implement → verify cycle