@xenonbyte/da-vinci-workflow 0.1.11 → 0.1.13

package/docs/prompt-presets/web-app.md

@@ -1,6 +1,6 @@
 # Web App Prompt Preset
 
-Recommended when the product is a browser-based application or product website with app-like surfaces.
+Recommended when the product is a browser-based application or a web product with app-like surfaces.
 
 Pair with:
 
@@ -8,40 +8,78 @@ Pair with:
 
 Use this when the workflow needs:
 
-- responsive page hierarchy
+- responsive hierarchy
 - separation between marketing and product surfaces
-- careful handling of empty, loading, error, and authenticated states
-- decomposition of complex flows into real surfaces instead of one oversized page
+- careful treatment of empty, loading, error, and authenticated states
 
-Recommended prompt:
+## How To Choose
+
+- Use `Simple redesign` when the web product has a limited product surface or only a few major pages.
+- Use `Complex redesign` when the product mixes marketing, auth, onboarding, app surfaces, dialogs, drawers, and materially different states.
+- Use `Design-only` when you want the design chain and bindings but no code changes yet.
+- Use `Continue` when the workflow already has artifacts and needs to resume.
+
+## Simple Redesign
 
 ```text
 $da-vinci use redesign-from-code to redesign this existing web product.
 
 Existing code is the behavior source of truth, not the layout truth.
 Preserve current business logic, routes, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
-Inventory responsive surfaces, authenticated areas, settings pages, dialogs, drawers, overlays, and important states before broad Pencil work.
-Separate marketing-style surfaces from product-workflow surfaces when they require different visual treatment.
-Decompose complex pages into subpages, overlays, materially different states, and implementation surfaces.
+Inventory the current product surfaces and important states before Pencil work.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Do not pass design checkpoint if the result is a generic SaaS card grid or a recolor of the old interface.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
-When to switch to `intake` first:
+## Complex Redesign
 
-- the product mixes marketing, auth, onboarding, and app surfaces
-- the first workflow prompt is hard to phrase cleanly
-- there are external design references that must stay subordinate to existing behavior
+```text
+$da-vinci use redesign-from-code to redesign this existing web product.
 
-`intake` variant:
+Existing code is the behavior source of truth, not the layout truth.
+Preserve current business logic, routes, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
+Inventory responsive product surfaces, marketing surfaces, authenticated areas, settings pages, dialogs, drawers, overlays, and materially different states before broad Pencil work.
+Separate marketing-style surfaces from product-workflow surfaces when they require different visual treatment.
+Decompose complex pages into subpages, overlays, materially different states, and implementation surfaces.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+Treat the resolved primary visual adapter as the first-pass design lead.
+Use Pencil guides only as responsive layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Do not pass design checkpoint if the result is a generic SaaS card grid, repeated placeholder scaffolds, or a recolor of the old interface.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+## Design-Only
 
 ```text
-$da-vinci use intake for this existing web product.
+$da-vinci use redesign-from-code to redesign this existing web product.
 
-I need to redesign the UI while preserving current behavior.
 Existing code is the behavior source of truth, not the layout truth.
+Preserve current behavior, routes, permissions, integrations, and state transitions.
 Inventory product surfaces, marketing surfaces, overlays, and important states.
-Decompose complex pages before Pencil work.
-Generate the best executable Da Vinci workflow prompt for the next step.
+Decompose complex pages into real design surfaces before Pencil work.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+If the product is complex, design 1-3 anchor surfaces first, review screenshots, then expand.
+Stop after DA-VINCI.md, design-registry.md, page-map.md, proposal.md, specs, design.md, pencil-design.md, pencil-bindings.md, and tasks.md.
+Do not start code changes yet.
 ```
+
+## Continue
+
+```text
+$da-vinci use continue for this existing web-product redesign workflow.
+
+Use the existing Da Vinci artifacts in this project.
+Do not restart discovery unless an artifact is missing or clearly wrong.
+Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth.
+If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
+Continue into the next unfinished stage and do not stop at tasks.md when the active intent is full-delivery.
+```
+
+## When To Switch To Intake First
+
+- the product mixes many surface types and truth sources
+- external references complicate the first workflow request
+- the first prompt is still hard to phrase cleanly

package/docs/visual-adapters.md

@@ -116,6 +116,7 @@ Use the fields like this:
   - the priority list of local skills you want Da Vinci to try first
   - order matters
   - if multiple listed skills are available, Da Vinci should still resolve one primary adapter
