@vmz/vmz-skills 0.1.22 → 0.1.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/vmz-application/SKILL.md +11 -10
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vmz/vmz-skills",
3
- "version": "0.1.22",
3
+ "version": "0.1.24",
4
4
  "description": "Agent Skills for authoring, reviewing, testing, and deploying VMZ applications",
5
5
  "type": "module",
6
6
  "license": "MPL-2.0",
package/skills/vmz-application/SKILL.md CHANGED
@@ -17,22 +17,23 @@ SSR/resume behavior, `vmz test`, or deployment artifact.
17
17
  - Keep server-only imports behind `#server`; never leak secrets or repositories into browser output.
18
18
  - Prefer the official `@vmz/core`, `@vmz/ui`, `vmz`, and `@vmz/test` surfaces already present in the project.
19
19
 
20
- ## Code highlighting (Shiki — preferred)
20
+ ## Code highlighting (`default`)
21
21
 
22
- When the user needs **syntax-colored** source (docs, marketing snippets, API samples, tutorials):
22
+ When the user needs syntax-colored source:
23
23
 
24
- 1. Install and wire **`@vmz/plugin-shiki`** (peer `shiki` is fine as a dependency of the app).
25
- 2. In `vmz.config.ts`: `plugins: [shiki({ themes: […] })]` and usually `engines: { code: 'shiki' }`.
26
- 3. In templates use **`<Shiki :code="…" lang="…" theme="…" />`** or **`<Code :code="…" lang="…" />`** (facade after engines).
27
- 4. Restart **`vmz dev`** after changing `vmz.config.*` (config is not watch-reloaded).
24
+ 1. Use the `default` code highlighting contract.
25
+ 2. For build, SSR, and static export, consume the Rust-generated `NativeCodeArtifact`.
26
+ 3. For runtime highlighting, use **`@vmz/highlighter`** and install **`@vmz/highlighter-unknown-wasm32`** when unknown-language fallback is needed.
27
+ 4. For non-VMZ applications, prefer the **`vmz-highlighter`** Custom Element. It does not require the VMZ runtime.
28
28
 
29
29
  **Do not:**
30
30
 
31
- - Import `shiki` / `createHighlighter` in app components and paint HTML by hand.
32
- - Invent a local `*.vmz` highlighter, copy `Shiki.vmz` from the plugin into the app as a permanent substitute, or wrap raw `<pre>` as a fake highlighter.
33
- - Expect `@vmz/ui` **`CodeBlock`** to colorize — it is caption/Copy/`<pre>` chrome only (`CodeBlock ≠ Shiki`).
31
+ - Import a native renderer or WASM implementation directly into application components.
32
+ - Paint highlighted HTML by hand or create a second VMZ-local highlighter surface.
33
+ - Put native rendering dependencies in browser runtime or client chunks.
34
+ - Expect `@vmz/ui` **`CodeBlock`** to execute a highlighter. It consumes static artifacts or plain text and provides presentation chrome.
34
35
 
35
- Plain uncolored samples → `CodeBlock`. Colored reading experience → plugin Shiki. Editors → Monaco / CodeMirror plugins, not Shiki stretched into an editor.
36
+ Plain uncolored samples → `CodeBlock`. Runtime colored reading → `@vmz/highlighter`. Editors remain a separate editor integration, not a highlighter stretched into an editor.
36
37
 
37
38
  ## Delivery / dist layout (multi-artifact)
38
39