菜单
Build a conceptual model for a prototype or feature: actors, objects, actions, states, rules, and transitions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run a cognitive walkthrough and create Beads issues from the findings. Converts walkthrough breakdowns (Q1-Q4 failures) into trackable Beads tasks with priorities and dependencies.
Build a conceptual model and create Beads issues from the findings. Converts ambiguities, overloaded concepts, and unclear states into trackable Beads tasks with priorities and dependencies.
Audit cross-screen consistency and create Beads issues from the findings. Converts consistency breaks and invariant violations into trackable Beads tasks with priorities and dependencies.
Audit failure paths and create Beads issues from the findings. Converts unhandled failure states, missing empty states, and broken recovery paths into trackable Beads tasks with priorities and dependencies.
Run a heuristic evaluation and create Beads issues from the findings. Converts Nielsen heuristic violations into trackable Beads tasks with priorities and dependencies.
Review information architecture and create Beads issues from the findings. Converts orphan screens, mislabeled navigation, and grouping problems into trackable Beads tasks with priorities and dependencies.
| name | conceptual-model |
| description | Build a conceptual model for a prototype or feature: actors, objects, actions, states, rules, and transitions. |
Create a conceptual model for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, prototype, docs, screenshots, routes, components, and visible states. If details are missing, infer cautiously and mark assumptions.
Write docs/hci/conceptual-model.md unless the user asked for another path.
Create the directory if it does not exist.
| Actor | Goal | Main tasks | Notes |
| Object | Definition | Key attributes | Related objects |
| Action | Target object | Preconditions | Result |
| Object | State | Meaning | Entered by | Exited by |
Note: keep this state table high-level (name and one-line meaning only). Full lifecycle definition belongs in the state-model artifact. If a state-model artifact already exists, reference it rather than repeating it.
Add Mermaid diagrams:
A strong conceptual model should make these obvious:
Flag anything that breaks these expectations.