+  - do not assume cross-platform equivalence between near-name adapters such as `frontend-skill` and `frontend-design`; resolve the actual installed adapter names for the current environment
 - `Scope`
   - the only areas where adapters are allowed to influence the workflow
   - keep this limited to presentation-quality work such as composition, spacing, and Pencil refinement
@@ -178,9 +179,12 @@ Recommended fields:
 ```md
 ## Visual Adapter Resolution
 - Requested adapters: frontend-skill, ui-ux-pro-max
+- Available requested adapters: frontend-skill
+- Unavailable requested adapters: none
 - Resolved primary adapter: frontend-skill
 - Secondary helpers: none
 - Status: active
+- Runtime declaration: explicitly stated before first anchor pass
 - Scope: DA-VINCI.md, design.md, pencil-design.md
 - Fallback reason if native Da Vinci rules were used: none
 ```
@@ -202,9 +206,23 @@ If no adapter is available:
 When a visual adapter is active:
 
 - use it before or during Pencil work to sharpen composition and hierarchy
+- treat the resolved primary adapter as the art-direction lead for the first pass, not as a note that merely gets copied into `design-registry.md`
+- explicitly state the resolved primary adapter in the runtime log before the first anchor-screen pass
+- write a visual thesis, content plan, and interaction thesis before the first anchor-screen pass under that adapter's lead
 - keep page names and states aligned with `page-map.md`
 - keep final `.pen` decisions grounded in Pencil, not in adapter prose
 
+For complex redesigns:
+
+- do not start by scaffolding many screens with empty placeholders
+- design 1-3 anchor surfaces first
+- make each anchor surface fully composed before broad expansion
+- for each anchor surface, explain briefly how the new composition differs structurally from the current layout
+- use screenshot review on each anchor surface before cloning variants or expanding the rest of the product
+- do not treat screenshot analysis as an automatic pass; if the review flags hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues, revise before expanding
+- define a small shared primitive family from the approved anchor surfaces before broad page expansion
+- if the output is still placeholder-heavy or repetitious, mark `design checkpoint` as `BLOCK` and reset from the anchor surfaces instead of layering more screens on top
+
 Record the outcome in `pencil-design.md`.
 
 Recommended fields:
@@ -234,6 +252,15 @@ If it is unavailable, fall back to native Da Vinci design rules and continue.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
+For complex Android or multi-surface product redesigns, add this bias explicitly:
+
+```text
+Use frontend-skill explicitly as the primary visual reasoning source.
+Use Pencil guides only as layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+```
+
 ## Suggested Adapter Choices
 
 - `frontend-skill`

package/docs/visual-assist-presets/README.md

@@ -19,6 +19,7 @@ If the project is design-critical or previous outputs were weak, generic, or too
 - move `frontend-skill` to the first slot
 - consider `Require Adapter: true`
 - raise the design checkpoint bar before broad Pencil generation
+- switch to anchor-first generation: design 1-3 anchor surfaces, review screenshots, then expand
 
 Available presets:
 
@@ -33,3 +34,4 @@ How to use them:
 2. copy the `## Visual Assist` block into `DA-VINCI.md`
 3. adjust adapter order only if the project clearly needs a different visual bias
 4. keep `Require Adapter: false` unless the project truly must stop without a specific local skill
+5. for complex redesigns, do not treat the preset alone as enough; pair it with anchor-first Pencil generation and screenshot review

package/docs/workflow-examples.md

@@ -56,10 +56,11 @@ Expected flow:
 4. write behavior in `specs/<capability>/spec.md`
 5. define pages in `page-map.md`
 6. resolve any requested visual adapter and record it in `design-registry.md`
-7. register and generate Pencil sources
-8. bind implementation pages to Pencil pages
-9. generate tasks
-10. build and verify
+7. register the project-local Pencil source
+8. design 1-3 anchor surfaces first and review screenshots before broad expansion
+9. bind implementation pages to Pencil pages
+10. generate tasks
+11. build and verify
 
 ## 3. `redesign-from-code`
 
@@ -79,11 +80,13 @@ Expected flow:
 4. define redesign scope in `proposal.md`
 5. split broad redesign work into `specs/<slice>/spec.md` files when one large `ui-refresh` spec would be too coarse
 6. rebuild or refine `page-map.md`, including subpages, overlays, and materially different states
