菜单
Create a full HCI review pack for a prototype: conceptual model, state model, journeys, glossary, information architecture, consistency audit, failure path audit, heuristic evaluation, cognitive walkthrough, scorecard, and summary.
用 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 | prototype-hci-pack |
| description | Create a full HCI review pack for a prototype: conceptual model, state model, journeys, glossary, information architecture, consistency audit, failure path audit, heuristic evaluation, cognitive walkthrough, scorecard, and summary. |
Build a full solo-review pack for this prototype or interface area:
$ARGUMENTS
Use ultrathink. Work from the current repository, current files, current screenshots, current docs, and current prototype state. Do not wait for user research unless absolutely blocked. If something is unknown, make the smallest reasonable assumption and label it clearly.
Write them to docs/hci/ unless the user asked for another path.
docs/hci/conceptual-model.mddocs/hci/state-model.mddocs/hci/user-journeys.mddocs/hci/glossary.mddocs/hci/information-architecture.mddocs/hci/consistency-audit.mddocs/hci/failure-path-audit.mddocs/hci/heuristic-evaluation.mddocs/hci/cognitive-walkthrough.mddocs/hci/hci-scorecard.mddocs/hci/hci-summary.mdCreate the directory if it does not exist.
Extract and document:
Use the conceptual-model skill logic:
For every stateful entity in the system:
Identify the 3 to 7 most important journeys for the scope. For each journey document:
Include Mermaid flowcharts where useful. Prioritize:
Create a glossary of canonical nouns, verbs, statuses, and labels. For each term include:
Flag any concept drift such as one thing being called different names in different places.
Review consistency across screens and flows:
Create a table with:
Review every non-happy-path state:
Create a summary table: category, items audited, handled, partial, not handled, critical gaps.
Apply Nielsen-style heuristics rigorously:
Output a severity-ranked issues table:
For each critical journey, step through the interface and answer:
Log breakdowns with exact step references.
Create hci-scorecard.md rating the prototype 1-5 on each dimension:
Include total score out of 40, top 3 strengths, top 3 weaknesses, and priority fixes.
Create hci-summary.md with: