@taloswork/ose-shared 0.1.9 → 0.1.11

package/skills/document/rewrite.md

@@ -1,28 +1,30 @@
 # Generate / edit documents (L3)
 
-## Themes — the presentation layer for `doc-gen` DOCUMENTS (docx / pdf / spec-pptx)
+## Themes — the presentation layer for `doc-gen` DOCUMENTS (docx / pdf)
 
 > **Decks use skins, not themes.** For an html2pptx deck (路演/汇报/pitch), pick a
 > **skin** via `--style` (`styles/README.md`, the SKILL deck route) — NOT a
 > `themes/*.json`. The `themes/` + `--theme` system below is for `doc-gen`
-> DOCUMENTS (Word/PDF reports, structured-spec decks) — a separate, still-valid path.
+> DOCUMENTS (Word/PDF reports) — a separate, still-valid path. `doc-gen` makes no
+> decks at all; `html2pptx --theme` reads a theme's colors/fonts and its three
+> slide colors (`pptx{background,titleColor,textColor}`).
 
 Content (the spec) and presentation (the theme) are separate. A theme is a JSON
-file — template skills ship their own; this skill ships **8 built-ins** in `themes/`
-(theme = colors/fonts for `doc-gen` output): `cool-tech` · `apple-keynote` ·
-`mckinsey-consulting` · `anthropic-clay` · `black-gold` · `hand-drawn` · `mono` ·
-`warm-editorial`. For a plain Word/PDF report, `mckinsey-consulting` (white · deep
+file — template skills ship their own; this skill ships **12 built-ins** in `themes/`
+(theme = colors/fonts for `doc-gen` output; `themes/README.md` lists them with their
+best fit): `cool-tech` · `apple-keynote` · `mckinsey-consulting` · `anthropic-clay` ·
+`black-gold` · `hand-drawn` · `mono` · `warm-editorial` · `ivory-gold` · `cinereel` ·
+`magazine-ink` · `swiss-grid`. For a plain Word/PDF report, `mckinsey-consulting` (white · deep
 navy · structured tables) is a safe default; `mono` for a stark minimal look.
 
 ```
 node <skill>/bin/doc-gen.cjs docx out.docx spec.json --theme <skill>/themes/mckinsey-consulting.json
 ```
 
-**Topic-adaptive color (pptx, when the user hasn't named a theme/brand)**: pass
-`--topic "<deck subject>"` (or put `"topic"` in the spec). The engine picks a
+**Topic-adaptive color (when the user hasn't named a theme/brand)**: pass
+`--topic "<subject>"` (or put `"topic"` in the spec). The engine picks a
 palette that FITS the subject — deterministically, by keyword then stable hash —
-instead of the same default on every deck (the #1 "AI-generated" tell), and turns
-on the richness tokens (motif + gradient wash + depth). `--palette <id>` forces a
+instead of the same default every time (the #1 "AI-generated" tell). `--palette <id>` forces a
 named one; `doc-gen --list-palettes` prints the library. A `--theme` file or a
 saved/brand preference (step 1 below) still wins — use `--topic` for the "just
 make it look designed-for-this" case, not when the user has a look in mind.
@@ -60,10 +62,10 @@ existing deck can seed one too: `pptx-theme ref.pptx <skill>/themes/custom/x.jso
 
 ```
 node <skill>/bin/pptx-theme.cjs ref.pptx /tmp/ref-theme.json
-node <skill>/bin/doc-gen.cjs pptx out.pptx spec.json --theme /tmp/ref-theme.json
+node <skill>/bin/html2pptx.cjs deck.html out.pptx --theme /tmp/ref-theme.json
 ```
 
-This captures colors/fonts/title-body sizes (heuristic fallbacks print on
+This captures colors/fonts (heuristic fallbacks print on
 stderr), NOT slide layouts — to reuse the deck's actual LAYOUTS, tokenize it into
 a fillable template instead (see "Reuse a user's UPLOADED deck" below:
 `pptx-tokenize` → `doc-fill`).
@@ -71,26 +73,18 @@ a fillable template instead (see "Reuse a user's UPLOADED deck" below:
 Theme fields (all optional; invalid values default + warn on stderr, never fail):
 `bestFor` (one-line 适用场景, for the picker) · `fonts{heading,body}` ·
 `colors{primary,accent,secondary,text,muted,tableHeaderBg,tableBorder}`
-(`accent` drives timeline markers/card bars/KPI numbers and defaults to
-`primary`; `secondary` defaults to `muted`) ·
-`page{size:A4|Letter,margin,header,footer}` (`{title}` `{page}` `{pages}` interpolate;
+(`accent` defaults to `primary`; `secondary` defaults to `muted`) ·
+`page{size:A4|Letter,margin,header,footer}` (`margin` is a CSS length string such as `margin:"20mm"` — mm/cm/in/pt/px; a bare number is not accepted and falls back to the default margin, which changes the page count; `{title}` `{page}` `{pages}` interpolate;
 **page header/footer: prefer Latin/digits — CJK there renders blank in the PDF path**) ·
 `heading{h1..h4}{size,color,bold,spaceAfter}` (color takes hex or a palette key like `"primary"`) ·
 `body{size,lineHeight,justify}` · `cover{enabled,subtitle,date,logo}` (base64 logo; title moves onto the cover) ·
-`pptx{background,titleColor,textColor,titleSize,bodySize,logo,logoPos,slideNumber,
-motif:"none|corner|sidebar",bgWash,depth}`
-(dark deck = dark `background` + light `titleColor`/`textColor`; docx/PDF stay
-white-paper regardless. `motif` stamps a repeated accent on content slides;
-`bgWash` makes the master background a subtle gradient; `depth` gives statement
-slides (cover/section/ending) a gradient background + an oversized ghosted accent
-shape (layered, not flat). Background lives on the slide MASTER — edit it once in
-PowerPoint to reflow every slide.)
+`pptx{background,titleColor,textColor}` — read only by `html2pptx --theme`, as the
+slide background / title / body CSS colors (dark deck = dark `background` + light
+`titleColor`/`textColor`; docx/PDF stay white-paper regardless).
 
 Per format the theme becomes: **pdf** CSS + cover page + live page headers/footers;
 **docx** real document styles (Heading1–4, default font/size, table header shading)
-+ header/footer parts + cover page; **pptx** a slide master (background/logo/footer/
-slide numbers) + themed title/body — and content **flow-layouts**: it never overlaps,
-overflow spills to a "(续)" continuation slide. A spec may embed `"theme": {...}`;
++ header/footer parts + cover page. A spec may embed `"theme": {...}`;
 `--theme <file>` wins.
 
 ## Template decks — `bin/pptx-clone` (one styled slide per data item)
@@ -192,18 +186,20 @@ each, drop the template slide).
 layouts → `pptx-theme` (extract palette) + our families. Repeat a styled slide
 per data row → `pptx-clone`.
 
-All-Node generation (no Python): `docx`, `pptxgenjs`, `exceljs`, `pdf-lib`. Same
-capability tier as the Anthropic docx/pptx/xlsx skills.
+All-Node generation (no Python): `docx`, `exceljs`, and Chromium for PDF; decks go
+through html2pptx. Same capability tier as the Anthropic docx/pptx/xlsx skills.
 
 ## Generate — `bin/doc-gen` (self-contained; no npm install, works offline)
 
 ```
-node <skill>/bin/doc-gen.cjs <docx|xlsx|pptx|pdf> <out> <spec.json>
+node <skill>/bin/doc-gen.cjs <docx|xlsx|pdf> <out> <spec.json>
 ```
 Simple spec shapes:
 - **docx / pdf**: `{ "title"?: "...", "paragraphs": ["...", ...] }`
 - **xlsx**: `{ "sheets": { "SheetName": [["h1","h2"], ["a", 1], ...] } }` (row 1 = bold header)
-- **pptx**: `{ "slides": [{ "title"?: "...", "bullets"?: ["...", ...] }] }`
+
+`doc-gen pptx` exits 64 and points at html2pptx: decks are laid out as HTML
+(deck-design.md), never generated from a slide spec.
 
 `doc-gen` validates these shapes **strictly before rendering**: unknown fields are
 errors, not ignored. For DOCX/PDF use `paragraphs` and/or `blocks`—never
@@ -221,76 +217,20 @@ Rich spec shapes (use these for real documents, not just prose):
 - **xlsx** per sheet, either the row array above OR
   `{ "rows": [...], "header"?, "columnWidths"?: [n...], "numFmt"?: ["#,##0.00"...] }`.
   A cell string starting with `=` is written as a **live formula** (e.g. `"=SUM(A2:A3)"`).
-- **pptx** per slide, add any of `"table": [[...]]`, `"image": {data, x,y,w,h}`,
-  `"chart": {type:"bar|line|pie|doughnut|area", labels:[...], series:[{name, values:[...]}]}` —
-  charts are NATIVE (PowerPoint-editable c:chart parts), series colors cycle the
-  theme's layered palette (accent→secondary→primary), dark decks get readable
-  axis/legend text automatically. Prefer a chart over a numbers table when the
-  point is a trend or comparison.
-- **pptx design archetypes** (per slide — USE THESE for pitch/roadshow decks
-  (路演/汇报/评审/宣讲), not bullets-of-everything; all theme-colored,
-  flow-layouted, overflow-safe). **For a substantive deck, first read
-  content-pipeline.md** (research → pyramid structure → per-page content
-  structure → the mapping to these archetypes → density + diversity rules).
-  Catalog:
-  - **Role**: `"cover": {title, subtitle?, presenter?, date?, variant?}` (封面,
-    own slide) · `"toc": {items:[{index?,title,desc?}], variant?:"numbered|grid"}`
-    (目录) · `"section": {title, subtitle?, index?, variant?:"centered|left|index"}`
-    (章节页,own slide) · `"ending": {message, cta?, contact?, variant?}` (结尾).
-  - **Metrics**: `"kpiCards"` — array OR `{items:[{value,label?,delta?,icon?}], variant?:"row|grid|hero|iconTop"}`
-    ("+x%" green, "-x%" red; `iconTop` shows the card's lucide `icon` above the number) ·
-    `"bigStat": {value, label?, context?, sub?:[kpi]}` (单个巨型数字).
-  - **Content**: `"cards"` — array OR `{items:[{title,text?,accent?,icon?,image?}], variant?:"accentBar|numbered|iconCircle|imageTop"}`
-    (`iconCircle` = lucide `icon` in an accent circle; `imageTop` = the card's base64 `image` as a top banner) ·
-    `"comparison": {columns:[{title,badge?,rows:[…],recommended?}], dimensions?:[…], variant?:"columns|matrix"}`
-    (2–3 栏对比;`matrix` = 特性打勾矩阵,cells 是 有/是/✓ → 绿勾、无/否/- → 叉,否则文字) ·
-    `"quadrant": {xAxis?,yAxis?, cells:[TL,TR,BL,BR]}` (2×2 矩阵) ·
-    `"iconList": {items:[{icon?,title,text?,accent?}], variant?:"rows|grid"}` (icon = a
-    lucide name e.g. "zap"/"shield"/"target"/"users"/"trending-up"; unknown → marker fallback) ·
-    `"quote": {text, author?, role?}`.
-  - **Process/time**: `"steps": {items:[{label,detail?,output?,duration?}], variant?:"horizontal|vertical"}` ·
-    `"timeline"` — array OR `{items:[{label,text?}], variant?:"horizontal|vertical|detailCards"}`
-    (`detailCards` = nodes on a line each with a styled detail card beneath).
-  - **Media**: `"splitImage": {image:{data}, side?:"left|right", title?, bullets?:[…], cards?:[…]}`.
-  Render order within a slide: kpiCards → cards → comparison → quadrant → bigStat →
-  quote → toc → steps → iconList → splitImage → timeline → bullets → table → image → chart.
-  **Vary variants across pages** (content-pipeline.md diversity rule) — a
-  monotone deck of one variant reads as lazy.
-
-  **Designed HTML render (`--design html`, in-app, magazine ceiling)**: the SAME
-  spec, but `cover`/`section`/`bigStat`/`comparison`/`quadrant`/`splitImage`/
-  `iconList` slides render through curated HTML/CSS templates (fuller design)
-  instead of native shapes:
-  `doc-gen.cjs pptx out.pptx spec.json --theme <t> --design html`.
-  Trade-off — richer look, but the output is a flat collage (editable text, **no
-  master/placeholder structure**); charts fall back to native. It needs the
-  app's Chromium; **headless or any slide without a designed template auto-falls
-  back to the native renderer** (same spec, no failure). Use it when the user
-  wants a polished pitch/cover and the deck is mostly the covered archetypes;
-  stick with the default (native) for editable structure, charts, or headless.
-  A layout the templates still can't express → deck-design.md freeform html2pptx.
-
-Under the hood it uses `docx` / `exceljs` / `pptxgenjs` / `pdf-lib` — the same
+Under the hood it uses `docx` / `exceljs`, and prints PDF in Chromium — the same
 tier as the Anthropic docx/pptx/xlsx skills, but all-Node (no Python /
 LibreOffice) and bundled into the script. For anything past these shapes, write a
 short Node script using those libraries directly (they are on the skill's path).
 
-**PDF rendering (two engines, automatic):**
-- **In-app (default): Chromium `printToPDF`.** When running inside Talos,
-  `doc-gen pdf` renders your spec as HTML through the main process → professional
-  CJK line-breaking, per-glyph font fallback (Latin + 中文 mixed just works),
-  justification, tables. This is the formal-delivery path. Output tags
-  `[pdf (chromium)]`. The spec's `blocks` (headings/lists/tables) are supported
-  here too, not just `title`/`paragraphs`.
-- **Headless fallback: pdf-lib.** Outside the app (no render service), it uses the
-  bundled pdf-lib engine (word-wrap + CJK char-wrap + per-script fonts). For CJK
-  it embeds a subset Unicode font from a system font or `$TALOS_PDF_FONT` /
-  `spec.fontPath`; if none is found it errors clearly — set `$TALOS_PDF_FONT`, or
-  generate `.docx` (OOXML references fonts by name, so CJK just works). Output
-  tags `[pdf (pdf-lib)]`.
-
-Either way, **prefer `.docx` for the richest CJK layout** when a PDF isn't
-strictly required.
+**PDF rendering (always Chromium, one layout everywhere):** `doc-gen pdf`
+renders your spec as themed HTML and prints it in Chromium — professional CJK
+line-breaking, per-glyph font fallback (Latin + 中文 mixed just works),
+justification, tables, clickable links that wrap inside the page, and the
+theme's page size and margin. Inside Talos it goes through the app's service
+(`[pdf (chromium)]`); elsewhere it uses a headless Chromium
+(`[pdf (headless chromium)]`, needs Playwright). With neither it exits 69 and
+writes nothing — tell the user the PDF could not be produced. The spec's
+`blocks` (headings/lists/tables) are supported, not just `title`/`paragraphs`.
 
 ## Fill a template — `bin/doc-fill` (preserves styling; the best "edit" path)
 
@@ -361,9 +301,13 @@ node <skill>/bin/doc-run.cjs --list          # the guaranteed module registry
 ```
 
 Inside the script, plain CommonJS `require()` of these names is guaranteed:
-`pptxgenjs` (decks) · `docx` (Word) · `xlsx` (SheetJS workbooks) ·
-`pdf-lib` (PDF assembly) · `jszip` / `pizzip` (OOXML zip surgery) ·
-`hyperformula` (formula evaluation). Nothing else is guaranteed — do not
+`pptxgenjs` (non-deck pptx only — data tables, one-off shapes; every deck goes through html2pptx) · `docx` (Word) · `exceljs` (formatted workbooks: fills,
+fonts, borders, merges, formulas) · `xlsx` (SheetJS: reading and plain-data
+workbooks only — it writes no cell styles) · `pdf-lib` (PDF assembly) ·
+`jszip` / `pizzip` (OOXML zip surgery) · `hyperformula` (formula evaluation).
+An exceljs formula is written without a cached result; run
+`bin/xlsx-recalc.cjs` on the file when the values must show before Excel
+recalculates. Nothing else is guaranteed — do not
 `require` other packages, and never run `npm install`.
 
 Rules of the tier ladder (try in this order, don't skip levels). **NOTE — decks

package/skills/document/styles/README.md

@@ -126,13 +126,6 @@ Opt-outs (auto-pick skips these; `--backdrop` still works explicitly if ever
 needed): `mckinsey`, `mono` → 纯色(no backdrop, by design) · `cinereel` → 常驻胶片
 取景框(每页恒定,故意排除在自动挑选之外).
 
-Leave `--backdrop` unset and html2pptx **auto-picks one of the skin's available
-`backdrop*.html` variants**, seeded by the deck's HTML content — the same
-deck.html always resolves to the same variant (stable across the QA fix-loop's
-re-renders), but different decks land on different variants, so repeat
-generations of the same skin don't all look identical. Pass `--backdrop
-<variant>` only when you need a specific one pinned.
-
 ## Extend
 
 Add a skin = **one `styles/<name>/skin.css`** defining the full class contract

package/skills/document/theme-system.md

@@ -43,6 +43,7 @@ rewrite a layout.
 ```json
 {
   "style": "cool",
+  "scenario": "发布会",
   "themeVersion": 2,
   "decorRhythm": "auto",
   "mediaStyle": "device-stage",

package/skills/document/themes/README.md

@@ -1,11 +1,11 @@
 # Built-in themes
 
-**12 套主题**,`doc-gen --theme themes/<name>.json` 或 `html2pptx --theme` 使用。每个文件
-是 doc-theme 契约的纯 JSON(`bestFor` = 适用场景)。
+**12 套主题**,给 `doc-gen --theme themes/<name>.json`(Word/PDF 文档)使用;`html2pptx --theme`
+是 legacy 路径,deck 一律用 `--style <catalog id>`。每个文件是 doc-theme 契约的纯 JSON
+(`bestFor` = 适用场景)。
 
-**一个主题 = 一套自洽视觉**,与一个 `templates/<家族>` **一一对应**:主题管**颜色 / 字体**,
-家族管**版式**(slide 布局 + 签名装饰)。用户选一次主题 = 同时定了配色和布局。
-非 deck 文档(Word/PDF/Excel)没有家族概念,只吃主题的调色板(白纸 + 品牌色标题/表格)。
+主题只管**颜色 / 字体**;"配对家族"一列是同名 deck 风格(`catalog.json` 的 entry),
+方便文档与 deck 配色一致。非 deck 文档没有版式概念,只吃主题的调色板(白纸 + 品牌色标题/表格)。
 
 | 主题 | 配对家族 | 基调 | 适用场景 |
 |---|---|---|---|

package/skills/document/themes/anthropic-clay.json

@@ -33,12 +33,6 @@
   "pptx": {
     "background": "#f0eee6",
     "titleColor": "#191919",
-    "textColor": "#191919",
-    "titleSize": 26,
-    "bodySize": 16,
-    "motif": "none",
-    "bgWash": true,
-    "depth": true,
-    "slideNumber": true
+    "textColor": "#191919"
   }
 }

package/skills/document/themes/apple-keynote.json

@@ -25,12 +25,6 @@
   "pptx": {
     "background": "#000000",
     "titleColor": "#f5f5f7",
-    "textColor": "#f5f5f7",
-    "titleSize": 32,
-    "bodySize": 18,
-    "motif": "none",
-    "bgWash": true,
-    "depth": false,
-    "slideNumber": false
+    "textColor": "#f5f5f7"
   }
 }

package/skills/document/themes/black-gold.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#0b0b0d",
     "titleColor": "#f5e6b8",
-    "textColor": "#cbbd97",
-    "slideNumber": true
+    "textColor": "#cbbd97"
   }
 }

package/skills/document/themes/cinereel.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#0D0D0C",
     "titleColor": "#F5F4F0",
-    "textColor": "#C7C5BE",
-    "slideNumber": true
+    "textColor": "#C7C5BE"
   }
 }

package/skills/document/themes/cool-tech.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#0a0e1a",
     "titleColor": "#ffffff",
-    "textColor": "#aab6d4",
-    "slideNumber": true
+    "textColor": "#aab6d4"
   }
 }

package/skills/document/themes/hand-drawn.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#fbfaf6",
     "titleColor": "#2b2b2b",
-    "textColor": "#3a3a3a",
-    "slideNumber": true
+    "textColor": "#3a3a3a"
   }
 }

package/skills/document/themes/ivory-gold.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#EEE8DA",
     "titleColor": "#A97C3F",
-    "textColor": "#2B2823",
-    "slideNumber": true
+    "textColor": "#2B2823"
   }
 }

package/skills/document/themes/magazine-ink.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#F1F3F5",
     "titleColor": "#0A1F3D",
-    "textColor": "#384962",
-    "slideNumber": true
+    "textColor": "#384962"
   }
 }

package/skills/document/themes/mckinsey-consulting.json

@@ -41,12 +41,6 @@
   "pptx": {
     "background": "#ffffff",
     "titleColor": "#051c2c",
-    "textColor": "#1c2b3a",
-    "titleSize": 24,
-    "bodySize": 15,
-    "motif": "none",
-    "bgWash": false,
-    "depth": false,
-    "slideNumber": true
+    "textColor": "#1c2b3a"
   }
 }

package/skills/document/themes/mono.json

@@ -14,7 +14,6 @@
   "pptx": {
     "background": "#ffffff",
     "titleColor": "#0a0a0a",
-    "textColor": "#555555",
-    "slideNumber": true
+    "textColor": "#555555"
   }
 }

