@xenonbyte/da-vinci-workflow 0.1.11 → 0.1.12

package/CHANGELOG.md

@@ -4,6 +4,14 @@
 
 - No unreleased changes yet.
 
+## v0.1.12 - 2026-03-27
+
+### Changed
+- visual-adapter resolution now documents that the resolved primary adapter must actively lead the first design pass instead of being recorded only for traceability
+- complex redesign guidance now requires anchor-first Pencil generation: design 1-3 anchor surfaces, review screenshots, then expand the rest of the product
+- design-checkpoint guidance now explicitly blocks placeholder-heavy repeated scaffolds and broad multi-screen generation that starts before anchor surfaces are compositionally stable
+- prompt presets for mobile, desktop, web, and tablet surfaces now include `Simple redesign`, `Complex redesign`, `Design-only`, and `Continue` variants in both English and Chinese
+
 ## v0.1.11 - 2026-03-27
 
 ### Changed

package/README.md

@@ -27,10 +27,14 @@ This workflow is intended for:
 
 Latest published npm package:
 
-- `@xenonbyte/da-vinci-workflow@0.1.10`
+- `@xenonbyte/da-vinci-workflow@0.1.12`
 
 Release highlights:
 
+- visual-adapter resolution now requires the resolved primary adapter to actively lead the first design pass
+- complex redesigns now default to anchor-first Pencil generation: design 1-3 anchor surfaces, review screenshots, then expand
+- design checkpoint now explicitly blocks placeholder-heavy repeated scaffolds and premature broad multi-screen generation
+- prompt presets for mobile, desktop, web, and tablet now include `Simple redesign`, `Complex redesign`, `Design-only`, and `Continue` variants
 - `redesign-from-code` now states explicitly that existing code is behavior truth, not layout truth
 - complex pages are now expected to decompose into subpages, overlays, materially different states, and implementation surfaces before broad Pencil redesign
 - design-checkpoint guidance now explicitly blocks skin-swap redesigns, generic card mosaics, weak visual anchors, and decorative clutter
@@ -147,6 +151,9 @@ Selection rules:
 
 - keep `ui-ux-pro-max` first for dense app and dashboard surfaces when the visual bar is moderate
 - move `frontend-skill` to the first slot when art direction, composition quality, and premium visual hierarchy matter more
+- when `Preferred adapters` are configured, the resolved primary adapter should actively lead the first design pass instead of being recorded only for traceability
+- use Pencil guides as platform/buildability constraints, not as the main art-direction source
+- on complex redesigns, design 1-3 anchor surfaces first and review screenshots before broad multi-screen generation
 - keep `Fallback: native-da-vinci` unless you explicitly want missing adapters to block the workflow
 - keep `Require Adapter: false` by default and raise it to `true` only for design-critical work
 - keep `Scope` limited to presentation quality; do not use it to delegate behavior, routes, or state truth
@@ -515,6 +522,7 @@ See:
 
 - `docs/prompt-entrypoints.md`
 - `docs/prompt-presets/`
+  - includes `Simple redesign`, `Complex redesign`, `Design-only`, and `Continue` variants in each surface file
 - `docs/codex-natural-language-usage.md`
 - `docs/visual-adapters.md`
 - `docs/visual-assist-presets/`
@@ -527,6 +535,7 @@ Chinese companion documents are included in this repository:
 
 - `README.zh-CN.md`
 - `docs/zh-CN/prompt-presets/`
+  - each surface file also includes `Simple redesign`, `Complex redesign`, `Design-only`, and `Continue`
 - `docs/zh-CN/visual-adapters.md`
 - `docs/zh-CN/visual-assist-presets/`
 - `docs/zh-CN/`

package/README.zh-CN.md

@@ -29,10 +29,14 @@ Da Vinci 是一个把产品需求一路推进到结构化规格、Pencil 设计
 
 最新已发布 npm 包：
 
-- `@xenonbyte/da-vinci-workflow@0.1.10`
+- `@xenonbyte/da-vinci-workflow@0.1.12`
 
 已发布版本重点：
 
+- visual adapter 解析现在要求“解析出来的主 adapter 必须真正主导首轮设计”，而不是只登记在工件里
+- 复杂重设计现在默认采用 anchor-first 的 Pencil 生成策略：先做 1 到 3 个 anchor surface，截图审查后再扩展
+- design checkpoint 现在会明确拦截大量空占位、重复模板和过早的大批量多页面脚手架
+- 移动端、桌面端、Web、平板的提示词模板现在都包含 `Simple redesign`、`Complex redesign`、`Design-only`、`Continue`
 - `redesign-from-code` 现在明确写清：现有代码只是真相行为，不是真相布局
 - 复杂页面现在明确要求在大规模 Pencil 重设计前拆成 subpage、overlay、明显不同 state 和 implementation surface
 - design checkpoint 现在明确会拦截旧 UI 换皮、通用卡片拼贴、弱视觉锚点和装饰性噪音
