菜单
Error and recovery UX in scenarios — slips vs mistakes, root cause in design not actors. Use when mapping failure scenarios in run.json.
用 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-error-handling |
| description | Error and recovery UX in scenarios — slips vs mistakes, root cause in design not actors. Use when mapping failure scenarios in run.json. |
| metadata | {"lamina":{"id":"error-handling","problems":["error message design","slip vs mistake diagnosis","recovery UX"],"related":["lamina-forms","lamina-edge-cases","lamina-feedback-and-status"],"tags":["audit-default"]}} |
Every failure mode gets a scenarios[] entry with actor-visible recovery — never blame the actor in copy or findings.
scenarios:
- id: venue-conflict
category: conflict
trigger:
operation: assign venue
when: concurrent_edit
ux: error_state
recovery: refresh and retry; show who holds lock
| Error type | Design response |
|---|---|
| Slip (right goal, wrong execution) | Undo, constraints, immediate feedback |
| Mistake (wrong goal/plan) | Better signifiers, conceptual model in copy |
idempotency-concurrency).