agentleFS
parhambparhamb/design-skills/ux-information-architecture/SKILL.md

ux-information-architecture

Skill21 starsChanged 5 months agoMITView on GitHub

Information architecture (IA): content categorization, labeling, screen titles, sort and filter, settings structure, data hierarchy, and minimizing cognitive load. Use when designing app structure, auditing content organization, creating a sitemap, or improving how information is grouped and labeled.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Card sorting: Run an open card sort with 10 to 15 representative users before finalizing category labels.

    line 38
  2. Distinctive:

    Use words your users use, not what your engineers or product managers call things internally.

    line 54
  3. Distinctive:

    When applying this checklist to a screen, flow, or codebase:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Information Architecture (IA)

IA is the practice of organizing, structuring, and labeling content so users can find what they need. Poor IA is the invisible reason users say "I just couldn't find it."


Checklist

ItemGuidance
Content categorizationGroup by user mental models, not the internal org chart or database structure.
Well-structured contentMaximum 2 levels of hierarchy in any list. Never nest deeper than that.
Screen titlesEvery screen has a clear, descriptive title that matches the nav item that opened it.
Sort optionsDefault sort is the most useful (date, relevance). User can change it.
Filter optionsActive filter count shown ("3 filters active"). All filters can be cleared in one tap.
Minimal scrollingCritical information is visible without scrolling. Details load progressively.
Timestamp visibilityRelative time near the event ("2 hours ago"), full timestamp accessible on tap.
Settings organizationSettings are grouped by theme: Account, Notifications, Privacy, Appearance, About.
F-pattern layoutMost important content is at the top and left of each screen.
Quick checkoutPurchase flow is 5 steps or fewer. Guest checkout is available.

IA Research Methods

Card sorting: Run an open card sort with 10 to 15 representative users before finalizing category labels. Use the results to name categories with the words users actually choose, not internal terminology.

Tree testing: Validate your structure by asking users to find items in a text-only tree with no visual design. If users fail to find items in the tree, the IA is the problem — not the visual design.

First-click testing: Research shows that 85% of users who click correctly on their first attempt go on to complete the task. Test key flows with first-click tests before investing in full prototypes.


Labeling Principles

Use words your users use, not what your engineers or product managers call things internally. Avoid jargon and acronyms for first-time users. Keep navigation labels to 1 or 2 words. Be consistent — if one section is called "Saved," do not call the same concept "Bookmarks" elsewhere in the app.


How to Review

When applying this checklist to a screen, flow, or codebase:

  1. Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
  2. Cite specific evidence for each finding: the screen, component, file, or line it applies to.
  3. Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
  4. End the review with the top 3 recommended fixes, ranked by user impact.

Related Skills

  • ux-navigation — how the structure is surfaced to users
  • ux-search — search as a complement to browsing
  • ux-content — labeling and terminology consistency

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.