information-architecture

此技能定义了产品或网站的结构骨架，位于设计简报与构建工作之间。请在撰写完简报后、创建任务前运行此技能。

示例提示词

• “开始构建这个应用前，先规划信息架构”
• “梳理导航和页面结构”
• “我需要整理文档网站的内容”
• “定义新手引导体验中的用户流程”

流程

1. 查找 .design/*/DESIGN_BRIEF.md 中是否已有设计简报。如果存在多个子文件夹，请使用最近修改的那个，或询问用户正在开发哪个功能。如果不存在简报，请询问用户要构建什么，以及面向哪些用户。

2. 探索现有代码库，了解已有的结构：

   • 路由：Next.js app/ 或 pages/ 目录、React Router 配置、Vue Router、SvelteKit 路由或静态 HTML 页面文件
   • 导航组件：页眉、侧边栏、导航栏、面包屑、页脚组件
   • 布局组件：根布局、嵌套布局、页面包装器、容器组件
   • 页面目录：当前页面在文件系统中的组织方式
   • URL 模式：现有 slug、动态片段、查询参数约定
   • CMS 或数据层：内容模型、API 路由、数据获取模式、MDX/内容目录
   • 如果已有结构，此技能应在其基础上扩展和改进。不要提出忽略现有构建成果的新架构。

3. 就结构决策采访用户。针对每个问题，提供你推荐的答案。

   至少涵盖：

   • 用户最需要查找或完成哪些主要事项？按出现频率排序。
   • 导航深度最多可接受几层？
   • 哪些内容会随着时间增长，哪些内容是固定的？
   • 是否有不同类型的用户需要不同的入口？
   • 用户有 80% 的时间会花在哪个页面/视图上？

4. 达成共识后，使用下方模板生成 IA 文档，并将其保存为 INFORMATION_ARCHITECTURE.md，放在与设计简报相同的 .design/<feature-slug>/ 子文件夹中。

IA 文档模板

# 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 first
2. [Second priority] -- Why this comes second
3. [Third priority] -- Rationale
4. [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]