Information Architecture

julianoczkowski/designer-skills/information-architecture

作者 julianoczkowskic259656c76d9无许可证577 个星标收录于 2026年10月8日更新于 2026年10月8日仓库3个月前更新

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 architecture".

仅含说明Design & Creative

AI 生成的概览

规划产品或网站的信息架构：导航、内容层级、页面结构、URL 模式与用户流程。

功能: 该技能在视觉设计与开发开始之前，产出一份定义产品或网站结构骨架的信息架构文档。它会查看已有的设计简报以及代码库中的路由、导航、布局和内容模式，就结构决策访谈用户，并写出 INFORMATION_ARCHITECTURE.md 文件。文档涵盖站点地图、导航模型、内容层级、用户流程、命名规范、组件复用、内容增长和 URL 策略。
适用场景: 当用户想要规划站点结构、定义导航、梳理用户流程、组织内容，或明确提到信息架构或 IA 时使用。它适合在设计简报完成之后、实现任务创建之前运行。
运行要求: 不附带脚本，仅为指令。它需要访问项目代码库以及位于 .design/*/DESIGN_BRIEF.md 的设计简报，并将 INFORMATION_ARCHITECTURE.md 写入对应的 .design/ / 文件夹。

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.
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.
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?
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

markdown

# Information Architecture: [Product/Site Name]
## Site Map
A hierarchical map of every page or view. Use indentation to show nesting. Include the URL pattern for each.
- Home `/`  - Feature A `/feature-a`    - Sub-page `/feature-a/detail`  - Feature B `/feature-b`- Settings `/settings`  - Profile `/settings/profile`
## Navigation Model
Describe the navigation system:- **Primary navigation**: What appears in the main nav? Maximum items.- **Secondary navigation**: Sidebar, tabs, or contextual links within sections.- **Utility navigation**: Account, settings, help, and anything outside the main content hierarchy.- **Mobile navigation**: How navigation adapts. Hamburger, bottom tabs, or something else.
## Content Hierarchy
For each major page or view, define the content priority:
### [Page Name]1. [Highest priority content] -- Why this comes first2. [Second priority] -- Why this comes second3. [Third priority] -- Rationale4. [Below the fold / secondary]
## User Flows
The critical paths through the product. Each flow is a sequence of steps with decision points noted.
### [Flow Name] (e.g., "New user onboarding" or "Create a project")1. User lands on [page]2. User sees [content/prompt]3. User takes action: [action]   - If [condition A] -> [outcome]   - If [condition B] -> [outcome]4. User arrives at [destination]
## Naming Conventions
A glossary of terms used in the interface. Consistency matters. Pick one word and use it everywhere.
| Concept | Label in UI | Notes ||---------|-------------|-------|| [thing] | [what we call it] | [why this word] |
## Component Reuse Map
Which structural components (layouts, containers, navigation elements) are shared across pages.
| Component | Used on | Behavior differences ||-----------|---------|---------------------|| [layout/component] | [pages] | [any variations] |
## Content Growth Plan
Which sections of the site will accumulate content over time and how the IA accommodates that growth (pagination, filtering, search, archive patterns).
## URL Strategy
Rules for URL construction:- Pattern: [e.g., `/section/subsection/item-slug`]- Dynamic segments: [what is parameterized]- Query parameters: [filtering, sorting, pagination]

# Information Architecture: [Product/Site Name]
## Site Map
A hierarchical map of every page or view. Use indentation to show nesting. Include the URL pattern for each.
- Home `/`  - Feature A `/feature-a`    - Sub-page `/feature-a/detail`  - Feature B `/feature-b`- Settings `/settings`  - Profile `/settings/profile`
## Navigation Model
Describe the navigation system:- **Primary navigation**: What appears in the main nav? Maximum items.- **Secondary navigation**: Sidebar, tabs, or contextual links within sections.- **Utility navigation**: Account, settings, help, and anything outside the main content hierarchy.- **Mobile navigation**: How navigation adapts. Hamburger, bottom tabs, or something else.
## Content Hierarchy
For each major page or view, define the content priority:
### [Page Name]1. [Highest priority content] -- Why this comes first2. [Second priority] -- Why this comes second3. [Third priority] -- Rationale4. [Below the fold / secondary]
## User Flows
The critical paths through the product. Each flow is a sequence of steps with decision points noted.
### [Flow Name] (e.g., "New user onboarding" or "Create a project")1. User lands on [page]2. User sees [content/prompt]3. User takes action: [action]   - If [condition A] -> [outcome]   - If [condition B] -> [outcome]4. User arrives at [destination]
## Naming Conventions
A glossary of terms used in the interface. Consistency matters. Pick one word and use it everywhere.
| Concept | Label in UI | Notes ||---------|-------------|-------|| [thing] | [what we call it] | [why this word] |
## Component Reuse Map
Which structural components (layouts, containers, navigation elements) are shared across pages.
| Component | Used on | Behavior differences ||-----------|---------|---------------------|| [layout/component] | [pages] | [any variations] |
## Content Growth Plan
Which sections of the site will accumulate content over time and how the IA accommodates that growth (pagination, filtering, search, archive patterns).
## URL Strategy
Rules for URL construction:- Pattern: [e.g., `/section/subsection/item-slug`]- Dynamic segments: [what is parameterized]- Query parameters: [filtering, sorting, pagination]

来源与署名

来源：julianoczkowski/designer-skills位于information-architecture提交c259656

许可证：无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Information Architecture

Example prompts

Process

IA Document Template

来源与署名

更多来自 julianoczkowski/designer-skills 的技能

Brief To Tasks

Design Brief

Grill Me

Frontend Design

Design Tokens

Design Flow

更多Design & Creative技能

Theme Factory

Slack Gif Creator

Frontend Design

Canvas Design

Brand Guidelines

Frontend Design