information-architecturelisted

This skill defines the structural skeleton of a product or site. It sits between the design brief and the build. Run this after the brief is 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. Look for an existing design brief at `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. If no brief exists, ask the user what they are building and for whom. 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 the file system - **URL patterns**: existing slugs, dynamic segments, query parameter conventions - **CMS or data layer**: content models, API routes, data fetching patterns, MDX/content directories - If structure exists, this skill extends and improves it. Do not propose a new architecture that ignores what is already built. 3. Interview the user abo