@@ -152,6 +156,9 @@ Da Vinci V2 支持四种模式：
 
 - 高密度 app、dashboard、工具型界面，且视觉要求中等时，优先把 `ui-ux-pro-max` 放第一位
 - 如果更重视 art direction、构图和高级感，就把 `frontend-skill` 放第一位
+- 一旦配置了 `Preferred adapters`，解析出来的主 adapter 应该真正主导首轮设计，而不是只登记在工件里
+- Pencil 的 guide 只应该约束平台布局和可实现性，不应该替代主 adapter 成为设计方向来源
+- 面对复杂重设计时，先做 1 到 3 个 anchor surface，并完成截图审查，再扩展到更多页面
 - 默认保留 `Fallback: native-da-vinci`
 - `Require Adapter` 默认保持 `false`，只有设计要求很高时再改成 `true`
 - `Scope` 只管 presentation 质量，不要拿它去定义 behavior、route 或 state truth
@@ -428,6 +435,7 @@ Continue into full-delivery.
 - `docs/codex-natural-language-usage.md`
 - `docs/prompt-entrypoints.md`
 - `docs/prompt-presets/`
+  - 每个场景文件都包含 `Simple redesign`、`Complex redesign`、`Design-only`、`Continue`
 - `docs/visual-adapters.md`
 - `docs/visual-assist-presets/`
 - `docs/workflow-examples.md`
@@ -438,6 +446,7 @@ Continue into full-delivery.
 
 - `README.zh-CN.md`
 - `docs/zh-CN/prompt-presets/`
+  - 每个场景文件也都包含 `Simple redesign`、`Complex redesign`、`Design-only`、`Continue`
 - `docs/zh-CN/visual-adapters.md`
 - `docs/zh-CN/visual-assist-presets/`
 - `docs/zh-CN/`

package/SKILL.md

@@ -185,7 +185,9 @@ Do not repeatedly ask for inputs that are already stable in the artifacts.
 Treat visual adapters as optional design-assist layers.
 
 - resolve them from the user request first, then `DA-VINCI.md`, then locally available skills
+- when `DA-VINCI.md` or the request declares `Preferred adapters`, the resolved primary adapter must actively lead first-pass design reasoning instead of being recorded only for traceability
 - use them to improve visual contract quality, composition, hierarchy, spacing, and motion guidance
+- use Pencil guides and platform constraints as buildability aids only; they must not replace the resolved primary adapter as the art-direction source
 - do not let them redefine behavior, page truth, route truth, or acceptance rules
 - if a requested adapter is unavailable locally, continue with native Da Vinci design rules and record the fallback
 
@@ -474,6 +476,8 @@ When visual adapters are requested:
 - resolve them from local availability when possible
 - choose one primary adapter when multiple helpers are available
 - record the requested adapters, resolved primary adapter, any secondary helpers, and fallback status in `design-registry.md`
+- treat the resolved primary adapter as the design lead for the first Pencil pass, especially on anchor screens and quality-critical surfaces
+- if `Require Adapter: true` and the requested adapter is unavailable, treat that as a blocker instead of silently downgrading the visual bar
 - continue with native Da Vinci design rules when no adapter is available unless the user explicitly requires a specific adapter
 
 If the request is too vague to design or implement safely, ask a short clarification question before generating artifacts.
@@ -517,16 +521,21 @@ When creating or editing Pencil designs:
 - use the workflow-owned `.pen` path from `design-registry.md` as the active design target
 - do not keep designing in whichever Pencil document happens to be open unless it already matches the registered project-local path
 - use the resolved visual adapter, when available, for composition, hierarchy, restraint, and motion guidance
+- on complex redesigns, design only 1-3 anchor surfaces first before broad multi-screen generation
+- make each anchor surface fully composed with real hierarchy and content structure before expanding the rest of the product
 - before broad page generation, write a visual thesis, a content plan, and an interaction thesis for the current surface
+- use screenshot review after each anchor surface and revise before cloning or expanding variants
 - Keep page names, section names, and labels aligned with the specs
 - Make important states explicit when they change implementation: empty, loading, success, error, restricted, unavailable
 - Prefer layout clarity and information hierarchy over decorative complexity
 - Reject generic UI patterns such as dashboard-card mosaics, weak visual anchors, decorative clutter, or motion with no hierarchy value
+- reject placeholder-heavy scaffolds; unresolved placeholder rectangles are not acceptable substitutes for real screen composition
 - For `redesign-from-code`, redesign from page responsibilities and state decomposition, not by recoloring or slightly rearranging the old UI
 - After changes, inspect the result visually before treating it as implementation-ready
 
 When multiple pages exist:
 
+- derive the remaining pages from approved anchor surfaces and shared primitives rather than from an empty repeated template
 - keep one canonical Pencil page or screen per implementation page
 - record the `.pen` file in `design-registry.md`
 - record the mapping in `pencil-bindings.md`

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

