agentleFS
45ck45ck/hci-review-skill/.claude/skills/information-architecture/SKILL.md

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

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.
  • solinkzSkill

    micro-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

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
  1. Distinctive:

    Use ultrathink. Work from the repo, routes, navigation components, page layouts, menus, and any existing sitemap or docs.

    line 11
  2. Very specific:

    Write docs/hci/information-architecture.md unless the user asked for another path.

    line 14
  3. Distinctive:

    Create the directory if it does not exist.

    line 15
  4. Distinctive:

    Create a hierarchical map of all screens, pages, or views in the system.

    line 20
  5. Distinctive:

    Document how users move between screens:

    line 45
  6. Distinctive:

    Create Mermaid diagrams for:

    line 90
  7. Distinctive:

    If a user would need to memorize a path, the architecture has a problem.

    line 106

“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.

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

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
    └── System

For 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

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.