@tycoworks/tycoslide 0.16.0 → 0.16.1

package/README.md

@@ -4,7 +4,7 @@ Create editable PowerPoint slides from markdown, using your existing .pptx templ
 
 ## Getting started
 
-1. **Create a tycoslide theme.** Install the [create-theme](skills/create-theme) skill (`npx skills add tycoworks/tycoslide --skill create-theme`) and give an agent such as Claude Code or Codex your `.pptx`. You'll get back an npm package of mapped layouts, colors, and visual assets, like the [tycoworks-theme](https://github.com/tycoworks/tycoworks-theme).
+1. **Create a tycoslide theme.** Install the [create-theme](skills/create-theme) skill (`npx skills add tycoworks/tycoslide`) and give an agent such as Claude Code or Codex your `.pptx`. You'll get back an npm package of mapped layouts, colors, and visual assets, like the [tycoworks-theme](https://github.com/tycoworks/tycoworks-theme).
 2. **Write slides in markdown.** GitHub-flavored markdown is supported; see [Markdown support](#markdown-support) below. tycoslide themes also include an agent skill, so an agent can write the slides for you.
 3. **Build.** `npx tycoslide build deck.md` compiles the markdown into an editable PowerPoint file.
 

package/dist/agents/commands.js

@@ -3,7 +3,7 @@ import { basename, posix, resolve } from "node:path";
 import { loadThemeConfig } from "../index.js";
 import { loadAssetCatalog } from "./catalog.js";
 import { extractTemplate, summarizeExtraction } from "./extract.js";
-import { ASSETS_DIR, ASSETS_FILE, MANIFEST_FILE, PACKAGE_JSON, SKILL_FILE, SKILL_ZIP_EXT, TEMPLATE_FILE, THEME_CONFIG, THEME_PACKAGE_DIR, } from "./files.js";
+import { ASSETS_DIR, ASSETS_FILE, MANIFEST_FILE, PACKAGE_JSON, SKILL_FILE, SKILL_TEMPLATE_FILE, SKILL_ZIP_EXT, TEMPLATE_FILE, THEME_CONFIG, THEME_PACKAGE_DIR, } from "./files.js";
 import { generateManifest } from "./manifest.js";
 import { renameSkill, skillPackageJson, zipDir } from "./skill.js";
 /** The CLI's line for something written, with an optional note on what it holds. */
@@ -12,7 +12,7 @@ function wrote(target, detail) {
 }
 /** Register the agent layer's commands on the CLI program. */
 export function registerAgentCommands(program, tool) {
-    const skillMdPath = resolve(tool.root, THEME_PACKAGE_DIR, SKILL_FILE);
+    const skillMdPath = resolve(tool.root, THEME_PACKAGE_DIR, SKILL_TEMPLATE_FILE);
     program
         .command("package")
         .description("Zip the theme into an Agent Skill for AI agents")

package/dist/agents/files.d.ts

@@ -18,6 +18,7 @@ export declare const ASSETS_FILE = "assets.json";
 export declare const ASSETS_ARCHIVE = "assets.dat";
 export declare const SKILL_FILE = "SKILL.md";
 export declare const THEME_PACKAGE_DIR = "theme-package";
+export declare const SKILL_TEMPLATE_FILE = "SKILL.template.md";
 /**
  * npm's package manifest: the theme's, which names the skill, and the packaged
  * skill's own, which it installs from (authored rather than copied).

package/dist/agents/files.js

@@ -20,9 +20,11 @@ export const ASSETS_ARCHIVE = "assets.dat";
 // the root of a skill folder, and a case-sensitive filesystem will not find any
 // other.
 export const SKILL_FILE = "SKILL.md";
-// The folder holding the SKILL.md template copied into each packaged theme, kept
-// out of the repo root so skill installers do not mistake it for this repo's own skill.
+// The folder holding the deck skill that `package` puts in each packaged theme.
 export const THEME_PACKAGE_DIR = "theme-package";
+// The deck skill as tycoslide ships it, named so skill installers scanning this
+// repo don't offer it as a skill of its own; `package` writes it as SKILL_FILE.
+export const SKILL_TEMPLATE_FILE = "SKILL.template.md";
 /**
  * npm's package manifest: the theme's, which names the skill, and the packaged
  * skill's own, which it installs from (authored rather than copied).

package/docs/markdown.md

@@ -215,7 +215,7 @@ The theme owns all styling. These directives are rejected at build time:
 
 Each parameter or slot in the layout definition may declare:
 - **`accepts`** (slots, required) -- an array of `text`, `table`, `image`.
-- **`required: true`** -- the slide has no usable default and the build fails if the parameter/slot has no value (e.g. team-member photos, icon-grid icons, the quote logo).
+- **`required: true`** -- the slide has no usable default and the build fails if the parameter/slot has no value.
 - **optional (the default)** -- a parameter or slot you leave unfilled is dropped from the slide (its shape is removed), so a layout with numbered slots (e.g. up to six sections, up to four stats) renders only the ones you fill.
 
 Each layout also declares a `slideNumber` pointing at the physical slide in the theme's template -- unique per layout (one layout maps to one physical slide).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tycoworks/tycoslide",
-  "version": "0.16.0",
+  "version": "0.16.1",
   "description": "Create editable PowerPoint slides from markdown, using your existing .pptx templates.",
   "type": "module",
   "main": "dist/index.js",
@@ -26,9 +26,9 @@
     "format": "biome format --write ."
   },
   "dependencies": {
-    "@xmldom/xmldom": "^0.9.10",
+    "@xmldom/xmldom": "^0.9.12",
     "commander": "^15.0.0",
-    "image-size": "^2.0.2",
+    "image-size": "^2.0.4",
     "jszip": "^3.10.1",
     "mermaid": "^11.16.1",
     "playwright-core": "^1.62.1",

package/theme-package/{SKILL.md → SKILL.template.md}

@@ -3,6 +3,7 @@ name: slides
 description: >
   Build branded slides, presentations, pitch decks, or sales collateral as a .pptx.
   Trigger on "deck," "slides," "presentation," "pitch," ".pptx," or "build me a deck."
+compatibility: Needs Node 23.6+ and network access to npm on first use. LibreOffice (soffice) and poppler (pdftoppm) to preview slides. Chrome only if decks contain mermaid diagrams.
 ---
 
 # slides
@@ -16,7 +17,7 @@ npm install
 unzip -nq assets.dat
 ```
 
-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.
+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. Run every `npx tycoslide` command from this folder too, since that is where the engine is installed and npx finds it nowhere else.
 
 
 ## Overview
@@ -44,7 +45,7 @@ Study each layout's `slots` before writing any slides.
 
 ### Images
 
-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.
+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 -B2 "clock" assets.json` and `grep -i -B2 "bolt" assets.json` find the icon you wanted, with its path and fit on the lines above.
 
 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:
 
@@ -127,7 +128,7 @@ soffice --headless --convert-to pdf --outdir . <deck>.pptx
 pdftoppm -png -r 96 <deck>.pdf <name>
 ```
 
-Read each slide image and check for:
+LibreOffice substitutes any font it can't find, so line breaks in the images can differ slightly from PowerPoint's. Read each slide image and check for:
 
 - **Word wrapping** -- text that breaks mid-word or overflows its container
 - **Cramped text** -- content too dense for the slide area