package/skills/document/themes/swiss-grid.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#FAFAF8",
     "titleColor": "#0A0A0A",
-    "textColor": "#3D3D3B",
-    "slideNumber": true
+    "textColor": "#3D3D3B"
   }
 }

package/skills/document/themes/warm-editorial.json

@@ -18,7 +18,6 @@
   "pptx": {
     "background": "#f7f2ea",
     "titleColor": "#241a12",
-    "textColor": "#6b5d4c",
-    "slideNumber": true
+    "textColor": "#6b5d4c"
   }
 }

package/skills/image-layout/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: image-layout
-description: "Use this skill whenever the user wants EXISTING images combined or altered as pixels — 拼图 / 拼接 / 拼一张 / 宫格 / 九宫格 / 长图 / 对比图 / 前后对比 / 加水印 / 加标签 / 加边框 / 裁剪 / 圆角 / 缩放, or stitch / combine / merge images / collage / contact sheet / side-by-side / before-after / watermark / label / crop / round corners / resize. Examples: 'combine these four into one picture', '把生成的几张图拼成九宫格', 'add a caption under each'. Method: HTML+CSS rendered by this skill's bin/html2img.cjs. The mechanical test: if the images do not exist as files yet, this is NOT the skill. Do NOT trigger for: generating NEW images, INCLUDING when the request names a layout word — '生成一张九宫格的图' asks for ONE generated picture whose COMPOSITION is a grid, not for tiling existing files; documents / PDF / PowerPoint (document skill); Xiaohongshu cards (talos-xhs-ops); or upscaling / background removal / content-aware fill, which need a model, not CSS."
+description: "Use when EXISTING images (files already on disk) are combined or altered as pixels: 拼图 / 拼接 / 宫格 / 九宫格 / 长图 / 对比图 / 加水印 / 加标签 / 裁剪 / 圆角 / 缩放, stitch / combine / collage / contact sheet / side-by-side / before-after / watermark / label / crop / resize. The mechanical test: if the images do not exist as files yet, this is NOT the skill. Do NOT trigger for generating NEW images, INCLUDING when the request names a layout word ('生成一张九宫格的图' is one generated picture); documents (document skill); Xiaohongshu cards (talos-xhs-ops); or upscaling / background removal, which need a model."
 license: Proprietary. LICENSE.txt has complete terms
 ---
 

