メニュー
Represented model matches domain — UI must not imply illegal states or permissions. Use when run.json domain and screens diverge from implementation shape.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use only when explicitly invoked as lamina-design. Turn an incomplete product idea or brownfield change into a minimum sufficient product behavior graph: actors, entities, operations, workflows, rules, dependencies, decisions, persona perspectives, and distinct risks; then generate an implementation-ready contract.
Use only when explicitly invoked as lamina-init. Turn an incomplete product idea into usable business context and evidence-grounded personas, asking only high-leverage questions and labeling provisional assumptions for later product-graph design.
Product design workflows — domain contracts, implement brief, verify loop. Load via Read or Skill tool when /lamina-* workflows need it.
Use only when explicitly invoked as lamina. Route product design for developers building with AI — design, verify, or direct capability answers.
Use only when explicitly invoked as lamina-verify. Verify a live or brownfield product against its product graph: critical promises, reachable workflows, authority, invariants, state integrity, recovery, accessibility, and contract drift; emit evidence-backed fixes before merge.
Business context UX guidance. Use when bootstrapping Lamina for a project; answering business questions UX work needs; updating context after a pivot or scope change.
| name | lamina-product-behavior |
| description | Represented model matches domain — UI must not imply illegal states or permissions. Use when run.json domain and screens diverge from implementation shape. |
| metadata | {"lamina":{"id":"product-behavior","problems":["UI mirrors database or org structure","represented vs mental model","behavior before build"],"related":["lamina-flow-design","lamina-user-modeling","lamina-platform-posture","lamina-invariants"]}} |
The represented model in run.json must match how actors conceive tasks — simpler than implementation, aligned with domain invariants.
| Layer | Artifact |
|---|---|
| Domain truth | entities[], invariants[] |
| What actors can do | actors.permissions, workflows |
| What UI shows | surfaces[] — no affordance for forbidden operations |
| Illegal states | scenarios[] + disabled/hidden actions in screen spec |
Implementation model stays in external code. Lamina specifies represented model only.
decisions.md when pillars conflict.implement.md, don't prescribe UI library.entities[] vocabulary.decisions.md.ux.