@adia-ai/adia-ui-factory 0.8.9 → 0.8.10

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "adia-factory",
-  "version": "0.8.9",
+  "version": "0.8.10",
   "description": "Author and verify apps built ON the adia-ui (@adia-ai) light-DOM web-component framework \u2014 orient, scaffold, compose, wire, verify, and migrate across SPA and SSR rendering modes. Wires the a2ui MCP for catalog retrieval, UI generation, and validation.",
   "author": {
     "name": "Kim",

package/.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "a2ui": {
       "command": "npx",
-      "args": ["-y", "@adia-ai/a2ui-mcp@0.8.9"]
+      "args": ["-y", "@adia-ai/a2ui-mcp@0.8.10"]
     }
   }
 }

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog — adia-factory
 
+## [0.8.10] — 2026-07-20
+
+### Added
+- **`adia-charts` knowledge skill** (`skills/adia-charts/`; gh#381) — which component to use for which chart/graph/sparkline/gauge/heatmap need, data binding, legend wiring, and theming, grounded in `chart-ui`/`chart-legend-ui`/`heatmap-ui`'s real prop surface. Sibling to `adia-patterns`/`adia-tokens`/`adia-shells`. `chart-legend-ui[for]` auto-mirrors `chart-ui` only (verified `heatmap-ui` never populates `.legendData`/dispatches `legend-update`, despite a stale docstring elsewhere claiming otherwise); `heatmap-ui` is included as a genuine chart-family member (`chart.yaml` itself routes density-grid asks there).
+- **`adia-tables` knowledge skill** (`skills/adia-tables/`; gh#382) — contained vs. uncontained/bleed chrome, `[raw]` (a separate axis from data-driven rendering — see the `@adia-ai/web-components` gh#385 fix), striped rows (opt-in, not default — corrects a stale assumption in the original ticket), column resize/sort (opt-out for JS `.columns`, opt-in for declarative `<col-def>` — the two forms have opposite defaults), and the inline-edit-grid + tree/hierarchical-row patterns. `list-window-ui` named as the escape hatch for 1,000+-row collections.
+- **`evals/evals.json` behavioral test-case files for 15 skills** (gh#369) — the file `release_gate.py`'s G7 coverage check actually reads (a schema distinct from `evals/routing-corpus.json`). Derived from each skill's already-vetted `routing-corpus.json` phrases where genuinely good behavioral tests, with real judgment applied rather than a mechanical paste (independently reviewed, sampled across both plugins).
+
+### Fixed
+- **`evals/routing-corpus.json` unified onto one schema across all skills** (gh#355) — converged the two mutually-incompatible per-skill corpus shapes (forge's `{positives,negatives}` vs. factory's `{phrases}`) onto the `{phrases:[{id,phrase,expected,expected_shape?,rationale?}]}` shape `scripts/skills/run-skill-evals.mjs` already reads, since that's the one in-repo runner that actually exercises these corpora. Fixed 4 missing `.agents/skills/` symlinks that blocked discovery entirely, independent of schema (`adia-site-docs`, `adia-ssr`, `adia-audit`, `adia-patterns`). Coverage: 97 reachable phrases (8 skills invisible) → 572 phrases across all 22 skills existing at the time.
+- **`adia-patterns`: routes are a client-rendered SPA — never plain-fetch** (`skills/adia-patterns/SKILL.md`; PR #362) — a non-browser fetch of any `ui-kit.exe.xyz` route returns the identical loading shell whether the path is valid or not, so `WebFetch`/`curl` can't distinguish a live route from a dead one. Documents the file-resolution alternative (`node_modules` install, or a monorepo checkout).
+
+### Maintenance
+- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
+
 ## [0.8.9] — 2026-07-19
 
 ### Maintenance

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adia-ai/adia-ui-factory",
-  "version": "0.8.9",
+  "version": "0.8.10",
   "description": "Author and verify apps built ON the adia-ui (@adia-ai) light-DOM web-component framework \u2014 orient, scaffold, compose, wire, verify, and migrate across SPA and SSR rendering modes. Wires the a2ui MCP for catalog retrieval, UI generation, and validation.",
   "keywords": [
     "adia-ui",

package/skills/adia-audit/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "adia-audit",
+  "note": "Trigger-routing suite (gh#369). expect=trigger: the skill should fire on the prompt in a fresh session. expect=no-trigger: a near-miss owned elsewhere (owner named per case) or generic knowledge with no AdiaUI skill involved. Cases derived from evals/routing-corpus.json's phrases array (gh#355 vetted corpus, with expected_shape/rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
+  "cases": [
+    { "id": "t01", "prompt": "Audit this AdiaUI app before I start making changes", "expect": "trigger" },
+    { "id": "t02", "prompt": "I inherited a repo that uses @adia-ai — what state is it in?", "expect": "trigger" },
+    { "id": "t03", "prompt": "Is this app on the latest @adia-ai version, or has it drifted?", "expect": "trigger" },
+    { "id": "t04", "prompt": "The dashboard renders unstyled and broken, what's wrong?", "expect": "trigger" },
+    { "id": "t05", "prompt": "This screen doesn't match the reference design, why?", "expect": "trigger" },
+    { "id": "t06", "prompt": "Components render empty even though the data is set — root-cause it", "expect": "trigger" },
+    { "id": "t07", "prompt": "Check this repo for hand-rolled things the library now ships natively", "expect": "trigger" },
+    { "id": "t08", "prompt": "Give me a health report on our AdiaUI consumer app", "expect": "trigger" },
+    { "id": "n01", "prompt": "We're starting a new internal claims tool on adia-ui, plan it", "expect": "no-trigger", "owner": "adia-orient" },
+    { "id": "n02", "prompt": "Run the migration sweep to bump @adia-ai from 0.6 to 0.8", "expect": "no-trigger", "owner": "adia-migrate" },
+    { "id": "n03", "prompt": "QA this screen in the browser and check a11y", "expect": "no-trigger", "owner": "adia-verify" },
+    { "id": "n04", "prompt": "Build the settings screen from this plan", "expect": "no-trigger", "owner": "adia-compose" },
+    { "id": "n05", "prompt": "Cut a release and write the migration guide", "expect": "no-trigger", "owner": "adia-release" },
+    { "id": "n06", "prompt": "Audit our npm dependencies for security vulnerabilities", "expect": "no-trigger" }
+  ]
+}

package/skills/adia-audit/evals/routing-corpus.json

@@ -1,42 +1,158 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "name": "adia-audit routing accuracy corpus",
-  "version": "1.0.0",
+  "version": "2.1.0",
   "purpose": "Routing-eval corpus for adia-audit (adia-ui-factory plugin). Each phrase declares whether adia-audit SHOULD be the routing target. Scored by the estate's TF-IDF routing-eval runner against the skill's description (heuristic token overlap).",
   "scoring_notes": "Heuristic signal, not ground truth. Treat misroutes as a prompt to tighten the skill description, never as a reason to keyword-stuff it. Real harness routing is LLM-driven.",
   "license": "internal",
-  "scope": "adia-audit routing — does this phrase activate adia-audit (diagnose/recon/root-cause an EXISTING @adia-ai consumer repo), and does it correctly stay OUT of adia-orient (classify a greenfield to plan a build), adia-migrate (the mechanical sweep AFTER a confirmed diagnosis), adia-verify (browser QA of a built surface), and adia-compose (author a new screen)?",
-
+  "scope": "adia-audit routing \u2014 does this phrase activate adia-audit (diagnose/recon/root-cause an EXISTING @adia-ai consumer repo), and does it correctly stay OUT of adia-orient (classify a greenfield to plan a build), adia-migrate (the mechanical sweep AFTER a confirmed diagnosis), adia-verify (browser QA of a built surface), and adia-compose (author a new screen)?",
+  "phrases": [
+    {
+      "id": "audit-health-01",
+      "phrase": "audit this AdiaUI app",
+      "expected": "adia-audit",
+      "expected_shape": "audit-health",
+      "rationale": "Canonical audit request on an existing consumer repo."
+    },
+    {
+      "id": "audit-health-02",
+      "phrase": "review this @adia-ai codebase before we touch it",
+      "expected": "adia-audit",
+      "expected_shape": "brownfield-recon",
+      "rationale": "Recon-before-edit on an inherited repo."
+    },
+    {
+      "id": "audit-health-03",
+      "phrase": "I inherited a repo that uses @adia-ai \u2014 what state is it in",
+      "expected": "adia-audit",
+      "expected_shape": "brownfield-recon",
+      "rationale": "Inherited-repo health check."
+    },
+    {
+      "id": "audit-current-01",
+      "phrase": "is this app on the latest @adia-ai version",
+      "expected": "adia-audit",
+      "expected_shape": "is-it-current",
+      "rationale": "Version-currency question \u2014 the recon 3-tuple."
+    },
+    {
+      "id": "audit-current-02",
+      "phrase": "is our AdiaUI setup up to date or drifted",
+      "expected": "adia-audit",
+      "expected_shape": "is-it-current",
+      "rationale": "Drift-detection framing."
+    },
+    {
+      "id": "audit-migrate-01",
+      "phrase": "what should we migrate in this AdiaUI app",
+      "expected": "adia-audit",
+      "expected_shape": "what-to-migrate",
+      "rationale": "Diagnosis-first: the audit produces the ranked what, adia-migrate executes it."
+    },
+    {
+      "id": "audit-wrong-01",
+      "phrase": "the dashboard renders unstyled and broken, what's wrong",
+      "expected": "adia-audit",
+      "expected_shape": "wrong-output-root-cause",
+      "rationale": "Wrong-output symptom \u2192 the correction loop."
+    },
+    {
+      "id": "audit-wrong-02",
+      "phrase": "this screen doesn't match the reference, why",
+      "expected": "adia-audit",
+      "expected_shape": "wrong-output-root-cause",
+      "rationale": "Mismatch-vs-reference \u2192 root-cause triage."
+    },
+    {
+      "id": "audit-wrong-03",
+      "phrase": "the admin shell topbar looks mispositioned",
+      "expected": "adia-audit",
+      "expected_shape": "wrong-output-root-cause",
+      "rationale": "The Light-DOM zeroth-question archetype."
+    },
+    {
+      "id": "audit-wrong-04",
+      "phrase": "components render empty even though the data is set",
+      "expected": "adia-audit",
+      "expected_shape": "wrong-output-root-cause",
+      "rationale": "Silent no-op symptom \u2014 attribute/scheme drift."
+    },
+    {
+      "id": "audit-gap-01",
+      "phrase": "why does npm run dev fail to resolve @adia-ai imports",
+      "expected": "adia-audit",
+      "expected_shape": "audit-health",
+      "rationale": "Class-0 manifest-gap symptom."
+    },
+    {
+      "id": "audit-gap-02",
+      "phrase": "check this repo for hand-rolled things the library now ships",
+      "expected": "adia-audit",
+      "expected_shape": "audit-health",
+      "rationale": "Class-3 capability drift."
+    },
+    {
+      "id": "audit-report-01",
+      "phrase": "give me a health report on our AdiaUI consumer app",
+      "expected": "adia-audit",
+      "expected_shape": "audit-health",
+      "rationale": "The diagnostic-report deliverable."
+    },
+    {
+      "id": "audit-recon-01",
+      "phrase": "before I edit this brownfield surface, what's the repo's adoption state",
+      "expected": "adia-audit",
+      "expected_shape": "brownfield-recon",
+      "rationale": "Recon-earns-remediation, the core posture."
+    },
+    {
+      "id": "adv-orient-01",
+      "phrase": "we're starting a new internal claims tool on adia-ui, plan it",
+      "expected": null,
+      "expected_shape": "adia-orient",
+      "rationale": "GREENFIELD classification/planning \u2014 adia-orient, not a brownfield audit."
+    },
+    {
+      "id": "adv-migrate-01",
+      "phrase": "run the migration sweep to bump @adia-ai from 0.6 to 0.8",
+      "expected": null,
+      "expected_shape": "adia-migrate",
+      "rationale": "The mechanical sweep AFTER a confirmed plan \u2014 adia-migrate executes; audit only diagnoses."
+    },
+    {
+      "id": "adv-verify-01",
+      "phrase": "QA this screen in the browser and check a11y",
+      "expected": null,
+      "expected_shape": "adia-verify",
+      "rationale": "Browser QA of a built surface \u2014 adia-verify, not repo diagnosis."
+    },
+    {
+      "id": "adv-compose-01",
+      "phrase": "build the settings screen from this plan",
+      "expected": null,
+      "expected_shape": "adia-compose",
+      "rationale": "Authoring a new surface \u2014 the audit hands off to a builder, never authors."
+    },
+    {
+      "id": "adv-release-01",
+      "phrase": "cut a release and write the migration guide",
+      "expected": null,
+      "expected_shape": "adia-forge:adia-release",
+      "rationale": "Framework release engineering \u2014 a different plugin entirely."
+    },
+    {
+      "id": "adv-generic-01",
+      "phrase": "audit our npm dependencies for security vulnerabilities",
+      "expected": null,
+      "expected_shape": "none",
+      "rationale": "Generic dependency audit unrelated to @adia-ai consumer health."
+    }
+  ],
   "minimums_per_spec": {
     "trigger_phrases": 14,
     "adversarial_phrases": 6,
     "task_shapes_covered": "audit-health, wrong-output-root-cause, is-it-current, what-to-migrate, brownfield-recon",
     "adversarial_fraction": "30%"
   },
-
-  "phrases": [
-    { "id": "audit-health-01", "phrase": "audit this AdiaUI app", "should_route_to_audit": true, "expected_shape": "audit-health", "rationale": "Canonical audit request on an existing consumer repo." },
-    { "id": "audit-health-02", "phrase": "review this @adia-ai codebase before we touch it", "should_route_to_audit": true, "expected_shape": "brownfield-recon", "rationale": "Recon-before-edit on an inherited repo." },
-    { "id": "audit-health-03", "phrase": "I inherited a repo that uses @adia-ai — what state is it in", "should_route_to_audit": true, "expected_shape": "brownfield-recon", "rationale": "Inherited-repo health check." },
-    { "id": "audit-current-01", "phrase": "is this app on the latest @adia-ai version", "should_route_to_audit": true, "expected_shape": "is-it-current", "rationale": "Version-currency question — the recon 3-tuple." },
-    { "id": "audit-current-02", "phrase": "is our AdiaUI setup up to date or drifted", "should_route_to_audit": true, "expected_shape": "is-it-current", "rationale": "Drift-detection framing." },
-    { "id": "audit-migrate-01", "phrase": "what should we migrate in this AdiaUI app", "should_route_to_audit": true, "expected_shape": "what-to-migrate", "rationale": "Diagnosis-first: the audit produces the ranked what, adia-migrate executes it." },
-    { "id": "audit-wrong-01", "phrase": "the dashboard renders unstyled and broken, what's wrong", "should_route_to_audit": true, "expected_shape": "wrong-output-root-cause", "rationale": "Wrong-output symptom → the correction loop." },
-    { "id": "audit-wrong-02", "phrase": "this screen doesn't match the reference, why", "should_route_to_audit": true, "expected_shape": "wrong-output-root-cause", "rationale": "Mismatch-vs-reference → root-cause triage." },
-    { "id": "audit-wrong-03", "phrase": "the admin shell topbar looks mispositioned", "should_route_to_audit": true, "expected_shape": "wrong-output-root-cause", "rationale": "The Light-DOM zeroth-question archetype." },
-    { "id": "audit-wrong-04", "phrase": "components render empty even though the data is set", "should_route_to_audit": true, "expected_shape": "wrong-output-root-cause", "rationale": "Silent no-op symptom — attribute/scheme drift." },
-    { "id": "audit-gap-01", "phrase": "why does npm run dev fail to resolve @adia-ai imports", "should_route_to_audit": true, "expected_shape": "audit-health", "rationale": "Class-0 manifest-gap symptom." },
-    { "id": "audit-gap-02", "phrase": "check this repo for hand-rolled things the library now ships", "should_route_to_audit": true, "expected_shape": "audit-health", "rationale": "Class-3 capability drift." },
-    { "id": "audit-report-01", "phrase": "give me a health report on our AdiaUI consumer app", "should_route_to_audit": true, "expected_shape": "audit-health", "rationale": "The diagnostic-report deliverable." },
-    { "id": "audit-recon-01", "phrase": "before I edit this brownfield surface, what's the repo's adoption state", "should_route_to_audit": true, "expected_shape": "brownfield-recon", "rationale": "Recon-earns-remediation, the core posture." },
-
-    { "id": "adv-orient-01", "phrase": "we're starting a new internal claims tool on adia-ui, plan it", "should_route_to_audit": false, "expected_shape": "adia-orient", "rationale": "GREENFIELD classification/planning — adia-orient, not a brownfield audit." },
-    { "id": "adv-migrate-01", "phrase": "run the migration sweep to bump @adia-ai from 0.6 to 0.8", "should_route_to_audit": false, "expected_shape": "adia-migrate", "rationale": "The mechanical sweep AFTER a confirmed plan — adia-migrate executes; audit only diagnoses." },
-    { "id": "adv-verify-01", "phrase": "QA this screen in the browser and check a11y", "should_route_to_audit": false, "expected_shape": "adia-verify", "rationale": "Browser QA of a built surface — adia-verify, not repo diagnosis." },
-    { "id": "adv-compose-01", "phrase": "build the settings screen from this plan", "should_route_to_audit": false, "expected_shape": "adia-compose", "rationale": "Authoring a new surface — the audit hands off to a builder, never authors." },
-    { "id": "adv-release-01", "phrase": "cut a release and write the migration guide", "should_route_to_audit": false, "expected_shape": "adia-forge:adia-release", "rationale": "Framework release engineering — a different plugin entirely." },
-    { "id": "adv-generic-01", "phrase": "audit our npm dependencies for security vulnerabilities", "should_route_to_audit": false, "expected_shape": "none", "rationale": "Generic dependency audit unrelated to @adia-ai consumer health." }
-  ],
-
   "evaluator_notes": "adia-audit's tightest confusables are adia-orient (greenfield vs brownfield) and adia-migrate (diagnose vs execute). The description leads with EXISTING/brownfield and fences both explicitly."
 }

package/skills/adia-charts/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: adia-charts
+description: >-
+  Which adia-ui component renders a chart, graph, sparkline, gauge, or
+  heatmap, and how to wire its data/legend/theming. Use for "add a chart",
+  "show a graph", "visualize this data", "add a sparkline/gauge/heatmap", or
+  "wire a chart legend". NOT for the surrounding screen (adia-compose),
+  color tokens (adia-tokens), or data fetching (adia-data).
+disable-model-invocation: false
+user-invocable: false
+---
+
+# adia-charts — chart & graph component usage
+
+`<chart-ui>` is the single declarative SVG chart primitive — 18 types behind one `type`
+attribute, one data shape, one event contract. `<chart-legend-ui>` and `<heatmap-ui>` are its
+two chart-family siblings. This pack answers "which component / prop / wiring" for chart-shaped
+asks; it never composes the screen around the chart.
+
+`<chat-thread-ui>` (the chat-message scroll primitive) is unrelated to this pack despite the
+name collision with "chart" — it belongs to the chat/messaging family (`chat-thread.yaml`
+keywords: chat, message, conversation), not the chart family. Don't route chat-shaped asks here.
+
+## Which component for which need
+
+| Need | Component | `type` / notes |
+| --- | --- | --- |
+| any of bar/line/pie/donut/radar/area/scatter/gauge/funnel/treemap/sankey/composed | **chart-ui** | `type="…"` — see [chart-type-catalog.md](references/chart-type-catalog.md) for the full 18-type map |
+| a keyboard-toggleable series legend beside a chart | **chart-legend-ui** | `[for]` id-ref auto-mirrors **chart-ui only** (reads `.legendData`/`legend-update`, which heatmap-ui never populates or dispatches); `items=` for standalone |
+| calendar/contribution grid or a density matrix | **heatmap-ui** | `type="day-grid"` \| `matrix` \| `density` — NOT chart-ui; chart.yaml explicitly routes density-grid asks here. Its legend equivalent is the built-in Less/More strip (`no-legend` prop to hide it), not `chart-legend-ui` |
+| a single prominent KPI number (+ delta, + optional inline mini-chart) | **stat-ui** | not itself a chart; composes a `<chart-ui type="sparkline" slot="chart">` via its `chart` slot + `[bleed]` |
+| a labeled completion bar/percentage, not a plotted series | **progress-ui** | boundary case — see stat.yaml's own rule: "stat for standalone metrics, progress for completion bars" |
+
+Full type-by-type mapping (data shape, x/y semantics, when each of the 18 `chart-ui` types
+fits) is in [chart-type-catalog.md](references/chart-type-catalog.md) — consult it before
+picking a `type` value for anything beyond the five common cases in the table above.
+
+## Data binding — the shared shape (except Sankey)
+
+Most `chart-ui` types consume an array of plain objects, keyed by the `x` and `y` attributes —
+**not** the Chart.js `{labels, datasets}` envelope:
+
+```html
+<chart-ui type="bar" x="month" y="revenue"></chart-ui>
+<script>
+  document.querySelector('chart-ui').data = [
+    { month: 'Jan', revenue: 3200 },
+    { month: 'Feb', revenue: 4100 },
+  ];
+</script>
+```
+
+`type="sankey"` is the exception: it ignores `x`/`y` and expects flow-link rows shaped
+`{ source, target, value }` instead. See
+[chart-type-catalog.md](references/chart-type-catalog.md).
+
+- `.data` (JS property) is the canonical entry point; a declarative `data='[…]'` JSON-array
+  attribute is also accepted and hydrated once at connect — useful for static-HTML demos.
+- `y` is comma-separated for multi-series types (`y="revenue,users"` → `stacked-bar` /
+  `grouped-bar` / `multi-line` / `composed`); single-series types read only the first key.
+- Passing a non-array (the Chart.js envelope, `null`, an object) is silently coerced to `[]` —
+  a blank chart with a one-shot console warning, not a thrown error. If a chart renders empty,
+  check the data shape first.
+- Past ~5,000 rows, `chart-ui` re-renders the full SVG string on every `.data` write and
+  perf degrades — downsample (LTTB, bucket aggregation) at the data layer before setting
+  `.data`, or raise the budget via `--chart-perf-budget` for a deliberate large render.
+
+## Composition patterns
+
+- **Chart + legend, auto-wired**: give the chart an `id`, point the legend's `[for]` at it —
+  toggling a legend row hides/dims that series in the chart, no manual event wiring needed.
+  ```html
+  <chart-ui id="rev" type="multi-line" x="month" y="revenue,users"></chart-ui>
+  <chart-legend-ui for="rev" shape="line" position="bottom"></chart-legend-ui>
+  ```
+- **Standalone legend**: `items='[{"key":"revenue","label":"Revenue","slot":0}, …]'` when no
+  chart-ui sibling exists, or the legend represents a chart rendered elsewhere.
+- **KPI card with inline trend**: `<stat-ui bleed>` + a `<chart-ui slot="chart" type="sparkline">`
+  child — the value/label/change stack left, the chart bleeds the card's right column.
+- **Dashboard grid**: `<stat-ui>` cards for headline KPIs + `<chart-ui>` cards for trend detail,
+  laid out via `Grid`/`Card` — see chart.yaml's own `chart-dashboard` example for the canonical
+  a2ui shape (KPI row + two chart cards). Screen-level grid/layout choices are `adia-compose`'s
+  job, not this pack's.
+- **Empty state**: a `slot="empty"` child (typically `<empty-state-ui>`) renders in place of the
+  SVG when `.data` is empty/unset; visibility is CSS-toggled via `[data-has-data]` — no
+  imperative show/hide needed.
+- **Loading**: `loading` boolean prop swaps in a `skeleton-ui` placeholder that preserves the
+  chart's footprint (parity with `table-ui[loading]` / `stat-ui[loading]`).
+- **Hover/tooltip**: `chart-ui` and `heatmap-ui` both emit the canonical `chart-hover` /
+  `chart-leave` / `chart-select` event trio (heatmap re-emits `cell-hover`/`cell-click` under
+  these same names) — wire a shared `tooltip-ui[follows="pointer"][for]` once instead of a
+  per-chart-kind listener. Full event payload shapes and the a11y/keyboard contract are in
+  [composition-and-theming.md](references/composition-and-theming.md).
+
+## Theming & responsive — framework-level conventions
+
+- **Never a raw color.** `color="accent|success|warning|danger|info"` picks the intent palette;
+  per-series identity colors come from the 10-slot categorical ramp (`--chart-0`…`--chart-9`,
+  aliasing `--a-data-0`…`--a-data-9`) — the same law `adia-tokens` states for chart identity vs.
+  semantic-state tokens. Recolor one named series by overriding `--color-{key}` at any ancestor;
+  never hand-write a hex or `oklch()` value into chart CSS.
+- **Number formatting** is a prop, not per-chart math: `format="abbr|decimal|currency|percent"`
+  (currency's `$` prefix is itself a token, `--chart-currency-prefix`, so locale retuning never
+  touches markup).
+- **Responsive by container, not viewport.** A chart derives width from its actual rendered
+  container width (`ResizeObserver`-driven) and height from a 4:3 aspect ratio unless an explicit
+  height is set; `--chart-max-height` (default `28rem`) caps runaway heights on wide viewports.
+  Font/label sizing auto-classes to `sm`/`md`/`lg` off the smallest rendered dimension — the
+  `size` prop overrides the auto-class when a fixed density is wanted regardless of container.
+- **Never wrap in a fixed-pixel container to "make it responsive.**" Size the parent (`Grid`
+  column, `Card` section, `%`/`fr` width) and let `chart-ui` read that.
+
+Token roster, per-series override mechanics, keyboard/a11y contract, and the full event-payload
+shapes: [composition-and-theming.md](references/composition-and-theming.md).
+
+## Consult table
+
+| Ask | Answer from |
+| --- | --- |
+| "which chart-ui type for X" | [chart-type-catalog.md](references/chart-type-catalog.md) |
+| "how do I color/theme a chart" | Theming section above, then [composition-and-theming.md](references/composition-and-theming.md) |
+| "wire a legend to a chart" | Composition patterns above |
+| "chart renders blank" | Data binding section — check the `.data` shape first |
+| "chart-ui vs heatmap-ui vs stat-ui" | Which-component table above |
+| "build the whole dashboard screen" | `adia-compose` — this pack answers per-chart usage, not screen composition |
+| "which token/color role" (beyond the chart identity ramp) | `adia-tokens` |
+| "fetch/hydrate the chart's data" | `adia-data` |

package/skills/adia-charts/evals/evals.json

@@ -0,0 +1,20 @@
+{
+  "skill": "adia-charts",
+  "note": "Trigger-routing suite (gh#369). expect=trigger: the skill should fire on the prompt in a fresh session. expect=no-trigger: a near-miss owned elsewhere (owner named per case) or generic knowledge with no AdiaUI skill involved. Cases derived from evals/routing-corpus.json's phrases array (gh#355 vetted corpus, with rationale) plus the SKILL.md description's own trigger/NOT-fence language.",
+  "cases": [
+    { "id": "t01", "prompt": "Add a bar chart showing monthly revenue", "expect": "trigger" },
+    { "id": "t02", "prompt": "What component do I use for a donut chart?", "expect": "trigger" },
+    { "id": "t03", "prompt": "Show a sparkline inside a KPI card", "expect": "trigger" },
+    { "id": "t04", "prompt": "Add a calendar heatmap like GitHub's contribution graph", "expect": "trigger" },
+    { "id": "t05", "prompt": "My chart-ui data isn't showing anything on the page", "expect": "trigger" },
+    { "id": "t06", "prompt": "Wire a legend so clicking a series hides it in the chart", "expect": "trigger" },
+    { "id": "t07", "prompt": "How do I recolor just one series in a multi-line chart?", "expect": "trigger" },
+    { "id": "t08", "prompt": "Listen for hover events on chart datapoints", "expect": "trigger" },
+    { "id": "n01", "prompt": "Build the analytics dashboard screen with charts and stat cards", "expect": "no-trigger", "owner": "adia-compose" },
+    { "id": "n02", "prompt": "Which color role should a warning badge use?", "expect": "no-trigger", "owner": "adia-tokens" },
+    { "id": "n03", "prompt": "Fetch the chart's data from our backend API", "expect": "no-trigger", "owner": "adia-data" },
+    { "id": "n04", "prompt": "Add a chat thread showing the conversation with the assistant", "expect": "no-trigger" },
+    { "id": "n05", "prompt": "Add a progress bar showing 40 percent complete", "expect": "no-trigger" },
+    { "id": "n06", "prompt": "The page renders blank after I added a chart, check the console errors", "expect": "no-trigger", "owner": "adia-verify" }
+  ]
+}

package/skills/adia-charts/evals/routing-corpus.json

@@ -0,0 +1,155 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "name": "adia-charts-routing-corpus",
+  "version": "1.0.0",
+  "purpose": "Routing floor for the adia-charts knowledge pack: 'which chart component / how do I wire it' asks reach it; screen composition, data hydration, token-role, and chat-primitive asks route past it.",
+  "scoring_notes": "Heuristic TF-IDF proxy (scripts/skills/run-skill-evals.mjs); the real harness routes on descriptions. Treat misroutes as description-tightening signals.",
+  "license": "internal",
+  "scope": "adia-ui-factory plugin, consumer-side. Covers chart-ui, chart-legend-ui, and heatmap-ui (the chart family); explicitly excludes chat-thread-ui (chat/messaging primitive, unrelated despite the name collision with 'chart').",
+  "phrases": [
+    {
+      "id": "charts-which-01",
+      "phrase": "add a bar chart showing monthly revenue",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "Flagship ask — chart type to component mapping."
+    },
+    {
+      "id": "charts-which-02",
+      "phrase": "what component do I use for a donut chart",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "Type-to-component lookup."
+    },
+    {
+      "id": "charts-which-03",
+      "phrase": "show a sparkline inside a KPI card",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "stat-ui + chart-ui[type=sparkline] composition, still this pack's territory."
+    },
+    {
+      "id": "charts-which-04",
+      "phrase": "add a calendar heatmap like GitHub contributions",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "heatmap-ui is a chart-family sibling, not chart-ui itself, but the ask is chart-shaped."
+    },
+    {
+      "id": "charts-which-05",
+      "phrase": "which chart type works for a signup-to-purchase conversion funnel",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "type=funnel lookup from the catalog."
+    },
+    {
+      "id": "charts-which-06",
+      "phrase": "add a gauge showing progress toward a target number",
+      "expected": "adia-charts",
+      "expected_shape": "which-component",
+      "rationale": "type=gauge lookup; distinct from progress-ui's completion-bar territory."
+    },
+    {
+      "id": "charts-data-01",
+      "phrase": "my chart-ui data isn't showing anything on the page",
+      "expected": "adia-charts",
+      "expected_shape": "data-binding",
+      "rationale": "Blank-chart triage — data shape check per chart.js's own shape-warning."
+    },
+    {
+      "id": "charts-data-02",
+      "phrase": "how do I pass an array of data objects to chart-ui",
+      "expected": "adia-charts",
+      "expected_shape": "data-binding",
+      "rationale": "The x/y-keyed row shape, not the Chart.js envelope."
+    },
+    {
+      "id": "charts-compose-01",
+      "phrase": "wire a legend so clicking a series hides it in the chart",
+      "expected": "adia-charts",
+      "expected_shape": "composition-legend",
+      "rationale": "chart-legend-ui [for] auto-mirror + toggle wiring."
+    },
+    {
+      "id": "charts-theme-01",
+      "phrase": "how do I recolor just one series in a multi-line chart",
+      "expected": "adia-charts",
+      "expected_shape": "theming",
+      "rationale": "--color-{key} per-series override mechanics."
+    },
+    {
+      "id": "charts-theme-02",
+      "phrase": "make the chart values display as currency",
+      "expected": "adia-charts",
+      "expected_shape": "theming",
+      "rationale": "format=currency prop + --chart-currency-prefix token."
+    },
+    {
+      "id": "charts-responsive-01",
+      "phrase": "the chart looks huge and stretched on a wide screen",
+      "expected": "adia-charts",
+      "expected_shape": "responsive",
+      "rationale": "Container-based sizing + --chart-max-height cap."
+    },
+    {
+      "id": "charts-events-01",
+      "phrase": "listen for hover events on chart datapoints",
+      "expected": "adia-charts",
+      "expected_shape": "events",
+      "rationale": "chart-hover/chart-leave/chart-select payload contract."
+    },
+    {
+      "id": "charts-adv-01",
+      "phrase": "build the analytics dashboard screen with charts and stat cards",
+      "expected": "adia-compose",
+      "rationale": "Adversarial — screen/grid composition consumes the answer; the ask is a build.",
+      "expected_alternative_raw": "adia-compose (adia-ui-factory)"
+    },
+    {
+      "id": "charts-adv-02",
+      "phrase": "which color role should a warning badge use",
+      "expected": "adia-tokens",
+      "rationale": "Adversarial — a token-role ask with no chart in it at all.",
+      "expected_alternative_raw": "adia-tokens (adia-ui-factory)"
+    },
+    {
+      "id": "charts-adv-03",
+      "phrase": "fetch the chart's data from our backend API",
+      "expected": "adia-data",
+      "rationale": "Adversarial — data hydration/fetch is adia-data's territory; this pack only covers the .data shape once it arrives.",
+      "expected_alternative_raw": "adia-data (adia-ui-factory)"
+    },
+    {
+      "id": "charts-adv-04",
+      "phrase": "add a chat thread showing the conversation with the assistant",
+      "expected": null,
+      "rationale": "Adversarial — chat-thread-ui is a chat/messaging primitive, unrelated to the chart family despite the name collision; resolved explicitly out of scope for this pack (gh#381).",
+      "expected_alternative_raw": "chat/messaging surface (chat-shell / chat-thread-ui) — not this pack"
+    },
+    {
+      "id": "charts-adv-05",
+      "phrase": "add a progress bar showing 40 percent complete",
+      "expected": null,
+      "rationale": "Adversarial — a completion bar is progress-ui's territory, not a chart type; stat.yaml's own rule draws this exact boundary.",
+      "expected_alternative_raw": "progress-ui (not a chart-family primitive)"
+    },
+    {
+      "id": "charts-adv-06",
+      "phrase": "the page renders blank after I added a chart",
+      "expected": "adia-verify",
+      "rationale": "Adversarial — a broken render is the browser gate's territory, not a chart-usage question.",
+      "expected_alternative_raw": "adia-verify (adia-ui-factory)"
+    }
+  ],
+  "minimums_per_spec": {
+    "trigger_phrases": 13,
+    "adversarial_phrases": 6,
+    "task_shapes_covered": "which-component, data-binding, composition-legend, theming, responsive, events",
+    "adversarial_fraction": "32%"
+  },
+  "evaluator_notes": {
+    "known_limitations": "The chat-thread-ui exclusion (charts-adv-04) is the corpus's only defense against the reporter's original ambiguity (gh#381 linked chat-thread alongside chart/chart-legend) — treat any future misroute here as a description regression, not noise.",
+    "promotion_criteria": "F1 >= 0.85 across 3+ runs",
+    "review_cadence": "on any description edit; on /eval-run findings"
+  }
+}