/ia-model
Build information architecture from an entity inventory plus task flows. Derives nav structure, labeling, and screen map from the domain nouns.
/ia-modelType it bare, or paste it with loose context after — Claude figures out the rest.
Screens get designed before the nouns behind them are named. Nav drifts across pages.
One entity map that drives every downstream screen. Nav stays clean because the model is clean.
Takes in
- Task flows from spec
- Entity inventory from decompose
Returns
- Entity model diagram
- Navigation shape
- Screen inventory
What it does
Build the IA from entities and their relationships. For data-heavy operator tools, the IA is entity-driven — screens derive from objects, not content hierarchies.
List every object the system represents:
Read the full skill
The complete instructions live at .claude/skills/ia-model/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Information architecture — nav + entity model + screen map.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
Shipped by @kingofrock · Read the essays
/decompose
Audit responsibilities before you build. Reads sequence diagrams. Assigns GRASP roles. Identifies interfaces. Audits cross-cutting concerns. Selects patterns from GoF, Fowler, and stack idioms. Bridges design and build.
/interaction-design
Turn IA plus task flows into interaction design — state diagrams, sequence diagrams, user flows. Final step in the UX translation chain before decompose.