information-architecture

Structure navigation, content hierarchy, and labeling systems into sitemaps.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill information-architecture-j-cogburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/information-architecture
Command: npx skills add https://github.com/j-cogburn/d3 --skill information-architecture-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical issue of users being unable to find required content or features within a product, not because the functionality is missing, but because of poor navigation design, unclear labeling, or disorganized content hierarchy that buries key information.

Core Features & Use Cases

  • Structured IA Framework: Provides a 7-step process for inventorying existing content, understanding user mental models, applying organization principles, designing hierarchy, writing effective labels, selecting navigation patterns, and producing formal sitemaps.
  • Navigation Pattern Guidance: Includes best practices for top nav bars, sidebars, bottom mobile nav, and tab bars, with clear use cases for each pattern.
  • Anti-Pattern Mitigation: Covers common IA mistakes like "Other/Misc" categories, excessive navigation depth, and internal jargon labels, with counter-arguments for common rationalizations and red flags to watch for.
  • Use Case Example: If your support team is receiving repeated tickets from users unable to locate the order returns page, use this Skill to audit your current navigation, align labels with user vocabulary, and restructure your sitemap to make the returns page discoverable in 2 clicks or less.

Quick Start

Use the information-architecture skill to audit your product's current navigation and identify why users are unable to locate the account settings page.

Frequently Asked Questions about information-architecture

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

FAQPage Schema
How do I structure navigation and content hierarchy to reduce user friction?

To structure navigation and content hierarchy, apply a 7-step process: inventory content, understand user mental models, apply organization principles, design hierarchy, write effective labels, select navigation patterns, and produce formal sitemaps to eliminate user friction.

Why are users unable to find required content and features within my digital product?

Users cannot find required content because of poor navigation design, unclear labeling, or disorganized content hierarchy that buries key information, not because the functionality is missing. Audit your sitemap to identify these information architecture issues.

What is the best way to audit existing product navigation for findability issues?

The best way to audit existing product navigation is to inventory current content, evaluate user mental models against your labeling systems, and check for information architecture anti-patterns like excessive navigation depth or internal jargon labels.

How do I write effective navigation labels that align with user vocabulary?

To write effective navigation labels, map your user mental models and eliminate internal jargon. Replace vague categories like "Other/Misc" with user-aligned vocabulary to ensure content findability and reduce support ticket volume.

When should I use a sidebar versus a top navigation bar for my digital product?

Use a top navigation bar for primary navigation patterns and a sidebar for secondary filters or deeper content hierarchy. Select navigation patterns based on the specific use case and mobile constraints like bottom mobile nav.

What are common information architecture anti-patterns that cause user drop-off?

Common information architecture anti-patterns causing user drop-off include "Other/Misc" categories, excessive navigation depth, and internal jargon labels. Mitigating these findability issues reduces user friction and support ticket volume.