laminalisted

# /lamina Use this as the compact Lamina router. The public catalog has four workflow skills and six capability skills. Load only the entrypoint and topic references needed for the current request. Before graph work, read [the CLI prerequisite](orchestrator/prerequisites/cli-required.md). `/lamina-init` is the one explicit onboarding action. After initialization, ordinary product implementation language is the primary route. ## Workflow routes - `/lamina-init`: use [lamina-init](../lamina-init/SKILL.md). - Ordinary feature, behavior fix, flow refactor, or UI work: prepare the graph context, complete design gaps with [lamina-design](../lamina-design/SKILL.md), derive and check the WorkMap, implement, collect evidence, and run `lamina work verify`. - Explicit `/lamina-design`: use [lamina-design](../lamina-design/SKILL.md) as a graph-only advanced override; never edit application source in that phase. - Explicit `/lamina-verify`: use [lamina-verify](../lamina-verify/SKILL.md) as a source-read-only advanced override; never edit application source in that phase. - Focused product question: select one primary capability below, read its `SKILL.md`, then read the smallest relevant topic set before answering. Start the response with `Using <capability>: <topic(s)>` so routing is visible and deprecated focused names are never implied. Never recommend `/lamina-design` or `/lamina-verify` as a next step in normal flow. Execute the required phase implicitly. Ask a