用途
Design State 是 Designpowers 工作流中的共享、持续更新的设计文档，随着工作流推进不断累积设计决策。每个 Designpowers 智能体在开始工作前都会读取它，完成后更新它。它是当前设计状态的唯一事实来源。
欢迎门禁
在初始化或读取设计状态之前，先检查本次会话是否已展示 Designpowers 欢迎序列。如果用户尚未看到欢迎内容（鸟、问候语和引导说明），必须先调用 using-designpowers 技能并完成欢迎序列，然后再回到此处。任何工作开始前鸟必须先出现，没有例外。
文件位置
设计状态位于项目根目录（或工作目录）下的 design-state.md。每个项目一个文件。
何时使用
- 初始化：当 design-discovery 完成且 brief 获批后，创建设计状态文件
- 读取：在派发任何 Designpowers 智能体之前，确认设计状态文件存在且为最新
- 更新：任何智能体完成工作后，将其决策和输出追加到状态文件
- 审查：在 critique 或 verification 期间，将状态文件作为已决定内容的权威记录
结构
按以下结构创建和维护设计状态文件：
# Design State: [Project Name]
_Last updated: [date] by [agent name]_
## Brief
- **Problem:** [one-line problem statement]
- **Primary persona:** [name and context]
- **Success metric:** [what "done" looks like]
- **Brief document:** [relative path to full brief]
## Personas
[Link to personas document]
- [Persona 1 name] — [one-line context]
- [Persona 2 name] — [one-line context]
- ...
## Design Principles
1. [Principle] — [what it means in practice]
2. [Principle] — [what it means in practice]
3. ...
## Taste Profile
- **Emotional target:** [2-3 words — e.g., "calm confidence", "playful warmth"]
- **Quality level:** [Prototype / Production / Flagship]
- **Key references:** [names/URLs]
- **Aesthetic principles:** [list]
- **Taste document:** [path to full taste profile]
_If no taste calibration was done, note: "No taste profile — craft evaluation uses general quality standards only."_
## Decisions Log
Append-only. Each entry records who decided, what, and why.
| Date | Agent | Decision | Rationale |
|------|-------|----------|-----------|
| [date] | design-strategist | Bottom tab navigation, 3 items | Minimises cognitive load per principle #1 |
| [date] | design-lead | Mint/sage palette, category colour coding | Warm, approachable, passes AA contrast |
| ... | ... | ... | ... |
## Open Questions
Things that need resolution. Remove when resolved (move decision to log).
- [ ] [Question — who needs to answer it]
- [ ] ...
## Artefact Index
Paths to key documents produced during the workflow.
| Artefact | Path | Status |
|----------|------|--------|
| Brief | [path] | Approved |
| Personas | [path] | Complete |
| Strategy | [path] | Complete |
| Plan | [path] | In progress |
| Heuristic evaluation | [path] | [Pending/Complete] |
| Synthetic test results | [path] | [Pending/Complete] |
| ... | ... | ... |
## Design Debt Register
Deferred findings from critique, accessibility review, heuristic evaluation, and synthetic user testing. Managed by `design-debt-tracker`.
_Items: 0 | Critical: 0 | Oldest: —_
| ID | Date | Source | Severity | What | Who is affected | Suggested fix | Status | Notes |
|----|------|--------|----------|------|----------------|---------------|--------|-------|
## Handoff Chain
Track which agent handed off to which. Each entry includes the conversational babble message that the agent wrote when handing off. These messages are shown to the user.
### [timestamp] design-strategist → design-lead
> "The core users are families with a new puppy, kids aged 8-14 taking the lead. Principle #1 says 'celebrate effort, not perfection' — so nothing should feel like a report card. The setup flow needs progressive disclosure. Over to you for the visual direction."
### [timestamp] design-lead → motion-designer
> "I've gone with frosted glass cards and a mint/sage palette. The progress ring is the hero moment — when it hits 100% it needs to feel like a celebration, not just a colour change. Keep it subtle everywhere else."
**🎨 User override:** "Use my existing design system instead of mint/sage. The tokens are in /tokens/colors.json."
### [timestamp] motion-designer → design-builder
> "Progress ring gets a 600ms spring fill. Checkboxes get 150ms bounce. Reduced-motion fallbacks swap to opacity fades."
### [timestamp] ...
规则
- 每个智能体开始前都读取设计状态——如果它不存在，说明出了问题，回到 discovery
- 每个智能体完成后都追加到决策日志——未被记录的决策等于没有发生
- 永不从决策日志中删除——它是仅追加的。如果某个决策被推翻，添加一条新条目取代它
- 开放问题仅在解决后移除——解决方案写入决策日志
- 交接链是强制性的——每次智能体到智能体的转换都记录传递了什么、需要注意什么
- 保持可扫读——该文件会被每个智能体读取。用表格和单行，而非段落
初始化
首次创建设计状态时（discovery 之后）：
- 在项目根目录创建 design-state.md
- 从获批的设计 brief 填写 Brief 部分
- 如果 Personas 已存在则填写
- 如果 strategy 已完成则填写 Design Principles
- 用已做出的决策启动 Decisions Log
- 添加任何已知的开放问题
- 用 brief 路径启动 Artefact Index
智能体工作后更新
当智能体完成其工作时：
- 读取当前设计状态
- 将新决策追加到 Decisions Log（含日期、智能体名称、决策、理由）
- 解决已得到回答的开放问题
- 添加出现的任何新开放问题
- 用产生的新文档更新 Artefact Index
- 编写交接 babble 消息（2-4 句对话式句子，写给下一个智能体）
- 将 babble 添加到 Handoff Chain——这会展示给用户
- 更新 "Last updated" 行