SkillAgentSearch skills...

information-architecture

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

Install / Use

npx skills add Owl-Listener/designer-skills --skill information-architecture

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Zed

Our assessment of information-architecture

information-architecture scores 80/100 on our quality scale, 380th of 421 Education & Research skills we index.

Its SKILL.md is 3.3 KB long, well organised into 11 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so information-architecture is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

information-architecture compared with similar skills

All 4 of these similar skills score higher than information-architecture; compare them before choosing.

SkillScoreStarsUpdatedFormat
information-architecture (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install information-architecture?
Run npx skills add Owl-Listener/designer-skills --skill information-architecture. The install tabs above show the steps for each supported agent.
Which AI agents does information-architecture work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is information-architecture safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is information-architecture still maintained?
The repository was last updated about 2 months ago, so information-architecture is actively maintained.

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

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

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryEducation
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions