Menu

Individual skill

ux-information-architecture-audit

0upvotes

Run a structured information architecture audit on a sitemap, navigation tree, category structure, menu labels, or multi-screen product. Produces a severity-rated issue list with concrete fixes — catches scheme/task mismatches, narrow-and-deep hierarchies, low-information-scent labels, inconsistent labeling systems, single-path findability, and dead-end pages. Use when auditing IA, site structure, categories, taxonomy, or labels, or as a validation step after generating navigation or any multi-screen structure.

ux/audits/information-architecture/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Information Architecture Audit Skill

## What this skill changes vs. default behavior

By default, Claude critiques a structure by eyeballing the category names — it rarely tests whether the *organization scheme* matches how users actually seek, whether labels carry information scent before the click, whether the hierarchy's breadth/depth ratio forces click-tunneling, or whether users landing mid-site can orient at all. This audit forces four things: every finding names the violated IA principle; labels are tested for scent ("could a user predict the destination?"), consistency, and vocabulary fit; the structure is checked against the seeking modes it must serve, not just the browse-from-homepage path; and findings come severity-rated with concrete fixes — including which research method (card sort, search-log analysis, free listing) would settle a contested call.

This is an **evaluative** skill: it auto-runs whenever a sitemap, navigation structure, category system, or multi-screen flow is being reviewed — and as a validation step after generative skills that structure content (`ux-navigation`, `ux-menus`, `ux-search`).

**Scope discipline.** When invoked directly (the user named this audit), review **only this concern** — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (`ux-design-review`) or a generative skill calls it under `docs/orchestration-policy.md`, where it sits in **Tier B — offered**. Explicit scope always wins.

---

## The framework — what to check and what a violation looks like
Back to top