
Information Architecture
You're about to wire up routing or build navigation and realize you should probably figure out where everything goes first. This sits between the design brief and actual implementation, mapping out your site structure, navigation patterns, URL conventions, and user flows. It reads your existing routing setup (Next.js app directory, React Router, whatever you have), interviews you about how users will actually move through the thing, then writes a structured IA document. The real win is it forces you to answer the hard questions about navigation depth and content priority before you're three components deep and regretting your choices. Run it after you know what you're building but before you create tasks.
- skills.sh installs
- 6.1K
- GitHub stars
- 601
- last updated
- Aug 21, 2026
Install
$ npx -y skills add julianoczkowski/designer-skills --skill information-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
- 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.
Sponsors
Details
- Repository
- github.com/julianoczkowski/designer-skills
- Categories
- Code Review & Quality, Productivity & Planning, Design & UI/UX
- First seen
- May 16, 2026