@xenonbyte/da-vinci-workflow 0.1.8 → 0.1.9

package/CHANGELOG.md

@@ -4,6 +4,16 @@
 
 - No unreleased changes yet.
 
+## v0.1.9 - 2026-03-27
+
+### Added
+- `docs/visual-adapters.md` and `docs/zh-CN/visual-adapters.md` to explain visual-adapter configuration, resolution, and fallback behavior
+- `docs/visual-assist-presets/` and `docs/zh-CN/visual-assist-presets/` with ready-to-copy `Visual Assist` presets for mobile, desktop, web, and tablet product surfaces
+
+### Changed
+- forward-test example artifacts now show `Visual Assist`, `Visual Adapter Resolution`, and project-local `.pen` persistence patterns
+- workflow examples and README navigation now point to the new visual-adapter and preset documentation
+
 ## v0.1.8 - 2026-03-27
 
 ### Added

package/README.md

@@ -27,10 +27,13 @@ This workflow is intended for:
 
 Latest published npm package:
 
-- `@xenonbyte/da-vinci-workflow@0.1.8`
+- `@xenonbyte/da-vinci-workflow@0.1.9`
 
 Release highlights:
 
+- visual-adapter configuration is now documented explicitly, including field meanings, resolution order, and fallback behavior
+- ready-to-copy `Visual Assist` presets are now included for mobile, desktop, web, and tablet scenarios
+- the repo-local forward test now shows how `Visual Assist`, adapter resolution, and persisted `.pen` paths should be recorded
 - Codex natural-language usage is now documented explicitly, including `intake`, `prompt`, `continue`, and direct mode entry patterns
 - project-local Pencil `.pen` files are now documented to persist under `.da-vinci/designs/`
 - design registry and artifact templates now record preferred persisted `.pen` paths for project-local reuse
@@ -230,6 +233,14 @@ Rules:
 - `page-map.md` is the source of truth for implementation pages
 - `pencil-bindings.md` is the source of truth for implementation page -> Pencil page mapping
 
+Optional visual-adapter policy:
+
+- `DA-VINCI.md` may declare preferred visual adapters for design assistance
+- visual adapters are optional helpers for composition, hierarchy, spacing, and motion guidance
+- they may refine `DA-VINCI.md`, `design.md`, and `pencil-design.md`
+- they must not override behavior truth, route truth, page-state truth, or acceptance rules
+- if a requested adapter is unavailable locally, Da Vinci should continue with native design rules and record the fallback in `design-registry.md`
+
 When a relevant mapping already exists:
 
 - iterate on the mapped Pencil source
@@ -256,6 +267,7 @@ Before generating Pencil designs for a greenfield project, Da Vinci should colle
 - density
 - brand direction
 - responsive priority
+- optional visual-adapter preferences
 
 Preferred inference order:
 
@@ -270,6 +282,12 @@ If `DA-VINCI.md` does not exist:
 - generate it from stable user preferences, existing project signals, or inferred defaults
 - save it before generating many project pages, so later pages do not drift stylistically
 
+If the project requests visual adapters:
+
+- resolve them from the user request first, then `DA-VINCI.md`, then locally available skills
+- choose one primary adapter when multiple helpers are available
+- treat them as non-blocking unless the user explicitly requires a specific adapter
+
 ## Installation
 
 Install the package:
@@ -417,6 +435,8 @@ See:
 
 - `docs/prompt-entrypoints.md`
 - `docs/codex-natural-language-usage.md`
+- `docs/visual-adapters.md`
+- `docs/visual-assist-presets/`
 - `docs/workflow-examples.md`
 - `docs/mode-use-cases.md`
 
@@ -425,6 +445,8 @@ See:
 Chinese companion documents are included in this repository:
 
 - `README.zh-CN.md`
+- `docs/zh-CN/visual-adapters.md`
+- `docs/zh-CN/visual-assist-presets/`
 - `docs/zh-CN/`
 
 ## Repository layout

package/README.zh-CN.md

@@ -29,10 +29,13 @@ Da Vinci 是一个把产品需求一路推进到结构化规格、Pencil 设计
 
 最新已发布 npm 包：
 
-- `@xenonbyte/da-vinci-workflow@0.1.8`
+- `@xenonbyte/da-vinci-workflow@0.1.9`
 
 已发布版本重点：
 
