Agent skill

Information Architecture

by Owl-Listener in Owl-Listener/designer-skills

Design content structure, hierarchy, labelling, and the navigation model.

MITAuto-check passedFrontend & Design

Install Information Architecture

skills CLI
$ npx skills add Owl-Listener/designer-skills --skill information-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/designer-skills information-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ux-strategy/skills/information-architecture .claude/skills/information-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
information-architecture
GitHub stars
2.9k
Used in
1 other repo
Token cost
~839 tokens
SKILL.md length
414 words
Files
1
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

Design content structure, hierarchy, labelling, and the navigation model.

  • Works in 5 steps: Audit: inventory existing content and… → Research: card sort (open for new… → Draft: sketch candidate hierarchies;… → …
  • Organising what exists
  • SKILL.md covers What You Do, Core IA Deliverables, IA Heuristics and Process, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Information Architecture is an agent skill from Owl-Listener/designer-skills. 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).

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UX design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.

When your agent uses it

  • Organising what exists
  • Tasks that involve UX design

Example prompts

  • “/information-architecture”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Audit: inventory existing content and map current structure
  2. Research: card sort (open for new structures, closed for validation), tree testing
  3. Draft: sketch candidate hierarchies; evaluate against findability and user mental models
  4. Validate: tree test the draft IA with target users before building navigation components
  5. Document: produce sitemap and content model for the team

What it can do on your machine

Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Information Architecture loads about 839 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 414 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~839

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 414 words, ~839 tokens.

Download SKILL.mdSave it as .claude/skills/information-architecture/SKILL.md (or your agent's skills folder).
name
information-architecture
description
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).

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

  • Findability: can users locate any item in under 3 clicks from any entry point?
  • Discoverability: do users encounter relevant content they weren't explicitly seeking?
  • Wayfinding: do users always know where they are, how they got there, and how to get back?
  • Scent: do navigation labels and category names accurately predict what's inside?
  • Depth vs breadth: prefer shallower hierarchies (3 levels max for primary content); wide flat structures are harder to navigate than moderate depth with clear labels
Show full SKILL.md (153 more words)Show less

Process

  1. Audit: inventory existing content and map current structure
  2. Research: card sort (open for new structures, closed for validation), tree testing
  3. Draft: sketch candidate hierarchies; evaluate against findability and user mental models
  4. Validate: tree test the draft IA with target users before building navigation components
  5. Document: produce sitemap and content model for the team

Common Mistakes

  • Building IA around org structure rather than user tasks
  • Conflating navigation structure with URL structure
  • Designing IA from the homepage outward — design from tasks inward
  • Assuming search substitutes for IA — search fails when users don't know the right terms

Best Practices

  • Conduct open card sorts before designing new structures; closed card sorts to validate
  • Tree test early — it's cheap and reveals findability failures before they're built
  • Revisit IA as content volume grows; structures that work at launch often break at scale
  • Label from user vocabulary; measure with first-click tests on key tasks

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ux-strategy/skills/information-architecture of Owl-Listener/designer-skills.

Open the folder on GitHubat commit 9a6930c

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Information Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Information Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Information Architecture this skillOwl-Listener/designer-skills2.9k1 repos~839Automated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Interface Design for Dashboards and Appsholaboss-ai/holaOS11k3 repos~6kAutomated safety check: PassMIT
Animategrowupanand/ConvoForm1026 repos~1.9kAutomated safety check: PassApache-2.0
Migrate Content Iadocker/docs4.7k—~5.1kAutomated safety check: PassApache-2.0
UX WalkthroughXiaoMi/hiui879—~1.3kAutomated safety check: PassMIT

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Frontend & DesignAuto-check passed
  • Animate

    growupanand/ConvoForm

    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

    102 GitHub starsUsed in 6 repos~1.9k tokens
    Frontend & DesignAuto-check passed
  • Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • UX Walkthrough

    XiaoMi/hiui

    体验走查 skill。适用于代码库、URL、截图三种输入,输出结构化体验问题报告,并同步生成本地 docx 报告。触发词:体验走查、UX review、交互走查、界面审查、体验问题。

    879 GitHub stars~1.3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed
  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    743 GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed

More from Owl-Listener/designer-skills

All 107 skills in this repo
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Auto-check passed
  • Accessibility Test Plan

    Owl-Listener/designer-skills

    Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

    2.9k GitHub starsUsed in 1 repo~478 tokens
    Auto-check passed
  • Aesthetic Usability

    Owl-Listener/designer-skills

    Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.

    2.9k GitHub starsUsed in 1 repo~678 tokens
    Auto-check passed
  • Affinity Diagram

    Owl-Listener/designer-skills

    Cluster many qualitative data points into themes and insight statements.

    2.9k GitHub starsUsed in 1 repo~520 tokens
    Auto-check passed
  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Auto-check passed
  • Business Design

    Owl-Listener/designer-skills

    Read financials, map competitive landscapes, and argue design decisions in the language of value.

    2.9k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Questions about Information Architecture

What does Information Architecture do?

Design content structure, hierarchy, labelling, and the navigation model. Information Architecture is an agent skill from Owl-Listener/designer-skills. Design content structure, hierarchy, labelling, and the navigation model.

When should I use Information Architecture?

Information Architecture fits situations like: organising what exists; tasks that involve UX design.

How do I install Information Architecture in Claude Code?

Run `npx skills add Owl-Listener/designer-skills --skill information-architecture -a claude-code`. Or copy the skill folder (ux-strategy/skills/information-architecture in Owl-Listener/designer-skills) into .claude/skills/information-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Information Architecture in Codex?

Run `npx skills add Owl-Listener/designer-skills --skill information-architecture -a codex`. Or copy the skill folder (ux-strategy/skills/information-architecture in Owl-Listener/designer-skills) into .agents/skills/information-architecture in your project. Codex loads it when a task matches its description.

Can I use Information Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill information-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/information-architecture, .gemini/skills/information-architecture, .github/skills/information-architecture and .opencode/skills/information-architecture in your project.

What does Information Architecture need to run?

SKILL.md names no scripts, command-line tools or credentials: Information Architecture is instructions for the agent only.

Does Information Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Information Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Information Architecture use?

Information Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Information Architecture use?

About 839 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Information Architecture?

Skills that share tags, products or a category with Information Architecture: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 102 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Information Architecture?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.

Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.