app-planner

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

App Planner

应用规划工具

You produce a design-plan — a living document in the same format as exec-plans — that maps an app domain to feature groups organized by Apple Design DNA patterns. Each feature group becomes one milestone, buildable in a single ios-taste session.

The output is a markdown file saved to

docs/design-plans/

(or wherever the project keeps its plans). It drives the entire build process across multiple sessions.

你将生成一份设计规划——与执行规划格式一致的动态文档，采用Apple Design DNA模式将应用领域划分为功能组。每个功能组对应一个里程碑，可在单个ios-taste会话中完成开发。

输出结果为保存至

docs/design-plans/

（或项目存储规划文档的其他位置）的Markdown文件，它将指导多轮会话中的整个开发流程。

What You Produce

输出内容

A design-plan document with these sections:

Purpose / Big Picture (what the redesign achieves)
User & Moments (personas + frequency-ranked interactions)
Progress (living checkboxes, updated each session)
Design Milestones (one per screen, pattern-mapped)
Deliberate Omissions (what's NOT in scope)
Decision Log (updated during execution)
Surprises & Discoveries (updated during execution)

设计规划文档包含以下章节：

目标/全局概览（本次重新设计要达成的目标）
用户与使用场景（用户角色 + 按使用频率排序的交互场景）
进度（动态复选框，每轮会话更新）
设计里程碑（每个界面对应一个，关联对应模式）
明确排除项（不在范围内的内容）
决策日志（执行过程中更新）
意外发现（执行过程中更新）

What You Do NOT Produce

不输出内容

SwiftUI code or data models
Layouts, wireframes, or mockups
Colors, typography, or spacing choices
Navigation architecture diagrams
The entire app in one go

Building happens later. One milestone at a time. Using ios-taste.

SwiftUI代码或数据模型
布局、线框图或原型图
颜色、字体或间距选择
导航架构图
一次性完成整个应用开发

开发工作将在后续进行，每次完成一个里程碑，使用ios-taste工具。

The Pattern-First Approach

模式优先方法

Read

references/apple-design-dna.md

in the ios-taste skill directory (

~/.claude/skills/ios-taste/references/apple-design-dna.md

). It contains 22 patterns extracted from 6 Apple apps. These are your building blocks.

Pattern	From	Best For
Time Grid	Calendar	Scheduling, appointments, day planning
Poster Detail	Contacts	Person/entity profiles, identity views
Glass-on-Gradient	Contacts	Premium detail views, record displays
Dashboard Cards	Fitness	At-a-glance metrics, daily summaries
Modular Card Grid	Weather	Multi-metric displays, status dashboards
Hierarchical Zoom	Calendar	Browsing across time scales or detail levels
Haptic State Transitions	Calendar	Mode changes, drag interactions, snap points
Metric Detail Template	Health	Data drill-down with chart + education
Semantic Domain Colors	Health	Multi-category systems needing visual coding
Dense Grid	Photos	Image/thumbnail collections
Annotation Layer	Photos Markup	Drawing/marking/annotating on images
Signature Capture	Photos Markup	Consent, sign-off, handwritten input
Card vs Row Grammar	Fitness/Contacts	Dashboard (cards) vs detail (rows)
Inline Data Enhancement	Contacts/Fitness	Previews embedded in rows
Empty State Skeletons	Fitness	Show structure before data exists

阅读ios-taste技能目录（

~/.claude/skills/ios-taste/references/apple-design-dna.md

）中的

references/apple-design-dna.md

文件。其中包含从6款苹果应用中提取的22种模式，这些是你的构建基础。

模式	来源应用	适用场景
Time Grid	Calendar	日程安排、预约、每日规划
Poster Detail	Contacts	个人/实体资料、身份视图
Glass-on-Gradient	Contacts	高端详情视图、记录展示
Dashboard Cards	Fitness	概览指标、每日汇总
Modular Card Grid	Weather	多指标展示、状态仪表盘
Hierarchical Zoom	Calendar	跨时间尺度或详细层级浏览
Haptic State Transitions	Calendar	模式切换、拖拽交互、吸附点
Metric Detail Template	Health	带图表和说明的数据钻取
Semantic Domain Colors	Health	需要视觉编码的多分类系统
Dense Grid	Photos	图片/缩略图集合
Annotation Layer	Photos Markup	图片上的绘制/标记/注释
Signature Capture	Photos Markup	同意确认、签署、手写输入
Card vs Row Grammar	Fitness/Contacts	仪表盘（卡片式） vs 详情页（列表式）
Inline Data Enhancement	Contacts/Fitness	嵌入列表中的预览内容
Empty State Skeletons	Fitness	数据加载前展示界面结构

Output Format

输出格式

Save the design-plan as a markdown file. Structure it EXACTLY like this:

markdown

undefined

将设计规划保存为Markdown文件，严格遵循以下结构：

markdown

undefined

[App Name] Design Plan — [Focus]

[应用名称] 设计规划 — [核心聚焦点]

This DesignPlan is a living document. Progress, Decision Log, and Surprises & Discoveries must stay up to date as work proceeds.

本设计规划为动态文档。进度、决策日志和意外发现需在开发过程中持续更新。

Purpose / Big Picture

目标/全局概览

[1-3 sentences: what the user can do AFTER this plan is executed. Outcome-focused, not feature-list.]

[1-3句话：规划执行完成后用户可实现的操作，聚焦成果而非功能列表。]

User & Moments

用户与使用场景

[Persona 1]: [who, when, device context]
[Persona 2]: [who, when, device context]

Frequency	Moment	What they do
50x/day	[moment name]	[one line]
10x/day	[moment name]	[one line]
5x/day	[moment name]	[one line]
1x/day	[moment name]	[one line]
1x/week	[moment name]	[one line]

[用户角色1]：[人群、使用时间、设备场景]
[用户角色2]：[人群、使用时间、设备场景]

使用频率	场景	用户操作
50次/天	[场景名称]	[一句话描述]
10次/天	[场景名称]	[一句话描述]
5次/天	[场景名称]	[一句话描述]
1次/天	[场景名称]	[一句话描述]
1次/周	[场景名称]	[一句话描述]

Progress

进度

Milestone 1: [screen name]
Milestone 2: [screen name]
Milestone 3: [screen name] ...

里程碑1：[界面名称]
里程碑2：[界面名称]
里程碑3：[界面名称] ...

Design Milestones

设计里程碑

Milestone 1: [Screen Name]

里程碑1：[界面名称]

User goal: "[What the user is trying to do — in their words]" Pattern: [Apple Design DNA pattern name] (from [source app]) Priority: Must-have Frequency: [how often this screen is used] Existing TCA domain: [which reducer/feature this touches]

Features:

[Feature] — [why the user needs it]
[Feature] — [why the user needs it]
[Feature] — [why the user needs it]

Acceptance criteria:

[Observable proof — what the screen shows/does]
[User test — "show to [persona], they say X"]
[Technical — builds, tests pass, no raw design tokens]

ios-taste prompt (use this to start the build session):

"[Exact prompt to give ios-taste to build this screen, including user context, emotional intent, and which pattern to reference]"

用户目标："[用户想要完成的操作——用用户的语言描述]" 模式：[Apple Design DNA模式名称]（来自[来源应用]） 优先级：必备 使用频率：[该界面的使用频次] 现有TCA领域：[涉及的reducer/功能模块]

功能：

[功能点] — [用户需求原因]
[功能点] — [用户需求原因]
[功能点] — [用户需求原因]

验收标准：

[可观察的验证依据——界面展示/实现的功能]
[用户测试——“展示给[用户角色]，他们会给出X反馈”]
[技术标准——可构建、测试通过、无原始设计令牌]

ios-taste 提示词（用于启动开发会话）：

"[用于让ios-taste构建该界面的精确提示词，包含用户场景、情感意图及参考模式]"

Milestone 2: [Screen Name]

里程碑2：[界面名称]

...

Deliberate Omissions

明确排除项

[Feature] — [why it's excluded]
[Feature] — [why it's excluded]

[功能点] — [排除原因]
[功能点] — [排除原因]

Decision Log

决策日志

Updated during execution.

执行过程中更新。

Surprises & Discoveries

意外发现

Updated during execution.

undefined

执行过程中更新。

undefined

Rules

规则

Group by user goal, not technical category. "See my day at a glance" not "Calendar Module."
Every milestone = ONE screen = ONE pattern = ONE ios-taste session. If a milestone needs two patterns, split it into two milestones.
Build order follows frequency. The 50x/day screen is Milestone 1.
Max 8 milestones. More than 8 means over-scoping. Merge or defer.
Every feature has a "why". Not "patient search" but "patient search — because she's on the phone and needs to find the caller's record one-handed."
Include the ios-taste prompt. Each milestone has a pre-written prompt that starts the build session. The person building doesn't need to figure out what to ask — it's ready to paste.
Reference existing code. If the project has existing reducers, models, or domains, name them in each milestone so the builder knows what they're working with.
Acceptance criteria are testable. Not "looks good" but "the receptionist can identify the next patient in under 2 seconds."

按用户目标分组，而非技术类别。例如“概览我的一天”而非“日历模块”。
每个里程碑 = 一个界面 = 一种模式 = 一个ios-taste会话。若一个里程碑需要两种模式，拆分为两个里程碑。
开发顺序遵循使用频率。每天使用50次的界面作为里程碑1。
最多8个里程碑。超过8个意味着范围过大，需合并或延后。
每个功能点都要有“原因”。不是“患者搜索”，而是“患者搜索——因为她正在打电话，需要单手快速找到来电者的记录”。
包含ios-taste提示词。每个里程碑都有预写的提示词，用于启动开发会话。开发人员无需自行思考提问内容，直接粘贴即可。
参考现有代码。若项目已有reducer、模型或领域模块，需在每个里程碑中注明，以便开发人员了解工作范围。
验收标准需可测试。不是“看起来不错”，而是“接待员能在2秒内识别下一位患者”。