@getvitops/cli 8.2.0-alpha.0 → 8.2.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@getvitops/cli",
3
- "version": "8.2.0-alpha.0",
3
+ "version": "8.2.0",
4
4
  "description": "CLI for the Vitops design-system generator: generate, init, and validate a design-system.json.",
5
5
  "homepage": "https://docs.vitops.ca",
6
6
  "bugs": "https://github.com/getvitops/design-system/issues",
@@ -29,8 +29,8 @@
29
29
  "access": "public"
30
30
  },
31
31
  "dependencies": {
32
- "@getvitops/generator": "8.2.0-alpha.0",
33
- "@getvitops/utils": "8.2.0-alpha.0"
32
+ "@getvitops/generator": "8.2.0",
33
+ "@getvitops/utils": "8.2.0"
34
34
  },
35
35
  "devDependencies": {},
36
36
  "engines": {
package/skill/SKILL.md CHANGED
@@ -106,22 +106,23 @@ live from this project's `design-system.json` and the installed package version,
106
106
  never stale and always names the project's actual tokens. (If `vitops` isn't on PATH, use
107
107
  `pnpm exec vitops docs <topic>` or `npx vitops docs <topic>`.)
108
108
 
109
- | Run | When you need |
110
- | ------------------------ | ---------------------------------------------------------------------- |
111
- | `vitops docs classes` | which class to apply — the full class vocabulary as naming rules |
112
- | `vitops docs authoring` | what a `design-system.json` field means / what's valid |
113
- | `vitops docs config` | the three-section config: `designSystem` / `organization` / `site` |
114
- | `vitops docs formats` | tailwind vs css vs bricks output — incl. which utilities Tailwind owns |
115
- | `vitops docs color` | how the colour system works (seeded OKLCH scales, roles, dark mode) |
116
- | `vitops docs scales` | how the fluid type/space scales work |
117
- | `vitops docs patterns` | how pattern CSS is assembled (token cascade, override hooks, states) |
118
- | `vitops docs components` | which tier provides a pattern (classes / `wc-*` / Astro / Bricks) |
119
- | `vitops docs icons` | semantic icon names across sets, bundle derivation, sprite delivery |
120
- | `vitops docs consent` | the consent gate — gating a tag, demand-driven prompting, the API |
121
- | `vitops docs tracking` | ad-click attribution, the `_ac` cookie, conversion notifications |
122
- | `vitops docs search` | what search engines accept, Search Console onboarding + notification |
123
- | `vitops docs legal` | how the policy / terms / cookie notice derive from config facts |
124
- | `vitops docs elements` | the custom Bricks Builder elements and their controls |
109
+ | Run | When you need |
110
+ | ------------------------ | ----------------------------------------------------------------------- |
111
+ | `vitops docs classes` | which class to apply — the full class vocabulary as naming rules |
112
+ | `vitops docs authoring` | what a `design-system.json` field means / what's valid |
113
+ | `vitops docs config` | the three-section config: `designSystem` / `organization` / `site` |
114
+ | `vitops docs formats` | tailwind vs css vs bricks output — incl. which utilities Tailwind owns |
115
+ | `vitops docs color` | how the colour system works (seeded OKLCH scales, roles, dark mode) |
116
+ | `vitops docs scales` | how the fluid type/space scales work |
117
+ | `vitops docs patterns` | how pattern CSS is assembled (token cascade, override hooks, states) |
118
+ | `vitops docs blocks` | EmDash Portable Text blocks and every field (needs `@getvitops/emdash`) |
119
+ | `vitops docs components` | which tier provides a pattern (classes / `wc-*` / Astro / Bricks) |
120
+ | `vitops docs icons` | semantic icon names across sets, bundle derivation, sprite delivery |
121
+ | `vitops docs consent` | the consent gate — gating a tag, demand-driven prompting, the API |
122
+ | `vitops docs tracking` | ad-click attribution, the `_ac` cookie, conversion notifications |
123
+ | `vitops docs search` | what search engines accept, Search Console onboarding + notification |
124
+ | `vitops docs legal` | how the policy / terms / cookie notice derive from config facts |
125
+ | `vitops docs elements` | the custom Bricks Builder elements and their controls |
125
126
 
126
127
  `vitops docs` (no topic) lists the topics; `vitops docs --all` prints everything.
127
128