القائمة
Product invariants — rules that must always hold, impossible states prevented, errors defined out of existence. Use when defining what can never happen in the product.
التثبيت باستخدام 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-invariants |
| description | Product invariants — rules that must always hold, impossible states prevented, errors defined out of existence. Use when defining what can never happen in the product. |
| metadata | {"lamina":{"id":"invariants","problems":["impossible states","business rules that must always hold","preventing duplicate or inconsistent records","illegal state transitions"],"related":["lamina-system-structure","lamina-dependencies","lamina-consistency-guarantees","lamina-idempotency-concurrency","lamina-edge-cases"],"tags":["design-default"]}} |
Rules the product must never violate. Design so illegal states are unrepresentable — not merely error-handled after the fact.
Each invariants[] id gets a probe in /lamina-verify — attempt violation on live product; UI must prevent or recover per linked scenarios[].
Invariants vs dependencies: Invariants are predicates that must hold in valid states. Dependencies are reachability edges — what must exist before a workflow can succeed. Do not collapse them; use Dependencies for cross-feature setup.
Invariant: A predicate that must hold for every valid system state (one hall ticket per student per exam; venue capacity not exceeded; cancelled tickets cannot be downloaded).
run.json domain; link scenarios to violation attempts.Define errors out of existence: Redesign flows so invalid actions are unavailable, not allowed-then-rejected (disable download when unpaid; hide regenerate when exam completed).
Illegal transitions: State machine edges that must never occur (confirmed → draft without admin audit; issued → unissued without void record).
domain; scenarios cover blocked attempts.run.json for verify-phase checks.scenarios[].invariant_ref to domain rules for traceability.