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
- mahirautela2020-design/claude-skills-uxtheir own version, first seen Mar 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mahirautela2020-design/claude-skills-ux★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-generalSkill
- ux-help-onboardingSkill
- ux-navigationSkill
- ux-networkSkill
- ux-notificationsSkill
- ux-reviewSkill
- ux-safety-privacySkill
- ux-searchSkill
- ux-settingsSkill
- ux-user-accountSkill
- ux-utilitySkill
- ux-visual-designSkill
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
- Distinctive: line 38
Card sorting: Run an open card sort with 10 to 15 representative users before finalizing category labels.
- Distinctive: line 54
Use words your users use, not what your engineers or product managers call things internally.
- Distinctive: line 63
When applying this checklist to a screen, flow, or codebase:
≈ “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.
Files
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
| Item | Guidance |
| Content categorization | Group by user mental models, not the internal org chart or database structure. |
| Well-structured content | Maximum 2 levels of hierarchy in any list. Never nest deeper than that. |
| Screen titles | Every screen has a clear, descriptive title that matches the nav item that opened it. |
| Sort options | Default sort is the most useful (date, relevance). User can change it. |
| Filter options | Active filter count shown ("3 filters active"). All filters can be cleared in one tap. |
| Minimal scrolling | Critical information is visible without scrolling. Details load progressively. |
| Timestamp visibility | Relative time near the event ("2 hours ago"), full timestamp accessible on tap. |
| Settings organization | Settings are grouped by theme: Account, Notifications, Privacy, Appearance, About. |
| F-pattern layout | Most important content is at the top and left of each screen. |
| Quick checkout | Purchase 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:
- Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
- Cite specific evidence for each finding: the screen, component, file, or line it applies to.
- Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
- End the review with the top 3 recommended fixes, ranked by user impact.
Related Skills
ux-navigation— how the structure is surfaced to usersux-search— search as a complement to browsingux-content— labeling and terminology consistency
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
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.

