@vmz/vmz-skills 0.0.0 → 0.1.14
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.
- package/README.md +33 -2
- package/package.json +16 -5
- package/skills/vmz-application/SKILL.md +37 -0
package/README.md
CHANGED
|
@@ -1,3 +1,34 @@
|
|
|
1
|
-
#
|
|
1
|
+
# `@vmz/vmz-skills`
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Agent Skills for building with VMZ. Install the skill in a project, then describe the application outcome you want: the agent can place components, choose client/server boundaries, run the right VMZ checks, and explain generated artifacts.
|
|
4
|
+
|
|
5
|
+
## Install
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
npx skills add @vmz/vmz-skills --skill vmz-application -y
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
Preview or install globally:
|
|
12
|
+
|
|
13
|
+
```bash
|
|
14
|
+
npx skills add @vmz/vmz-skills --list
|
|
15
|
+
npx skills add @vmz/vmz-skills --skill vmz-application -y -g
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Requires Node.js 18+ for the installer. The skill is docs-only and does not pretend to replace the VMZ CLI or runtime.
|
|
19
|
+
|
|
20
|
+
## Start with a prompt
|
|
21
|
+
|
|
22
|
+
```text
|
|
23
|
+
Create a VMZ page for a searchable customer list. Keep data access server-only,
|
|
24
|
+
make the table interactive, and tell me which conformance checks prove the boundary.
|
|
25
|
+
|
|
26
|
+
Review this .vmz component for accidental client imports, oversized hydration,
|
|
27
|
+
and state updates wider than the affected regions.
|
|
28
|
+
|
|
29
|
+
Explain why this component became an Island and how to test its resume behavior.
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
## Scope
|
|
33
|
+
|
|
34
|
+
The `vmz-application` skill covers the VMZ author surface, `#server` capabilities, compiler-visible state, SSR, resumption, `vmz test`, and deployment evidence. It does not teach Vue compatibility or authorize inventing `useX`/`createX` APIs.
|
package/package.json
CHANGED
|
@@ -1,10 +1,21 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vmz/vmz-skills",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"description": "
|
|
5
|
-
"
|
|
6
|
-
"
|
|
3
|
+
"version": "0.1.14",
|
|
4
|
+
"description": "Agent Skills for authoring, reviewing, testing, and deploying VMZ applications",
|
|
5
|
+
"type": "module",
|
|
6
|
+
"license": "MPL-2.0",
|
|
7
7
|
"files": [
|
|
8
|
+
"skills",
|
|
8
9
|
"README.md"
|
|
9
|
-
]
|
|
10
|
+
],
|
|
11
|
+
"publishConfig": {
|
|
12
|
+
"access": "public"
|
|
13
|
+
},
|
|
14
|
+
"scripts": {
|
|
15
|
+
"typecheck": "node -e \"console.log('docs-only skill package')\""
|
|
16
|
+
},
|
|
17
|
+
"repository": {
|
|
18
|
+
"type": "git",
|
|
19
|
+
"url": "git+https://github.com/doki-land/vmz-framework.git"
|
|
20
|
+
}
|
|
10
21
|
}
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: vmz-application
|
|
3
|
+
description: Help users design, author, review, test, and deploy VMZ applications while preserving VMZ-native component, server, SSR, resume, and deployment boundaries.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# VMZ Application
|
|
7
|
+
|
|
8
|
+
Use this skill when a user asks to build or review a VMZ application, `.vmz` component, server capability, route,
|
|
9
|
+
SSR/resume behavior, `vmz test`, or deployment artifact.
|
|
10
|
+
|
|
11
|
+
## Core model
|
|
12
|
+
|
|
13
|
+
- Treat VMZ as a full-stack application compiler, not a Vue compatibility layer.
|
|
14
|
+
- Components are authoring units; compiler regions, capabilities, Islands, and deployment outputs are execution
|
|
15
|
+
boundaries.
|
|
16
|
+
- `public` class fields are props. Ordinary non-public fields are compiler-visible component state.
|
|
17
|
+
- Keep server-only imports behind `#server`; never leak secrets or repositories into browser output.
|
|
18
|
+
- Prefer the official `@vmz/core`, `@vmz/ui`, `vmz`, and `@vmz/test` surfaces already present in the project.
|
|
19
|
+
|
|
20
|
+
## Delivery / dist layout (multi-artifact)
|
|
21
|
+
|
|
22
|
+
- `vmz build` is **multi-artifact**. Default `--out-dir` is `dist` (workspace root) — **not** the CDN publish tree.
|
|
23
|
+
- Three layers: **profile id** (e.g. `static`) · **assembly** (`web-static`) · **`name`** (subdir under out-dir).
|
|
24
|
+
- Static CDN: `profiles.static` with `assembly: 'web-static'` and `name: 'cdn'` → publish **`dist/cdn`** only.
|
|
25
|
+
- Omit `name` → default `dist/static`.
|
|
26
|
+
- **Never** teach `--out-dir dist/cdn` as the naming mechanism.
|
|
27
|
+
- Downstream apps call published npm `vmz`. Do not require sibling overlay / `link:` for CI.
|
|
28
|
+
|
|
29
|
+
## Workflow
|
|
30
|
+
|
|
31
|
+
1. Inspect the existing project layout and `vmz.config.ts` before proposing files.
|
|
32
|
+
2. Express the requested behavior in a component and capability boundary that the compiler can analyze.
|
|
33
|
+
3. Run the narrowest relevant `vmz` check or conformance test.
|
|
34
|
+
4. Explain any conservative bundling, Island, SSR, or deployment decision with its evidence.
|
|
35
|
+
|
|
36
|
+
Do not invent hooks, factories, VDOM layers, or frontend mocks. When a capability is not implemented, state that clearly
|
|
37
|
+
and identify the nearest supported contract.
|