@xenonbyte/da-vinci-workflow 0.1.10 → 0.1.12

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

@@ -0,0 +1,84 @@
+# Tablet App Prompt Preset
+
+Recommended when the product is tablet-first or relies on expanded touch surfaces.
+
+Pair with:
+
+- `docs/visual-assist-presets/tablet-app.md`
+
+Use this when the workflow needs:
+
+- split-pane or multi-column composition
+- orientation-aware design thinking
+- clear decomposition of tool regions, side regions, and overlays
+
+## How To Choose
+
+- Use `Simple redesign` when the tablet surface is limited, mostly single-flow, or only lightly adapted from a phone layout.
+- Use `Complex redesign` when the product has split panes, orientation changes, expanded canvases, overlays, or many materially different surfaces.
+- Use `Design-only` when you want the design chain and bindings but no code changes yet.
+- Use `Continue` when the workflow already created artifacts and needs to resume.
+
+## 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 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/.
+```
+
+## Complex 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 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/.
+```
+
+## Design-Only
+
+```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 current behavior, permissions, integrations, and state transitions.
+Inventory split-pane regions, sidebars, dialogs, sheets, orientation changes, and important states.
+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.
+```
+
+## When To Switch To Intake First
+
+- the product mixes phone and tablet surfaces
+- orientation or multi-pane behavior complicates the first workflow request
+- the first prompt is still hard to phrase cleanly

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

@@ -0,0 +1,85 @@
+# Web App Prompt Preset
+
+Recommended when the product is a browser-based application or a web product with app-like surfaces.
+
+Pair with:
+
+- `docs/visual-assist-presets/web-app.md`
+
+Use this when the workflow needs:
+
+- responsive hierarchy
+- separation between marketing and product surfaces
+- careful treatment of empty, loading, error, and authenticated states
+
+## 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 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/.
+```
+
+## Complex 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 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 redesign-from-code to redesign this existing web product.
+
+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 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

@@ -202,9 +202,18 @@ 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`
 - 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
+- use screenshot review on each anchor surface before cloning variants or expanding the rest of the product
+- 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 +243,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

@@ -9,12 +9,17 @@ Each preset is intentionally conservative:
 - clear scope boundaries
 - non-blocking behavior by default
 
+Use them together with:
+
+- `docs/prompt-presets/`
+
 If the project is design-critical or previous outputs were weak, generic, or too close to the old UI:
 
 - keep the same preset family
 - 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:
 
@@ -29,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`
 
@@ -80,9 +81,10 @@ Expected flow:
 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. bind routes and pages to Pencil screens
-9. generate tasks aligned to the redesign slices
-10. build and verify
+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
 
 ### Complex Android example
 
@@ -92,6 +94,9 @@ $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.
+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 just a skin-swap of the old UI.
 ```
 

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

@@ -70,6 +70,17 @@ $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

@@ -86,10 +86,11 @@ Da Vinci 应该：
 4. 生成 `specs/<capability>/spec.md`
 5. 生成 `page-map.md`
 6. 生成 `design-registry.md`
+   - 先解析出工作流自动维护的项目内 `.pen` 路径
    - 优先登记 `.da-vinci/designs/` 下的本地 `.pen` 路径
 7. 生成 `design.md`
 8. 生成 `pencil-design.md`
-   - 在可行时把当前 `.pen` 文件保存或导出到 `.da-vinci/designs/`
+   - 确保当前设计真正落到登记好的 `.da-vinci/designs/` 路径
 9. 生成 `pencil-bindings.md`
 10. 生成 `tasks.md`
 11. 进入实现
@@ -110,7 +111,7 @@ Da Vinci 应该：
 5. 生成 `specs/<capability>/spec.md`
 6. 生成 `page-map.md`
 7. 继续到设计、绑定、任务和实现
-   - 在可行时把当前 `.pen` 文件保存或导出到 `.da-vinci/designs/`
+   - 把当前设计真正落到登记好的 `.da-vinci/designs/` 路径
 
 ## 3. `redesign-from-code`
 
@@ -126,13 +127,16 @@ Da Vinci 应该：
 2. 生成或对齐 `DA-VINCI.md`
 3. 生成 `design-registry.md`
    - 如已有本地 `.pen` 文件，优先登记 `.da-vinci/designs/` 下的路径
+   - 为这次重设计解析一个工作流自动维护的项目内 `.pen` 路径
 4. 生成 `proposal.md`
 5. 按 redesign slice 拆分 `specs/`
 6. 重建或更新 `page-map.md`
    - 把复杂页面拆成 subpage、state、overlay、fragment surface
 7. 生成 `design.md`
 8. 生成 `pencil-design.md`
-   - 在可行时把新的 Pencil 基线持久化到 `.da-vinci/designs/`
+   - 先做 1 到 3 个 anchor surface，再扩展更多页面
+   - 首轮设计由解析出来的主 visual adapter 主导
+   - 把新的 Pencil 基线真正落到登记好的 `.da-vinci/designs/` 路径
 9. 生成 `pencil-bindings.md`
 10. 生成 `tasks.md`
 11. 进入实现
@@ -142,7 +146,14 @@ Da Vinci 应该：
 - 现有代码决定 behavior，不决定新的视觉布局
 - `redesign-from-code` 默认应该基于页面职责和状态重新构图
 - 不能把“旧页面换个配色、换点间距、挪一点位置”当成真正的重设计
+- 一旦配置了 `Preferred adapters`，解析出来的主 adapter 应该主导首轮设计，而不是只登记不使用
+- 不要让 Pencil 的 guide 或样式模板取代主 adapter 成为设计方向来源
+- 不要一上来就批量搭很多空 screen
+- 对复杂产品，先把 1 到 3 个 anchor surface 做到通过截图审查，再扩展其他页面
 - 一个实现页如果包含多个 Fragment、多个 tab、多个状态或多个 overlay，应该拆成多个设计 surface
+- `design-registry.md` 里的首选 `.pen` 路径由工作流自动维护，不应该依赖用户手工填写
+- 不要因为当前 Pencil 里正好打开了一个文档，就直接在那个文档上继续做重设计
+- 如果 Pencil MCP 没有自动把登记路径的 `.pen` 文件落到磁盘，就应该先补写这个项目内文件，再把 mapping 或 implementation 视为完成
 
 ## 4. `feature-change`
 
@@ -158,7 +169,7 @@ Da Vinci 应该：
 4. 复用或更新 `design-registry.md`
    - 如果已有项目内 `.pen` 文件，优先登记 `.da-vinci/designs/` 下的路径
 5. 生成 `pencil-design.md` 增量
-   - 在可行时把更新后的 `.pen` 文件保存或导出到 `.da-vinci/designs/`
+   - 把更新后的 `.pen` 文件真正落到登记好的 `.da-vinci/designs/` 路径
 6. 更新 `pencil-bindings.md`
 7. 生成 `tasks.md`
 8. 进入实现

package/docs/zh-CN/prompt-entrypoints.md

@@ -77,6 +77,10 @@
 
 ## 平台语法
 
+如果你只想直接复制不同场景的起始提示词，也可以看：
+
+- `docs/zh-CN/prompt-presets/`
+
 ### Codex
 
 ```text

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

@@ -0,0 +1,35 @@
+# 场景提示词模板
+
+这些模板用于在不同产品形态下，快速拿到可直接执行的起始提示词。
+
+它们建议和下面这组文档配合使用：
+
+- `docs/zh-CN/visual-assist-presets/`
+
+推荐使用方式：
+
+1. 先选最接近产品形态的提示词模板
+2. 再选对应的 `Visual Assist` 模板
+3. 再选和项目复杂度、交付意图匹配的提示词版本
+4. 两者一起放进工作流设置
+5. 只有在项目存在特殊真相源或平台约束时，再继续收紧提示词
+
+可用模板：
+
+- `mobile-app.md`
+- `desktop-app.md`
+- `web-app.md`
+- `tablet-app.md`
+
+设计规则：
+
+- 提示词模板负责定义工作流意图、拆分规则和真相源处理方式
+- `Visual Assist` 模板负责定义 UI 设计增强偏好
+- 两者一起使用，结果通常更稳
+
+现在每个场景模板里都固定包含：
+
+- `Simple redesign`
+- `Complex redesign`
+- `Design-only`
+- `Continue`

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

@@ -0,0 +1,84 @@
+# 桌面端应用提示词模板
+
+适用于桌面优先的工具型或工作台型产品。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/desktop-app.md`
+
+适合这种需求：
+
+- 高密度工作区层级
+- 明确的主工作面和次级面板
+- 克制的 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 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 workspace hierarchy remains unclear.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+## Complex 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 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/.
+```
+
+## Design-Only
+
+```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 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

@@ -0,0 +1,84 @@
+# 移动端 App 提示词模板
+
+适用于以手机为主的产品界面。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/mobile-app.md`
+
+适合这种需求：
+
+- 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 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/.
+```
+
+## Complex 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 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.
+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.
+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 redesign-from-code to redesign this existing mobile app.
+
+Existing code is the behavior source of truth, not the layout truth.
+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

@@ -0,0 +1,84 @@
+# 平板应用提示词模板
+
+适用于平板优先，或强依赖扩展触控区域的产品。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/tablet-app.md`
+
+适合这种需求：
+
+- split-pane 或 multi-column 构图
+- orientation-aware 的设计思路
+- 明确拆分工具区、侧边区域和 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 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/.
+```
+
+## Complex 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 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/.
+```
+
+## Design-Only
+
+```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 current behavior, permissions, integrations, and state transitions.
+Inventory split-pane regions, sidebars, dialogs, sheets, orientation changes, and important states.
+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 行为让第一条请求更复杂
+- 第一条工作流提示词仍然很难一次说对