القائمة
Define the state machines and lifecycles for all key entities in the system -- states, transitions, invalid transitions, and user-visible cues per state.
التثبيت باستخدام 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 | state-model |
| description | Define the state machines and lifecycles for all key entities in the system -- states, transitions, invalid transitions, and user-visible cues per state. |
| disable-model-invocation | true |
Define the state machines and lifecycles for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, routes, components, database schemas, API endpoints, and visible UI states. If details are missing, infer conservatively and mark assumptions.
Write docs/hci/state-model.md unless the user asked for another path.
Create the directory if it does not exist.
Find every object in the system that has a lifecycle -- anything that changes state over time. Common examples: requests, tasks, users, sessions, approvals, documents, payments, invitations.
| State | Meaning | User-visible cue | Entry condition | Exit condition |
| From | To | Trigger | Who can trigger | Side effects |
| From | To | Why invalid | What happens if attempted |
Flag any state that is:
Create Mermaid state diagrams for each entity. Include:
Identify where one entity's state depends on another's. Document:
For each state, check:
Create a coverage table: | Entity | State | Has visual cue | Has available actions | Has transition feedback | Gap |
End with:
