agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/information-architecture/SKILL.md

information-architecture

Skill4 starsChanged 3 months agoMITView on GitHub

Design intuitive, scalable navigation structures. Use when building a sitemap, defining navigation menus, or organizing complex feature sets.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief-to-tasks, design-flow and 5 more.

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

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • julianoczkowskiSkill

    design-flow

    Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".

    Also in 6 projects that use this

  • nandanosqlSkill

    design-brief

    Create a design brief that clearly communicates the product context, user needs, constraints, and success criteria to the design team — bridging PM requirements and design execution.

    Also in 8 projects that use this

  • 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

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 9 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Use consistent grammar: Category hubs use plural nouns ("Customers", "Invoices").

    line 32
  2. Distinctive:

    Avoid internal company acronyms or generic labels ("Other", "Tools", "Data Hub").

    line 33
  3. Distinctive:

    When a system scales beyond 15–20 views:

    line 46

“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

Information Architecture

Information architecture is the skeleton of understanding — if users cannot locate a capability within 3 interactions or mental jumps, it does not exist.

Pipeline Integration

  • Upstream: Pulls from product-discovery (user mental models) and business-model-reading (feature domains).
  • Downstream: Consumed by route-integrity-checker (validating link destinations), dashboard-scaffolding-contract (nav groups), dashboard-layout-patterns (shell selection), and module-registry-sync (navGroup annotations).

1. Inventory & domain entity clustering

Extract all key domain nouns (e.g. Invoices, Clients, Transactions) and user verbs (Create, Reconcile, Export). Cluster them into distinct functional hubs based on the user's mental model, not database schema tables.

2. Establish hierarchy & grouping rules

Organize the product into a shallow, predictable tree (Maximum 7 top-level categories, Maximum 3 levels deep):

graph TD
    Home[Dashboard Overview] --> Ops(Operations)
    Home --> Fin(Finance)
    Home --> Settings(Workspace Settings)
    Ops --> Ops1[Inventory]
    Ops --> Ops2[Suppliers]
    Fin --> Fin1[Invoices]
    Fin --> Fin2[Bank Feeds]
    Settings --> Set1[Team & Permissions]
    Settings --> Set2[Billing & Plan]

3. Precision labeling

  • Use consistent grammar: Category hubs use plural nouns ("Customers", "Invoices"); discrete actions use active verbs ("New Order", "Export").
  • Avoid internal company acronyms or generic labels ("Other", "Tools", "Data Hub").

4. Apply Role-Based Access Control (RBAC) navigation overlay

For products with multi-role permissions (Admin, Manager, Member, Guest):

  • Annotate each navigation item with minimum required permissions.
  • Rule of thumb: Hide navigation items entirely if a user has zero access; do not tease them with dead-end "403 Forbidden" screens.
  • Provide a clear annotation matrix: | Nav Item | Route | Required Role / Scope | Behavior for Unauthorized Roles | |---|---|---|---| | Invoices | /finance/invoices | read:finance | Hidden if unauthorized | | Billing Settings | /settings/billing | admin:workspace | Hidden for non-admins |

5. Architect discovery alternatives (Search & ⌘K Command Palette)

When a system scales beyond 15–20 views:

  • Design a global Command Palette (⌘K / Ctrl+K) supporting instant fuzzy search across navigation routes, recent entities, and common quick actions.
  • Define search indexing scopes (Navigation items vs. Data entities vs. Help documentation).

Navigation Anti-patterns

  • More than 7 items in any navigation group (causes cognitive overload).
  • Nesting navigation 4+ levels deep (users get lost).
  • Mixing nouns and verbs haphazardly in the same menu tier.
  • Displaying disabled/locked navigation links with no explanatory context.

Completion Criteria

  • Hierarchy structured within 7 top-level groups and ≤ 3 levels deep
  • Labels follow strict grammatical consistency (nouns for hubs, verbs for actions)
  • Multi-role navigation visibility matrix documented with permission scopes
  • Global search / Command Palette indexing rules established for complex apps
  • Sitemap Mermaid diagram matches dashboard-scaffolding-contract and route-intents.json

Output Format

A sitemap.md artifact containing the hierarchical tree, Mermaid navigation diagram, RBAC role-visibility matrix, and Command Palette shortcut schema.

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.