@@ -73,6 +73,13 @@ For surface-specific prompt starting points, also see:
 
 - `docs/prompt-presets/`
 
+Each surface file includes:
+
+- `Simple redesign`
+- `Complex redesign`
+- `Design-only`
+- `Continue`
+
 ### 1. New project with clear requirements
 
 ```text

package/docs/mode-use-cases.md

@@ -324,6 +324,8 @@ Register the design sources, extract DA-VINCI.md from them, bind covered pages,
 
 6. create or update `pencil-design.md`
    - build the new redesign baseline in Pencil
+   - design 1-3 anchor surfaces first before broad multi-screen expansion
+   - let the resolved primary visual adapter lead that first pass
    - persist that baseline into the registered `.da-vinci/designs/` file
 
 7. create or update `pencil-bindings.md`
@@ -339,6 +341,11 @@ Register the design sources, extract DA-VINCI.md from them, bind covered pages,
 
 ### Critical rule in this mode
 
+- treat the resolved primary visual adapter as the first-pass design lead when `Preferred adapters` are configured
+- do not let Pencil guides or generic style packs replace that adapter as the art-direction source
+- do not start broad redesign work by scaffolding many empty screens
+- for complex products, get 1-3 anchor surfaces through screenshot review before expanding the rest of the redesign
+
 For redesign work:
 
 - current code decides behavior

package/docs/prompt-presets/README.md

@@ -10,8 +10,9 @@ Recommended flow:
 
 1. choose the prompt preset closest to the product surface
 2. choose the matching `Visual Assist` preset
-3. copy both into your workflow setup
-4. tighten the prompt further only when the project has unusual truth sources or platform constraints
+3. choose the prompt variant that matches project complexity and delivery intent
+4. copy both into your workflow setup
+5. tighten the prompt further only when the project has unusual truth sources or platform constraints
 
 Available presets:
 
@@ -25,3 +26,10 @@ Design rule:
 - prompt presets define workflow intent, decomposition rules, and truth-source handling
 - visual-assist presets define UI-design helper preferences
 - use both together for the strongest result
+
+Each scene preset should now include:
+
+- `Simple redesign`
+- `Complex redesign`
+- `Design-only`
+- `Continue`

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

@@ -9,38 +9,76 @@ Pair with:
 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
+- clear primary and secondary working regions
+- disciplined panel, dialog, and inspector treatment
 
-Recommended prompt:
+## How To Choose
+
+- Use `Simple redesign` when the desktop surface is narrow, mostly single-workspace, or has limited state branching.
+- Use `Complex redesign` when the product has multiple workspaces, side panels, overlays, inspectors, or materially different states.
+- Use `Design-only` when you want the design chain and task readiness without 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 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/.
 ```
 
-When to switch to `intake` first:
+## Complex Redesign
+
+```text
+$da-vinci use redesign-from-code to redesign this existing desktop product.
 
-- the desktop architecture is large
-- modules and workspace boundaries are unclear
-- there are multiple existing design references or mixed product surfaces
+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` variant:
+## 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.
+```
+
+## When To Switch To Intake First
+
+- workspace boundaries are unclear
+- there are multiple truth sources or mixed product surfaces
+- the first workflow prompt is still hard to phrase cleanly

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

@@ -1,6 +1,6 @@
 # Mobile App Prompt Preset
 
-Recommended when the project is a phone-first product surface.
+Recommended when the product surface is a phone-first app.
 
 Pair with:
 
@@ -8,39 +8,77 @@ Pair with:
 
 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
+- touch-first hierarchy
+- clear handling of tabs, sheets, dialogs, and nested flows
+- state decomposition that matches real app behavior
 
-Recommended prompt:
+## How To Choose
+
+- Use `Simple redesign` when the app surface is small, mostly contained, or has only a few canonical screens.
+- Use `Complex redesign` when the app has multiple activities, fragments, tabs, overlays, or materially different states.
+- Use `Design-only` when you want the full design chain but do not want code changes yet.
+- Use `Continue` when `.da-vinci/` artifacts already exist and the workflow needs to resume.
+
+## 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/.
 ```
 
-When to switch to `intake` first:
+## Complex Redesign
 
-- 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
+```text
+$da-vinci use redesign-from-code to redesign this existing mobile app.
 
-`intake` variant:
+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 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.
 ```
+
+## When To Switch To Intake First
+
+- the project has multiple truth sources
+- the UI stack is unclear
+- the first workflow prompt is still hard to phrase cleanly

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

@@ -10,37 +10,75 @@ 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
+- clear decomposition of tool regions, side regions, and overlays
 
-Recommended prompt:
+## 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 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/.
 ```
 
-When to switch to `intake` first:
+## Complex Redesign
+
+```text
+$da-vinci use redesign-from-code to redesign this existing tablet product.
 
-- 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
+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` variant:
+## 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.
 ```
+
+## 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

@@ -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

@@ -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

@@ -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