Skill map

Lamina installs as exactly 10 public skills. Four are workflow entrypoints and six group related product capabilities. Each capability keeps its focused guidance as topic references that agents load only when relevant.

Workflow skills

Skill	Use it for
`lamina`	Route ordinary product implementation and focused questions
`lamina-init`	Initialize a project’s business context and provider rules
`lamina-design`	Run the explicit graph-only design phase
`lamina-verify`	Run the explicit source-read-only verification phase

Ordinary product work starts through lamina; design and verification phases run implicitly. /lamina-design and /lamina-verify remain advanced explicit overrides.

Capability skills

Skill	Topics inside it
`lamina-research`	Evidence scoping, actor walks, grounding, interviews, task analysis, synthesis, communication
`lamina-product-discovery`	Problem framing, business context, stakeholders, feature discovery and priority, requirements, tradeoffs, decisions
`lamina-ux`	Flows, IA, navigation, content, forms, controls, onboarding, feedback, errors, accessibility, disclosure, trust, edge cases
`lamina-product-behavior`	Represented models, platform posture, side effects, invariants, consistency, concurrency, time, dependencies, boundaries, multi-view integrity
`lamina-systems`	System structure, feedback loops, traps, leverage points, evolutionary rules
`lamina-evaluation`	Persona usability evaluation, heuristic review, quantitative validation

Install with --skill '*'. All 10 public entrypoints and their nested references arrive together, so an audit profile can name an exact topic without exposing dozens of focused skills to the user.

Progressive loading

Start with one public skill. Read its SKILL.md topic index, then load only the references required by the request or audit profile. Internal orchestration lives under skills/lamina/orchestrator/; it is packaged with lamina but is not separately discoverable.

Old focused skill names are not aliases. The machine-readable skills/migration-map.json maps each former name to its compact skill and exact topic.

Examples


/lamina What invariants should a booking hold enforce?

Routes to lamina-product-behavior and its invariants topic.


/lamina How should permission denial appear during checkout?

Routes to lamina-ux edge-case and error-handling topics, plus product behavior when authorization rules need clarification.

Next steps

/lamina command — router and ordinary mode
Orchestrator — audit-profile coordination
Glossary — product graph terms