Back to Skills

information-architecture

verified

Use when organizing content for digital products, designing navigation systems, restructuring information hierarchies, improving findability, creating taxonomies or metadata schemas, or when users mention information architecture, IA, sitemap, navigation design, content structure, card sorting, tree testing, taxonomy, findability, or need help making information discoverable and usable.

View on GitHub

Marketplace

Plugin

thinking-frameworks-skills

Repository

lyndonkl/claude
15stars

skills/information-architecture/SKILL.md

Last Verified

January 24, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/lyndonkl/claude/blob/main/skills/information-architecture/SKILL.md -a claude-code --skill information-architecture

Installation paths:

Claude
.claude/skills/information-architecture/
Powered by add-skill CLI

Instructions

# Information Architecture

## Purpose

Information architecture (IA) is the practice of organizing, structuring, and labeling content to help users find and manage information effectively. Good IA makes complex information navigable, discoverable, and understandable.

Use this skill when:
- **Designing navigation** for websites, apps, documentation, or knowledge bases
- **Restructuring content** that users can't find or understand
- **Creating taxonomies** for classification, tagging, or metadata
- **Organizing information** at scale (hundreds or thousands of items)
- **Improving findability** when search and browse both fail
- **Designing mental models** that match how users think about content

Information architecture bridges user mental models and system structure. The goal: users can predict where information lives and find it quickly.

---

## Common Patterns

### Pattern 1: Content Audit → Card Sort → Sitemap

**When**: Redesigning existing site/app with lots of content

**Process**:
1. **Content audit**: Inventory all existing content (URLs, titles, metadata)
2. **Card sorting**: Users group content cards into categories
3. **Analyze patterns**: What categories emerge? What's grouped together?
4. **Create sitemap**: Translate patterns into hierarchical structure
5. **Validate with tree testing**: Can users find content in new structure?

**Example**: E-commerce site with 500 products. Audit products → Card sort with 15 users → Patterns show users group by "occasion" not "product type" → New navigation: "Daily Essentials", "Special Occasions", "Gifts" instead of "Electronics", "Clothing", "Home Goods"

### Pattern 2: Taxonomy Design (Faceted Navigation)

**When**: Users need multiple ways to slice/filter information

**Structure**: Orthogonal facets (dimensions) that combine
- **Facet 1**: Category (e.g., "Shoes", "Shirts", "Pants")
- **Facet 2**: Brand (e.g., "Nike", "Adidas", "Puma")
- **Facet 3**: Price range (e.g., "$0-50", "$50-100", "$100+")
- **Facet 

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
13994 chars