dragoon0x/everything-design-taste

information-architecture

Information architecture, content structure, taxonomy, and navigation structure design.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill information-architecture

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,566 B
  • docs SUMMARY.md 119 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Information Architecture

IA Methods

Card Sorting

  • Give users cards with content/feature names.
  • Ask them to group cards into categories.
  • Open sort: Users create and name categories.
  • Closed sort: You provide category names, users sort into them.
  • 15-30 participants for meaningful patterns.

Tree Testing

  • Give users a text-only tree (your proposed IA).
  • Ask them to find specific items.
  • Measures: success rate, directness, time to complete.
  • Tests whether your IA works without visual design influence.

Taxonomy Rules

  1. Mutually exclusive categories. Items should belong to one category, not three.
  2. User language. Label categories with user terms, not internal jargon.
  3. Balanced depth. 2-3 levels deep. Flat + search beats deep hierarchy.
  4. Balanced breadth. 5-8 items per level. More than 10 needs subdivision.
  5. Consistent granularity. Don't mix "Documentation" (broad) with "Webhook Reference" (narrow) at the same level.

Navigation Structures

  • Hierarchical: Tree structure. Best for content sites, documentation.
  • Flat: All items at same level. Best for small sites, dashboards.
  • Hub-and-spoke: Central hub, content branches. Best for apps with distinct modes.
  • Network: Interconnected, no hierarchy. Best for wikis, knowledge bases.