/lamina-design

Turn a domain into a build-ready contract. Lamina models product behavior at the intersection of UX, product rules, and systems thinking — then writes implement.md for your coding agent.

Quick path

1. Confirm /lamina-init has run (init gate)
2. Run /lamina-design with a specific flow or feature
3. Check run.json status is ready_to_build
4. Hand implement.md to your coding agent

Prerequisites

Valid .lamina/business-context.md from /lamina-init. Without it, design is blocked.

When to use

• After /lamina-init on a new or brownfield project
• When starting a new feature or flow
• When you need states, roles, dependencies, and edge cases specified before coding
• When verify finds fix_target: contract gaps

Examples

/lamina-design Guest checkout with inventory hold, payment, and cancellation

/lamina-design Hotel onboarding with property review and admin approval gate

/lamina-design Hall ticket download with payment gate and venue assignment

What Lamina does

1. Models the domain — entities, states, invariants, dependencies (reachability graph)
2. Defines actors — roles, goals, permissions (references personas.json)
3. Maps workflows — primary paths, alternate paths, operations over states
4. Enumerates scenarios — permission denials, unmet dependencies, invariant violations
5. Specifies screens — structural UX surfaces tied to workflows (no styling)
6. Writes implement.md — stack-agnostic build brief at ready_to_build

What it writes

Output lands in .lamina/runs/<id>/:

Brownfield design

On existing codebases, Lamina performs a bounded repo scan to ground the contract in what already exists. Existing screens are marked status: existing with repo source paths in surfaces[].

What to do next

Hand implement.md to your coding agent:

Implement from .lamina/runs/<id>/implement.md

Lamina never writes app source. Your agent builds using your stack, framework, and UI library.

After implementation, run /lamina-verify guest checkout at http://localhost:3000 (or the flow you designed).

Tips

• Scope one flow per design call — “guest checkout” not “the entire app”
• Include constraints in natural language: “hold expires after 15 minutes”
• Check run.json status is ready_to_build before implementing
• Reference dependency ids in workflows, not free-text preconditions

Next steps

• run.json schema — full contract reference
• /lamina-verify — verify after implementation
• Per-run artifacts — file-by-file reference