+- visual adapter 的配置字段、解析顺序和回退行为现在有单独文档说明
+- 现在提供按移动端、桌面端、Web、平板拆分的 `Visual Assist` 可复制模板
+- 仓库内的 forward test 示例现在展示了 `Visual Assist`、adapter 解析结果和 `.pen` 持久化记录方式
 - Codex 的自然语言用法现在有单独文档，明确说明 `intake`、`prompt`、`continue` 和直接 mode 调用方式
 - 项目内 Pencil `.pen` 文件现在明确约定默认持久化到 `.da-vinci/designs/`
 - 设计源登记和工件模板现在会记录项目内优先使用的 `.pen` 路径
@@ -183,6 +186,14 @@ project/
 - `page-map.md` 是实现页面和状态的真相源
 - `pencil-bindings.md` 是实现页面到 Pencil 页面绑定的真相源
 
+可选 visual adapter 规则：
+
+- `DA-VINCI.md` 可以声明期望使用的 visual adapter 来辅助设计
+- visual adapter 只用于增强构图、层级、留白、节奏和 motion 判断
+- 它可以影响 `DA-VINCI.md`、`design.md`、`pencil-design.md`
+- 它不能覆盖 behavior truth、路由真相、页面状态真相或验收规则
+- 如果本地没有请求的 adapter，Da Vinci 应继续使用原生设计规则，并在 `design-registry.md` 里记录回退结果
+
 当已有页面映射存在时：
 
 - 优先复用已绑定的 Pencil 设计源
@@ -200,6 +211,13 @@ project/
 - 在可行时把基线保存到 `.da-vinci/designs/`
 - 并在 `design-registry.md` 里记录准确路径
 
+如果项目声明了 visual adapter：
+
+- 先看用户请求，其次看 `DA-VINCI.md`，再看本地可用 skill
+- 如果存在多个可用辅助 skill，收敛出一个 primary adapter，必要时再保留 secondary helpers
+- 默认把它当成非阻塞增强层
+- 只有用户明确要求必须使用某个 adapter 时，缺失才应阻塞工作流
+
 ## 安装
 
 安装 npm 包：
@@ -330,6 +348,8 @@ Continue into full-delivery.
 
 - `docs/codex-natural-language-usage.md`
 - `docs/prompt-entrypoints.md`
+- `docs/visual-adapters.md`
+- `docs/visual-assist-presets/`
 - `docs/workflow-examples.md`
 - `docs/mode-use-cases.md`
 - `references/`
@@ -337,6 +357,8 @@ Continue into full-delivery.
 中文文档：
 
 - `README.zh-CN.md`
+- `docs/zh-CN/visual-adapters.md`
+- `docs/zh-CN/visual-assist-presets/`
 - `docs/zh-CN/`
 
 ## 仓库布局

package/SKILL.md

@@ -151,6 +151,7 @@ Before generating new Pencil designs for a greenfield project, collect or infer:
    - detect whether `DA-VINCI.md` already exists
    - if it exists, treat it as the visual baseline for future pages
    - if it does not exist, generate it from stable user preferences, existing project signals, or inferred defaults before broad Pencil page generation
+   - if it declares preferred visual adapters, treat them as optional design-assist preferences, not as behavior truth
 
 1. product form factor
    - desktop software
@@ -180,6 +181,13 @@ Use this priority order:
 
 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
+- use them to improve visual contract quality, composition, hierarchy, spacing, and motion guidance
+- 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
+
 ## Default Workflow
 
 Run the workflow in this order:
@@ -396,6 +404,13 @@ Use `DA-VINCI.md` as the project-level visual source of truth for:
 - typography direction
 - component tone
 - rules for cross-page consistency
+- optional visual adapter preferences
+
+Treat visual adapters as optional helpers for presentation quality only.
+
+- they may refine `DA-VINCI.md`, `design.md`, and `pencil-design.md`
+- they must not override behavior truth from requirements or existing code
+- they must not replace `page-map.md`, `design-registry.md`, or `pencil-bindings.md`
 
 When a relevant mapping already exists:
 
@@ -407,6 +422,7 @@ When `DA-VINCI.md` already exists:
 
 - use it as the baseline visual contract
 - do not regenerate visual direction from scratch unless the change explicitly rebrands or resets the product style
+- if it declares preferred visual adapters, try to resolve them without blocking the workflow
 
 When page-to-Pencil bindings already exist:
 
@@ -435,6 +451,13 @@ When a Pencil session cannot yet be exported locally:
 - record why local persistence is pending
 - do not hide the lack of a project-local `.pen` path
 