-7. create new or updated Pencil pages from fresh composition rather than a recolor of the old UI, preferring persistence under `.da-vinci/designs/`
-8. run `design-source checkpoint` to confirm the registered project-local `.pen` path, the active Pencil source, and the shell-visible file all agree
-9. bind routes and pages to Pencil screens
-10. generate tasks aligned to the redesign slices
-11. build and verify
+7. write the visual thesis, content plan, interaction thesis, and structural-delta notes for the anchor surfaces
+8. create new or updated Pencil pages from fresh composition rather than a recolor of the old UI, preferring persistence under `.da-vinci/designs/`
+9. verify the registered project-local `.pen` path becomes shell-visible immediately after the first successful Pencil write
+10. run `design-source checkpoint` to confirm the registered project-local `.pen` path, the active Pencil source, and the shell-visible file all agree
+11. bind routes and pages to Pencil screens
+12. generate tasks aligned to the redesign slices
+13. build and verify
 
 ### Complex Android example
 
@@ -93,6 +96,17 @@ $da-vinci use redesign-from-code to redesign this existing Android app.
 Existing code is the behavior source of truth, not the layout truth.
 Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, and important states.
 Decompose complex screens into separate design surfaces before Pencil work.
+Use frontend-skill explicitly as the primary visual reasoning source.
+State the resolved primary visual adapter explicitly in the log before the first anchor surface.
+Write a visual thesis, content plan, and interaction thesis before the first anchor surface.
+Use Pencil guides only as layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep `.da-vinci/designs/` reserved for `.pen` files only.
 Do not pass design checkpoint if the result is just a skin-swap of the old UI.
 ```
 

package/docs/zh-CN/codex-natural-language-usage.md

@@ -74,6 +74,13 @@ $da-vinci use <mode> to <goal>
 
 - `docs/zh-CN/prompt-presets/`
 
+每个场景文件现在都固定包含：
+
+- `Simple redesign`
+- `Complex redesign`
+- `Design-only`
+- `Continue`
+
 ### 1. 新项目，需求清晰
 
 ```text

package/docs/zh-CN/mode-use-cases.md

@@ -35,6 +35,7 @@ project/
 - `DA-VINCI.md` 放根目录
 - 其他工作流工件放 `.da-vinci/`
 - 项目内持久化的 Pencil `.pen` 文件默认放 `.da-vinci/designs/`
+- `.da-vinci/designs/` 里只应该放 `.pen` 文件，不应该混入工作流 markdown
 
 ## 快速选 mode
 
@@ -134,7 +135,11 @@ Da Vinci 应该：
    - 把复杂页面拆成 subpage、state、overlay、fragment surface
 7. 生成 `design.md`
 8. 生成 `pencil-design.md`
+   - 在大规模 anchor 设计前，先写 visual thesis、content plan、interaction thesis 和 structural-delta 说明
+   - 先做 1 到 3 个 anchor surface，再扩展更多页面
+   - 首轮设计由解析出来的主 visual adapter 主导
    - 把新的 Pencil 基线真正落到登记好的 `.da-vinci/designs/` 路径
+   - 在第一次成功写入 Pencil 后，立即验证登记的 `.pen` 路径已经成为 shell 可见文件
 9. 生成 `pencil-bindings.md`
 10. 生成 `tasks.md`
 11. 进入实现
@@ -144,10 +149,22 @@ Da Vinci 应该：
 - 现有代码决定 behavior，不决定新的视觉布局
 - `redesign-from-code` 默认应该基于页面职责和状态重新构图
 - 不能把“旧页面换个配色、换点间距、挪一点位置”当成真正的重设计
+- 一旦配置了 `Preferred adapters`，解析出来的主 adapter 应该主导首轮设计，而不是只登记不使用
+- 运行时必须明确声明解析出来的主 adapter，以及哪些请求的 adapter 当前不可用
+- 不要把跨平台的近名 adapter 默认当成同一个能力源，应该按当前环境里真实安装的名字解析
+- 当主 adapter 生效时，先写 visual thesis、content plan 和 interaction thesis，再开始第一个 anchor screen
+- 不要让 Pencil 的 guide 或样式模板取代主 adapter 成为设计方向来源
+- 不要一上来就批量搭很多空 screen
+- 对复杂产品，先把 1 到 3 个 anchor surface 做到通过截图审查，再扩展其他页面
+- 对每个 anchor surface，都要说明“新的构图与当前布局结构相比具体改了什么”
+- 只要截图分析指出 hierarchy、spacing、clarity、inconsistency 或 unresolved placeholder 问题，就不能自动判通过
+- 在扩展更多页面前，先从已通过的 anchor surface 中抽出一组 shared primitives
+- 只使用 Pencil 支持的属性，不要继续使用 `flex`、`margin` 这类 Web/CSS 属性
 - 一个实现页如果包含多个 Fragment、多个 tab、多个状态或多个 overlay，应该拆成多个设计 surface
 - `design-registry.md` 里的首选 `.pen` 路径由工作流自动维护，不应该依赖用户手工填写
 - 不要因为当前 Pencil 里正好打开了一个文档，就直接在那个文档上继续做重设计
 - 如果 Pencil MCP 没有自动把登记路径的 `.pen` 文件落到磁盘，就应该先补写这个项目内文件，再把 mapping 或 implementation 视为完成
