@tycoworks/tycoslide 0.13.0 → 0.13.1

package/README.md

@@ -68,7 +68,7 @@ my-theme/
   assets/icons/
   theme.json
   package.json
-  skill.md          # generated by `tycoslide package`
+  SKILL.md          # generated by `tycoslide package`
   syntax.md         # generated by `tycoslide package`
   manifest.json     # generated by `tycoslide package` -- the theme's layouts
   assets.json       # generated by `tycoslide package` -- the theme's picture catalog

package/SKILL.md

@@ -37,7 +37,7 @@ This skill builds on-brand decks from a markdown deck file. The theme provides s
 
 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`.
 
-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 the concept you want (`grep -i "arrow" assets.json`) and use the `$category.name` you find.
+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.
@@ -89,7 +89,7 @@ A deck file has three parts:
 
 ### Slide frontmatter
 
-Every slide must have a `layout:` key. All other frontmatter keys map 1:1 to the layout's **parameters**.
+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
 ---
@@ -141,7 +141,7 @@ Keep each slot's content to what its region comfortably holds. When content over
 - **Don't repeat the same layout** -- vary layouts for visual rhythm
 - **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.
+- **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
 

package/dist/cli.js

@@ -8,9 +8,9 @@ import { compileDeck, loadThemeConfig, parseSlideDocument, RESERVED_KEY } from "
 import { renameSkill, skillPackageJson, zipDir } from "./skillZip.js";
 const DEFAULT_CONFIG = "theme.json";
 const MANIFEST_FILE = "manifest.json";
-// The theme skill is written as lowercase skill.md (copied from tycoslide's own
-// SKILL.md), so the skill folder can live at the theme repo root.
-const SKILL_FILE = "skill.md";
+// SKILL.md, uppercase: the Agent Skills format requires that exact filename at the
+// root of a skill folder, and a case-sensitive filesystem will not find any other.
+const SKILL_FILE = "SKILL.md";
 const SYNTAX_FILE = "syntax.md";
 const sdkDir = dirname(fileURLToPath(import.meta.url));
 const skillMdPath = resolve(sdkDir, "..", "SKILL.md");

package/dist/skillZip.d.ts

@@ -1,6 +1,6 @@
 import type { CompilerThemeConfig } from "./markdown/types.js";
 /**
- * Rewrite the `name:` value in a skill.md's leading YAML frontmatter so the
+ * 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.
@@ -28,7 +28,7 @@ export declare function skillPackageJson(theme: Record<string, unknown>, engine:
  * 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
+ * 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.
  */

package/dist/skillZip.js

@@ -5,7 +5,7 @@ import { TEMPLATE_DIR } from "./engine/index.js";
 const FRONTMATTER = /^---\n([\s\S]*?)\n---/;
 const NAME_LINE = /^name:[ \t]*.*$/m;
 /**
- * Rewrite the `name:` value in a skill.md's leading YAML frontmatter so the
+ * 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.
@@ -13,9 +13,9 @@ const NAME_LINE = /^name:[ \t]*.*$/m;
 export function renameSkill(md, name) {
     const block = md.match(FRONTMATTER);
     if (!block)
-        throw new Error("skill.md has no YAML frontmatter block");
+        throw new Error("SKILL.md has no YAML frontmatter block");
     if (!NAME_LINE.test(block[1]))
-        throw new Error('skill.md frontmatter has no "name:" line');
+        throw new Error('SKILL.md frontmatter has no "name:" line');
     return md.replace(block[0], block[0].replace(NAME_LINE, `name: ${name}`));
 }
 /** The manifest a packaged skill installs from, authored rather than copied. */
@@ -71,7 +71,7 @@ function skillPaths(config, generated) {
  * 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
+ * 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.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tycoworks/tycoslide",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Create editable, on-brand PowerPoint slides from markdown.",
   "type": "module",
   "main": "dist/index.js",