docs(skill): layout-query + P1.8 post-gen prompts + theme strips

crates/aionui-app/assets/builtin-skills/workmate-presentation/SKILL.md

@@ -10,11 +10,11 @@ Create a compact `*.workmate-deck.json`; never emit OOXML, HTML/CSS, or hundreds
 ## Two-stage workflow
 
 1. Extract the goal, audience, evidence, key conclusion, language, and suggested page count.
-2. Ask which catalog theme to use (or propose one) before filling slide content. Record the choice on `theme.id`.
+2. Ask which catalog theme to use (or propose one) before filling slide content. Record the choice on `theme.id`. When offering choices, describe CSBU WorkMate theme preview strips (Studio token bands / `references/theme-strips/*.svg`) — never third-party theme grids.
 3. Write `stage: "outline"` with stable slide IDs, page roles, titles, theme choice, and empty semantic blocks only where useful.
 4. Ask the user to confirm the outline in Presentation Studio (goal, audience, theme, and slide titles). Do not silently advance this file to `ready`, and do not fill layouts/blocks until that confirmation.
 5. After the user confirms (studio sets `stage: "ready"`), fill layouts, typed blocks, speaker notes, and asset requirements.
-6. Right after outline confirmation, briefly suggest Studio polish the user can do themselves: switch same-role layouts, adjust moduleCount/balance/mediaSide controls, fill pending images (upload/generate), or change the deck theme. Do not block filling content on these suggestions.
+6. Right after outline confirmation — and again after the first full fill — proactively offer Studio polish (see dialogue cases below). Do not block filling content on these suggestions.
 7. Run `officecli deck validate <spec> --json`. Resolve every error before export.
 8. Let WorkMate/AionCore build the PPTX; do not call low-level PPTX shape operations.
 
@@ -38,10 +38,33 @@ Create a compact `*.workmate-deck.json`; never emit OOXML, HTML/CSS, or hundreds
 - When several layouts share a role, prefer the one whose module capacity is closest to the number of items/KPIs, and that accepts chart/image blocks when the slide needs them.
 - Optional: set `slides[].candidates` to the top-k layout ids from layout-query (Studio chips prefer these). Export still uses `layoutId` only; validate rejects unknown candidate ids.
 
+## Post-outline / post-fill proactive dialogue (CSBU WorkMate)
+
+Offer short, concrete next steps in the user’s language. Each case is original WorkMate wording — adapt names/ids to the open deck.
+
+1. **Layout switch via layout-query** (after outline confirm, before or during fill)  
+   “大纲已确认。我可以按内容量跑 `officecli deck layout-query`，给 KPI 页在 `metrics` / `metrics-row-4` / `chart-with-kpis` 里挑更贴合的版式，并把 top-k 写入 `slides[].candidates`，你在 Studio 芯片上一键切换；导出仍只看当前 `layoutId`。”
+
+2. **Media fill for pending assets** (right after first fill when any asset is `pending`)  
+   “正文已填好，但还有几张图是 pending。你要我现在按页生成配图并落到 `.assets/`，还是你在 Studio 里用「上传 / 工作区 / 生成图」自己补？跳过未用图也不会挡住导出。”
+
+3. **Theme remap with WorkMate strips** (outline stage or after fill)  
+   “主题还可以换皮：Studio 大纲区有 CSBU WorkMate 自产样张条（token 色带，不是外部主题栅格）。例如从 `consulting-clean` 换到 `boardroom-navy` 只改 `theme.id`，版式与正文槽位保留。要我按听众正式程度帮你挑一个吗？”
+
+4. **Slot visibility toggles** (after fill on layouts with toggleable slots)  
+   “这一页的 insight / 模块槽在 Studio 里可以按 `slot.<id>.visible` 显隐，预览和导出一致。若某一栏暂时没证据，我可以帮你关掉对应槽并重排 moduleCount，而不是删掉整页。”
+
+5. **Chart type control** (trend / metrics pages with chart blocks)  
+   “趋势页现在是柱状图。如果你更想看占比或漏斗，我可以在不改数据的前提下把 `controls.chartType` 调成 `line` / `doughnut` / `funnel`（以 catalog 控件选项为准），你确认后我再 validate。”
+
+6. **Candidates pin polish** (optional follow-up when user likes two layouts)  
+   “这两个同角色版式你都觉得可用的话，我可以把备选 id 留在 `candidates[]`，Studio 芯片会优先展示；点芯片会走换布局并尽量保留 blocks，导出不会把候选写成第二套正文。”
+
 ## Safety and quality
 
 - Use only catalog theme, layout, slot, and control IDs returned by `officecli deck catalog --json`.
 - Keep one idea per slide and add speaker notes to every content slide.
 - Use charts and tables only for real structured data. Never encode them as screenshots.
 - Keep all asset paths relative and inside the deck directory. Never download remote URLs during compilation.
 - Preserve `schemaVersion`; increment `revision` for each saved semantic edit.
+- Branding stays CSBU WorkMate; do not vendor AGPL decks or third-party theme preview assets.

crates/aionui-app/assets/builtin-skills/workmate-presentation/references/deckspec-v1.md

@@ -11,3 +11,5 @@ Required root fields are `schemaVersion: 1`, a non-negative `revision`, `stage`,
 - Assets use a relative `path`, type `image`, status `pending`, `ready`, or `error`, and useful `alt` text.
 
 Limits: 100 slides, 64 blocks per slide, 2 MB source, 25 MB per asset, and 200 MB total assets. `ready` decks cannot export while required slots or assets are unresolved.
+
+Theme previews for outline picking are CSBU WorkMate token strips under `references/theme-strips/` (and Studio programmatic bands). Do not embed third-party theme grids.

crates/aionui-app/assets/builtin-skills/workmate-presentation/references/theme-strips/README.md

@@ -0,0 +1,4 @@
+# CSBU WorkMate theme preview strips
+
+Original programmatic SVG swatches generated from OfficeCLI catalog tokens.
+Branding: CSBU WorkMate only. Do not replace with Dashi or other third-party assets.