+- `.da-vinci/designs/` 应该只作为 `.pen` 目录使用，不应该混入 inventory、proposal 之类的 markdown
 
 ## 4. `feature-change`
 

package/docs/zh-CN/prompt-presets/README.md

@@ -10,8 +10,9 @@
 
 1. 先选最接近产品形态的提示词模板
 2. 再选对应的 `Visual Assist` 模板
-3. 两者一起放进工作流设置
-4. 只有在项目存在特殊真相源或平台约束时，再继续收紧提示词
+3. 再选和项目复杂度、交付意图匹配的提示词版本
+4. 两者一起放进工作流设置
+5. 只有在项目存在特殊真相源或平台约束时，再继续收紧提示词
 
 可用模板：
 
@@ -25,3 +26,10 @@
 - 提示词模板负责定义工作流意图、拆分规则和真相源处理方式
 - `Visual Assist` 模板负责定义 UI 设计增强偏好
 - 两者一起使用，结果通常更稳
+
+现在每个场景模板里都固定包含：
+
+- `Simple redesign`
+- `Complex redesign`
+- `Design-only`
+- `Continue`

package/docs/zh-CN/prompt-presets/desktop-app.md

@@ -9,38 +9,76 @@
 适合这种需求：
 
 - 高密度工作区层级
-- 明确的工具面板和主工作面
-- 克制的 modal 和 secondary panel 处理
-- 把复杂页面拆成真正有意义的 surface
+- 明确的主工作面和次级面板
+- 克制的 modal、inspector 和 secondary panel 处理
 
-推荐提示词：
+## 如何选择
+
+- `Simple redesign` 适合 workspace 不多、状态分支有限、结构相对收敛的项目。
+- `Complex redesign` 适合多工作区、多侧栏、多 inspector、多 overlays、状态变化明显的项目。
+- `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
+- `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
+
+## Simple Redesign
 
 ```text
 $da-vinci use redesign-from-code to redesign this existing desktop product.
 
 Existing code is the behavior source of truth, not the layout truth.
-Preserve behavior, flows, integrations, and validation rules unless explicitly required otherwise.
-Inventory primary workspaces, side panels, secondary panels, dialogs, settings flows, overlays, and important states before broad Pencil work.
-Decompose complex screens into primary surfaces, secondary surfaces, overlays, and materially different states.
+Preserve current behavior, flows, integrations, and validation rules unless explicitly required otherwise.
+Inventory the current workspaces, dialogs, overlays, and important states before Pencil work.
 Use the Visual Assist preferences declared in DA-VINCI.md.
-Do not pass design checkpoint if the result is just a boxed-up recolor of the old UI or if panel hierarchy remains unclear.
+Do not pass design checkpoint if the result is just a boxed-up recolor of the old UI or if workspace hierarchy remains unclear.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
-什么时候先走 `intake`：
+## Complex Redesign
+
+```text
+$da-vinci use redesign-from-code to redesign this existing desktop product.
 
-- 桌面端架构较大
-- 模块和 workspace 边界不够清晰
-- 存在多个设计参考源或混合产品形态
+Existing code is the behavior source of truth, not the layout truth.
+Preserve current behavior, flows, integrations, and validation rules unless explicitly required otherwise.
+Inventory primary workspaces, side panels, inspectors, dialogs, settings flows, overlays, and materially different states before broad Pencil work.
+Decompose complex screens into primary surfaces, secondary surfaces, overlays, and implementation surfaces.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+Treat the resolved primary visual adapter as the first-pass design lead.
+Use Pencil guides only as workspace constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Do not pass design checkpoint if the result is a repeated placeholder scaffold, flat panel soup, or a recolor of the old desktop shell.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
 
