القائمة
Audit all failure paths, edge cases, and non-happy-path states -- empty states, validation errors, permission failures, loading, undo, and recovery.
التثبيت باستخدام 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 | failure-path-audit |
| description | Audit all failure paths, edge cases, and non-happy-path states -- empty states, validation errors, permission failures, loading, undo, and recovery. |
| disable-model-invocation | true |
Audit failure paths and edge cases for this scope:
$ARGUMENTS
Use ultrathink. Happy paths make prototypes look coherent. Failure paths reveal whether they actually are. Review the actual codebase, components, error handling, and UI states.
Write docs/hci/failure-path-audit.md unless the user asked for another path.
Create the directory if it does not exist.
For every screen or list that can be empty: | Screen/component | What is empty | Current empty state treatment | Has illustration/guidance? | Has call to action? | Rating |
Rating: OK = empty state is handled well; PARTIAL = present but incomplete; MISSING = no empty state handling.
Check:
For every async operation: | Operation | Current loading indicator | Location | Blocks interaction? | Has timeout handling? |
Check:
For every form or input: | Form/input | Validation rules | When validation runs | Error message | Error placement | Recovery path |
Check:
For every protected action or screen: | Action/screen | Required permission | What happens without permission | User feedback |
Check:
| Operation | Behavior on network failure | Retry available? | Data preserved? | Offline fallback? |
Check:
| Flow | Can be partially completed? | What happens if abandoned? | Can be resumed? | Is progress saved? |
Check:
| Action | Reversible? | Undo mechanism | Confirmation required? | Time limit on undo? |
Check:
| Scenario | Current handling | User feedback |
Check:
| Category | Items audited | Handled well | Partially handled | Not handled | Critical gaps |
|---|
End with:
