@xenonbyte/da-vinci-workflow 0.1.12 → 0.1.13

package/CHANGELOG.md

@@ -4,6 +4,14 @@
 
 - No unreleased changes yet.
 
+## v0.1.13 - 2026-03-27
+
+### Changed
+- visual-adapter execution now requires explicit runtime declaration of the resolved primary adapter, available and unavailable requested adapters, and pre-anchor thesis writing instead of relying on artifact metadata alone
+- redesign guidance now requires anchor-surface structural-delta notes, shared primitives before broad page expansion, and screenshot review that cannot auto-pass when analysis reports hierarchy, spacing, clarity, or inconsistency issues
+- `.da-vinci/designs/` is now documented more strictly as a `.pen`-only directory, and design-source guidance now expects shell-visible `.pen` persistence immediately after the first successful Pencil write
+- Pencil workflow guidance now explicitly rejects web-only properties such as `flex` and `margin`, and platform-adapter docs now warn against assuming cross-platform equivalence between near-name visual adapters
+
 ## v0.1.12 - 2026-03-27
 
 ### Changed

package/README.md

@@ -27,10 +27,17 @@ This workflow is intended for:
 
 Latest published npm package:
 
-- `@xenonbyte/da-vinci-workflow@0.1.12`
+- `@xenonbyte/da-vinci-workflow@0.1.13`
 
 Release highlights:
 
+- visual-adapter execution now requires explicit runtime declaration of the resolved primary adapter and any unavailable requested adapters
+- cross-platform near-name adapters such as `frontend-skill` and `frontend-design` are now treated as distinct unless the current environment explicitly resolves them
+- complex `redesign-from-code` runs now require a visual thesis, content plan, interaction thesis, and anchor-surface structural-delta notes before broad Pencil generation
+- screenshot review is now documented as a binding gate; analysis that reports hierarchy, spacing, clarity, or inconsistency issues cannot be treated as an automatic pass
+- `.da-vinci/designs/` is now documented more strictly as a `.pen`-only directory, and project-local `.pen` persistence must be verified as shell-visible immediately after the first Pencil write
+- multi-surface redesign guidance now requires a shared primitive family to be defined from approved anchor surfaces before broad page expansion
+- Pencil generation guidance now explicitly rejects web-only properties such as `flex` and `margin`
 - 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
@@ -152,8 +159,16 @@ 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
+- state the resolved primary adapter explicitly at runtime and name any requested adapters that are unavailable
+- do not assume cross-platform equivalence between near-name adapters
+- write a visual thesis, content plan, and interaction thesis before the first anchor surface
 - 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
+- for each anchor surface, explain how the new composition differs structurally from the current layout
+- do not auto-pass screenshot review when analysis reports hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues
+- define shared primitives from the approved anchor surfaces before broad page expansion
+- keep `.da-vinci/designs/` reserved for `.pen` files only and verify the registered `.pen` path is shell-visible after the first Pencil write
+- use only Pencil-supported properties; do not rely on web-only props such as `flex` or `margin`
 - 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

package/README.zh-CN.md

@@ -29,10 +29,17 @@ Da Vinci 是一个把产品需求一路推进到结构化规格、Pencil 设计
 
 最新已发布 npm 包：
 
-- `@xenonbyte/da-vinci-workflow@0.1.12`
+- `@xenonbyte/da-vinci-workflow@0.1.13`
 
 已发布版本重点：
 
+- visual adapter 的执行现在要求在运行时明确声明解析出来的主 adapter，以及哪些请求的 adapter 当前不可用
+- `frontend-skill`、`frontend-design` 这类跨平台近名 adapter 现在明确视为不同能力源，除非当前环境真的解析到了它们
+- 复杂 `redesign-from-code` 现在要求在大规模 Pencil 设计前先写 visual thesis、content plan、interaction thesis 和 anchor surface 的 structural-delta 说明
+- screenshot review 现在被明确强调为硬闸门；只要分析指出 hierarchy、spacing、clarity 或 inconsistency 问题，就不能自动判通过
+- `.da-vinci/designs/` 现在更明确只用于放 `.pen` 文件，而且第一次 Pencil 写入后就要验证对应 `.pen` 已经成为 shell 可见文件
+- 多 surface 重设计现在要求先从已通过的 anchor surface 中抽出 shared primitive family，再扩展更多页面
+- Pencil 生成规则现在明确拒绝 `flex`、`margin` 这类 Web 属性
 - visual adapter 解析现在要求“解析出来的主 adapter 必须真正主导首轮设计”，而不是只登记在工件里
 - 复杂重设计现在默认采用 anchor-first 的 Pencil 生成策略：先做 1 到 3 个 anchor surface，截图审查后再扩展
 - design checkpoint 现在会明确拦截大量空占位、重复模板和过早的大批量多页面脚手架
@@ -157,8 +164,16 @@ Da Vinci V2 支持四种模式：
 - 高密度 app、dashboard、工具型界面，且视觉要求中等时，优先把 `ui-ux-pro-max` 放第一位
 - 如果更重视 art direction、构图和高级感，就把 `frontend-skill` 放第一位
 - 一旦配置了 `Preferred adapters`，解析出来的主 adapter 应该真正主导首轮设计，而不是只登记在工件里
+- 运行时必须明确写出解析出来的主 adapter，以及哪些请求的 adapter 当前不可用
+- 不要默认把跨平台的近名 adapter 当成同一个能力源
+- 在第一个 anchor surface 之前，先写 visual thesis、content plan 和 interaction thesis
 - Pencil 的 guide 只应该约束平台布局和可实现性，不应该替代主 adapter 成为设计方向来源
 - 面对复杂重设计时，先做 1 到 3 个 anchor surface，并完成截图审查，再扩展到更多页面
+- 对每个 anchor surface，都要说明“新的构图和当前布局结构相比，具体改了什么”
+- 如果截图分析指出 hierarchy、spacing、clarity、inconsistency 或 unresolved placeholder 问题，就不能自动判通过
+- 在扩展更多页面前，先从已通过的 anchor surface 中抽出 shared primitives
+- `.da-vinci/designs/` 只应该放 `.pen` 文件，并且第一次 Pencil 写入后就要验证登记路径已经成为 shell 可见文件
+- 只使用 Pencil 支持的属性，不要继续使用 `flex`、`margin` 这类 Web 属性
 - 默认保留 `Fallback: native-da-vinci`
 - `Require Adapter` 默认保持 `false`，只有设计要求很高时再改成 `true`
 - `Scope` 只管 presentation 质量，不要拿它去定义 behavior、route 或 state truth

package/SKILL.md

@@ -185,7 +185,10 @@ 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
+- do not assume cross-platform equivalence between near-name adapters such as `frontend-skill` and `frontend-design`; only resolve adapters that are explicitly named and actually installed in the current environment
+- record which requested adapters were available, which were unavailable, and which adapter became the resolved primary adapter
 - 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
+- when a resolved primary adapter is available, state that runtime resolution explicitly before the first anchor-screen design pass and let it drive the visual thesis, content plan, and interaction thesis
 - 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
@@ -213,6 +216,17 @@ Default completion rule:
 - if the request is `design-only`, stop after design artifacts and bindings
 - otherwise assume `full-delivery` and continue through implementation and verification
 
+## Pencil Generation Rules
+
+During active Pencil work:
+
+- keep `.da-vinci/designs/` reserved for project-local `.pen` files; do not write workflow markdown such as inventories, proposals, or checkpoints into that directory
+- on `redesign-from-code`, write a short structural-delta note for each anchor surface explaining how the new composition differs from the current XML or layout grouping
+- after the first successful Pencil write, verify that the registered project-local `.pen` path exists as a shell-visible file before treating the design source as persistent
+- use only Pencil-supported properties; do not emit web- or CSS-only layout properties such as `flex` or `margin`
+- on complex redesigns, turn approved anchor surfaces into a small shared primitive family before broad page expansion
+- screenshot review is binding: if the review calls out hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues, revise the screen before treating the checkpoint as `PASS`
+
 ## Load References On Demand
 
 Load only the reference that matches the current step:

package/commands/claude/da-vinci.md

@@ -22,6 +22,9 @@ Notes:
 - Requirements decide behavior.
 - Pencil decides presentation.
 - Code must follow both.
+- If `Visual Assist` is configured, resolve and state the actual primary visual adapter for this environment instead of assuming cross-platform skill equivalence.
+- Keep `.da-vinci/designs/` reserved for `.pen` files only.
+- On complex redesigns, design 1-3 anchor surfaces first and treat screenshot review as a binding gate before broad expansion.
 - Use `intake` when the user needs help phrasing the first workflow request.
 - Use `continue` when `.da-vinci/` artifacts already exist and the workflow must resume.
 - Keep workflow semantics shared across Codex, Claude, and Gemini.

package/commands/codex/prompts/da-vinci.md

@@ -21,6 +21,9 @@ Available routes:
 
 Important:
 - Treat `/prompts:*` as action selectors in Codex.
+- If `Visual Assist` is configured, resolve and state the actual primary visual adapter for this environment instead of assuming cross-platform skill equivalence.
+- Keep `.da-vinci/designs/` reserved for `.pen` files only.
+- On complex redesigns, design 1-3 anchor surfaces first and treat screenshot review as a binding gate before broad expansion.
 - Use `intake` when the user does not know how to phrase the first request.
 - Use `continue` when `.da-vinci/` artifacts already exist and the workflow must resume.
 - If details are still needed after route selection, provide them in the next message.

package/commands/gemini/da-vinci.toml

@@ -24,6 +24,9 @@ Notes:
 - Requirements decide behavior.
 - Pencil decides presentation.
 - Code must follow both.
+- If `Visual Assist` is configured, resolve and state the actual primary visual adapter for this environment instead of assuming cross-platform skill equivalence.
+- Keep `.da-vinci/designs/` reserved for `.pen` files only.
+- On complex redesigns, design 1-3 anchor surfaces first and treat screenshot review as a binding gate before broad expansion.
 - Use `intake` when the user needs help phrasing the first workflow request.
 - Use `continue` when `.da-vinci/` artifacts already exist and the workflow must resume.
 - Keep workflow semantics shared across Claude, Codex, and Gemini.

package/docs/mode-use-cases.md

@@ -42,6 +42,7 @@ Rule:
 - only `DA-VINCI.md` belongs at the project root
 - all other workflow outputs should stay under `.da-vinci/`
 - persisted project-local Pencil files should stay under `.da-vinci/designs/`
+- `.da-vinci/designs/` should contain `.pen` files only, not workflow markdown
 
 ## Quick mode selection
 
@@ -324,9 +325,11 @@ 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
+   - write the visual thesis, content plan, interaction thesis, and structural-delta notes before broad anchor generation
    - 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
+   - verify that registered `.pen` path is shell-visible immediately after the first successful Pencil write
 
 7. create or update `pencil-bindings.md`
    - bind pages to redesign screens
@@ -342,9 +345,16 @@ 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
+- state the resolved primary adapter explicitly at runtime, including which requested adapters were unavailable
+- do not assume cross-platform equivalence between near-name adapters; resolve the installed adapter names for the current environment
+- when a primary adapter is active, write the visual thesis, content plan, and interaction thesis before the first anchor screen
 - 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 each anchor surface, explain briefly how the new composition differs from the current layout grouping
+- do not auto-pass screenshot review if the analysis reports hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues
+- define a small shared primitive family from the approved anchor surfaces before broad page expansion
+- use only Pencil-supported properties; do not rely on web-only props such as `flex` or `margin`
 
 For redesign work:
 
