information-architecture

Audit content hierarchy and define taxonomy with sitemap templates and glossaries.

7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill information-architecture-kentoshimizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/information-architecture
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill information-architecture-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Information architecture (IA) defines the structure and labeling of content across product surfaces to improve findability, consistency, and scalability. This skill helps teams articulate explicit hierarchy, taxonomy, and localization-ready terminology before design and development proceed.

Core Features & Use Cases

  • Audit current content hierarchy and identify duplicate or ambiguous pathways to surface a clear structure.
  • Define taxonomy, labeling rules, and ownership to ensure consistent terminology across locales and teams.
  • Deliver IA artifacts such as sitemap templates, taxonomy glossaries, and validation checklists to guide design, content strategy, and navigation decisions.
  • Validate navigation depth and label clarity across locales using the referenced guidelines to reduce localization risk.

Quick Start

Audit your current content structure and draft a sitemap using the provided templates to begin.

Frequently Asked Questions about information-architecture

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

FAQPage Schema
How do I structure product information architecture for multiple locales?

Information architecture structures product content by defining navigation hierarchies, taxonomy glossaries, and localization-ready terminology. This ensures labeling consistency and improves content findability across web and app surfaces in multiple locales.

What is the best way to audit existing content hierarchy for navigation clarity?

The best way to audit content hierarchy is to inventory current content data and identify duplicate or ambiguous pathways. This process surfaces a clear, validated structure by mapping existing navigation depth and label clarity.

How do I create a sitemap template and taxonomy glossary for web and app surfaces?

Create sitemap templates and taxonomy glossaries by defining explicit navigation hierarchies and labeling ownership rules. These deliverables guide design decisions and ensure consistent terminology across web and app product surfaces.

Does information architecture work for both web and app navigation hierarchies?

Information architecture applies directly to product surfaces across both web and app experiences. It enforces consistent navigation hierarchies, taxonomy definitions, and localization-ready terminology regardless of the target platform.

What do I need to validate navigation depth and label clarity across locales?

Validating navigation depth and label clarity requires current content inventory data, localization constraints, and an IA validation checklist. Applying these referenced guidelines reduces localization risk across multiple locales.

When should I not use a structured taxonomy for content findability?

Avoid defining a structured taxonomy when lacking current content inventory data or defined localization constraints. Without these inputs, explicit hierarchy and ownership rules cannot effectively reduce localization risk or improve findability.