-`intake` 版本：
+## Design-Only
 
 ```text
-$da-vinci use intake for this existing desktop product.
+$da-vinci use redesign-from-code to redesign this existing desktop product.
 
-I need to redesign the UI while preserving current behavior.
 Existing code is the behavior source of truth, not the layout truth.
-Inventory workspaces, panels, dialogs, overlays, settings flows, and important states.
-Decompose complex screens before Pencil work.
-Generate the best executable Da Vinci workflow prompt for the next step.
+Preserve current behavior, flows, and integrations.
+Inventory workspaces, side panels, dialogs, overlays, and important states.
+Decompose complex screens into real design surfaces before Pencil work.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+If the product is complex, design 1-3 anchor surfaces first, review screenshots, then expand.
+Stop after DA-VINCI.md, design-registry.md, page-map.md, proposal.md, specs, design.md, pencil-design.md, pencil-bindings.md, and tasks.md.
+Do not start code changes yet.
 ```
+
+## Continue
+
+```text
+$da-vinci use continue for this existing desktop-product redesign workflow.
+
+Use the existing Da Vinci artifacts in this project.
+Do not restart discovery unless an artifact is missing or clearly wrong.
+Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth.
+If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
+Continue into the next unfinished stage and do not stop at tasks.md when the active intent is full-delivery.
+```
+
+## 什么时候先走 Intake
+
+- workspace 边界还不清晰
+- 有多个真相源或混合产品形态
+- 第一条工作流提示词仍然很难一次说对

package/docs/zh-CN/prompt-presets/mobile-app.md

@@ -8,39 +8,85 @@
 
 适合这种需求：
 
-- app-first 的层级结构
-- touch-first 的交互界面
-- 强状态拆分
-- 明确处理 sheets、dialogs、tabs 和 nested navigation
+- touch-first 的层级和交互
+- 明确处理 tabs、dialogs、sheets 和 nested flows
+- 让状态拆分真正贴合 app 行为
 
-推荐提示词：
+## 如何选择
+
+- `Simple redesign` 适合界面较少、状态不爆炸、产品表面相对收敛的项目。
+- `Complex redesign` 适合多 activity、多 fragment、多 tabs、多 overlays、状态差异明显的项目。
+- `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
+- `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
+
+## Simple Redesign
 
 ```text
 $da-vinci use redesign-from-code to redesign this existing mobile app.
 
 Existing code is the behavior source of truth, not the layout truth.
 Preserve business logic, navigation, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
-Inventory routes, screens, tabs, dialogs, bottom sheets, nested flows, and important states before broad Pencil work.
-Decompose complex screens into subpages, overlays, materially different states, and implementation surfaces.
+Inventory the current screens and important states before Pencil work.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Do not pass design checkpoint if the result is a skin-swap of the old UI, a generic card grid, or a weak mobile hierarchy.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
-什么时候先走 `intake`：
+## Complex Redesign
 
-- 项目有多个真相源
-- UI 栈不清晰
-- 重设计跨度大，第一条提示词很难一次说对
+```text
+$da-vinci use redesign-from-code to redesign this existing mobile app.
 
-`intake` 版本：
+Existing code is the behavior source of truth, not the layout truth.
+Preserve business logic, navigation, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
+Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, overlays, and materially different states before broad Pencil work.
+Decompose complex screens into subpages, overlays, materially different states, and implementation surfaces.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+Treat the resolved primary visual adapter as the first-pass design lead.
+State the resolved primary visual adapter explicitly in the log and name any requested adapters that are unavailable.
+Before the first anchor surface, write a visual thesis, content plan, and interaction thesis.
+Use Pencil guides only as layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep non-`.pen` workflow artifacts out of `.da-vinci/designs/`.
+Define shared primitives from the approved anchor surfaces before broad page expansion.
+Do not pass design checkpoint if the result is a skin-swap of the old UI, a generic card grid, repeated placeholder templates, or weak visual anchors.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+## Design-Only
 
 ```text
-$da-vinci use intake for this existing mobile app.
+$da-vinci use redesign-from-code to redesign this existing mobile app.
 
-I need to redesign the UI while preserving current behavior.
 Existing code is the behavior source of truth, not the layout truth.
-Inventory screens, tabs, dialogs, bottom sheets, nested flows, and important states.
-Decompose complex screens before Pencil work.
-Generate the best executable Da Vinci workflow prompt for the next step.
+Preserve current behavior and navigation.
+Inventory screens, tabs, dialogs, bottom sheets, nested flows, overlays, and important states.
+Decompose complex screens into real design surfaces before Pencil work.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+If the app is complex, design 1-3 anchor surfaces first, review screenshots, then expand.
+Stop after DA-VINCI.md, design-registry.md, page-map.md, proposal.md, specs, design.md, pencil-design.md, pencil-bindings.md, and tasks.md.
+Do not start code changes yet.
 ```
