Menu
Define the information architecture for a prototype -- sitemap, navigation model, grouping logic, labeling, and action placement.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | information-architecture |
| description | Define the information architecture for a prototype -- sitemap, navigation model, grouping logic, labeling, and action placement. |
| disable-model-invocation | true |
Define the information architecture for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, routes, navigation components, page layouts, menus, and any existing sitemap or docs. Infer missing structure conservatively and mark assumptions.
Write docs/hci/information-architecture.md unless the user asked for another path.
Create the directory if it does not exist.
Create a hierarchical map of all screens, pages, or views in the system.
Format as an indented list or Mermaid diagram:
Home
├── Dashboard
├── Projects
│ ├── Project List
│ ├── Project Detail
│ │ ├── Settings
│ │ ├── Members
│ │ └── Activity
│ └── Create Project
├── Settings
│ ├── Profile
│ ├── Notifications
│ └── Security
└── Admin
├── Users
└── System
For each node include: route/path, purpose, primary action.
Document how users move between screens: | Navigation element | Type (global nav, sidebar, breadcrumb, tab, link, button) | What it connects | Always visible? |
Identify:
For each group of items in the navigation or layout, answer:
| Group | Items | Grouping logic | Potential confusion |
For every navigation label, page title, and section heading: | Label | What it actually leads to | Clear to new user? | Alternative label |
Flag:
For each primary action in the system: | Action | Where it lives now | Where users would look for it | Mismatch? |
Check:
Create Mermaid diagrams for:
End with: