@xenonbyte/da-vinci-workflow 0.1.9 → 0.1.11

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

@@ -0,0 +1,46 @@
+# Desktop App Prompt Preset
+
+Recommended when the product is a desktop-first tool or workspace.
+
+Pair with:
+
+- `docs/visual-assist-presets/desktop-app.md`
+
+Use this when the workflow needs:
+
+- dense workspace hierarchy
+- clear tool panels and primary working surfaces
+- disciplined modal and secondary-panel treatment
+- decomposition of complex screens into meaningful surfaces
+
+Recommended prompt:
+
+```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.
+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.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+When to switch to `intake` first:
+
+- the desktop architecture is large
+- modules and workspace boundaries are unclear
+- there are multiple existing design references or mixed product surfaces
+
+`intake` variant:
+
+```text
+$da-vinci use intake for 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.
+```

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

@@ -0,0 +1,46 @@
+# Mobile App Prompt Preset
+
+Recommended when the project is a phone-first product surface.
+
+Pair with:
+
+- `docs/visual-assist-presets/mobile-app.md`
+
+Use this when the workflow needs:
+
+- app-first hierarchy
+- touch-first interaction surfaces
+- strong state decomposition
+- clear treatment of sheets, dialogs, tabs, and nested navigation
+
+Recommended prompt:
+
+```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.
+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/.
+```
+
+When to switch to `intake` first:
+
+- the project has multiple truth sources
+- the UI stack is unclear
+- the redesign spans many modules and the first workflow prompt is hard to phrase
+
+`intake` variant:
+
+```text
+$da-vinci use intake for 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.
+```

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

@@ -0,0 +1,46 @@
+# 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
+- decomposition of tool surfaces, side regions, and overlays
+- treatment of both touch-first and canvas-first interaction patterns
+
+Recommended prompt:
+
+```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.
+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/.
+```
+
+When to switch to `intake` first:
+
+- the product has both phone and tablet surfaces
+- orientation or multi-pane logic is complicated
+- the design references do not map cleanly to the real implementation surfaces
+
+`intake` variant:
+
+```text
+$da-vinci use intake for 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.
+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.
+```

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

@@ -0,0 +1,47 @@
+# Web App Prompt Preset
+
+Recommended when the product is a browser-based application or product website with app-like surfaces.
+
+Pair with:
+
+- `docs/visual-assist-presets/web-app.md`
+
+Use this when the workflow needs:
+
+- responsive page 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
+
+Recommended prompt:
+
+```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.
+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:
+
+- 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
+
+`intake` variant:
+
+```text
+$da-vinci use intake for 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.
+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.
+```

package/docs/visual-adapters.md

@@ -28,6 +28,15 @@ Those still come from requirements, existing code, `page-map.md`, and `pencil-bi
 
 Configure visual-adapter preferences inside `DA-VINCI.md`.
 
+Start from one of these two setups:
+
+- balanced default
+  - keep delivery non-blocking
+  - better for most app and dashboard work
+- quality-first redesign
+  - raise the visual bar
+  - better when prior outputs were generic, ugly, or too close to the old UI
+
 Recommended shape:
 
 ```md
@@ -49,6 +58,56 @@ Recommended shape:
 
 Use `Require Adapter: true` only when the workflow must stop if the preferred adapter is unavailable locally.
 
+## Quick-Start Configurations
+
+Balanced default:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - ui-ux-pro-max
+  - frontend-skill
+- Scope:
+  - visual contract refinement
+  - page composition
+  - hierarchy and spacing
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - false
+```
+
+Use this when:
+
+- the project is an app, dashboard, desktop tool, or dense product surface
+- you want stronger layout discipline but still want the workflow to continue without a local helper
+
+Quality-first redesign:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - frontend-skill
+  - ui-ux-pro-max
+- Scope:
+  - visual contract refinement
+  - page composition
+  - hierarchy and spacing
+  - motion guidance
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - true
+```
+
+Use this when:
+
+- the project is design-sensitive or premium-facing
+- the previous redesign attempt produced generic card grids, weak anchors, or a skin-swap of the old UI
+- you would rather stop than silently continue without a strong local design helper
+
 ## What Each Field Means
 
 Use the fields like this:
@@ -75,6 +134,27 @@ Recommended default:
 - use `Fallback: native-da-vinci`
 - keep `Scope` narrowly focused on visual-quality decisions
 