@@ -362,6 +372,7 @@ Fresh-layout rule:
 Project-local `.pen` rule:
 
 - the preferred `.pen` path in `design-registry.md` is owned by the workflow, not by user hand-editing
+- keep `.da-vinci/designs/` reserved for `.pen` files rather than workflow markdown
 - do not keep redesign work inside an unrelated active Pencil editor just because it is currently open
 - if Pencil MCP does not materialize the registered shell-visible file automatically, reconstruct and write that `.pen` file before mapping or implementation is treated as complete
 

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

@@ -43,9 +43,17 @@ Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, ove
 Decompose complex screens into subpages, overlays, materially different states, and implementation surfaces.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Treat the resolved primary visual adapter as the first-pass design lead.
+State the resolved primary visual adapter explicitly in the log and name any requested adapters that are unavailable.
+Before the first anchor surface, write a visual thesis, content plan, and interaction thesis.
 Use Pencil guides only as layout constraints, not as the design direction.
 Do not start with broad multi-screen scaffolding.
 Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep non-`.pen` workflow artifacts out of `.da-vinci/designs/`.
+Define shared primitives from the approved anchor surfaces before broad page expansion.
 Do not pass design checkpoint if the result is a skin-swap of the old UI, a generic card grid, repeated placeholder templates, or weak visual anchors.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```

package/docs/visual-adapters.md

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

package/docs/workflow-examples.md

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

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

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

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

@@ -43,9 +43,17 @@ Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, ove
 Decompose complex screens into subpages, overlays, materially different states, and implementation surfaces.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Treat the resolved primary visual adapter as the first-pass design lead.
+State the resolved primary visual adapter explicitly in the log and name any requested adapters that are unavailable.
+Before the first anchor surface, write a visual thesis, content plan, and interaction thesis.
 Use Pencil guides only as layout constraints, not as the design direction.
 Do not start with broad multi-screen scaffolding.
 Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep non-`.pen` workflow artifacts out of `.da-vinci/designs/`.
+Define shared primitives from the approved anchor surfaces before broad page expansion.
 Do not pass design checkpoint if the result is a skin-swap of the old UI, a generic card grid, repeated placeholder templates, or weak visual anchors.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```

package/docs/zh-CN/visual-adapters.md

@@ -118,6 +118,7 @@ visual adapter 是可选的 presentation 质量增强层。
   - 你希望 Da Vinci 优先尝试的本地 skill 列表
   - 顺序有意义
   - 即使多个 skill 都可用，最终也应该收敛出一个 primary adapter
+  - 不要把不同平台上的近名 adapter（例如 `frontend-skill` 和 `frontend-design`）默认当成同一个能力源，应该按当前环境里真实已安装、真实命名的 adapter 来解析
 - `Scope`
   - adapter 被允许影响的范围
   - 应该限制在构图、层级、spacing、Pencil refinement 这类 presentation 质量问题
@@ -180,9 +181,12 @@ adapter 的解析顺序建议固定为：
 ```md
 ## Visual Adapter Resolution
 - Requested adapters: frontend-skill, ui-ux-pro-max
+- Available requested adapters: frontend-skill
+- Unavailable requested adapters: none
 - Resolved primary adapter: frontend-skill
 - Secondary helpers: none
 - Status: active
+- Runtime declaration: explicitly stated before first anchor pass
 - Scope: DA-VINCI.md, design.md, pencil-design.md
 - Fallback reason if native Da Vinci rules were used: none
 ```
@@ -205,6 +209,8 @@ adapter 的解析顺序建议固定为：
 
 - 在 Pencil 设计前或设计过程中，用它来增强构图和层级判断
 - 解析出来的主 adapter 应该成为首轮设计的 art direction 主导，而不是只登记在 `design-registry.md` 里
+- 在第一个 anchor screen 设计前，必须在运行日志里明确写出解析结果
+- 在第一个 anchor screen 之前，先在这个 adapter 的主导下写出 visual thesis、content plan 和 interaction thesis
 - 页面命名和状态覆盖仍然要服从 `page-map.md`
 - 最终 presentation 真相仍然落在 Pencil `.pen` 数据里，而不是 adapter 的文字建议里
 