package/skills/cozy-static-svg/SKILL.md

@@ -1,76 +0,0 @@
----
-name: cozy-static-svg
-description: "手工编写纯静态 SVG 插画：柔和渐变、圆润主体、舒适留白，可配温柔短句或贴题的唐宋诗词；色系自由、默认明快。适用于手绘 SVG、静态插画、治愈插画、诗词配图、沿用上次画风、再画一张等请求。"
----
-
-# 温柔静态 SVG 插画
-
-## 使用依据与范围
-
-用户以《月亮替你值夜班》为准，认可这套画风、精细度与制作流程；要求**手写直出原生 SVG、不转 PNG**：以速查表约束画风，以质检脚本守住最后质量。
-
-- 认可原作：`references/moon_keeps_watch.svg`；风格参考：`references/approved-preview.png`。
-- **速查与配方（每幅开画前必读）**：`references/style-anchor.md`。
-- **跨平台速查**：`references/cross-platform.md`（macOS / Windows 命令对照、字体差异、转 PNG、故障对照）。
-- **脚本（两平台共用同一份，不写死绝对路径）**：`scripts/artkit.py` 质检（结构校验＋画风合规报告，秒级，不出图、不转 PNG；文件 / 目录 / 通配符都收，纯标准库）；`scripts/to_png.py` 转 PNG（仅在用户明确要 PNG 时用，跨平台自动挑后端）。
-- 首幅或题材类型首次出现时，可对照原作与风格参考复习一次；之后速查表＋质检即可。
-- 固定的是画风、方法、完成度，不是题材；不要每张重复同一主体、结构或坐标；成批出图按速查表的「题材轮换」主动错开。
-- 拼接已有作品用 image-layout 技能，保持原图，不要用简化重绘冒充。
-- 不改动原作母版；每次新建独立文件。
-
-## 提速工作流（默认按此执行）
-
-1. **一句话定创意**：主体姿态＋环境结构＋主光源位置。用户给了内容就直接用，不追问低风险细节。
-2. **读速查表**：`references/style-anchor.md`（画风、硬底线、题材轮换、配方与清单都在里面）。
-3. **手写整幅 SVG**：一次写全；defs+use 复用重复小元素；落盘前按速查表「开画前自查清单」过一遍。
-4. **一条命令质检**：
-
-   ```bash
-   python3 scripts/artkit.py 作品.svg      # macOS / Linux
-   py -3 scripts\artkit.py 作品.svg        # Windows
-   ```
-
-   参数给目录或通配符即为批量（如 `python3 scripts/artkit.py .`），通配符由脚本自己展开，
-   两个平台写法一致；细节见 `references/cross-platform.md`。
-   报告含结构、圆角裁切、引用、字体、调色清单、文案清单；**无 ✗ 才算过**。不通过就用 edit 精准修复（只动需要动的坐标 / 路径 / 层级），再跑一次；成功报告留着核对文案与调色。
-5. **交付**：`present_file` 直出原生 SVG；预览、脚本不交付。质检报告核对过后，直接用温柔、贴合画面意境的一两句话交付，**严禁输出“质检通过、直出原生 SVG”这类生硬的技术汇报**。
-
-- **成批出图**：先按顺序写完所有 SVG，再用一条命令批量质检（传目录或通配符即可），逐个按报告核对。
-- **不拆子 agent**：画 SVG 全程自己完成，不派子 agent、不并行外发。逐张手写、逐张落盘、最后统一质检；成批也是串行画完再批量质检，不用子 agent 分担画面。
-- **默认不渲染、不转 PNG**：直接交付原生 SVG。
-- 不调用生图模型替代手绘；不把位图包进 SVG。
-
-## 画风与底线（细节与配方见速查表）
-
-**画风（长什么样）**
-- 情绪：安静、柔软、温暖、有一点生活趣味；每张只讲一个看得懂的小故事。
-- 形状：手写贝塞尔与基础几何，圆润自然；大形先成立，细节克制；不以元素数量代替质量。
-- 构图：默认 1200×900；舒服的留白；远／中／近与承托面分层；全幅圆角由最外层 clipPath 统一裁切（含文字）。
-- 光与渐变：渐变过渡自然、层次分明、主光源统一（暖灯 / 冷月 / 落日 / 晨雾 / 日间自然光皆可）。
-
-**硬底线（不可让步，详见速查表）**
-- 明度均衡：不设固定色板——每幅按题材与情绪自由发挥、可多变；保持整幅协调；**默认明快，亮调与中间调为主，深色夜景只做少数**（原作那套夜色不是默认值）。
-- 对比度：明快不等于发飘——亮底要有深色锚点，深底要有大面积亮部；整幅留一处明确的明暗落差，且集中在少数区域。
-- 文字可读性：按文字所在区域的实际底色选色（不是按整幅平均色）；亮底深字、暗底亮字；字号越小对比要求越高；脸、轮廓、文字对比必须清楚。详见速查表的「文字可读性」。
-- 题材轮换：连续两张不同类型，每 4 张覆盖三类以上，同一母题最多两次。详见速查表的「题材轮换」。
-
-**文案与落款**
-- 上限：最多标题＋一句温柔注脚（＋少量落款）；字体栈含中文系统回退。
-- 诗词版：画面相宜时左下角可改题一首贴题的唐宋诗词（诗句两行＋出处一行），此时**去掉右下小字**，全图五处文字（左上标题、右上落款、左下诗句与出处）；标题写自己的话、诗句引原典，两者不重复。结构与对比照速查表的「诗词版」。
-- 落款名不写死：按当前使用者的称呼填写；不确定就改用中性落款（如「晚安」），宁可无名字也不要猜错。详见速查表的「落款名：按使用者替换，不要照抄」。
-
-**技术与可访问性**
-- 含命名空间；显式 width/height/viewBox；`role="img"` 与 `aria-labelledby`；title/desc 如实；纯静态、纯矢量、自包含（无动画 / 脚本 / 外链 / 位图）。
-
-## 交付前质量核对
-
-- 质检报告无 ✗：结构、圆角裁切（全部内容在框内）、引用、字体栈、静态底线。
-- 文字可读性已核对：各处文字（标题、注脚、诗词、落款、小字）在其底色上都能轻松读出来；没有低对比或横跨明暗交界的句子。
-- 对比度已核对：有一处明确的明暗落差，且集中在少数区域，没有整幅发飘或处处高对比。
-- 落款名已核对：是当前使用者的称呼，或中性落款；没有照抄示例里的名字。
-- 若用了诗词版：五处文字齐全（左上标题、右上落款、左下诗句与出处），右下无小字。
-- 成批时题材轮换已核对：连续两张不同类型，母题未超两次。
-- 整幅用色协调统一（色系自由、可多变）；文案逐句核对无错字、无残缺句。
-- 自查清单已勾完；最终交付 = 质检通过的最新版原生 SVG。
-
-

