菜单
Trust signals in contracts — transparency for payments, irreversible actions, and sensitive data. Use when actors hesitate on verify walks or scenarios lack honesty UX.
用 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-trust |
| description | Trust signals in contracts — transparency for payments, irreversible actions, and sensitive data. Use when actors hesitate on verify walks or scenarios lack honesty UX. |
| metadata | {"lamina":{"id":"trust","problems":["payment and sensitive action anxiety","opaque fees or consequences","actors abandon before commit"],"related":["lamina-feedback-and-status","lamina-content-design","lamina-controls-and-menus","lamina-product-behavior"]}} |
Trust is observable honesty in product behavior — specified in scenarios and screen copy, verified when simulated actors attempt high-stakes workflows.
For payment, PII, and irreversible operations:
surfaces[]: show fees, consequences, and final state before commitscenarios[]: false success, hidden charges, unclear irreversibility → category failure or findingworkflows[]: confirmation only when undo impossible (controls-and-menus)side-effects)consistency-guarantees).modularity-boundaries).HttpOnly, appropriate SameSite/Secure posture, and CSRF token or trusted-origin validation. Development fallbacks are visibly limited and production fails closed without required identity configuration.