@tycoworks/tycoslide 0.15.0 → 0.16.0

package/docs/theme.md

@@ -0,0 +1,144 @@
+# theme.json reference
+
+`theme.json` sits at the root of a theme package next to `template/`. It maps author-facing names onto shapes in the template `.pptx`: each layout names one slide, each parameter or slot names one shape on it. The template is never edited. At build time the engine clones the named slide, rewrites the named shapes, and removes any optional shape the author left unfilled. Every object is strict: an unknown key fails the load with `theme.json: invalid theme config` and `Unknown key(s): x. Valid keys: ...`.
+
+The one trap is `slideNumber`. It is the number in the file name `ppt/slides/slideN.xml`, not the slide's position in the deck. Reordering slides in PowerPoint changes positions but not file names. Always use the file number in `slideNumber` and `sourceSlide`.
+
+## `template`
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `template` | File name of the `.pptx`, resolved inside the theme's `template/` folder. Required. | `File not found: <path>` at build; `Theme declares "template/<name>", but no such file exists` at package. |
+
+## `layouts[]`
+
+One entry per slide the author may pick. Two layouts may not share a `slideNumber`; the load fails with `Layouts "A" and "B" share slideNumber N`. A slide with more than one arrangement becomes one layout with a multi-accept slot, never two layouts.
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `name` | The value authors write as `layout:` in slide frontmatter. Required, unique. | `unknown layout "xyz"` at deck compile, listing the valid names. |
+| `slideNumber` | File number of the slide to clone. Required. | Wrong slide is cloned; no error, wrong content. |
+| `description` | Neutral prose about the arrangement, shown to deck authors. Optional. | None. |
+| `variant` | `"light"` or `"dark"`: the surface the code panel sits on. Optional, required when `codeTheme` is a pair and the layout takes code. | `the theme's "codeTheme" is a { light, dark } pair, but this layout declares no "variant"`. |
+| `parameters` | Single-value text shapes filled from frontmatter. Required, may be `[]`. |  |
+| `slots` | Body regions filled from `::key::` markdown regions. Required, may be `[]`. |  |
+
+### `parameters[]`
+
+A parameter is a styled text shape whose text is rebuilt from a template string. The `{key}` placeholders are the frontmatter keys authors fill. There is no separate key field. A key may appear in only one parameter per layout: `key "title" (parameter "...") is declared twice`. Parameter shape names and slot keys share one namespace: `name "body" (slot) collides with another parameter or slot`.
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `shapeName` | Exact name of the text shape on the layout's slide. Required. | The build prints `Can't find element on slide N in source:` and leaves the placeholder text in place. |
+| `template` | The shape's full text with `{key}` placeholders; `\n` is a line break. Required. | `template has 2 lines but the shape has only 1 visual line(s)`; or `its styled sample text "..." does not fit the template` when styles inside a line do not match the placeholders. |
+| `required` | Whether the author must supply the keys. Optional, default `false`; an unfilled optional parameter has its shape removed. | `parameter "X" is marked required but its template has no keys to fill`; at compile, `requires parameter "X" (keys: ...); none provided`. |
+
+Keys match `[A-Za-z0-9_]+`. Write `{{` or `}}` for a literal brace. A shape with one line and one style is the safe case. A line that mixes styles must place a literal or style boundary between two placeholders, or the load fails with `variables "{a}" and "{b}" are adjacent with no separator`.
+
+### `slots[]`
+
+A slot is a body region. The author's markdown shape picks which accepted block fills it: prose or a code fence routes to `text`, a GFM table to `table`, an image reference or mermaid fence to `image`.
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `key` | The `::key::` region name. Required, unique within the layout. | `unknown slot "::x::" in layout "..."` at compile. |
+| `accepts` | The blocks this slot can become, at most one per `type`. Required. | `accepts two text blocks; each content type may appear once.` |
+| `frame` | `{x, y, cx, cy}` in EMU: the region a transplanted shape is positioned into. Required when any block's `sourceSlide` differs from `slideNumber`, otherwise optional. | `Layout "X" slot "y": a transplant block (sourceSlide ≠ N) requires a "frame"`. |
+| `required` | Whether the author must fill the region. Optional, default `false`; an unfilled optional slot has its shape removed. | `layout "X" requires slot "y"; none provided`. |
+
+### Blocks inside `accepts`
+
+Each block is discriminated by `type` and carries only its own option. A `bodyRows` on a text block or a `startAt` on a table block is an unknown key and fails the load.
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `type` | `"text"`, `"table"` or `"image"`. Required. | Schema error naming the invalid value. |
+| `sourceSlide` | File number of the slide carrying the specimen shape. Required. | Wrong shape cloned, or `Can't find element on slide N`. |
+| `shapeName` | Exact name of the specimen shape on `sourceSlide`. Required. | `Can't find element on slide N in source:` and the placeholder remains. |
+| `startAt` | Text only. Leave the first N specimen paragraphs untouched and rebuild from paragraph N. Optional, default 0. | `startAt 3 is past the last paragraph (shape has 2)`. |
+| `bodyRows` | Table only. `[start, end]`, 0-based inclusive: the rows that repeat for data. Required. Row 0 is always the header. Rows above `start` and below `end` render once, as fixed rows. | `bodyRows [s, e] is out of range; require 1 <= start <= end <= R-1 (row 0 is the header)`; `has no <a:tbl> element (is it actually a table?)`. |
+
+For an image block the shape must be a real picture: `is not a picture (missing <a:off>, <a:ext>, <p:blipFill>, or <p:cNvPr>)`.
+
+Transplants: a block whose `sourceSlide` differs from the layout's `slideNumber` is copied from that other slide onto the cloned slide, positioned into the slot's `frame`. The shape the slot replaces on the base slide is removed. This is how one slot accepts both text and a table when the styled table lives on a different slide, as the worked example's `Content` layout does with a table from slide 15. The frame is the observed `<a:xfrm>` of the shape being replaced, so a text block in the same slot fills in place and the table lands exactly where the text was. The transplanted shape is positioned and sized to the frame, so its own size on the source slide does not matter.
+
+## `fonts`
+
+Optional array of `@font-face` entries used only when rendering mermaid diagrams. PPTX text keeps the template's own fonts. Declare weights 400 and 700 for each family to avoid synthetic bold.
+
+| Field | Meaning | Error when wrong |
+|---|---|---|
+| `family` | CSS family name; must equal the mermaid variant's `fontFamily`. Required. | Warning `fontFamily "X" matches none of the declared theme fonts`, then a substitute font. |
+| `path` | A package specifier such as `@fontsource/inter/files/inter-latin-400-normal.woff2`, or a `./` or `/` file path. Required. | `could not resolve "path" from <rootDir>`; `file not found at ...`; `unsupported format ".otf"`. Supported: woff2, woff, ttf. |
+| `weight` | OpenType weight. Optional, default 400. | None. |
+
+## `codeTheme`
+
+Optional. A Shiki theme id such as `"github-light"`, or a pair `{ "light": "...", "dark": "..." }`. Required as soon as any deck uses a code fence: `deck contains a code fence but the theme declares no "codeTheme"`. A pair requires `variant` on every layout that takes code; each layout's `variant` picks the arm.
+
+## `mermaid`
+
+Optional record of named color variants. The record keys are free; every variant must carry all eleven fields. Colors are hex strings.
+
+| Key | Meaning |
+|---|---|
+| `primary` | Node fill color. |
+| `primaryContrast` | Text color on `primary` nodes. |
+| `text` | Default text, title and node label color. |
+| `line` | Edge and arrow color. |
+| `surface` | Subgraph, secondary node and edge-label background. |
+| `surfaceBorder` | Border color for nodes and subgraphs. |
+| `fontFamily` | CSS family name; match a `fonts` entry. |
+| `accents` | Array of colors assigned in order to `class` groups in a flowchart. |
+| `accentOpacity` | Percent, 0 to 100, applied to accent and subgraph fills. |
+| `accentTextColor` | Text color inside accent-classed nodes. |
+| `groupCornerRadius` | Subgraph corner radius in pixels; 0 for square. |
+
+A missing block fails with `theme has no "mermaid" block`.
+
+## `mermaidVariant`
+
+Optional string naming a key of `mermaid`. Required as soon as any deck has a mermaid fence: `declares no "mermaidVariant"`. A name that is not a key fails with `mermaid variant "x" not found in theme. Available variants: ...`. One variant per theme; pick the one matching most diagram layouts.
+
+## Minimal complete example
+
+```json
+{
+  "template": "composition.pptx",
+  "layouts": [
+    {
+      "name": "Composed",
+      "slideNumber": 1,
+      "description": "Title over one body region.",
+      "parameters": [
+        { "shapeName": "Title 1", "template": "{title}", "required": true }
+      ],
+      "slots": [
+        {
+          "key": "body",
+          "frame": { "x": 457200, "y": 1371600, "cx": 8229600, "cy": 2743200 },
+          "accepts": [
+            { "type": "text", "sourceSlide": 1, "shapeName": "Text 1" },
+            { "type": "table", "sourceSlide": 2, "shapeName": "Table 0", "bodyRows": [1, 1] },
+            { "type": "image", "sourceSlide": 3, "shapeName": "Image 0" }
+          ]
+        }
+      ]
+    },
+    {
+      "name": "TextOnly",
+      "slideNumber": 4,
+      "parameters": [],
+      "slots": [
+        { "key": "body", "accepts": [{ "type": "text", "sourceSlide": 4, "shapeName": "Text 1" }] }
+      ]
+    }
+  ]
+}
+```
+
+`TextOnly` has no `frame` because its only block lives on its own slide. `Composed` needs one because two blocks are transplants.
+
+## Full example
+
+The tycoworks theme is a complete 18-layout theme with a multi-accept slot, `variant`, a `codeTheme` pair, light and dark `mermaid` variants, and `fonts`: https://github.com/tycoworks/tycoworks-theme/blob/main/theme.json

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@tycoworks/tycoslide",
-  "version": "0.15.0",
-  "description": "Create editable, on-brand PowerPoint slides from markdown, using your existing .pptx templates.",
+  "version": "0.16.0",
+  "description": "Create editable PowerPoint slides from markdown, using your existing .pptx templates.",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -11,6 +11,7 @@
   "files": [
     "dist",
     "bin",
+    "docs",
     "theme-package"
   ],
   "engines": {

package/theme-package/SKILL.md

@@ -13,21 +13,22 @@ Before first use, install dependencies from the theme root:
 
 ```bash
 npm install
+unzip -nq assets.dat
 ```
 
-This installs the tycoslide engine and its dependencies. You only need to do this once.
+This installs the tycoslide engine and its dependencies, and unpacks the theme's images so you can copy them into decks. You only need to do this once. If there is no `assets.dat`, skip the unzip.
 
 
 ## Overview
 
-This skill builds on-brand decks from a markdown deck file. The theme provides slide layouts that control design. Your job: pick the right layouts, fill them with content, and build. You never restyle the layout; the engine clones the real slides, so brand, layout, fonts, and chrome come for free.
+This skill builds decks from a markdown deck file. The theme provides slide layouts that control design. Your job: pick the right layouts, fill them with content, and build. You never restyle the layout; the engine clones the real slides, so brand, layout, fonts, and chrome come for free.
 
 ## Quick Reference
 
 | Task | Guide |
 |------|-------|
 | Discover layouts | Read `manifest.json` |
-| Find a logo, illustration or icon | Search `assets.json` |
+| Find a logo, illustration or icon | Search `assets.json`, then copy it next to the deck (see [Images](#images)) |
 | Write a deck (structure, slots, assets) | See [Creating Slides](#creating-slides) below |
 | Fix build errors | See [QA](#qa-required) below |
 
@@ -35,88 +36,33 @@ This skill builds on-brand decks from a markdown deck file. The theme provides s
 
 ## Layout Discovery
 
-Before writing anything, read `manifest.json`. It lists the theme's **layouts** -- for each: `name`, `description`, `parameters` (frontmatter inputs) and `slots` (body regions). A layout is identified by its `name`; every parameter and slot by its `key`. Parameters carry a `type`, slots carry `accepts`, and either may be `required`.
+Before writing anything, read `manifest.json`. It lists the theme's **layouts** -- for each: `name`, `description`, `parameters` (frontmatter inputs) and `slots` (body regions). A layout is identified by its `name`; every parameter and slot by its `key`. Slots carry `accepts`, and either may be `required`.
 
-Pictures live in `assets.json`: every logo, illustration and icon the theme offers, keyed by category and name. **Search it, do not read it whole** -- an icon set alone can run to thousands of entries. Grep for it and use the `$category.name` you find -- but **search for what the icon depicts, not what you mean by it**: a catalog is indexed by picture, so "freshness" finds nothing while `grep -i "clock" assets.json` and `grep -i "bolt"` find the icon you wanted.
-
-A layout's inputs split two ways (see [syntax.md](syntax.md) for details):
-- **parameters** -- one value on a frontmatter line. Fill by putting a value under the parameter's key in the slide frontmatter.
-- **slots** -- a multi-line region in the body. Accept types: `text`, `table`, `image`. Fill as a `::key::` region, using the slot's `key` from the manifest; a fenced code block routes to a `text` slot, a fenced mermaid block to an `image` slot.
-
-A slot may accept more than one content type -- the manifest lists each slot's `accepts`, and the shape of the content you write selects which one.
-
-Parameters and slots you leave unfilled are dropped from the slide, so a layout with numbered slots (several sections, stats, columns) renders only the ones you fill -- fill as many as you have.
+A layout's inputs split two ways, parameters and slots; see [markdown.md](node_modules/@tycoworks/tycoslide/docs/markdown.md#parameters-and-slots) for how to fill each. Unfilled ones are dropped, so fill as many of a layout's numbered slots (sections, stats, columns) as you have content for.
 
 Study each layout's `slots` before writing any slides.
 
----
+### Images
 
-## Creating Slides
+Images live in `assets.json`: every logo, illustration and icon the theme offers, keyed by category and name, each with a `path`, a `fit` and a `description`. **Search it, do not read it whole** -- an icon set alone can run to thousands of entries. **Search for what the icon depicts, not what you mean by it**: a catalog is indexed by image, so "freshness" finds nothing while `grep -i "clock" assets.json` and `grep -i "bolt"` find the icon you wanted.
 
-> **Every layout, parameter, and slot name in the examples below is a placeholder.** Your theme's real names live in `manifest.json` — read it first, and never assume a name shown in an example exists in your theme.
+To use an image, copy it into your deck's folder at the same relative path, then write its `path` and `fit` in the image:
 
-Write a deck file in markdown. The file starts with a global frontmatter block declaring the theme, followed by slides separated by `---`.
+```bash
+mkdir -p <deck dir>/assets && cp <theme dir>/assets/hub.png <deck dir>/assets/
+```
 
 ```markdown
----
-theme: ./theme.json
----
-
----
-layout: Title             # ← a layout from your manifest.json
-title: Q2 Business Review # ← a parameter that layout declares
-subtitle: Engineering Division
----
-
----
-layout: Quote dark
-quote: Great products are built by great teams.
-attributionName: Jane Smith
-attributionTitle: CEO, Acme Corp
-logo: assets/clients/acme.png
----
+![Central hub connecting three services](assets/hub.png "fit: scale-down")
 ```
 
-A text shape that holds several lines (e.g. an attribution with a name over a title) surfaces as one key per line -- fill each as its own scalar (`attributionName`, `attributionTitle` above), never as a YAML list.
-
-### File structure
-
-A deck file has three parts:
+If your deck is in the theme folder, the file is already there, so skip the copy. An image the user gives you also goes in the deck's folder; choose its fit by looking at it (`contain` unless it is full-bleed art that may crop). Write alt text for this slide, describing what the image shows here rather than repeating the catalog description.
 
-1. **Global frontmatter** (required) -- the first `---`-delimited block. Must contain `theme:` pointing to the theme config file. The output `.pptx` is written next to the deck, named after it (`deck.md` → `deck.pptx`).
-2. **Slides** -- each begins with a `---` separator. A slide's frontmatter sits between `---` delimiters. Body content follows the closing `---`.
-3. **Slide separators** -- a `---` on its own line separates slides.
-
-### Slide frontmatter
-
-Every slide must have a `layout:` key. All other frontmatter keys map 1:1 to the layout's **parameters**. A value containing a colon-then-space must be quoted -- `title: "The change: compute on the difference"` -- or YAML reads it as a second key and the build fails.
-
-```yaml
 ---
-layout: Body
-title: Key Achievements
-subtitle: This Quarter
----
-```
-
-- `layout` is required and consumed by the compiler (not forwarded as content).
-- All other frontmatter keys fill parameters: `title` fills the `title` parameter, `subtitle` fills the `subtitle` parameter, etc. A multi-line text shape surfaces as several keys (e.g. `name` + `jobTitle`); fill each as its own scalar line.
-- Slots (accepting `text`, `table`, `image`) are filled by body regions, not frontmatter -- see below.
-- A slide may also carry a `notes:` block in frontmatter -- plain-text speaker notes for the slide's notes page (see [syntax.md](syntax.md#speaker-notes)). It is slide-level metadata, not a parameter or slot.
-
-### Body content, slots, and formatting
-
-See [syntax.md](syntax.md) for the full syntax reference: body content (paragraphs, bullets, nesting), inline formatting (bold, italic, strikethrough, underline, hyperlinks), named slots (`::key::` markers), and the parameter/slot split (slots accept: text, table, image).
-
-### Build
 
-Build the deck (replace `<deck.md>` with your deck file):
-
-```bash
-npx tycoslide build <deck.md>
-```
+## Creating Slides
 
-The `.pptx` is written next to your deck file (same directory as `<deck.md>`).
+Write a deck file in markdown, as [markdown.md](node_modules/@tycoworks/tycoslide/docs/markdown.md) describes (see its [full example](node_modules/@tycoworks/tycoslide/docs/markdown.md#full-example)), and build it as its [Build](node_modules/@tycoworks/tycoslide/docs/markdown.md#build) section shows.
 
 ---
 
@@ -142,8 +88,10 @@ Keep each slot's content to what its region comfortably holds. When content over
 - **Don't overstuff a slot** -- keep content to what its region comfortably holds; split across slides when there's too much
 - **Don't restyle the layout** -- the theme owns all design; you only fill slots
 - **Don't use an image that's wrong for the slot** -- a small slot wants a simple icon, not a dense illustration. If you get a `shrunk to X%` warning, look at the rendered slide: if the image is now too small to make out, use a simpler one. A `leaves X% of the frame empty` warning is the opposite: the image is a different shape from the slot. Neither fails the build -- judge both from the rendered slide.
-- **Don't invent layout or asset names** -- only use layouts from `manifest.json` and assets from `assets.json`
-- **Don't leave required parameters or slots empty** -- and don't leave a placeholder logo or dummy text in an image slot you care about
+- **Don't skip alt text** -- describe what a meaningful image shows and why it's there, not "image of". Leave it empty only for decoration, such as backgrounds and icons beside a heading.
+- **Don't crop what can't be cropped** -- copy the `fit` from `assets.json`. For your own images, never `fit: cover` a diagram, chart, screenshot or logo.
+- **Don't invent layout names or image paths** -- layouts come from `manifest.json`, and theme images from `assets.json`, copied next to the deck
+- **Don't leave required parameters or slots empty** -- and don't leave a placeholder logo or dummy text in an image slot you care about. If you don't have a suitable image, ask the user for one.
 
 ---
 
@@ -153,17 +101,12 @@ Keep each slot's content to what its region comfortably holds. When content over
 
 Your first draft almost never comes out clean. Approach QA as a debugging session, not a confirmation step. If you haven't run at least one build-fix cycle, you're not done.
 
-Build the deck again ([Build](#build)) and read the output carefully. Common errors and fixes:
+Build the deck again ([Build](node_modules/@tycoworks/tycoslide/docs/markdown.md#build)) and read the output carefully. Common errors and fixes are in [markdown.md](node_modules/@tycoworks/tycoslide/docs/markdown.md#build), and layout names are in `manifest.json`. Also:
 
 | Error | Fix |
 |-------|-----|
-| `unknown layout "xyz"` | Check layout names in `manifest.json` |
-| A parameter or slot didn't fill | Use the key names the layout declares -- parameters in frontmatter, slots as body regions |
-| An image didn't swap / placeholder remains | Write a `::key::` region using the image slot's key, containing `![]($category.name)` from `assets.json` |
-| YAML parse error | Fix the YAML syntax in the slide's frontmatter |
-| `Skipped setting relation target` | The asset image couldn't be placed; check the path and file |
-| `forbidden style directive` | Remove `style`, `classDef`, `linkStyle`, or `%%{init}` from your mermaid block -- use `class` for grouping instead |
-| `no "mermaid" block` | The theme has no mermaid color config -- add a `mermaid` section to theme.json |
+| An image didn't swap / placeholder remains | Write a `::key::` region using the image slot's key, containing `![alt](path "fit: …")` with the path relative to the deck |
+| `image "…" not found at …` | For a theme image, copy it into the deck's folder at the path you wrote (search `assets.json`; did you unzip `assets.dat`?) |
 
 ### Verification Loop
 
@@ -211,13 +154,7 @@ Check for:
 For each issue, suggest a specific fix.
 
 Read: /path/to/deck.md and the rendered PNGs in the working directory
-Also read: manifest.json (for layout documentation); search assets.json for pictures
+Also read: manifest.json (for layout documentation); search assets.json for images
 ```
 
 If the subagent finds issues, fix them and rebuild.
-
----
-
-## Full Example
-
-See [syntax.md](syntax.md#full-example) for a complete multi-slide deck example.

package/dist/engine/rels.d.ts

@@ -1,18 +0,0 @@
-/**
- * Post-write sweep of relationships whose target part no longer exists.
- *
- * pptx-automizer's `cleanup` removes media parts that no shape embeds any more,
- * and `removeExistingSlides` drops the root template's original slide parts.
- * Neither touches the `.rels` files that named them, so a filled picture leaves
- * two dead entries behind (the template's placeholder image and automizer's
- * copy of it) and every removed template slide leaves an orphan rels file.
- * PowerPoint treats a relationship to a missing part as a damaged package.
- *
- * Runs on the written file: cleanup is the last thing automizer does during
- * `write()`, and it offers no hook after it.
- */
-export type PruneResult = {
-    removedEntries: number;
-    removedParts: number;
-};
-export declare function pruneDanglingRels(outputPath: string): Promise<PruneResult>;

package/dist/engine/rels.js

@@ -1,55 +0,0 @@
-/**
- * Post-write sweep of relationships whose target part no longer exists.
- *
- * pptx-automizer's `cleanup` removes media parts that no shape embeds any more,
- * and `removeExistingSlides` drops the root template's original slide parts.
- * Neither touches the `.rels` files that named them, so a filled picture leaves
- * two dead entries behind (the template's placeholder image and automizer's
- * copy of it) and every removed template slide leaves an orphan rels file.
- * PowerPoint treats a relationship to a missing part as a damaged package.
- *
- * Runs on the written file: cleanup is the last thing automizer does during
- * `write()`, and it offers no hook after it.
- */
-import { readFileSync, writeFileSync } from "node:fs";
-import { posix } from "node:path";
-import { DOMParser, XMLSerializer } from "@xmldom/xmldom";
-import JSZip from "jszip";
-import { Attr, Tag } from "./dom.js";
-const SLIDE_RELS = /^ppt\/slides\/_rels\/(slide\d+\.xml)\.rels$/;
-const SLIDES_DIR = "ppt/slides";
-export async function pruneDanglingRels(outputPath) {
-    const zip = await JSZip.loadAsync(readFileSync(outputPath));
-    const parts = new Set(Object.keys(zip.files).filter((name) => !zip.files[name].dir));
-    const result = { removedEntries: 0, removedParts: 0 };
-    for (const relsPart of [...parts]) {
-        const match = SLIDE_RELS.exec(relsPart);
-        if (!match)
-            continue;
-        if (!parts.has(`${SLIDES_DIR}/${match[1]}`)) {
-            zip.remove(relsPart);
-            result.removedParts++;
-            continue;
-        }
-        const doc = new DOMParser().parseFromString(await zip.file(relsPart).async("string"), "text/xml");
-        const rels = doc.getElementsByTagName(Tag.RELATIONSHIP);
-        const dead = [];
-        for (let i = 0; i < rels.length; i++) {
-            const target = rels[i].getAttribute(Attr.TARGET);
-            if (!target || rels[i].getAttribute("TargetMode") === "External")
-                continue;
-            if (!parts.has(posix.normalize(posix.join(SLIDES_DIR, target))))
-                dead.push(rels[i]);
-        }
-        if (dead.length === 0)
-            continue;
-        for (const rel of dead)
-            rel.parentNode?.removeChild(rel);
-        result.removedEntries += dead.length;
-        zip.file(relsPart, new XMLSerializer().serializeToString(doc));
-    }
-    if (result.removedEntries > 0 || result.removedParts > 0) {
-        writeFileSync(outputPath, await zip.generateAsync({ type: "nodebuffer", compression: "DEFLATE" }));
-    }
-    return result;
-}

package/dist/manifest.d.ts

@@ -1,5 +0,0 @@
-import type { CompilerThemeConfig } from "./markdown/types.js";
-/** The layouts document: read whole, so it carries no open-ended list. */
-export declare function generateManifest(config: CompilerThemeConfig): string;
-/** The catalog document: searched by name, never read whole. */
-export declare function generateAssetCatalog(config: CompilerThemeConfig): string;

package/dist/skillZip.d.ts

@@ -1,49 +0,0 @@
-import type { CompilerThemeConfig } from "./markdown/types.js";
-/**
- * Pack `paths` (theme-relative, POSIX) into one archive, reading each through
- * `read`. Entries keep their declared paths, so expanding reproduces the layout
- * `theme.json` already refers to.
- */
-export declare function packAssets(paths: string[], read: (rel: string) => Buffer): Promise<Buffer>;
-/**
- * Expand a packaged theme's archive into its directory, so the files the catalog
- * names are on disk before anything fills with them. Idempotent per file; loose
- * files win, so a stale archive never overwrites a theme's real assets; the
- * archive itself stays put. A theme with no archive -- every theme under
- * development -- returns immediately.
- */
-export declare function expandAssets(rootDir: string): Promise<void>;
-/**
- * Rewrite the `name:` value in a SKILL.md's leading YAML frontmatter so the
- * packaged skill is named after the consuming theme, not the source template.
- * Only the leading `---`…`---` block is touched; the body is left byte-for-byte.
- * Throws if there is no frontmatter or no `name:` line — the caller names the file.
- */
-export declare function renameSkill(md: string, name: string): string;
-/**
- * The `package.json` a packaged skill installs from — deliberately NOT the theme's
- * own. A theme repo's manifest is a development document: it carries the script
- * that regenerates the skill, and lists the engine as a devDependency because the
- * repo builds with it rather than shipping it.
- *
- * Copying that verbatim breaks the consumer twice. The build script runs as a
- * postinstall inside their container, so anything it touches that is read-only
- * fails their whole `npm install`. And under `--omit=dev` the engine is never
- * installed, so neither the postinstall nor `npx tycoslide build` can find it.
- *
- * What ships instead declares only what the skill needs to RUN: the theme's own
- * dependencies plus the engine, as runtime dependencies, and no scripts at all.
- */
-export declare function skillPackageJson(theme: Record<string, unknown>, engine: {
-    name: string;
-    version: string;
-}): string;
-/**
- * Zip a theme into an uploadable Agent Skill archive whose entries all live
- * under a single root folder (e.g. `acme-slides/theme.json`), matching Anthropic's
- * custom-skill format. `generated` names the files the caller just wrote (the
- * config, manifest, SKILL.md, syntax.md); `packageJson` is the authored manifest
- * from `skillPackageJson`. Optional support files are skipped when absent;
- * anything the config declares but that is missing is an error.
- */
-export declare function zipDir(rootDir: string, folderName: string, config: CompilerThemeConfig, generated: string[], packageJson: string): Promise<Buffer>;