information-architecturelisted

This skill defines the structural skeleton of a product or site. It sits between the design brief and the build, and it fills one section — `## Structure` — of the feature's `.design/YYYY-MM-DD-<slug>.md`. Run it after the brief sections are written and before tasks are created. ## Example prompts - "Plan the IA for this app before I start building" - "Map out the navigation and page structure" - "I need to organize the content for a documentation site" - "Define user flows for the onboarding experience" ## Process 1. Find the feature's design file by the procedure in `${CLAUDE_SKILL_DIR}/../design/SKILL.md` → **Finding the design file**. Or ask the user which feature they are working on; if nothing exists, ask what they are building and for whom. In a legacy six-file folder, read `DESIGN_BRIEF.md` and write `INFORMATION_ARCHITECTURE.md` beside it, as before. Read `## Problem`, `## Solution`, `## Scope`, `## Experience` and `## Architecture` before writing. Routes and flows must match the API surface already named. 2. Explore the existing codebase to understand what structure already exists: - **Routing**: Next.js `app/` or `pages/` directory, React Router config, Vue Router, SvelteKit routes, or static HTML page files - **Navigation components**: header, sidebar, navbar, breadcrumb, footer components - **Layout components**: root layouts, nested layouts, page wrappers, container components - **Page directories**: how pages are currently organized in