/lamina
The optional entry point when you are unsure which Lamina command to run. Routes an explicit /lamina <request> to design, verify, or a focused capability skill based on intent. It is not required setup and does not replace /lamina-init.
Quick path
- Run
/laminawith no args to see available commands - Or run
/lamina <what you need>with your request in the same slash command - Lamina routes to the right workflow or answers directly
When to use
- You are not sure which slash command to run (optional router — not a substitute for
/lamina-init) - You have a focused product design question (direct mode)
- You want Lamina to interpret intent from an explicit
/lamina <request>command
Routing logic
Lamina parses your message and dispatches to the first strong match:
| Your intent | Routes to |
|---|---|
| ”Add hall ticket feature”, “spec booking flow” | /lamina-design workflow |
| ”We don’t know what to build”, early exploration | /lamina-design workflow |
| ”Implementation done”, “audit settings”, “fix flow” | /lamina-verify workflow |
| ”Redesign checkout”, “review existing UI” | /lamina-verify workflow |
| Single clear topic (e.g. “what invariants apply here?”) | Direct mode — one capability skill |
| Ambiguous | Lamina asks: design, verify, or focused question? |
Verify vs design
| You say | Route |
|---|---|
| ”Redesign checkout”, “audit settings”, “implementation done” | Verify |
| ”Add hall ticket feature”, “spec booking flow” | Design |
| ”We don’t know what to build” | Design (after init) |
Advanced: Implementing fixes from fix.md is not a Lamina command. Your coding agent reads .lamina/runs/<id>/fix.md in a normal coding session and writes app source outside Lamina.
Direct mode
When you ask a focused question, /lamina loads a single capability skill instead of a full workflow:
/lamina What invariants should a booking hold enforce?/lamina How should we handle permission denial in checkout?Direct mode skills cover systems thinking, UX, and agent simulation topics. See Skill map for the full list.
Prerequisite check
Before routing to design or verify, Lamina checks for valid .lamina/business-context.md. If missing, you get an init-blocked response directing you to /lamina-init.
Examples
/lamina/lamina Design guest checkout with inventory hold for a rental marketplace/lamina Verify guest checkout at http://localhost:3000/lamina What edge cases should we cover for concurrent booking holds?What Lamina writes
Only .lamina/ artifacts. Never app source. See Guardrails and Contracts and runs.
Next steps
- /lamina-init — bootstrap domain context
- /lamina-design — design a contract
- /lamina-verify — verify the live build