Define the structural layer of a product or site before visual design begins. Covers navigation, content hierarchy, page structure, URL patterns, and user flows. Use when user wants to plan site structure, define navigation, map user flows, organize content, or mentions "IA" or "information architec

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 about structural decisions. For each question, provide your recommended answer. Cover at minimum: What are the primary things a user needs to find or do? Rank by frequency. How many levels of navigation depth are acceptable? What content will grow over time vs. what is fixed? Are there distinct user types who need different entry points? What is the one page/view where the user spends 80% of their time? 4. Once you have a shared understanding, produce the IA document using the template below and save it as INFORMATION ARCHITECTURE.md in the same .design/<feature slug / subfolder as the design brief. IA Document Template

information-architecture