chiltepin 0.47.5 → 0.47.6

package/README.md

@@ -34,7 +34,7 @@ Written in Markdown. Drawn by code. Checked in CI.</p>
 **Your agent writes the content. Chiltepin handles the layout.** Compose prose and typed YAML blocks in a `.md` file. Get consistent diagrams, a document you can share, and a source diff you can review.
 
 ```bash
-npx -y chiltepin demo
+npx -y chiltepin@latest demo
 ```
 
 Explore the built-in examples without creating a project. **Node.js 20+ required.**
@@ -144,10 +144,10 @@ The skill guides block selection, schema lookup, composition, and validation. Yo
 Run these commands in your project directory:
 
 ```bash
-npx -y chiltepin init
-npx -y chiltepin check
-npx -y chiltepin html docs/getting-started.md -p
-npx -y chiltepin studio
+npx -y chiltepin@latest init
+npx -y chiltepin@latest check
+npx -y chiltepin@latest html docs/getting-started.md -p
+npx -y chiltepin@latest studio
 ```
 
 `init` creates a config and two starter documents, skipping existing files. `html -p` opens the rendered page. `studio` opens the local visual editor.
@@ -156,7 +156,7 @@ To pin the CLI in your project:
 
 ```bash
 npm install --save-dev chiltepin
-npx chiltepin check
+npx chiltepin@latest check
 ```
 
 See the [getting started guide](https://github.com/jdiejim/chiltepin/blob/main/docs/guides/getting-started.md) for the full workflow. `chiltepin skill` also prints the guide for tools with a system-prompt field.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chiltepin",
-  "version": "0.47.5",
+  "version": "0.47.6",
   "description": "Documentation-as-code CLI: write Markdown with typed YAML blocks for API docs, architecture & system design (C4, ERDs, sequence diagrams), frontend & design systems, ADRs and decision records, planning, and slide presentations. Validate like code with `chiltepin check`, export to HTML, slides, or PDF. AI-native — one-command agent skill (npx skills add jdiejim/chiltepin -g -y) and a visual Studio.",
   "license": "MIT",
   "type": "module",

package/templates/skill/SKILL.md

@@ -31,7 +31,7 @@ messages:
 ## Fast path
 
 Use the project's installed CLI (`pnpm exec chiltepin` or `npx --no-install chiltepin`)
-to match its dependency version. Otherwise, `npx -y chiltepin …` downloads and
+to match its dependency version. Otherwise, `npx -y chiltepin@latest …` downloads and
 runs the published CLI. In the Chiltepin source repo, use the built
 `node packages/cli/dist/bin.js`. The commands below show the fallback form.
 
@@ -42,28 +42,28 @@ at the end explains which reference each task needs.
    request. Use the table below. For a full doc, two to five structural blocks
    often suffice. A single diagram request needs only that diagram. Use prose
    when a small list communicates the same information more clearly.
-   Unsure which block exists: `npx -y chiltepin block` lists all 107 block types.
-2. **Look up each block you will write**: `npx -y chiltepin block <type>`.
+   Unsure which block exists: `npx -y chiltepin@latest block` lists all 107 block types.
+2. **Look up each block you will write**: `npx -y chiltepin@latest block <type>`.
    It prints the fields, enums, terse one-line forms, and a validating
    example. Read a family selection sheet only when the choice remains unclear.
 3. **Write the doc.** For a full doc, put `meta` first (title, subtitle, tag). A `##` heading
    above a block is its title. Prose carries why and consequence, never a
    description of the block below it. Rules in the two sections after the
    table.
-4. **Check**: `npx -y chiltepin check <file> --json`. Every diagnostic carries
+4. **Check**: `npx -y chiltepin@latest check <file> --json`. Every diagnostic carries
    a stable code and the failing value; `reference/check.md` maps each code
    to its fix. Fix errors and rerun while you make progress. Stop and report
    the blocker if a diagnostic repeats without a new fix or needs missing facts.
    Warnings do not fail the check by default; review them and report relevant ones.
    A non-zero exit is never "done". If the CLI is unavailable, report validation
    as unverified. Never invent a successful check.
-5. **Render**: after a clean check, `npx -y chiltepin html <file>` writes
+5. **Render**: after a clean check, `npx -y chiltepin@latest html <file>` writes
    `<file>.html` next to the source, so the reader gets the page as well as
    the Markdown. Add `-p` to open it. For a deck, `slides <file>` instead.
 
 Handoff: the `.md` and `.html` paths, the actual check result, and any
 unresolved diagnostics. Then one line on what to do next: open the `.html`
-in a browser, or run `npx -y chiltepin studio` to edit the document visually.
+in a browser, or run `npx -y chiltepin@latest studio` to edit the document visually.
 Explain block selection only when the user asks or a tradeoff needs explanation.
 
 Editing an existing doc: read it whole first. Change the one block, and

package/templates/skill/reference/blocks/INDEX.md

@@ -2,7 +2,7 @@
 
 Part of the **chiltepin** skill (the hub is `SKILL.md`, two folders up). One
 line per block, mapped to the family file that holds its selection guidance.
-For a block's fields and a validating example, run `npx -y chiltepin block
+For a block's fields and a validating example, run `npx -y chiltepin@latest block
 <type>`; bare `chiltepin block` prints this same list. Twelve old block names
 remain valid as permanent aliases — see the table at the bottom.
 

package/templates/skill/reference/check.md

@@ -15,7 +15,7 @@ chiltepin build                       # static site (index + nav + cross-doc lin
 chiltepin sync openapi spec.yaml --out docs/api.md   # doc from an OpenAPI spec
 ```
 
-Prefix every command with `npx -y chiltepin` when `chiltepin` is not on PATH.
+Prefix every command with `npx -y chiltepin@latest` when `chiltepin` is not on PATH.
 
 `chiltepin check` exits non-zero on any error and names the file, line, and
 offending value. Warnings never fail the check, but read each one: most name a

package/templates/skill/reference/writing.md

@@ -3,7 +3,7 @@
 Read this file when a YAML question is not answered by `chiltepin block <type>`.
 It holds the block grammar, the full terse-item table, the YAML traps, the
 reference scheme, and the naming rules. The field contract and an example
-for every block come from `npx -y chiltepin block <type>`.
+for every block come from `npx -y chiltepin@latest block <type>`.
 
 ## How a block looks