information-architecture

Define site structure, navigation, and user flows in an IA document.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/richardaum/sporty-group --skill information-architecture-richardaum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/richardaum/sporty-group/tree/main/.agents/skills/information-architecture
Command: npx skills add https://github.com/richardaum/sporty-group --skill information-architecture-richardaum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps designers and developers define the structural layout of a product or website, ensuring a logical and user-friendly organization from the outset.

Core Features & Use Cases

  • Site Mapping: Create detailed hierarchies of pages and views with URL patterns.
  • Navigation Design: Outline primary, secondary, and utility navigation systems for intuitive access.
  • User Flow Planning: Map critical user journeys through different pages or features.
  • Use Case: For a new SaaS app, plan the navigation layers and page hierarchy to improve user onboarding.
  • Documentation: Generate a comprehensive IA document to guide development and design teams.

Quick Start

Draft an IA for a new e-commerce platform, including site map, navigation model, and user flows, then save as INFORMATION_ARCHITECTURE.md.

Frequently Asked Questions about information-architecture

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

FAQPage Schema
How do I plan the site structure and navigation for a new SaaS app?

A site map provides a detailed hierarchy of pages and views, including URL patterns, to establish a logical product structure. This organization ensures users can navigate intuitively and development teams understand routing relationships.

What's the best way to map user flows through different website features?

The best way to map user flows is to outline the critical user journeys through different pages and features within your site structure. This process clarifies navigation requirements and ensures users reach key destinations without friction.

Do I need existing routing and content organization before defining information architecture?

Yes, understanding existing routing and content organization is required before defining information architecture. Analyzing current structures ensures the new navigation models and content hierarchies integrate logically rather than disrupting established user pathways.

Can I generate documentation for my site map and navigation model?

Yes, you can generate a comprehensive information architecture document that details site maps, navigation models, and user flows. Saving this output as a markdown file provides a persistent reference to guide development and design teams.

When should I not use a formal information architecture planning process?

You should avoid formal information architecture planning when a digital product lacks defined content or feature requirements. Without existing routing or content organization to analyze, structural layout decisions become speculative and fail to improve user experience.