package/skills/cozy-static-svg/references/cross-platform.md

@@ -1,73 +0,0 @@
-# 跨平台速查（macOS / Windows / Linux）
-
-这套技能本体是「手写 SVG 文本 + 纯标准库 Python 脚本」，没有平台依赖。
-真正需要按系统调整的只有两件事：**质检命令怎么写**、**转 PNG 用什么工具**。
-
-## 一、质检命令
-
-脚本 `scripts/artkit.py` 只用 Python 标准库（需 **Python 3.9+**），两个平台都能跑。
-参数支持**文件 / 目录 / 通配符**——目录会递归找全部 `.svg`；通配符由脚本自己展开，
-所以 PowerShell 不必先替命令展开 `*.svg`，两边的写法才真正一致。
-
-| 场景 | macOS / Linux | Windows |
-| --- | --- | --- |
-| 单张 | `python3 scripts/artkit.py 作品.svg` | `py -3 scripts\artkit.py 作品.svg` |
-| 整批（当前目录） | `python3 scripts/artkit.py .` | `py -3 scripts\artkit.py .` |
-| 整批（通配符） | `python3 scripts/artkit.py "out/*.svg"` | `py -3 scripts\artkit.py "out\*.svg"` |
-| 严格模式 | 加 `--strict`（提示也算不合格） | 同左 |
-
-- Windows 上用 `py -3` 最稳；若装了新版 Python 且 PATH 里有 `python`，也可用 `python scripts\artkit.py`。
-- 脚本已强制 UTF-8 输出，中文报告在 PowerShell / cmd 里不会乱码；个别老终端若仍乱码，先跑 `chcp 65001`。
-- 退出码：0 通过，1 有不合格项 —— 可接进任何平台的脚本里做关卡。
-
-## 二、转 PNG（默认不做，用户明确要才做）
-
-默认工作流是**直出原生 SVG，不转 PNG**。用户明确要 PNG 时用 `scripts/to_png.py`，
-它自动探测本机可用的后端，两个平台命令一致：
-
-```bash
-python3 scripts/to_png.py 作品.svg              # macOS / Linux
-py -3 scripts\to_png.py 作品.svg                # Windows
-python3 scripts/to_png.py --scale 2 .           # 整目录，2 倍图
-python3 scripts/to_png.py -o out 作品目录        # 指定输出目录
-```
-
-后端优先级：`rsvg-convert` → `inkscape` → `cairosvg` → `chrome/edge`（找不到可用的会给出安装提示）。
-也可以 `--backend inkscape` 手动指定。
-
-| 后端 | macOS | Windows | 备注 |
-| --- | --- | --- | --- |
-| rsvg-convert | `brew install librsvg` | MSYS2 `pacman -S mingw-w64-x86_64-librsvg` | 与手绘流程同源，首选 |
-| Inkscape | `brew install --cask inkscape` | 官网安装包（自带你丢命令行） | 图形界面顺手可编辑 |
-| cairosvg | `pip install cairosvg` | 同左（wheel 自带 cairo） | 纯 Python 路线 |
-| chrome / edge | 系统已有 Chrome/Edge 即可 | 系统自带 Edge 即可 | 零安装兜底，`--backend chrome` |
-
-- 默认**保留透明底**（画风四角是圆角）；要白底加 `--background FFFFFF`。
-- 不指定尺寸时按 SVG 原始宽高输出（默认画布 1200×900），`--scale 2` 得 2400×1800。
-- 不要用「截图整个屏幕」的方式凑 PNG；也不要把位图塞回 SVG。
-
-## 三、字体差异（唯一会看出区别的地方）
-
-字体栈固定为 `'PingFang SC','Noto Sans CJK SC','Microsoft YaHei',sans-serif`：
-
-- macOS → **苹方**（PingFang SC）；Windows → **微软雅黑**（Microsoft YaHei）；两者都不会掉成方块。
-- 字形与字宽略有差异（雅黑略宽、笔画更方），同一句话两平台占宽差几个百分点。
-  本套画风标题与注脚都留了大片留白，**不会溢出画布**；做像素级对齐要求极高的活儿时，
-  要么目标平台上装苹方（字体授权自行确认），要么把文字转成路径（代价：以后不能改文案）。
-- Linux 上若两者都没有，装 `fonts-noto-cjk` 即可命中第二顺位。
-
-## 四、常见问题对照
-
-| 现象 | 处理 |
-| --- | --- |
-| `python3: command not found`（Windows） | 改用 `py -3`；或到 python.org 装新版并勾选 Add to PATH |
-| PowerShell 报找不到 `*.svg` | 参数用目录 `.`，或给通配符加引号 `"out\*.svg"`，脚本会自己展开 |
-| 报告中文乱码 | 脚本已强制 UTF-8；老终端再执行 `chcp 65001` |
-| `rsvg-convert` 不存在（Windows） | 用 `--backend inkscape` 或 `--backend chrome`（系统自带 Edge） |
-| PNG 四角是透明格子 | 正常，画风就是圆角；要白底加 `--background FFFFFF` |
-| 提示缺少 Python 版本 | 需 3.9+（用到 `str.removesuffix`），脚本会直接告诉你当前版本 |
-
-## 五、底线
-
-- 交付物永远是**质检通过的原生 SVG**；PNG 只是复制品，改图只改 SVG 源文件。
-- 两个平台跑同一份 `scripts/`，不各自维护两套；路径一律相对技能目录，不写死绝对路径。