+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`
+- 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.
 
 ## Pencil Design Rules
@@ -446,6 +469,7 @@ When creating or editing Pencil designs:
 - Build the pages required by the current scope, not an abstract moodboard
 - follow `page-map.md` as the canonical page list
 - follow `design-brief.md` for form factor and visual direction when it exists
+- use the resolved visual adapter, when available, for composition, hierarchy, restraint, and motion guidance
 - 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

package/docs/mode-use-cases.md

@@ -505,6 +505,7 @@ Use it like this:
    - reuse it
    - avoid asking duplicate style questions
    - avoid page-by-page style reinvention
+   - read any declared visual-adapter preferences as optional design-assist guidance
 
 2. if it does not exist
    - generate it from stable user preference, existing code signals, or prior design sources
@@ -514,6 +515,13 @@ Use it like this:
    - update `DA-VINCI.md`
    - then propagate the new baseline through Pencil and implementation
 
+Recommended `DA-VINCI.md` pattern:
+
+- keep visual-adapter preferences inside `DA-VINCI.md`
+- treat them as optional presentation helpers
+- examples can include local skills such as `frontend-skill` or `ui-ux-pro-max`
+- if the preferred adapter is unavailable locally, continue with native Da Vinci design rules and record the fallback in `design-registry.md`
+
 ---
 
 ## How to choose between design sources

package/docs/visual-adapters.md

@@ -0,0 +1,173 @@
+# Visual Adapters
+
+Use this document when a project wants optional UI-design assistance from local skills such as `frontend-skill` or `ui-ux-pro-max`.
+
+## What A Visual Adapter Is
+
+A visual adapter is an optional presentation-quality helper.
+
+It may improve:
+
+- visual-contract quality
+- composition
+- hierarchy
+- spacing discipline
+- motion guidance
+- Pencil page refinement
+
+It must not redefine:
+
+- behavior truth
+- route truth
+- page-state truth
+- acceptance criteria
+
+Those still come from requirements, existing code, `page-map.md`, and `pencil-bindings.md`.
+
+## Where To Configure It
+
+Configure visual-adapter preferences inside `DA-VINCI.md`.
+
+Recommended shape:
+
+```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:
+  - false
+```
+
+Use `Require Adapter: true` only when the workflow must stop if the preferred adapter is unavailable locally.
+
+## What Each Field Means
+
+Use the fields like this:
+
+- `Preferred adapters`
+  - 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
+- `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
+  - do not use this field to delegate behavior, routes, or state truth
+- `Fallback`
+  - what Da Vinci should do if the preferred adapters are unavailable locally
+  - `native-da-vinci` means continue with the built-in rules instead of stopping
+- `Require Adapter`
+  - whether adapter availability is a hard requirement
+  - `false` means adapter use is optional and should not block delivery
+  - `true` means the workflow should stop if no acceptable adapter is available
+
+Recommended default:
+
+- use `Require Adapter: false`
+- use `Fallback: native-da-vinci`
+- keep `Scope` narrowly focused on visual-quality decisions
+
+## Resolution Order
+
+Resolve adapters in this order:
+
+1. explicit user request
+2. `DA-VINCI.md`
+3. locally available skills
+4. native Da Vinci rules
+
+When multiple helpers are available:
+
+- choose one primary adapter
+- keep secondary helpers only when they serve a clear non-conflicting role
+
+## Where To Record The Result
+
+Record runtime resolution in `design-registry.md`.
+
+Recommended fields:
+
+```md
+## Visual Adapter Resolution
+- Requested adapters: frontend-skill, ui-ux-pro-max
+- Resolved primary adapter: frontend-skill
+- Secondary helpers: none
+- Status: active
+- Scope: DA-VINCI.md, design.md, pencil-design.md
+- Fallback reason if native Da Vinci rules were used: none
+```
+
+If no adapter is available:
+
+```md
+## Visual Adapter Resolution
+- Requested adapters: frontend-skill
+- Resolved primary adapter: native-da-vinci
+- Secondary helpers: none
+- Status: fallback
+- Scope: DA-VINCI.md, design.md, pencil-design.md
+- Fallback reason if native Da Vinci rules were used: requested adapter unavailable locally
+```
+
+## How It Affects Pencil Work
+
+When a visual adapter is active:
+
+- use it before or during Pencil work to sharpen composition and hierarchy
+- keep page names and states aligned with `page-map.md`
+- keep final `.pen` decisions grounded in Pencil, not in adapter prose
+
+Record the outcome in `pencil-design.md`.
+
+Recommended fields:
+
+```md
+## Visual Adapter Use
+- Resolved primary adapter: frontend-skill
+- Secondary helpers: none
+- How it affected composition, hierarchy, or motion guidance:
+  - stronger hero anchor
+  - fewer card treatments
+  - more deliberate CTA placement
+- Whether native Da Vinci fallback was used: no
+```
+
+## Typical Use
+
+Example request:
+
+```text
+$da-vinci use redesign-from-code to globally replace the UI of this existing Android project.
+
+Existing Android code is the behavior source of truth.
+Use the visual-adapter preferences declared in DA-VINCI.md.
+If frontend-skill is available, use it as the primary visual adapter.
+If it is unavailable, fall back to native Da Vinci design rules and continue.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+## Suggested Adapter Choices
+
+- `frontend-skill`
+  - better for strong art direction, composition, and premium landing or brand surfaces
+- `ui-ux-pro-max`
+  - better for app surfaces, dashboards, admin UI, and dense product workflows
+- `native-da-vinci`
+  - use when no adapter is available or when the project only needs the built-in workflow rules
+
+## Scenario Presets
+
+Ready-to-copy presets live here:
+
+- `docs/visual-assist-presets/mobile-app.md`
+- `docs/visual-assist-presets/desktop-app.md`
+- `docs/visual-assist-presets/web-app.md`
+- `docs/visual-assist-presets/tablet-app.md`

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

@@ -0,0 +1,24 @@
+# Visual Assist Presets
+
+Use these presets as starting points for the `## Visual Assist` section inside `DA-VINCI.md`.
+
+Each preset is intentionally conservative:
+
+- one primary adapter direction
+- one fallback direction
+- clear scope boundaries
+- non-blocking behavior by default
+
+Available presets:
+
+- `mobile-app.md`
+- `desktop-app.md`
+- `web-app.md`
+- `tablet-app.md`
+
+How to use them:
+
+1. choose the preset closest to the product surface
+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

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