+Adapter-selection rule of thumb:
+
+- `ui-ux-pro-max` first for dense app, dashboard, and admin surfaces when the visual bar is moderate
+- `frontend-skill` first when art direction, composition quality, and visual restraint matter more than speed or density tuning
+
+## When The Output Still Looks Weak
+
+If the workflow is functionally correct but the Pencil result still looks generic or ugly:
+
+- move `frontend-skill` to the front of `Preferred adapters`
+- set a stronger visual direction in `DA-VINCI.md` instead of leaving it broad
+- treat `Require Adapter: true` as acceptable for design-critical work where plain fallback quality is not good enough
+- tighten the `Scope` toward composition, hierarchy, and Pencil refinement rather than vague style language
+- use the design checkpoint to block generic card mosaics, weak anchors, and decorative clutter
+
+For `redesign-from-code`, also do this:
+
+- restate that existing code is behavior truth, not layout truth
+- decompose complex activities, fragments, tabs, overlays, and materially different states before broad Pencil work
+- explicitly require fresh composition instead of recoloring or slightly rearranging the old UI
+
 ## Resolution Order
 
 Resolve adapters in this order:
@@ -163,6 +243,8 @@ Persist project-local Pencil files under .da-vinci/designs/.
 - `native-da-vinci`
   - use when no adapter is available or when the project only needs the built-in workflow rules
 
+If the output quality bar is especially high, promote `frontend-skill` to the first slot even for app surfaces and use `native-da-vinci` only as a fallback.
+
 ## Scenario Presets
 
 Ready-to-copy presets live here:

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

@@ -9,6 +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
+
 Available presets:
 
 - `mobile-app.md`

package/docs/visual-assist-presets/desktop-app.md

@@ -33,3 +33,4 @@ Notes:
 - prefer `ui-ux-pro-max` first for dense app layout decisions
 - keep section hierarchy stronger than decorative treatment
 - use `frontend-skill` only as a secondary visual-quality helper, not as a marketing-style override
+- if the result looks flat, over-boxed, or too generic, move `frontend-skill` to the first slot and raise the design checkpoint bar

package/docs/visual-assist-presets/mobile-app.md

@@ -33,3 +33,4 @@ Notes:
 - prefer `ui-ux-pro-max` first for app-surface density and control balance
 - keep motion guidance light and purposeful
 - do not let the adapter turn routine mobile product UI into a marketing page
+- if the output keeps collapsing into generic cards or weak hierarchy, move `frontend-skill` to the first slot and consider `Require Adapter: true`

package/docs/visual-assist-presets/tablet-app.md

@@ -33,3 +33,4 @@ Notes:
 - keep spacing more generous than desktop but more structured than phone UI
 - use adapter guidance to improve split layouts, canvases, and workspace balance
 - avoid over-compressing content into phone-like stacking
+- if the result still feels bland or over-framed, move `frontend-skill` to the first slot and require a stronger visual thesis before Pencil work

package/docs/visual-assist-presets/web-app.md

@@ -33,3 +33,4 @@ Notes:
 - keep `ui-ux-pro-max` first for product surfaces, dashboards, and operational UI
 - if the project is more brand-led than tool-led, swap the order and put `frontend-skill` first
 - do not let responsive polish erase product clarity
+- if the output feels like generic SaaS filler, switch `frontend-skill` to first and tighten the visual direction in `DA-VINCI.md`

package/docs/workflow-examples.md

@@ -78,11 +78,23 @@ Expected flow:
 3. register current `.pen` sources and visual-adapter resolution in `design-registry.md`
 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`
-7. create new or updated Pencil pages, 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
+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
+
+### Complex Android example
+
+```text
+$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.
+Do not pass design checkpoint if the result is just a skin-swap of the old UI.
+```
 
 ## 4. `feature-change`
 

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

@@ -70,6 +70,10 @@ $da-vinci use <mode> to <goal>
 
 ## 场景模板
 
+如果你想直接按产品形态选提示词，也可以看：
+
+- `docs/zh-CN/prompt-presets/`
+
 ### 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,16 +127,28 @@ 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/`
+   - 把新的 Pencil 基线真正落到登记好的 `.da-vinci/designs/` 路径
 9. 生成 `pencil-bindings.md`
 10. 生成 `tasks.md`
 11. 进入实现
 
+关键规则：
+
+- 现有代码决定 behavior，不决定新的视觉布局
+- `redesign-from-code` 默认应该基于页面职责和状态重新构图
+- 不能把“旧页面换个配色、换点间距、挪一点位置”当成真正的重设计
+- 一个实现页如果包含多个 Fragment、多个 tab、多个状态或多个 overlay，应该拆成多个设计 surface
+- `design-registry.md` 里的首选 `.pen` 路径由工作流自动维护，不应该依赖用户手工填写
+- 不要因为当前 Pencil 里正好打开了一个文档，就直接在那个文档上继续做重设计
+- 如果 Pencil MCP 没有自动把登记路径的 `.pen` 文件落到磁盘，就应该先补写这个项目内文件，再把 mapping 或 implementation 视为完成
+
 ## 4. `feature-change`
 
 适合：
@@ -150,7 +163,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,27 @@
+# 场景提示词模板
+
+这些模板用于在不同产品形态下，快速拿到可直接执行的起始提示词。
+
+它们建议和下面这组文档配合使用：
+
+- `docs/zh-CN/visual-assist-presets/`
+
+推荐使用方式：
+
+1. 先选最接近产品形态的提示词模板
+2. 再选对应的 `Visual Assist` 模板
+3. 两者一起放进工作流设置
+4. 只有在项目存在特殊真相源或平台约束时，再继续收紧提示词
+
+可用模板：
+
+- `mobile-app.md`
+- `desktop-app.md`
+- `web-app.md`
+- `tablet-app.md`
+
+设计规则：
+
+- 提示词模板负责定义工作流意图、拆分规则和真相源处理方式
+- `Visual Assist` 模板负责定义 UI 设计增强偏好
+- 两者一起使用，结果通常更稳

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

@@ -0,0 +1,46 @@
+# 桌面端应用提示词模板
+
+适用于桌面优先的工具型或工作台型产品。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/desktop-app.md`
+
+适合这种需求：
+
+- 高密度工作区层级
+- 明确的工具面板和主工作面
+- 克制的 modal 和 secondary panel 处理
+- 把复杂页面拆成真正有意义的 surface
+
+推荐提示词：
+
+```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.
+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.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+什么时候先走 `intake`：
+
+- 桌面端架构较大
+- 模块和 workspace 边界不够清晰
+- 存在多个设计参考源或混合产品形态
+
+`intake` 版本：
+
+```text
+$da-vinci use intake for 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.
+```

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

@@ -0,0 +1,46 @@
+# 移动端 App 提示词模板
+
+适用于以手机为主的产品界面。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/mobile-app.md`
+
+适合这种需求：
+
+- app-first 的层级结构
+- touch-first 的交互界面
+- 强状态拆分
+- 明确处理 sheets、dialogs、tabs 和 nested navigation
+
+推荐提示词：
+
+```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.
+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`：
+
+- 项目有多个真相源
+- UI 栈不清晰
+- 重设计跨度大，第一条提示词很难一次说对
+
+`intake` 版本：
+
+```text
+$da-vinci use intake for 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.
+```

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

@@ -0,0 +1,46 @@
+# 平板应用提示词模板
+
+适用于平板优先，或强依赖扩展触控区域的产品。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/tablet-app.md`
+
+适合这种需求：
+
+- split-pane 或 multi-column 构图
+- orientation-aware 的设计思路
+- 拆分工具区、侧边区域和 overlays
+- 同时考虑 touch-first 和 canvas-first 的交互
+
+推荐提示词：
+
+```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.
+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`：
+
+- 产品同时有 phone 和 tablet surface
+- orientation 或 multi-pane 逻辑很复杂
+- 设计参考与真实实现 surface 对不上
+
+`intake` 版本：
+
+```text
+$da-vinci use intake for 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.
+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.
+```

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

@@ -0,0 +1,47 @@
+# Web 应用提示词模板
+
+适用于浏览器中的产品型界面，或带有 app surface 的 Web 产品。
+
+建议搭配：
+
+- `docs/zh-CN/visual-assist-presets/web-app.md`
+
+适合这种需求：
+
+- responsive 页面层级
+- marketing 与 product surface 的区分
+- 明确处理 empty、loading、error、authenticated states
+- 把复杂流程拆成真实的设计 surface，而不是一个大页面
+
+推荐提示词：
+
+```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.
+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/.
+```
+
+什么时候先走 `intake`：
+
+- 同时混合 marketing、auth、onboarding 和 app surfaces
+- 第一条提示词很难一次说清
+- 存在外部设计参考，但它们必须服从现有行为真相
+
+`intake` 版本：
+
+```text
+$da-vinci use intake for 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.
+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.
+```