Information Architecture
Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use `navigation-patterns` (interaction-design); for user-generated grouping evidence use `card-sort-analysis` (design-research).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill information-architecturegit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/ux-strategy/skills/information-architecture ~/.claude/skills/information-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Information Architecture You are an expert in organizing information so users can find what they need and understand where they are. ## What You Do You design the underlying structure of a product — how content and features are categorized, labeled, and connected — and produce the deliverables that communicate that structure to teams. ## Core IA Deliverables ### Sitemap / Content Inventory - Hierarchical map of all screens, sections, and content types - Shows parent/child relationships and navigation depth - Distinguishes primary navigation from utility navigation - Flags orphaned content, redundant paths, and dead ends ### Navigation Model - **Global navigation**: present everywhere (header nav, bottom tab bar) - **Local navigation**: contextual to the current section (sidebar, tabs, breadcrumbs) - **Utility navigation**: account, settings, help — high reach, low frequency - **Contextual links**: inline links between related content ### Taxonomy & Labeling - Category names derived from user vocabulary (card sort data, interview language) - Consistent labeling across navigation, headings, search, and empty states - Avoid internal jargon — test labels with users, not colleagues ### Content Model - Define content types (article, product, event, profile…) - Attributes of each type (title, author, date, category, media…) - Relationships between types (article belongs to category, event has speakers…) ## IA Heuristics
Details
- Skill name
information-architecture- Repository
- Owl-Listener/designer-skills
- Path
ux-strategy/skills/information-architecture/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Information Architecture skill do?
Design content structure, hierarchy, labelling, and the navigation model. Use when organising what exists. For the UI that exposes it use `navigation-patterns` (interaction-design); for user-generated grouping evidence use `card-sort-analysis` (design-research).
How do I install the Information Architecture skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Information Architecture popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Opportunity Framework
3.4kOwl-Listener/designer-skills
Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use `design-brief`.
Remote Compute
2.1kai4s-research/open-science
Use when the user asks to run, submit, monitor, or cancel a job on a remote machine over SSH — their own GPU/CPU server, a workstation, or a Slurm cluster ("the cluster", a login node, "my 3090 box", "the compute server"). Picks a saved machine, runs the work directly over SSH (or via Slurm when present), tracks it, and fetches results back into the workspace.
Pattern Library
3.4kOwl-Listener/designer-skills
Structure a pattern entry — problem context, solution, usage examples, and related patterns. Use when documenting a recurring solution rather than a component. For a single component's API, use `component-spec`.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.