@rokkit/cli 1.6.0 → 1.7.0

package/agents/rokkit-chart-reviewer.md

@@ -39,7 +39,8 @@ the vocabulary — cite it, don't restate it.
   Colours/patterns/symbols come from `createChartPreset()` shared via `<ChartProvider>` (nest to
   scope a subtree); named presets (`default`/`accessible`/`print`, or `helpers.presets`) go through
   `spec.preset`. Adding a *new* colour/pattern/symbol means extending a registry
-  (`lib/palette.json` / `patterns/patterns.js` `PATTERNS` / `lib/brewing/marks/points.js`
+  (`@rokkit/core` `categoricalPalette` / `patterns/patterns.js` `PATTERNS` /
+  `lib/brewing/marks/points.js`
   `SYMBOL_NAMES`+`SYMBOL_TYPES`) then naming it in a preset — never inlining scattered raw colours.
 - **Colour follows the theme.** Preset shades resolve per light/dark mode; a chart should reskin
   from the preset/skin, not from hardcoded per-mark hex. Token-literal fills are fine when
@@ -81,7 +82,8 @@ results than blind grep. Fall back to Grep/Glob only if a tool errors or returns
    root, `opacity=` on a chart, `stack\b` as a boolean prop, `palette=` / `preset=` on a chart,
    raw `#[0-9a-fA-F]{3,8}`/`oklch(`/`rgb(` inside chart props. Map each hit to the correct
    channel/preset fix.
-4. If a new palette/pattern/symbol was added, verify it's in the right registry (`palette.json` /
+4. If a new palette/pattern/symbol was added, verify it's in the right registry
+   (`categoricalPalette` /
    `PATTERNS` / `SYMBOL_*`) with the right shape, and referenced by name in a preset. Run
    `rokkit doctor` if available and fold in its advisories.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rokkit/cli",
-  "version": "1.6.0",
+  "version": "1.7.0",
   "description": "Command line utilities for icon bundling and conversion.",
   "repository": {
     "type": "git",
@@ -28,7 +28,7 @@
   },
   "dependencies": {
     "@mdi/svg": "^7.4.47",
-    "@rokkit/unocss": "1.6.0",
+    "@rokkit/unocss": "1.7.0",
     "sade": "^1.8.1",
     "@iconify/tools": "^5.0.14",
     "@iconify/types": "^2.0.0",

package/skills/charts-rokkit/SKILL.md

@@ -119,7 +119,8 @@ Every categorical encoding is driven by a **preset** (`packages/chart/src/lib/pr
 
 Each list is **names into a registry**, cycled across your data's distinct values:
 
-- `colors` → palette names in **`lib/palette.json`** (each name → 11 shades `50–950`).
+- `colors` → palette names in **`@rokkit/core`'s `categoricalPalette`** (each name → 11 shades
+  `50–950`).
   `assignColors(values, mode, preset)` picks `palette[name][shades[mode].fill|stroke]` — so a chart
   re-colours correctly for light/dark automatically.
 - `patterns` → names in **`patterns/patterns.js`** (`PATTERNS`, the SVG mark defs).
@@ -134,7 +135,7 @@ and share it via `ChartProvider`:
 <script>
   import { ChartProvider, createChartPreset, BarChart, LineChart } from '@rokkit/chart'
   const preset = createChartPreset({
-    colors: ['teal', 'orange', 'rose'],   // subset/reorder of palette.json names
+    colors: ['teal', 'orange', 'rose'],   // subset/reorder of categoricalPalette names
     patterns: ['dots', 'hatch'],
     shades: { dark: { fill: '400' } }      // partial shade override (merges)
   })
@@ -157,7 +158,8 @@ and share it via `ChartProvider`:
 
 ### Add a NEW colour palette
 
-1. Add an 11-shade entry to `packages/chart/src/lib/palette.json` (shades `50`→`950`, light→dark):
+1. Add an 11-shade entry to `packages/core/src/colors/categorical.json` (shades `50`→`950`,
+   light→dark). It lives in core because `@rokkit/chart` and `@rokkit/graph` both consume it:
 
    ```json
    "brand": { "50": "#f4f7ff", "100": "…", "300": "#93b4ff", "500": "#3b6cff",