information-architecture
Skill19 starsChanged 6 days agoMITView on GitHub
Define the information architecture for a prototype -- sitemap, navigation model, grouping logic, labeling, and action placement.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- drinkspiller/skillstheir own version, first seen Nov 6, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- taro1037-design/claude-skillstheir own version, first seen Oct 20, 2026
- hakushiidev/claude-skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use micro-interactions.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
solinkzSkillmicro-interactions
Expert micro-interaction architect for mobile apps, web applications, and responsive websites. Use this skill when the user asks to add, build, fix, audit, or consult on micro-interactions, animations, transitions, motion design, gesture feedback, haptics, loading states, skeleton screens, pull-to-refresh, swipe actions, scroll animations, button states, form validation feedback, toast notifications, modals, dropdowns, toggles, progress indicators, shared element transitions, spring physics, easing curves, motion tokens, or any interaction that provides visual/haptic/auditory feedback to user actions. Triggers on: "micro-interaction", "animation", "transition", "motion", "easing", "spring", "gesture", "haptic", "feedback", "loading state", "skeleton", "shimmer", "pull to refresh", "swipe", "drag", "hover effect", "press state", "focus ring", "scroll animation", "parallax", "stagger", "orchestration", "reduced motion", "View Transitions", "layout animation", "shared element", "hero animation", "morphing", "Framer Motion", "GSAP", "Lottie", "Rive", "React Spring", "anime.js", or any request to make an interface "feel better", "feel alive", "feel snappy", "feel responsive", or "feel polished".
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- julianoczkowski/designer-skills★ 536same name
- dembrandt/dembrandt-skills★ 194same name
- mshadmanrahman/claude-for-designers★ 32same name
- yngchefcook/product_skills★ 28same name
- memi-design/design-skills★ 7same name
- botirkhaltaev/botir-skills★ 4same name
- RealTask/MAX-DESIGN★ 4same name
- Uwayxt/agent-skills★ 4same name
- digitaldreams/tuhin★ 3same name
- Geruyang/skills★ 2same name
13 more not listed
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 repository67 other files it gives its agents.
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- information-architectureSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- state-model-beadsSkill
- state-modelSkill
- task-analysis-writerSkill
- usability-test-plannerSkill
- vocabulary-audit-beadsSkill
- vocabulary-auditSkill
- wireframe-criticSkill
- accessibility-precheckSkill
- cognitive-friction-detectorSkill
- cognitive-walkthrough-beadsSkill
- cognitive-walkthroughSkill
- conceptual-model-beadsSkill
- conceptual-modelSkill
- consistency-audit-beadsSkill
- consistency-auditSkill
- error-and-time-metrics-analyzerSkill
- failure-path-audit-beadsSkill
- failure-path-auditSkill
- field-study-plannerSkill
- heuristic-eval-beadsSkill
- heuristic-evalSkill
- high-fidelity-prototype-plannerSkill
- information-architecture-beadsSkill
- interaction-type-selectorSkill
- journey-map-beadsSkill
- journey-mapSkill
- low-fidelity-prototype-plannerSkill
- mental-model-checkerSkill
- persona-synthesizerSkill
- prototype-hci-pack-beadsSkill
- prototype-hci-packSkill
- representative-task-writerSkill
- satisfaction-questionnaire-writerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use ultrathink. Work from the repo, routes, navigation components, page layouts, menus, and any existing sitemap or docs.
- Very specific: line 14
Write docs/hci/information-architecture.md unless the user asked for another path.
- Distinctive: line 15
Create the directory if it does not exist.
- Distinctive: line 20
Create a hierarchical map of all screens, pages, or views in the system.
- Distinctive: line 45
Document how users move between screens:
- Distinctive: line 90
Create Mermaid diagrams for:
- Distinctive: line 106
If a user would need to memorize a path, the architecture has a problem.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Define the information architecture for this scope:
$ARGUMENTS
Use ultrathink. Work from the repo, routes, navigation components, page layouts, menus, and any existing sitemap or docs. Infer missing structure conservatively and mark assumptions.
Output
Write docs/hci/information-architecture.md unless the user asked for another path.
Create the directory if it does not exist.
Required sections
1) Sitemap
Create a hierarchical map of all screens, pages, or views in the system.
Format as an indented list or Mermaid diagram:
Home
├── Dashboard
├── Projects
│ ├── Project List
│ ├── Project Detail
│ │ ├── Settings
│ │ ├── Members
│ │ └── Activity
│ └── Create Project
├── Settings
│ ├── Profile
│ ├── Notifications
│ └── Security
└── Admin
├── Users
└── SystemFor each node include: route/path, purpose, primary action.
2) Navigation model
Document how users move between screens: | Navigation element | Type (global nav, sidebar, breadcrumb, tab, link, button) | What it connects | Always visible? |
Identify:
- primary navigation (always visible)
- secondary navigation (contextual)
- tertiary navigation (in-page)
- escape hatches (how to get back/out)
3) Grouping analysis
For each group of items in the navigation or layout, answer:
- Why are these grouped together?
- Would a new user expect this grouping?
- Are there items that belong in a different group?
- Are there groups that should be split or merged?
| Group | Items | Grouping logic | Potential confusion |
4) Label audit
For every navigation label, page title, and section heading: | Label | What it actually leads to | Clear to new user? | Alternative label |
Flag:
- labels that are too vague ("Settings", "More", "Manage")
- labels that overlap ("Admin" vs "Settings" vs "Configuration")
- labels that use internal jargon
- labels that do not match the page content
5) Action placement
For each primary action in the system: | Action | Where it lives now | Where users would look for it | Mismatch? |
Check:
- Can the user find the action without hunting?
- Is it at the right level of the hierarchy?
- Is it near the objects it acts on?
- Are destructive actions separated from safe actions?
6) Depth and breadth analysis
- How deep is the deepest path? (clicks from home to leaf)
- How wide is the widest level? (items at the same level)
- Are there screens only reachable through non-obvious paths?
- Are there orphan screens with no navigation path?
Diagrams
Create Mermaid diagrams for:
- sitemap (tree structure)
- navigation flow (how screens connect)
Synthesis
End with:
- screens that are hard to find
- groupings that will confuse new users
- labels that need to change
- actions that are in the wrong place
- depth problems (too deep or too shallow)
- recommendations for restructuring
Quality bar
- Reference actual routes, file paths, and component names.
- The IA should make it obvious where everything lives and how to get there.
- If a user would need to memorize a path, the architecture has a problem.
Deliverable style
- Clear headings
- Markdown tables
- Mermaid diagrams where useful
- Direct language
- No filler
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.

