
Information Architecture
- 580 installs
- 305 repo stars
- Updated March 4, 2026
- aj-geddes/useful-ai-prompts
information-architecture is an agent skill that designs user-centered hierarchies, navigation systems, and taxonomies for documentation, apps, and websites for developers planning discoverable information structures befo
About
information-architecture is a useful-ai-prompts skill that helps agents structure large information spaces so users can find content intuitively. It guides creation of logical hierarchies, navigation patterns, mental models, and categorization schemes aligned to user tasks—covering website redesigns, documentation portals, and e-commerce catalogs called out in its when-to-use list. Developers reach for it when sitemaps, nav labels, or taxonomy drift cause support burden and search failure before a single React component ships. The skill includes quick-start flows, reference guides, and best-practice checklists for labeling, grouping, and cross-linking. It complements visual UI work by defining the skeleton developers implement in routes, menus, and CMS collections.
- 4-step IA process covering research, structure development, wireframing, and validation
- Supports card sorting, tree testing, sitemap creation, and taxonomy building
- Works for websites, documentation sites, e-commerce catalogs, and large information spaces
- Includes user journey mapping and competitive analysis templates
- Delivers navigation structures that match user mental models
Information Architecture by the numbers
- 580 all-time installs (skills.sh)
- Ranked #364 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill information-architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 580 |
|---|---|
| repo stars | ★ 305 |
| Last updated | March 4, 2026 |
| Repository | aj-geddes/useful-ai-prompts ↗ |
How do you structure app navigation and taxonomy?
Create clear, user-centered hierarchies, navigation systems, and taxonomies that make documentation, apps, and websites easy to understand and explore.
Who is it for?
Developers or PMs redesigning documentation sites, e-commerce catalogs, or large apps who need clear IA before frontend implementation.
Skip if: Teams needing pixel-level visual design, color systems, or component library coding without structural navigation planning.
When should I use this skill?
User asks to design navigation, sitemap, taxonomy, categorization, or information hierarchy for an app or docs site.
What you get
Navigation hierarchies, sitemap structures, taxonomy labels, and mental-model documentation for websites or apps.
- Sitemap or hierarchy outline
- Navigation and taxonomy specification
- Mental model documentation
Files
Information Architecture
Table of Contents
Overview
Information Architecture creates logical structures that help users find and understand information easily.
When to Use
- Website or app redesign
- Large information spaces (documentation, e-commerce)
- Navigation structure planning
- Taxonomy and categorization
- Search functionality design
- User journey mapping
Quick Start
Minimal working example:
IA Process:
1. Research & Discovery
- Interview users about mental models
- Card sorting sessions (open and closed)
- Analyze current usage patterns
- Competitive analysis
2. Structure Development
- Create organization scheme (hierarchical, faceted, etc.)
- Define categories and relationships
- Build taxonomy
- Plan navigation
3. Wireframing
- Sitemap creation
- Navigation structure
- Page templates
- User flows
4. Validation
- User testing with prototypes
- Tree testing (navigation only)
- Iterate based on feedback
// ... (see reference guides for full implementation)Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Card Sorting & Taxonomy | Card Sorting & Taxonomy |
| Sitemap & Navigation Structure | Sitemap & Navigation Structure |
| Search & Discovery | Search & Discovery |
Best Practices
✅ DO
- Start with user research
- Conduct card sorting studies
- Use user mental models
- Keep hierarchy 3 levels deep max
- Use clear, simple labels
- Enable multiple ways to find content
- Test navigation with users
- Update based on usage data
- Document taxonomy
- Provide search functionality
❌ DON'T
- Impose organizational structure without research
- Use jargon or technical terms
- Make hierarchy too deep
- Bury important content
- Rely only on navigation (provide search)
- Change navigation frequently
- Create ambiguous labels
- Forget about edge cases
- Ignore accessibility
- Assume desktop-only navigation
Card Sorting & Taxonomy
Card Sorting & Taxonomy
# Organize content into logical groups
class InformationArchitecture:
def conduct_card_sort(self, items):
"""Uncover user mental models"""
return {
'method': 'Open card sort (users create own categories)',
'participants': 15,
'items_sorted': len(items),
'analysis': self.analyze_card_sort_results(items),
'dendrograms': 'Show similarity between user groupings',
'categories': self.identify_categories(items)
}
def identify_categories(self, items):
"""Find natural groupings"""
categories = {}
frequency = {}
# Track how often items are grouped together
# Find dominant groupings
return {
'primary_categories': self.get_primary_categories(frequency),
'ambiguous_items': self.identify_ambiguous_items(frequency),
'user_created_labels': self.extract_labels()
}
def create_taxonomy(self, categories):
"""Build hierarchical structure"""
return {
'level1': ['Products', 'Services', 'Support', 'Company'],
'level2_products': ['Electronics', 'Clothing', 'Books'],
'level3_electronics': ['Phones', 'Laptops', 'Accessories'],
'relationships': 'Define parent-child and related items',
'synonyms': 'Identify similar terms'
}
def validate_ia(self, structure):
"""Test with users"""
return {
'testing_method': 'Tree testing',
'tasks': [
'Find product return policy',
'Locate shipping information',
'Access account settings'
],
'success_metrics': {
'task_completion': '90% target',
'time_to_complete': '<3 minutes',
'satisfaction': '>4/5'
}
}Search & Discovery
Search & Discovery
// Enable multiple ways to find content
class DiscoverabilityStrategy {
designSearchFunctionality() {
return {
search_box: {
location: "Header, prominent placement",
placeholder: "Clear example text",
autocomplete: true,
filters: ["Category", "Price", "Rating"],
},
search_results: {
ranking: "Relevance + popularity + freshness",
facets: "Allow filtering results",
snippets: "Show preview and highlights",
},
zero_results: {
suggestions: "Show did you mean, popular searches",
related: "Show related categories",
},
};
}
designBrowsing() {
return {
category_pages: {
structure: "Subcategories + featured items",
sorting: "By popularity, newest, price",
pagination: "Load more or paginate",
},
related_items: {
placement: "Product page, cart page",
logic: "Similar category, trending, recommended",
},
};
}
}Sitemap & Navigation Structure
Sitemap & Navigation Structure
Sitemap Example: E-commerce Site
Home
├── Products
│ ├── Electronics
│ │ ├── Phones
│ │ ├── Laptops
│ │ └── Accessories
│ ├── Clothing
│ │ ├── Men's
│ │ ├── Women's
│ │ └── Kids
│ └── Books
├── Services
│ ├── Shipping & Returns
│ ├── Extended Warranty
│ └── Installation
├── Support
│ ├── FAQ
│ ├── Contact Us
│ ├── Live Chat
│ └── Tickets
├── Account
│ ├── Orders
│ ├── Wishlist
│ ├── Returns
│ └── Settings
└── Company
├── About Us
├── Careers
├── Blog
└── Affiliates
---
Navigation Labels:
- Clear and predictable
- Avoid jargon
- Match user language
- Consistent across site#!/bin/bash
# scaffold-tests.sh - Generate test file scaffolding
# Usage: ./scaffold-tests.sh <source_file> [--framework jest|pytest|mocha]
set -euo pipefail
SOURCE_FILE="${{1:?Usage: $0 <source_file> [--framework jest|pytest|mocha]}}"
FRAMEWORK="${{2:-jest}}"
echo "Scaffolding tests for: $SOURCE_FILE (framework: $FRAMEWORK)"
# TODO: Implement test scaffolding logic
# - Parse source file for exported functions/classes
# - Generate test stubs for each export
# - Include setup/teardown boilerplate
# - Add common assertion patterns
echo "Test scaffolding complete."
// Test Template
// TODO: Customize for your testing framework and project
describe('ModuleName', () => {
// Setup
beforeEach(() => {
// TODO: Add test setup
});
afterEach(() => {
// TODO: Add cleanup
});
describe('functionName', () => {
it('should handle the happy path', () => {
// TODO: Add assertion
});
it('should handle edge cases', () => {
// TODO: Add edge case tests
});
it('should handle errors gracefully', () => {
// TODO: Add error handling tests
});
});
});
Related skills
FAQ
When should developers use information-architecture?
information-architecture fits website or app redesigns, large documentation spaces, e-commerce catalogs, and navigation planning whenever users struggle to find or understand grouped content.
What deliverables does information-architecture produce?
information-architecture yields logical hierarchies, navigation systems, taxonomy labels, and mental models that match user needs—foundational structure before visual UI or route implementation.