information-architecture

Organizes content structure and navigation using card sorting, taxonomy design, and tree testing.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/lyndonkl/hermesworld --skill information-architecture-lyndonkl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/lyndonkl/hermesworld/tree/main/packages/cognitive-design-architect/skills/design/information-architecture
Command: npx skills add https://github.com/lyndonkl/hermesworld --skill information-architecture-lyndonkl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Users cannot find content when navigation reflects internal org charts, jargon, or untested assumptions, leading to high bounce rates, failed searches, and abandoned tasks. ## Core Features & Use Cases - User Research Methods: Run open, closed, and hybrid card sorting with similarity matrices and dendrogram analysis to discover how users naturally group and label content. - Taxonomy & Navigation Design: Build MECE taxonomies, faceted navigation, and hub-and-spoke structures following depth and breadth guidelines (3-4 levels, 5-9 items per level). - Validation & Metrics: Validate structures with tree testing before development, targeting 70%+ success rates, and track findability metrics like time to find and search/browse balance. - Use Case: An e-commerce site with 10,000 products organized by internal logic runs a card sort with 20 users, discovers customers group by occasion rather than product type, rebuilds faceted navigation, and validates with tree testing before launch. ## Quick Start Use the information-architecture skill to audit my site's content and design a validated navigation structure with card sorting and tree testing.

Frequently Asked Questions about information-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a card sort to design website navigation?▼

Card sorting asks 15-30 users to group content cards into categories they name themselves (open sort) or fit into your predefined categories (closed sort). Analyze results with similarity matrices and dendrograms to find clusters with over 70% agreement, then translate those groupings into your sitemap.

What is tree testing and when should I use it?▼

Tree testing validates a navigation structure by giving 20-50 users text-based tasks like 'Where would you find X?' without any visual design. Run it before development begins, targeting at least 70% success rate and directness under 1.5 times the optimal path.

How many navigation levels should a website have?▼

Aim for 3-4 levels deep with 5-9 items per level, based on Hick's Law and Miller's 7±2 research. Deeper hierarchies cause users to get lost, while more than 12 top-level items overwhelm; supplement deep content with search and faceted filters.

What is the difference between faceted navigation and a hierarchy?▼

A hierarchy gives each item one location in a tree, while faceted navigation assigns orthogonal attributes like category, price, and brand that users filter in any combination. Facets scale better for catalogs over 500 items where users need multiple ways to slice content.

Why do users fail to find content even with a clear sitemap?▼

Common causes include vague labels like 'Resources' or 'Solutions', navigation mirroring the company org chart instead of user mental models, and structures never validated with real users. Card sorting reveals the vocabulary users actually expect, and tree testing catches confusing labels before launch.

When should I not rely on navigation alone for findability?▼

For content sets over 5,000 items or when users know exactly what they want, navigation alone is insufficient. Provide multiple access paths including search with autocomplete, faceted filters, tags, breadcrumbs, and related links to support both searchers and browsers.