@@ -213,7 +219,10 @@ adapter 的解析顺序建议固定为：
 - 不要一开始就批量搭很多空 screen
 - 先做 1 到 3 个 anchor surface
 - 每个 anchor surface 都要先做成完整构图，再扩展更多页面
+- 对每个 anchor surface，都要简短说明“新的构图与当前布局结构相比，具体改了什么”
 - 每做完一个 anchor surface 都先截图审查，再决定是否 clone 变体或继续扩展
+- 不要把截图分析结果自动当作通过；只要它指出 hierarchy、spacing、clarity、inconsistency 或 unresolved placeholder 问题，就应该先修再继续
+- 在扩展更多页面前，先从已通过的 anchor surface 中抽出一组 shared primitives
 - 如果结果仍然大量是占位块或重复模板，直接把 `design checkpoint` 判成 `BLOCK`，不要在坏底稿上继续叠更多页面
 
 把结果记录到 `pencil-design.md`。

package/docs/zh-CN/workflow-examples.md

@@ -91,11 +91,13 @@ $da-vinci use redesign-from-code to inventory the current app, identify current
 4. 在 `proposal.md` 中定义重设计范围
 5. 当范围过大时，把工作拆成多个 `specs/<slice>/spec.md`
 6. 重建或细化 `page-map.md`，把 subpage、overlay、重要 state 一起拆出来
-7. 创建新的或更新后的 Pencil 页面，基于重新构图而不是旧 UI 换皮，并优先持久化到 `.da-vinci/designs/`
-8. 运行 `design-source checkpoint`，确认登记的项目内 `.pen` 路径、当前 Pencil 设计源和 shell 可见文件是一致的
-9. 绑定路由和 Pencil 页面
-10. 生成和 redesign slice 对齐的任务
-11. 实现并验证
+7. 先写出 anchor surface 的 visual thesis、content plan、interaction thesis 和 structural-delta 说明
+8. 创建新的或更新后的 Pencil 页面，基于重新构图而不是旧 UI 换皮，并优先持久化到 `.da-vinci/designs/`
+9. 在第一次成功写入 Pencil 后，立即验证登记的项目内 `.pen` 路径已经成为 shell 可见文件
+10. 运行 `design-source checkpoint`，确认登记的项目内 `.pen` 路径、当前 Pencil 设计源和 shell 可见文件是一致的
+11. 绑定路由和 Pencil 页面
+12. 生成和 redesign slice 对齐的任务
+13. 实现并验证
 
 ### 复杂 Android 页面示例
 
@@ -106,8 +108,16 @@ Existing code is the behavior source of truth, not the layout truth.
 Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, and important states.
 Decompose complex screens into separate design surfaces before Pencil work.
 Use frontend-skill explicitly as the primary visual reasoning source.
