information-architecture

Information architecture workflow for navigation structure, content hierarchy, and labeling clarity across product surfaces. Use when content/navigation structure is unclear and teams need explicit hierarchy and taxonomy decisions before screen-level design; do not use for backend data-model or deployment pipeline decisions.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "information-architecture" with this command: npx skills add kentoshimizu/sw-agent-skills/kentoshimizu-sw-agent-skills-information-architecture

Information Architecture

Overview

Use this skill to make product information structures findable, scalable, and consistent across surfaces.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Navigation depth and labeling rules:
    • references/navigation-depth-and-labeling-rules.md

Templates And Assets

  • Sitemap template:
    • assets/sitemap-template.md
  • Taxonomy glossary template:
    • assets/taxonomy-glossary-template.csv
  • IA validation checklist:
    • assets/ia-validation-checklist.md

Inputs To Gather

  • Content inventory and navigation pain points.
  • User mental models and primary task priorities.
  • Localization constraints and terminology rules.
  • Product growth expectations affecting hierarchy scale.

Deliverables

  • Hierarchy and sitemap definition.
  • Taxonomy and labeling rules with ownership.
  • Navigation risks and ambiguity log.
  • Discoverability validation results.

Workflow

  1. Audit current hierarchy and duplicate pathways.
  2. Draft hierarchy in assets/sitemap-template.md.
  3. Define taxonomy in assets/taxonomy-glossary-template.csv.
  4. Validate labels with references/navigation-depth-and-labeling-rules.md.
  5. Run assets/ia-validation-checklist.md against key user tasks.

Quality Standard

  • Hierarchy is navigable without unnecessary depth.
  • Labels are clear across supported locales.
  • Critical tasks are discoverable in predictable steps.
  • Taxonomy ownership is defined for future changes.

Failure Conditions

  • Stop when taxonomy terms conflict across core surfaces.
  • Stop when navigation choices cannot explain task findability.
  • Escalate when critical tasks remain undiscoverable after redesign.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

architecture-clean-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

schema-evolution-governance

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

sqlalchemy-orm-patterns

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

redis-caching-patterns

No summary provided by upstream source.

Repository SourceNeeds Review