메뉴
Product density — how much complexity the domain tolerates on each surface. Not sovereign/transient platform essays.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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-design. Also matches /lamina-design and $lamina-design. Turn a product idea or brownfield change into a ready_to_build contract under .lamina/runs (run.json + implement.md). Prefer scripts/seed-ready-run.mjs for concrete feature briefs. Vague briefs must clarify-and-STOP before any seed.
Use only when explicitly invoked as lamina. Also handles /lamina-design, /lamina-verify, and /lamina-init. Route product design for developers building with AI — design, verify, init, or direct capability answers. For /lamina-design seed via seed-ready-run.mjs; for /lamina-verify seed via seed-verify-run.mjs.
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. Vague “audit our app” briefs must clarify-and-STOP before any seed.
Product design skill for developers who build with AI coding agents. Use when you need to know what to build before prompting your agent — domain model, workflows, edge cases, product states, and UX gaps handled upfront. Works alongside Cursor, Claude Code, Codex, Gemini, Pi. Any stack, any UI library. Do NOT use for visual styling, pixel layouts, or writing app source.
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.
| name | lamina-platform-posture |
| description | Product density — how much complexity the domain tolerates on each surface. Not sovereign/transient platform essays. |
| metadata | {"lamina":{"id":"platform-posture","problems":["information density","complexity budget"],"related":["lamina-information-architecture","lamina-discoverability"]}} |
Define complexity budget per actor and surface in the contract — when to expose power vs simplify.
surfaces[]: primary actions, deferred settings