+
+## Continue
+
+```text
+$da-vinci use continue for this existing mobile-app redesign workflow.
+
+Use the existing Da Vinci artifacts in this project.
+Do not restart discovery unless an artifact is missing or clearly wrong.
+Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth.
+If the redesign is complex, keep the anchor-first flow until the design checkpoint passes.
+Continue into the next unfinished stage and do not stop at tasks.md when the active intent is full-delivery.
+```
+
+## 什么时候先走 Intake
+
+- 项目有多个真相源
+- UI 栈还不清晰
+- 第一条工作流提示词仍然很难一次说对

package/docs/zh-CN/prompt-presets/tablet-app.md

@@ -10,37 +10,75 @@
 
 - split-pane 或 multi-column 构图
 - orientation-aware 的设计思路
-- 拆分工具区、侧边区域和 overlays
-- 同时考虑 touch-first 和 canvas-first 的交互
+- 明确拆分工具区、侧边区域和 overlays
 
-推荐提示词：
+## 如何选择
+
+- `Simple redesign` 适合表面不大、主要 flow 有限、只做轻量平板适配的项目。
+- `Complex redesign` 适合多列布局、方向切换、扩展 canvas、多 overlays、状态差异明显的项目。
+- `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
+- `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
+
+## Simple Redesign
 
 ```text
 $da-vinci use redesign-from-code to redesign this existing tablet product.
 
 Existing code is the behavior source of truth, not the layout truth.
-Preserve behavior, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
-Inventory split-pane regions, sidebars, expanded canvases, dialogs, sheets, orientation-driven changes, and important states before broad Pencil work.
-Decompose complex pages into multi-region surfaces, overlays, materially different states, and implementation surfaces.
+Preserve current behavior, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
+Inventory the current tablet surfaces and important states before Pencil work.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Do not pass design checkpoint if the result ignores tablet-scale composition or collapses into a stretched phone layout.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
-什么时候先走 `intake`：
+## Complex Redesign
+
+```text
+$da-vinci use redesign-from-code to redesign this existing tablet product.
 
-- 产品同时有 phone 和 tablet surface
-- orientation 或 multi-pane 逻辑很复杂
-- 设计参考与真实实现 surface 对不上
+Existing code is the behavior source of truth, not the layout truth.
+Preserve current behavior, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
+Inventory split-pane regions, sidebars, expanded canvases, dialogs, sheets, orientation-driven changes, and materially different states before broad Pencil work.
+Decompose complex pages into multi-region surfaces, overlays, materially different states, and implementation surfaces.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+Treat the resolved primary visual adapter as the first-pass design lead.
+Use Pencil guides only as tablet-layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Do not pass design checkpoint if the result collapses into a stretched phone layout, repeated placeholders, or weak multi-region hierarchy.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
 
-`intake` 版本：
+## Design-Only
 
 ```text
-$da-vinci use intake for this existing tablet product.
+$da-vinci use redesign-from-code to redesign this existing tablet product.
 
-I need to redesign the UI while preserving current behavior.
 Existing code is the behavior source of truth, not the layout truth.
+Preserve current behavior, permissions, integrations, and state transitions.
 Inventory split-pane regions, sidebars, dialogs, sheets, orientation changes, and important states.
-Decompose complex pages before Pencil work.
-Generate the best executable Da Vinci workflow prompt for the next step.
+Decompose complex pages into real design surfaces before Pencil work.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+If the product is complex, design 1-3 anchor surfaces first, review screenshots, then expand.
+Stop after DA-VINCI.md, design-registry.md, page-map.md, proposal.md, specs, design.md, pencil-design.md, pencil-bindings.md, and tasks.md.
+Do not start code changes yet.
+```
+
+## Continue
+
+```text
+$da-vinci use continue for this existing tablet-product redesign workflow.
+
+Use the existing Da Vinci artifacts in this project.
+Do not restart discovery unless an artifact is missing or clearly wrong.
+Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth.
+If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
+Continue into the next unfinished stage and do not stop at tasks.md when the active intent is full-delivery.
 ```
+
+## 什么时候先走 Intake
+
+- 产品同时混合了 phone 和 tablet surface
+- orientation 或 multi-pane 行为让第一条请求更复杂
+- 第一条工作流提示词仍然很难一次说对