@@ -0,0 +1,35 @@
+# Desktop App Preset
+
+Recommended when the product surface is desktop software or a dense productivity workspace.
+
+Use this when the UI needs:
+
+- high information density
+- strong workspace hierarchy
+- restrained chrome
+- panel and inspector judgment
+
+Recommended `DA-VINCI.md` block:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - ui-ux-pro-max
+  - frontend-skill
+- Scope:
+  - visual contract refinement
+  - workspace composition
+  - hierarchy and spacing
+  - motion guidance
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - false
+```
+
+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

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

@@ -0,0 +1,35 @@
+# Mobile App Preset
+
+Recommended when the product surface is a phone-first app.
+
+Use this when the UI needs:
+
+- compact but readable mobile hierarchy
+- strong tap-target discipline
+- restrained motion
+- app-first component judgment rather than brand-poster composition
+
+Recommended `DA-VINCI.md` block:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - ui-ux-pro-max
+  - frontend-skill
+- Scope:
+  - visual contract refinement
+  - mobile page composition
+  - hierarchy and spacing
+  - touch-first motion guidance
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - false
+```
+
+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

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

@@ -0,0 +1,35 @@
+# Tablet App Preset
+
+Recommended when the product surface is tablet-first or must work across tablet-heavy flows.
+
+Use this when the UI needs:
+
+- touch-aware spacing
+- larger compositional regions than phone UI
+- more balanced density than desktop software
+- strong split-pane or canvas-area judgment
+
+Recommended `DA-VINCI.md` block:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - ui-ux-pro-max
+  - frontend-skill
+- Scope:
+  - visual contract refinement
+  - tablet page composition
+  - hierarchy and spacing
+  - touch-aware motion guidance
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - false
+```
+
+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

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

@@ -0,0 +1,35 @@
+# Web App Preset
+
+Recommended when the product surface is a browser-based app, SaaS workspace, or hybrid product UI.
+
+Use this when the UI needs:
+
+- balanced density
+- clear workspace structure
+- stronger marketing-to-product bridge than a pure desktop tool
+- responsive layout judgment
+
+Recommended `DA-VINCI.md` block:
+
+```md
+## Visual Assist
+- Preferred adapters:
+  - ui-ux-pro-max
+  - frontend-skill
+- Scope:
+  - visual contract refinement
+  - page composition
+  - hierarchy and spacing
+  - responsive motion guidance
+  - Pencil design refinement
+- Fallback:
+  - native-da-vinci
+- Require Adapter:
+  - false
+```
+
+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

package/docs/workflow-examples.md

@@ -31,11 +31,12 @@ Expected flow:
 2. create `proposal.md`
 3. create `specs/<capability>/spec.md`
 4. create `page-map.md`
-5. register `.pen` sources in `design-registry.md`
-6. create Pencil pages and record them in `pencil-design.md`
-7. bind implementation pages in `pencil-bindings.md`
-8. generate `tasks.md`
-9. build and verify
+5. configure any optional visual-adapter preferences in `DA-VINCI.md`
+6. register `.pen` sources and visual-adapter resolution in `design-registry.md`
+7. create Pencil pages, persist the preferred `.pen` path, and record adapter use in `pencil-design.md`
+8. bind implementation pages in `pencil-bindings.md`
+9. generate `tasks.md`
+10. build and verify
 
 ## 2. `greenfield-brainstorm`
 
@@ -54,10 +55,11 @@ Expected flow:
 3. stabilize scope in `proposal.md`
 4. write behavior in `specs/<capability>/spec.md`
 5. define pages in `page-map.md`
-6. register and generate Pencil sources
-7. bind implementation pages to Pencil pages
-8. generate tasks
-9. build and verify
+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
 
 ## 3. `redesign-from-code`
 
@@ -72,14 +74,15 @@ $da-vinci use redesign-from-code to inventory the current app, identify current
 Expected flow:
 
 1. scan the existing product into `project-inventory.md`
-2. register any current `.pen` sources in `design-registry.md`
-3. define redesign scope in `proposal.md`
-4. split broad redesign work into `specs/<slice>/spec.md` files when one large `ui-refresh` spec would be too coarse
-5. rebuild or refine `page-map.md`
-6. create new or updated Pencil pages
-7. bind routes and pages to Pencil screens
-8. generate tasks aligned to the redesign slices
-9. build and verify
+2. read any visual-adapter preference from the request or `DA-VINCI.md`
+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
 
 ## 4. `feature-change`
 
@@ -96,12 +99,26 @@ Expected flow:
 1. define the change in `proposal.md`
 2. write affected behavior in `specs/<capability>/spec.md`
 3. update the affected subset of `page-map.md`
-4. reuse or update the active design source in `design-registry.md`
+4. reuse or update the active design source and visual-adapter resolution in `design-registry.md`
 5. create the Pencil delta in `pencil-design.md`
 6. update `pencil-bindings.md`
 7. generate tasks
 8. build and verify
 
+## Visual-adapter helper example
+
+When the project wants optional UI-design help from local skills:
+
+```text
+$da-vinci use redesign-from-code to redesign the current product UI.
+
+Existing code is the behavior source of truth.
+Use the visual-adapter preferences declared in DA-VINCI.md.
+If frontend-skill is available, use it as the primary visual adapter.
+If it is unavailable, fall back to native Da Vinci design rules and continue.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
 ## Cross-mode rule
 
 In every mode:
@@ -113,7 +130,9 @@ In every mode:
 And in every mode:
 
 - `design-registry.md` tracks the available `.pen` sources
+- `design-registry.md` also records visual-adapter resolution when one is requested
 - `pencil-bindings.md` tracks implementation page to Pencil page mapping
+- `pencil-design.md` records how the resolved adapter influenced the design pass when relevant
 - the workflow runs as `autonomous-by-default` unless a real blocker exists
 
 ## Complex redesign helper example

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

@@ -154,3 +154,11 @@ Da Vinci 应该：
 6. 更新 `pencil-bindings.md`
 7. 生成 `tasks.md`
 8. 进入实现
+
+## `DA-VINCI.md` 里的 visual adapter 应该怎么用
+
+- 把 visual adapter 偏好写在 `DA-VINCI.md` 里，而不是单独再造一个配置文件
+- 把它当成可选的 presentation 增强层
+- 可以用来辅助 `DA-VINCI.md`、`design.md`、`pencil-design.md`
+- 例如本地 skill 里的 `frontend-skill` 或 `ui-ux-pro-max`
+- 如果本地没有对应 adapter，就回退到 Da Vinci 原生设计规则，并把结果记录到 `design-registry.md`