Agent skill
ux-information-architecture
[UI/UX] Designs Information Architecture (IA) as ASCII diagrams. Systematically organizes screen hierarchies, navigation structures, and content classification. Use when requesting 'IA design', 'information architecture', 'screen hierarchy', or 'sitemap'.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/ux-information-architecture-cantagestudio-cosmicatlaspacker
SKILL.md
UX Information Architecture
A skill that designs Information Architecture (IA) as ASCII diagrams.
When to Use
- Designing overall screen hierarchy for apps/web
- Defining navigation structures
- Content classification and grouping
- Creating sitemaps
IA Diagram Symbols
Hierarchy Nodes
[Root] ← Top level (app/site)
├─[Section] ← Section (category)
│ ├─[Page] ← Page
│ │ └─[SubPage] ← Sub page
│ └─[Page]
└─[Section]
Node Types
[Page Name] ← Regular page
[[Core Page]] ← Core page (emphasis)
(Modal/Overlay) ← Modal/Overlay
{Dynamic Content} ← Dynamic content
<External Link> ← External link
[Page*] ← Auth required
IA Structure Patterns
Hierarchical Tree
[Application]
│
├─[Dashboard]
│ ├─[Overview]
│ └─[Statistics]
│
├─[Projects]
│ ├─[Project List]
│ │ └─{Project Item}
│ └─(New Project Modal)
│
└─[Settings]*
├─[Profile]
└─[Security]
IA Design Principles
- 3-click rule: Major content reachable within 3 levels
- Menu items: 7±2 recommended
- Hierarchy depth: 4 levels or less recommended
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?