+State the resolved primary visual adapter explicitly in the log before the first anchor surface.
+Write a visual thesis, content plan, and interaction thesis before the first anchor surface.
+Use Pencil guides only as layout constraints, not as the design direction.
 Do not start with broad multi-screen scaffolding.
 Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep `.da-vinci/designs/` reserved for `.pen` files only.
 Do not pass design checkpoint if the result is just a skin-swap of the old UI.
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xenonbyte/da-vinci-workflow",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "Requirement-to-design-to-code workflow skill for Codex, Claude, and Gemini",
   "bin": {
     "da-vinci": "bin/da-vinci.js"

package/references/artifact-templates.md

@@ -11,6 +11,7 @@ Write artifacts into the target project using this rule:
 - keep `DA-VINCI.md` at the project root
 - keep project-level workflow files in `.da-vinci/`
 - keep project-local Pencil `.pen` files in `.da-vinci/designs/`
+- keep workflow markdown out of `.da-vinci/designs/`; that directory is reserved for `.pen` sources only
 - keep change-level workflow files in `.da-vinci/changes/<change-id>/`
 
 Recommended placement:
@@ -86,6 +87,10 @@ Use this structure:
 - Route
 - Page purpose
 
+## Implementation Surfaces
+- Activity / fragment / tab / dialog / sheet / overlay
+- Materially different states
+
 ## UI Regions
 - Shared layout regions
 - Repeated page patterns
@@ -241,9 +246,12 @@ Use this structure:
 
 ## Visual Adapter Resolution
 - Requested adapters
+- Available requested adapters
+- Unavailable requested adapters
 - Resolved primary adapter
 - Secondary helpers
 - Status: active / fallback / unavailable
+- Whether runtime execution explicitly declared the resolved primary adapter
 - Scope
 - Fallback reason if native Da Vinci rules were used
 
@@ -255,6 +263,7 @@ Use this structure:
 - Why a source is active
 - Whether a source is safe to iterate
 - Whether shell-visible filesystem persistence exists
+- Whether shell-visible persistence was verified immediately after the first Pencil write
 - Whether the file had to be reconstructed from MCP-readable document data
 ```
 
@@ -399,9 +408,23 @@ Use this structure:
 ```md
 # Design
 
+## Visual Thesis
+- One-sentence art-direction statement
+
+## Content Plan
+- Primary anchor
+- Supporting rail
+- Action lane
+
+## Interaction Thesis
+- Motion or presence ideas that affect hierarchy or affordance
+
 ## Page Map
 - Pages and sections
 
+## Structural Delta From Current Layout
+- For each anchor surface, how the new composition differs from the current XML or layout grouping
+
 ## Interaction Model
 - Primary actions
 - Secondary actions
@@ -415,6 +438,12 @@ Use this structure:
 - Reusable blocks
 - Page-specific blocks
 
+## Shared Primitive Plan
+- Top bar
+- Segmented tabs
+- Metric rails
+- Tiles, rows, trays, overlays
+
 ## Content Notes
 - Key text
 - Priority order
@@ -442,16 +471,26 @@ Use this structure:
 
 ## Visual Adapter Use
 - Resolved primary adapter
+- Available requested adapters
+- Unavailable requested adapters
 - Secondary helpers
+- Whether runtime execution explicitly declared the resolved primary adapter
 - Whether the primary adapter actively led the first-pass composition
 - How it affected composition, hierarchy, or motion guidance
 - Whether native Da Vinci fallback was used
 
 ## Anchor Surfaces
 - Which 1-3 anchor screens were designed first
+- Structural-delta summary for each anchor surface
 - Screenshot review status for each anchor
+- Whether screenshot review found hierarchy, spacing, clarity, or inconsistency issues
+- Whether each anchor was revised after screenshot review
 - Whether broad multi-screen expansion is approved yet
 
+## Shared Primitives
+- Reusable UI family extracted from the approved anchors
+- Whether broad page expansion happened before or after the primitive family was defined
+
 ## Page Mapping
 - Requirement -> Pencil page
 
@@ -470,6 +509,7 @@ Use this structure:
 ## Implementation Notes
 - Important layout or styling constraints to preserve in code
 - Persistence notes if the project-local `.pen` file had to be reconstructed from MCP-readable document data
+- Confirmation that `.da-vinci/designs/` was used only for `.pen` files
 ```
 
 Recommended path:

package/references/checkpoints.md

@@ -37,6 +37,7 @@ Use the design checkpoint to confirm:
 - the current Pencil pages follow the same visual baseline
 - later pages are not re-inventing the product style from scratch
 - `redesign-from-code` is not treating the old UI layout as the new design baseline
+- non-design workflow markdown is not being written into `.da-vinci/designs/`, which should stay reserved for project-local `.pen` sources
 
 ## `discovery checkpoint`
 
@@ -49,6 +50,7 @@ Check:
 - product form factor and visual direction are known, inferred, or explicitly deferred
 - candidate pages or current pages are clear enough to move into `page-map.md`
 - open questions are explicitly tracked
+- workflow artifacts are being written to standard locations, especially keeping `.da-vinci/designs/` for `.pen` files rather than markdown notes
 
 Result meanings:
 
@@ -94,12 +96,16 @@ Check:
 - major layout strategy matches the design artifact
 - Pencil names and artifact names are aligned enough to implement from
 - Pencil pages follow the current `DA-VINCI.md` visual contract
+- runtime logs or artifacts explicitly name the requested adapters, which were available, which were unavailable, and which adapter was resolved as primary
 - if visual adapters were requested, the resolved primary adapter clearly shaped the first design pass instead of being recorded only as metadata
+- when a primary adapter is active, the workflow wrote a visual thesis, content plan, and interaction thesis before broad anchor-surface generation
 - complex redesigns have 1-3 fully composed anchor surfaces reviewed before broad multi-screen expansion
+- each anchor surface includes a short explanation of how its composition differs structurally from the current layout truth
 - each page has a clear visual anchor or primary working surface
 - section hierarchy is readable without relying on decorative chrome
 - the design does not collapse into generic card-grid or border-heavy filler UI
 - the design is not placeholder-heavy or built from repeated empty templates masquerading as finished screens
+- shared primitives or a reusable component family are identified before the workflow expands a multi-surface redesign from the anchor pages
 - motion ideas, if present, improve hierarchy or affordance instead of adding noise
 - complex pages with multiple fragments, subpages, overlays, or materially different states are decomposed clearly enough to design and implement from
 - `redesign-from-code` output is a fresh composition driven by page responsibility and state, not a skin-swap of the old UI
@@ -115,6 +121,8 @@ Automatic failures:
 - if broad Pencil generation starts before anchor surfaces are compositionally stable, treat the design checkpoint as `BLOCK`
 - if more than roughly 20% of a screen's primary content area is unresolved placeholder scaffolding, treat the design checkpoint as `BLOCK`
 - if multiple screens are effectively the same scaffold with title changes, treat the design checkpoint as `BLOCK`
+- if screenshot review or image analysis calls out hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues and the workflow marks the screen as passed without revision, treat the design checkpoint as `BLOCK`
+- if a redesign screen materially mirrors the current XML grouping with only recolor, spacing tweaks, or minor rearrangement, treat the design checkpoint as `BLOCK`
 
 ## `design-source checkpoint`
 
@@ -125,8 +133,9 @@ Check:
 - `design-registry.md` records one specific preferred project-local `.pen` path
 - the preferred `.pen` path is workflow-owned state, not a hand-wavy placeholder
 - the active Pencil editor path matches the preferred project-local `.pen` path, or the mismatch has been reconciled explicitly
-- if the workflow created or edited Pencil work, the preferred project-local `.pen` file exists as a shell-visible file
+- if the workflow created or edited Pencil work, the preferred project-local `.pen` file exists as a shell-visible file immediately after the first successful Pencil write, not just at workflow close
 - if Pencil MCP only exposed a live document, the workflow reconstructed and wrote the registered project-local `.pen` file from MCP-readable document data before continuing
+- `.da-vinci/designs/` is being used cleanly for project-local `.pen` files rather than mixed with workflow markdown
 - `design-registry.md`, `pencil-design.md`, and `pencil-bindings.md` describe the same active project-local `.pen` source clearly enough to map and implement from
 
 Result meanings:

package/references/design-inputs.md

@@ -9,6 +9,7 @@ Check for `DA-VINCI.md` first, then check whether the project already has persis
 - if it exists, treat it as the project visual contract
 - if `DA-VINCI.md` declares preferred visual adapters, treat them as optional design-assist preferences
 - if `.da-vinci/designs/*.pen` exists, treat those files as project-local design inputs and record the exact preferred path in `design-registry.md`
+- treat non-`.pen` files inside `.da-vinci/designs/` as artifact-placement drift that must be corrected instead of as valid design inputs
 - if it does not exist, generate it from the best stable inputs before broad Pencil page generation
 - avoid re-deriving the visual language page by page
 
@@ -107,9 +108,16 @@ If Pencil creates or updates a baseline during the workflow:
 If the project requests a visual adapter:
 
 - try to resolve it from locally available skills
+- do not assume that near-name adapters on different platforms are equivalent; resolve only adapters that are explicitly named and installed in the current environment unless the project intentionally maps them
 - choose one primary adapter when multiple helpers are available
-- record the requested adapters, resolved primary adapter, any secondary helpers, and fallback result in `design-registry.md`
+- record the requested adapters, which were available, which were unavailable, the resolved primary adapter, any secondary helpers, and fallback result in `design-registry.md`
 - treat the resolved primary adapter as the design lead for the first Pencil pass, especially for anchor screens and other quality-critical surfaces
+- if the resolved primary adapter is active, state that resolution explicitly in the runtime log before the first anchor-screen pass and let it shape the visual thesis, content plan, and interaction thesis
 - use Pencil guides or style helpers only as platform and buildability constraints, not as the art-direction source
 - if `Require Adapter: true` and the requested adapter is unavailable, block instead of silently downgrading the visual bar
 - if no adapter is available, continue with native Da Vinci design rules unless the user explicitly required a specific adapter
+
+For `redesign-from-code` on complex products:
+
+- write a short structural-delta note for each anchor surface explaining how the new composition differs from the current layout grouping
+- keep those notes in `design.md` or `pencil-design.md` before broad multi-screen generation begins

package/references/pencil-design-to-code.md

@@ -40,10 +40,28 @@ If the project resolved a visual adapter:
 
 - use it to lead early composition, hierarchy, spacing discipline, and motion suggestions before or during Pencil design work
 - on complex redesigns, apply it first to 1-3 anchor surfaces before expanding the rest of the screen set
+- if it is active, make that resolution explicit in the runtime log and let it shape the visual thesis, content plan, and interaction thesis before the first anchor screen
 - do not let Pencil guides, generic style packs, or repeated scaffolding override the resolved primary adapter's role in the first-pass art direction
 - do not let it override behavior, route truth, or page-state truth
 - treat it as a presentation-quality assistant, not as a replacement for Pencil or requirements
 
+For `redesign-from-code`:
+
+- preserve behavior from the current codebase, not the current layout grouping
+- write a short structural-delta note for each anchor surface explaining how the new composition differs from the current XML or screen grouping
+- if the result still mirrors the old layout with only recolor or spacing tweaks, treat it as a failed redesign pass
+
+## Pencil Operation Discipline
+
+When generating or editing Pencil data:
+
+- use only Pencil-supported properties and layout concepts
+- do not emit web- or CSS-only properties such as `flex` or `margin`
+- prefer smaller, schema-safe batches on anchor screens so errors do not roll back large composition chunks
+- verify the registered project-local `.pen` path becomes shell-visible immediately after the first successful Pencil write
+- keep workflow markdown out of `.da-vinci/designs/`; reserve that directory for `.pen` files only
+- after the first approved anchor surfaces, extract a shared primitive family before broad page expansion
+
 ## Map Pencil To Frontend
 
 Use these default mappings:
@@ -78,4 +96,5 @@ Before treating the code as complete:
 - compare major sections against Pencil
 - compare headline and CTA hierarchy against Pencil
 - compare panel grouping against Pencil
+- compare the implemented structure against the approved structural-delta notes for anchor surfaces
 - note any intentional deviations

package/references/platform-adapters.md

@@ -93,3 +93,9 @@ Keep these stable:
 - prompt helper semantics
 
 Platform adapters may differ in command syntax, but not in workflow semantics.
+
+Visual-adapter names may differ across platforms.
+
+- do not assume that near-name adapters such as `frontend-skill` and `frontend-design` are equivalent
+- resolve the actual installed adapter names for the current environment
+- record the requested adapters, available adapters, unavailable adapters, and resolved primary adapter explicitly in runtime artifacts