القائمة
Consistency across actor views — student, admin, and system surfaces must reflect the same domain truth. Use in multi-actor products when roles see different slices of one system.
التثبيت باستخدام 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-multi-view-integrity |
| description | Consistency across actor views — student, admin, and system surfaces must reflect the same domain truth. Use in multi-actor products when roles see different slices of one system. |
| metadata | {"lamina":{"id":"multi-view-integrity","problems":["multi-actor product design","admin vs user view mismatch","service handoffs between roles","backstage vs frontstage consistency"],"related":["lamina-modularity-boundaries","lamina-consistency-guarantees","lamina-user-modeling","lamina-side-effects"],"tags":["design-default"]}} |
One product, many actor views — each role sees what they need, but all views must agree on domain truth. Design handoffs and visibility across student, admin, exam cell, payment, and support paths.
Actor view: What this role sees, can do, and must not see — derived from permissions, not separate products.
actors in run.json + personas.json goals and permissions.Frontstage vs backstage: User-visible flow vs operations another role performs (student downloads ticket; exam cell assigns venue; payment gateway confirms fee).
Cross-view consistency check: Same entity id, same lifecycle state, compatible fields across views (admin "cancelled" → student sees cancelled, not downloadable).