information-architecture

Plan site structure, navigation, content hierarchy, and user flows before visual design begins.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill information-architecture-yashmishra2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: information-architecture
Source: https://github.com/yashmishra2006/LexWrite-Website/tree/main/.agents/skills/information-architecture
Command: npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill information-architecture-yashmishra2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into visual design or coding without defining how a product is structured, leading to confusing navigation, inconsistent naming, and pages that do not scale as content grows. This Skill produces a structured information architecture document that defines the skeleton of a product or site before any build work starts. ## Core Features & Use Cases - Site Map & URL Strategy: Generates a hierarchical map of every page with URL patterns, dynamic segments, and query parameter conventions. - Navigation & Content Hierarchy: Defines primary, secondary, utility, and mobile navigation models plus per-page content priority ordering. - User Flows & Naming Conventions: Documents critical user paths with decision points and a glossary enforcing consistent UI terminology. - Use Case: Before building a new feature in a Next.js app, run this Skill to inspect existing routes and layouts, interview stakeholders on structural decisions, and save an INFORMATION_ARCHITECTURE.md alongside the design brief. ## Quick Start Ask the AI to plan the information architecture for your product, mapping the navigation, page structure, and key user flows before you start building.

Frequently Asked Questions about information-architecture

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

FAQPage Schema
How do I plan information architecture for a website or app?

Start by identifying what users need to find or do, ranked by frequency, then define a site map with URL patterns, a navigation model, and per-page content hierarchy. This Skill guides that process through a structured interview and produces a complete IA document.

What should an information architecture document include?

An IA document should include a hierarchical site map with URLs, primary and secondary navigation models, content priority per page, critical user flows with decision points, naming conventions, a component reuse map, a content growth plan, and URL construction rules.

Does this work with an existing Next.js or React codebase?

Yes. The Skill inspects existing routing such as the Next.js app or pages directory, navigation components, layouts, and URL patterns, then extends and improves the current structure rather than proposing an architecture that ignores what is already built.

When should information architecture be defined in a project?

Define IA after the design brief is written and before tasks or visual design begin. It sits between the brief and the build, ensuring structural decisions about navigation, content, and flows are settled before implementation starts.

What are the limitations of a sitemap-only approach to IA?

A sitemap alone misses navigation behavior, content priority, user flow decision points, and growth planning. This Skill covers those gaps with dedicated sections for navigation models, content hierarchy, flows, naming conventions, and content growth strategies.