@event4u/agent-config 7.4.0 → 8.0.0

package/dist/agent-src/skills/design-system-capture/reference/design-system-json.md

@@ -0,0 +1,62 @@
+# `design-system.json` — import contract
+
+> Lazy-loaded by `design-system-capture` ONLY when importing an extracted design
+> system. Not in the always-on skill body. The **consumer-side contract**: any
+> external static-extraction tool (URL / git repo / local dir) emits this shape;
+> the skill READS it to seed/merge `DESIGN.md`. We own the contract, not the
+> crawler (council 2026-06-28).
+
+## Shape
+
+```json
+{
+  "source": { "kind": "url|repo|dir", "ref": "https://example.com", "captured_at": "<ISO-8601>" },
+  "colors": {
+    "light": { "<role>": "<value>" },
+    "dark":  { "<role>": "<value>" }
+  },
+  "typography": {
+    "families": [{ "role": "body|display|mono", "name": "<font>", "bundled_local": false }],
+    "scale": [{ "step": "xs|sm|base|lg|…", "size": "<rem/px>", "lineHeight": "<n>" }]
+  },
+  "spacing": { "base": "<px>", "scale": ["<px>", "…"] },
+  "radius":  { "<role>": "<px>" },
+  "shadow":  { "<role>": "<box-shadow>" },
+  "motion":  { "durations": { "<role>": "<ms>" }, "easings": { "<role>": "<cubic-bezier>" },
+               "_meta": { "detected_libs": ["gsap", "lottie"] } },
+  "components": [{ "name": "<Name>", "observed": { "classes": ["…"], "props": ["…"] } }]
+}
+```
+
+## Field rules
+
+- **Map to DTCG where it maps cleanly.** `colors` / `typography` / `spacing` /
+  `radius` / `shadow` = the DTCG `.tokens.json` shape `design-tokens` /
+  `brand-to-tokens` already author — reuse it; never a parallel token format.
+- **Mark extraction-only metadata.** Observation, not a token decision, lives
+  under `_meta` (`motion._meta.detected_libs`, `components[].observed`). Informs
+  the human; never becomes a token.
+- **`source` is mandatory** — `kind` + `ref` + `captured_at`. No provenance →
+  reject (can't confirm what you can't trace).
+- **`bundled_local`** is a flag, not an instruction: the package never
+  downloads/bundles fonts (out of scope); it records that the source did.
+
+## Trust posture (mandatory)
+
+An import is **observed, not authoritative** (mirrors `source-discovery`:
+evidence vs. authoritative). It seeds `DESIGN.md` as a **proposal the human
+confirms per field** — never a silent write. A field conflicting with a
+registered brand value (confirmed `.tokens.json` / brand token) is **flagged,
+never auto-applied** (`brand-source-of-truth`). Precedence: registered brand
+tokens > confirmed `DESIGN.md` > imported observation.
+
+## Two sources, one shape
+
+- **External target** (a site/repo you don't own) → external standalone tool
+  emits `design-system.json`; hand it to `design-system-capture`.
+- **Current repo** → prefer [`existing-ui-audit`](../../existing-ui-audit/SKILL.md):
+  it inventories the codebase and emits the same shape, so the import path is
+  identical either way.
+
+Package **owns this contract**; does **not** ship the crawler, the Playwright
+runtime, or a font-bundler.

package/dist/agent-src/skills/design-tokens/SKILL.md

@@ -63,17 +63,17 @@ under `dark.semantic.*` overriding the same semantic names (emitted as a
 
 ```bash
 # tokens.json → CSS variables (primitives + semantic + components + .dark)
-python3 <skills-root>/design-tokens/scripts/tokens.py generate \
+./scripts-run <skills-root>/design-tokens/scripts/tokens generate \
   --config tokens.json -o assets/design-tokens.css
 
 # tokens.json → Tailwind theme.extend.colors snippet
-python3 …/tokens.py generate --config tokens.json --format tailwind
+./scripts-run …/tokens generate --config tokens.json --format tailwind
 
 # token-discipline lint: hardcoded hex/rgb/px/rem outside token files
-python3 …/tokens.py validate --dir src/ [--json]
+./scripts-run …/tokens validate --dir src/ [--json]
 
 # embeddable inline CSS for standalone HTML artifacts
-python3 …/tokens.py embed --tokens assets/design-tokens.css --minimal --style
+./scripts-run …/tokens embed --tokens assets/design-tokens.css --minimal --style
 ```
 
 `validate --json` emits findings with `"kind": "token_violation"` — the
@@ -92,6 +92,12 @@ four-operation split assigns to *rules/linters*, not the corpus).
    actually uses.
 2. **Ground the values** — `design-intelligence` query gives the
    WCAG-checked semantic color set + typography pairing for the product.
+   No brand and no corpus match (a genuinely from-scratch palette) →
+   derive the accent set in `oklch()` with shared lightness and chroma,
+   varied hue (`oklch(50% 0.15 250)` / `… 200` / `… 280`) — equal L/C
+   keeps the hues perceptually balanced where random hex codes drift in
+   saturation; cross-check the result against C1/C5 avoidance before
+   locking it in.
 3. **Author `tokens.json`** from the starter: fill primitives, point
    semantics at them, add `dark.semantic` overrides.
 4. **Generate** CSS vars (and the Tailwind snippet when the stack is
@@ -129,6 +135,7 @@ four-operation split assigns to *rules/linters*, not the corpus).
 
 ## See also
 
+- [`design-canon.md`](../../../docs/guidelines/design-canon.md) § Colour references — a11y-contrast + culturally-specific palettes + named-system token models.
 - [`design-intelligence`](../design-intelligence/SKILL.md) — grounded value selection.
 - [`tailwind-engineer`](../tailwind-engineer/SKILL.md) — utility-discipline consumer.
 - [`react-shadcn-ui`](../react-shadcn-ui/SKILL.md) — shadcn token conventions.

package/dist/agent-src/skills/design-variations/SKILL.md

@@ -0,0 +1,127 @@
+---
+model_tier: inherit
+name: design-variations
+description: "Produce 3+ substantively distinct hi-fi design variations — basic to bold, one file with tweak controls — when the user asks for options, alternatives, or \"show me a few takes\"."
+domain: product
+personas: []
+workspaces:
+  - engineering
+packs:
+  - frontend-design
+trust:
+  level: professional
+install:
+  removable: true
+execution:
+  type: manual
+---
+
+# Design Variations
+
+Produce multiple substantively distinct design variations so the user can
+reject what they don't want and combine what they do. One design is one bet;
+three variations surface preferences the user didn't know they had.
+
+## When to use
+
+- The user asks for options, alternatives, "different takes", "show me a few"
+  on hi-fi UI work (screen, component, flow, visual treatment).
+- After a `wireframe` round settled the structure and the user wants styled
+  directions on top of it.
+
+**When NOT to use:** structure/flow exploration before any styling decision →
+[`wireframe`](../wireframe/SKILL.md) (lo-fi, disposable). Selecting ONE
+grounded direction without generating alternatives →
+[`design-intelligence`](../design-intelligence/SKILL.md). Reviewing an
+existing design → [`design-review`](../design-review/SKILL.md).
+
+## Procedure
+
+1. **Baseline.** Confirm what is varied (screen / component / flow / visual
+   treatment), the existing design context (DESIGN.md, brand tokens, UI kit —
+   run [`existing-ui-audit`](../existing-ui-audit/SKILL.md) when the output
+   lands in a real codebase, per the `ui-audit-gate` rule), the count
+   (default 3, ceiling 6), and the user's priority axis.
+2. **Pick 2–4 axes** to vary across: visual treatment (tone, density, shadow,
+   radius, type weight), layout (centered/asymmetric, single/multi-column,
+   full-bleed/inset), interaction model (single page vs multi-step, modal vs
+   inline), hierarchy (what is primary), tone (minimal/formal/playful/
+   editorial), component style. Map axes onto the project's Taste Dials
+   (Variance/Motion/Density) where DESIGN.md defines them.
+3. **Spec each variation BEFORE building** — one line per variation naming
+   its distinct palette family, type pairing, and layout skeleton. Left
+   unspecified, variations converge on one default look; variety must be
+   designed, not hoped for. Ground palette/type picks via
+   [`design-intelligence`](../design-intelligence/SKILL.md) and emit values
+   as tokens per [`design-tokens`](../design-tokens/SKILL.md).
+4. **Build basic → bold.** Variation 1 = by-the-book (matches existing
+   patterns); variation 2 = refined (same structure, one or two dimensions
+   pushed — often the actual pick); variation 3 = novel (genuinely different
+   layout/metaphor/aesthetic, deliberately off-distribution). Cover both
+   ends — an all-safe set wastes the round, an all-wild set ignores the brief.
+5. **Substantive, not cosmetic.** Two variations that differ only in button
+   color or shadow opacity are one variation — drop and replace. Litmus: the
+   user can articulate the difference between any two variations in one
+   sentence.
+6. **Present in a single file** with tweak controls — never `v1.html` /
+   `v2.html` / `v3.html`. Structure-sharing variants toggle via CSS custom
+   properties + a small floating "Tweaks" panel (3–8 controls: color picker,
+   font/variant dropdown, density slider, section toggles, copy inputs);
+   persist chosen values in `localStorage`. Structurally distinct variants
+   render side-by-side with labels. Even unasked, expose 1–2 tweak axes by
+   default.
+7. **Caption each variation** (1–2 sentences naming the axis it flexes) and
+   **close with a recommendation** — a designer offers an opinion; the user
+   decides.
+8. **Quality gate.** Novel ≠ sloppy: run `lint_design_slop` over the emitted
+   file (every variation individually passes; a DESIGN.md-declared direction
+   suppresses its flags) and honor the outward-artifact hygiene floor (Q13 in
+   [`design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)) —
+   no workspace paths, skill/tool names, or generator traces in the markup.
+   Final pass before delivery → [`design-review`](../design-review/SKILL.md).
+
+## Output format
+
+1. **One HTML/JSX file** containing all variations — side-by-side sections or
+   custom-property-driven variants with a floating Tweaks panel (3–8 controls,
+   `localStorage`-persisted); no per-variation file scatter.
+2. **Variation spec block** (comment or intro): per variation one line —
+   axis flexed, palette family, type pairing, layout skeleton.
+3. **Captions + one recommendation** naming the suggested pick and why, with
+   the trade-off of the runner-up.
+4. **Clean slop scan** — `lint_design_slop` output for the file (flags
+   resolved or DESIGN.md-justified), no Q13 violations.
+
+## Do NOT
+
+- Do NOT produce variations that differ only cosmetically (color swap, shadow
+  tweak) — replace with a substantive alternative.
+- Do NOT scatter `v1/v2/v3` files — one file, toggleable.
+- Do NOT let variations drift into one house style — spec palette/type/layout
+  per variation before building.
+- Do NOT skip the recommendation — presenting options without an opinion
+  pushes the decision cost back onto the user.
+- Do NOT invent brand values — consumer brand tokens win
+  (`brand-source-of-truth`); the corpus fills gaps only.
+- Do NOT embed system internals (paths, skill/tool names, generator traces)
+  in the emitted markup — Q13.
+
+## Gotcha
+
+- The "novel" variation is where slop concentrates: off-distribution choices
+  still pass the antipatterns catalog — deliberate ≠ default. Declare the
+  direction in the spec block so `lint_design_slop` gating reads intent.
+- Tweak panels leak into delivery: the panel must be removable (single
+  `<script>`/`<aside>` block, clearly marked) so the chosen variant ships
+  without exploration chrome.
+- More than 6 variations degrades choice quality — the user can't hold them
+  in mind; split into two rounds on different axes instead.
+
+## See also
+
+- [`wireframe`](../wireframe/SKILL.md) — lo-fi structure exploration before this.
+- [`design-intelligence`](../design-intelligence/SKILL.md) — grounded direction/palette/type selection.
+- [`design-tokens`](../design-tokens/SKILL.md) — token emission for variation values.
+- [`fe-design`](../fe-design/SKILL.md) — production heuristics the by-the-book variation follows.
+- [`design-review`](../design-review/SKILL.md) — final gate before delivery.
+- [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md) — catalog + Q13 outward-artifact hygiene.

package/dist/agent-src/skills/design-variations/evals/triggers.json

@@ -0,0 +1,17 @@
+{
+  "skill": "design-variations",
+  "last_eval": "2026-07-06",
+  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers hi-fi options/alternatives requests. Should-not-trigger covers near-miss neighbors: wireframe (lo-fi structure exploration), design-intelligence (single grounded direction), design-review (review existing), image generation, and single-implementation feature work.",
+  "queries": [
+    {"q": "show me 3 different takes on this pricing page", "trigger": true},
+    {"q": "give me a few design options for the dashboard header", "trigger": true},
+    {"q": "I can't decide on the hero layout — build some alternatives I can compare", "trigger": true},
+    {"q": "make this settings screen in a safe version and a bold version", "trigger": true},
+    {"q": "let me play with color and density options on this card grid", "trigger": true},
+    {"q": "sketch a few rough layout directions for the signup flow before we style anything", "trigger": false, "note": "lo-fi structure exploration → wireframe"},
+    {"q": "pick a visual direction and palette for our new SaaS app", "trigger": false, "note": "single grounded direction → design-intelligence"},
+    {"q": "review this landing page design for issues", "trigger": false, "note": "review of existing design → design-review"},
+    {"q": "generate 3 logo images in Midjourney", "trigger": false, "note": "AI image generation → image-provider-routing / logo-generation"},
+    {"q": "build the checkout form component", "trigger": false, "note": "single implementation, no options ask → fe-design / stack executor"}
+  ]
+}

package/dist/agent-src/skills/emit-tickets/SKILL.md

@@ -40,7 +40,7 @@ Steps at a glance:
 5. Write `manifest.yml` with acyclic `dependency_graph` and empty `linear_state`.
 6. Append `<!-- ticket: T-NNN -->` markers back into the roadmap.
 7. (Re)generate `agents/tickets/_registry.yml`.
-8. Run `lint_ticket_buildable.py` until exit 0 (max 3 attempts).
+8. Run `lint_ticket_buildable` until exit 0 (max 3 attempts).
 9. Tell the user the bundle is ready: paste a ticket into Linear/Jira, or have the agent create it via a tracker MCP server (ADR-102 — no API export).
 
 ### §0 — Locate the roadmap
@@ -97,7 +97,7 @@ Apply this floor **before** marking any ticket `lite`:
 - Any miss → split the ticket further, or escalate to `medium`
 - Architectural / multi-module → `high` (use `adr-create` first)
 
-**Gate:** run `python3 src/scripts/lint_ticket_buildable.ts agents/tickets/{slug}/`
+**Gate:** run `./scripts-run src/scripts/lint_ticket_buildable agents/tickets/{slug}/`
 and fix all errors before declaring any ticket `lite`. This is the only
 authoritative check — do not skip it.
 
@@ -154,7 +154,7 @@ If the file does not exist, create it with the `bundles:` root.
 ### §8 — Run the buildability gate
 
 ```bash
-python3 src/scripts/lint_ticket_buildable.ts agents/tickets/{slug}/
+./scripts-run src/scripts/lint_ticket_buildable agents/tickets/{slug}/
 ```
 
 Fix every reported error. Re-run until exit code 0. Max 3 attempts; if still
@@ -181,7 +181,7 @@ Do NOT auto-create tracker issues — paste/MCP is the user's call.
 
 - Implement or invent ticket content not traceable to a roadmap step.
 - Touch `src/scripts/**` — orchestrate; do not reimplement.
-- Mark a ticket `lite` before `lint_ticket_buildable.py` passes.
+- Mark a ticket `lite` before `lint_ticket_buildable` passes.
 - Create a circular `dependency_graph` — verify acyclicity before writing.
 - Auto-create tracker issues — paste/MCP is the user's call (ADR-102, no API export).
 - Reuse T-NNN numbers from another bundle in the same registry.

package/dist/agent-src/skills/existing-ui-audit/SKILL.md

@@ -199,6 +199,12 @@ violations will surface as new findings on every run.
 7. **`state.ui_audit.greenfield`** — boolean; when true, `greenfield_decision` MUST also be set before the dispatcher advances
 8. **`state.ui_audit.a11y_baseline`** *(optional)* — array of `{rule, selector, severity?}` entries documenting pre-existing a11y violations the review gate should treat as informational. Omit the key entirely when no baseline applies; do not write `[]` for "I checked and there are none" — that disables the gate's filter for every future run.
 
+**Design-system export (current-repo source):** to seed `DESIGN.md` from *this*
+repo, emit the inventory as a `design-system.json` artifact (the import contract
+in [`design-system-capture`](../design-system-capture/reference/design-system-json.md))
+and hand it to `design-system-capture` — same shape an external tool produces,
+so the import path is uniform.
+
 ## Gotcha
 
 - The model tends to skip the audit and start designing straight from the request — the dispatcher gate at `directives/ui/audit.py` enforces "no design without audit findings". Never treat this skill as optional for non-trivial UI.

package/dist/agent-src/skills/fe-design/SKILL.md

@@ -233,6 +233,26 @@ Animate `transform` and `opacity` only. Why: these run on the GPU compositor thr
 5. **Loading states** — Skeleton screens preferred over spinners. **Why:** skeletons reduce perceived wait time by showing structure immediately.
 6. **Error recovery** — Clear error messages with suggested actions. **Why:** "something went wrong" gives the user nothing to do; a specific message with a next step reduces support burden.
 
+## Craft details — typography & imagery
+
+- **`text-wrap: pretty` on body copy** — avoids widows/orphans without manual
+  breaks; cheap, no layout risk. (Display headlines: `text-wrap: balance`.)
+- **Honest placeholders over weak assets** — when the real image/illustration
+  is missing, use a striped placeholder with a monospace size label
+  (`repeating-linear-gradient(45deg, #E5E5E5 0 10px, #F5F5F5 10px 20px)` +
+  `product shot (1200×800)`) instead of a hand-drawn SVG or stock-ish filler.
+  A placeholder signals "asset needed"; a weak illustration signals nobody
+  had the asset. Never Lorem-ipsum copy in review-bound output
+  (per `output-discipline`) — use short label-style skeleton copy.
+
+## Presenting variants
+
+This skill produces ONE refined solution. When the user wants multiple options
+to compare (or a live tweak panel over one design), hand off to
+[`design-variations`](../design-variations/SKILL.md) — it owns the
+basic→bold variation method and the single-file tweak-panel mechanics
+(CSS custom properties + floating "Tweaks" panel + `localStorage`).
+
 ## Cross-task design memory — read DESIGN.md / PRODUCT.md first
 
 Before applying any heuristics from this reference, check the project root

package/dist/agent-src/skills/flux/SKILL.md

@@ -112,6 +112,10 @@ current state on the next polish round.
 - Flux has built-in validation display — don't add manual error rendering alongside it.
 - Don't mix Flux with raw HTML form elements in the same form.
 
+## Taste Dials
+
+`DESIGN.md` `## Taste Dials` → honour: Variance → layout-family spread + asymmetry; Motion → animation budget + reduced-motion posture; Density → spacing scale + info-per-viewport. Absent → follow brief's inferred dials.
+
 ## Do NOT
 
 - Do NOT use raw `<input>`, `<select>`, `<button>` when Flux equivalents exist.

package/dist/agent-src/skills/html-deck/SKILL.md

@@ -0,0 +1,123 @@
+---
+model_tier: inherit
+name: html-deck
+description: "Build a slide presentation as one HTML file — fixed 1920×1080 canvas letterboxed to any viewport, layout-system-first, type floors. Use for deck, slides, presentation, or pitch requests."
+domain: product
+personas: []
+workspaces:
+  - engineering
+packs:
+  - frontend-design
+trust:
+  level: professional
+install:
+  removable: true
+execution:
+  type: manual
+---
+
+# HTML Deck
+
+Build a slide presentation as a single HTML file with fixed-size slides that
+letterbox to any viewport. A deck is fixed-canvas media (default 1920×1080,
+16:9) — a different medium from responsive UI and from static posters.
+
+## When to use
+
+- The user asks for a deck, presentation, slides, or a pitch as a web/HTML
+  deliverable.
+
+**When NOT to use:** static single-image visual art (poster, PNG/PDF
+one-off) → [`canvas-design`](../canvas-design/SKILL.md). Responsive product
+UI → [`fe-design`](../fe-design/SKILL.md) + stack executor. Multiple styled
+options of one screen → [`design-variations`](../design-variations/SKILL.md).
+
+## Procedure
+
+1. **Discovery.** Confirm: audience (engineers / executives / customers —
+   determines tone and density), aspect ratio (16:9 default), slide count vs
+   time budget (~1 slide/minute; most decks land at 8–15), tone, source
+   material (PRD/doc — read it before sketching), speaker notes (off unless
+   requested), and the brand / design system. No brand →
+   [`design-intelligence`](../design-intelligence/SKILL.md) direction first.
+   A fully specified ask ("5-slide deck for the all-hands from this PRD")
+   skips the question round.
+2. **Commit to a layout system before any slide.** 4–6 layout types (cover,
+   section header, content, quote/pull-out, comparison two-column, closing/
+   CTA); per layout: background, headline size/position, body area, footer
+   treatment. 1–2 background colors across the deck (section headers may
+   break to a third). Record the system as a comment block at the top of the
+   file.
+3. **Start from the deck-shell starter** (`templates/deck-shell.html`,
+   skill-local): fixed-canvas scaling + letterboxing, keyboard/tap
+   navigation, slide counter, `localStorage` slide-index persistence,
+   print-to-PDF CSS. Each slide is a direct child `<section>` with a
+   1-indexed `data-screen-label` ("01 Title") so the user can reference
+   slides by the counter they see.
+4. **Build slide-by-slide, reveal early.** Show the file at 1–2 slides —
+   don't perfect 15 in private. Per slide: one primary message; **type
+   floors on a 1080p canvas: body ≥24px (32px+ preferred), headlines
+   60–96px+**; tokens from the active brand/design system (precedence per
+   `brand-source-of-truth`, emission per
+   [`design-tokens`](../design-tokens/SKILL.md)); honest placeholders for
+   missing imagery (striped background + monospace size label — see
+   [`fe-design § Craft details`](../fe-design/SKILL.md)); cut filler slides
+   ("Why choose us?", "About this deck") and data that doesn't support the
+   slide's point.
+5. **Speaker notes only when requested** — as a toggleable overlay or
+   per-slide `<aside hidden>`, never printed.
+6. **Quality gate.** Run `lint_design_slop` over the file; honor the
+   outward-artifact hygiene floor (Q13 in
+   [`design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md))
+   — no workspace paths, skill/tool names, or generator traces in markup or
+   comments; final pass → [`design-review`](../design-review/SKILL.md).
+   Verify scaling + navigation + persistence once in a browser before
+   delivery.
+
+## Output format
+
+1. **One self-contained HTML file** built on the deck-shell: fixed-canvas
+   `<section>` slides with 1-indexed `data-screen-label`s, letterbox scaling,
+   keyboard/tap navigation, slide counter, `localStorage` persistence,
+   print-to-PDF CSS.
+2. **Layout-system comment block** at the top of the file naming the 4–6
+   layout types and the background-color budget.
+3. **Type-floor compliance** — body ≥24px, headlines 60–96px+ on the 1080p
+   canvas; deviations only with a stated reason.
+4. **Clean slop scan + Q13** — `lint_design_slop` findings resolved or
+   DESIGN.md-justified; no system internals in the artifact.
+
+## Do NOT
+
+- Do NOT hand-roll the scaling/navigation — start from the deck-shell
+  starter; re-derived viewport math drifts.
+- Do NOT use responsive units/breakpoints inside slides — a deck is
+  fixed-canvas; the shell scales the whole stage.
+- Do NOT drop body text below 24px on a 1080p canvas — projector legibility
+  is the floor, not a preference.
+- Do NOT pad with filler slides or invented stats — every slide earns its
+  place.
+- Do NOT introduce per-slide ad-hoc colors/spacing — the layout system from
+  step 2 is the budget.
+- Do NOT embed system internals (paths, skill/tool names, generator traces)
+  in the file — Q13.
+
+## Gotcha
+
+- `localStorage` persistence keys on `location.pathname` — two decks served
+  from the same path share a slide index; rename the file per deck or extend
+  the key when hosting several decks under one path.
+- Print-to-PDF uses the fixed canvas per page: browsers map it onto the
+  paper size — set the print dialog to landscape + "fit to page" or the
+  slides clip; test one print preview before shipping a PDF.
+- Emoji in slide headlines is the CP5 tell exactly as in product UI — the
+  deck medium doesn't exempt it.
+
+## See also
+
+- `templates/deck-shell.html` (skill-local) — the canonical shell; copy, don't re-derive.
+- [`canvas-design`](../canvas-design/SKILL.md) — static posters/one-frame art (not decks).
+- [`design-intelligence`](../design-intelligence/SKILL.md) — direction/palette/type grounding.
+- [`design-tokens`](../design-tokens/SKILL.md) / [`brand-to-tokens`](../brand-to-tokens/SKILL.md) — token precedence and emission.
+- [`design-review`](../design-review/SKILL.md) — final review gate.
+- [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md) — catalog, CP5, Q13.

package/dist/agent-src/skills/html-deck/evals/triggers.json

@@ -0,0 +1,17 @@
+{
+  "skill": "html-deck",
+  "last_eval": "2026-07-06",
+  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers deck/slides/presentation/pitch builds in HTML. Should-not-trigger covers near-miss neighbors: canvas-design (posters/static art), fe-design (responsive UI), design-variations (options), PowerPoint-file requests, and content-only outline asks.",
+  "queries": [
+    {"q": "make a 10-slide deck for the investor pitch", "trigger": true},
+    {"q": "build a presentation from this PRD for the engineering all-hands", "trigger": true},
+    {"q": "turn these notes into HTML slides I can present tomorrow", "trigger": true},
+    {"q": "create a pitch deck with our brand colors, 16:9", "trigger": true},
+    {"q": "I need a slide presentation that also prints to PDF", "trigger": true},
+    {"q": "design a poster for the conference booth", "trigger": false, "note": "static one-frame art → canvas-design"},
+    {"q": "build the landing page hero section", "trigger": false, "note": "responsive UI → fe-design / stack executor"},
+    {"q": "show me 3 design options for this dashboard", "trigger": false, "note": "options → design-variations"},
+    {"q": "write an outline for my talk", "trigger": false, "note": "content-only ask, no HTML deliverable"},
+    {"q": "export our Google Slides to PowerPoint", "trigger": false, "note": "file conversion, not an HTML deck build"}
+  ]
+}

package/dist/agent-src/skills/html-deck/templates/deck-shell.html

@@ -0,0 +1,77 @@
+<!doctype html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>Deck</title>
+<style>
+  /* Deck shell — fixed-canvas slides (default 1920×1080) letterboxed to any
+     viewport. Slides are direct children <section> of <main class="deck">. */
+  :root { --deck-w: 1920; --deck-h: 1080; }
+  * { margin: 0; padding: 0; box-sizing: border-box; }
+  html, body { height: 100%; background: #111; overflow: hidden; }
+  .deck { position: absolute; top: 50%; left: 50%; width: calc(var(--deck-w) * 1px); height: calc(var(--deck-h) * 1px); transform-origin: center center; }
+  .deck > section { position: absolute; inset: 0; display: none; overflow: hidden; background: #fafafa; color: #1a1a1a; }
+  .deck > section.active { display: block; }
+  .deck-counter { position: fixed; right: 16px; bottom: 12px; font: 14px/1 monospace; color: #888; z-index: 10; }
+  @media print {
+    html, body { height: auto; overflow: visible; background: none; }
+    .deck { position: static; transform: none !important; width: auto; height: auto; }
+    .deck > section { position: relative; display: block; width: calc(var(--deck-w) * 1px); height: calc(var(--deck-h) * 1px); page-break-after: always; }
+    .deck-counter { display: none; }
+  }
+</style>
+</head>
+<body>
+<main class="deck">
+  <!-- Each slide: <section data-screen-label="01 Title">…</section> (1-indexed
+       labels match the counter the viewer sees). Replace the samples. -->
+  <section data-screen-label="01 Title">
+    <h1 style="font-size:96px;padding:120px">Deck title</h1>
+  </section>
+  <section data-screen-label="02 Content">
+    <h2 style="font-size:64px;padding:120px 120px 40px">Section</h2>
+    <p style="font-size:32px;padding:0 120px">Body text on a 1080p canvas stays at 24px minimum; 32px preferred.</p>
+  </section>
+</main>
+<div class="deck-counter" aria-hidden="true"></div>
+<script>
+(() => {
+  const deck = document.querySelector(".deck");
+  const slides = Array.from(deck.querySelectorAll(":scope > section"));
+  const counter = document.querySelector(".deck-counter");
+  const KEY = "deck-slide:" + location.pathname;
+  let i = Math.min(parseInt(localStorage.getItem(KEY) || "0", 10) || 0, slides.length - 1);
+
+  function show(n) {
+    i = Math.max(0, Math.min(n, slides.length - 1));
+    slides.forEach((s, k) => s.classList.toggle("active", k === i));
+    counter.textContent = (i + 1) + " / " + slides.length;
+    localStorage.setItem(KEY, String(i));
+  }
+
+  function fit() {
+    const w = parseFloat(getComputedStyle(document.documentElement).getPropertyValue("--deck-w"));
+    const h = parseFloat(getComputedStyle(document.documentElement).getPropertyValue("--deck-h"));
+    const scale = Math.min(innerWidth / w, innerHeight / h);
+    deck.style.transform = "translate(-50%, -50%) scale(" + scale + ")";
+  }
+
+  addEventListener("keydown", (e) => {
+    if (e.key === "ArrowRight" || e.key === "PageDown" || e.key === " ") show(i + 1);
+    else if (e.key === "ArrowLeft" || e.key === "PageUp") show(i - 1);
+    else if (e.key === "Home") show(0);
+    else if (e.key === "End") show(slides.length - 1);
+  });
+  // Tap/click navigation: right two-thirds advances, left third goes back.
+  addEventListener("click", (e) => {
+    if (e.target.closest("a, button, input, textarea, select, [contenteditable]")) return;
+    show(e.clientX < innerWidth / 3 ? i - 1 : i + 1);
+  });
+  addEventListener("resize", fit);
+  fit();
+  show(i);
+})();
+</script>
+</body>
+</html>

package/dist/agent-src/skills/iconography/SKILL.md

@@ -82,6 +82,7 @@ execution:
 
 ## See also
 
+- [`design-canon.md`](../../../docs/guidelines/design-canon.md) § Icon systems — prefer a named system's icon set (Material Symbols / SF Symbols / Fluent / Carbon) when that system is in play.
 - [`design-tokens`](../design-tokens/SKILL.md) — token system the icon color/size variables should reference.
 - [`typography-system`](../typography-system/SKILL.md) — sibling visual-consistency skill.
 - [`fe-design`](../fe-design/SKILL.md) — broader frontend design discipline.

package/dist/agent-src/skills/image-editing/evals/triggers.json

@@ -1,17 +1,17 @@
 {
+  "skill": "image-editing",
   "last_eval": "2026-06-16",
-  "true": [
-    "edit the background of this product shot to a white studio setting",
-    "inpaint the logo out of the upper-right corner of this image",
-    "make a variation of this hero image in a warmer colour palette",
-    "remove the person standing on the left side of the photo",
-    "modify this existing render — I want the sky replaced with a sunset"
-  ],
-  "false": [
-    "generate a new product shot from scratch — I have no existing image",
-    "which image provider should I use for this job?",
-    "create a logo for my company",
-    "how do I write a good prompt for Ideogram?",
-    "do I need a rights check before using a celebrity's likeness in my image?"
+  "description": "5 should-trigger + 5 should-not-trigger. Should-trigger covers inpainting, background replacement, colour variation, object removal, and targeted render modification. Should-not covers near-miss neighbours: greenfield image generation (image-creator/image-generation), provider selection (image-provider-routing), prompt writing (image-creator), rights/licence check (media governance).",
+  "queries": [
+    { "q": "edit the background of this product shot to a white studio setting", "trigger": true },
+    { "q": "inpaint the logo out of the upper-right corner of this image", "trigger": true },
+    { "q": "make a variation of this hero image in a warmer colour palette", "trigger": true },
+    { "q": "remove the person standing on the left side of the photo", "trigger": true },
+    { "q": "modify this existing render — I want the sky replaced with a sunset", "trigger": true },
+    { "q": "generate a new product shot from scratch — I have no existing image", "trigger": false, "note": "greenfield generation → image-creator / image-generation" },
+    { "q": "which image provider should I use for this job?", "trigger": false, "note": "provider routing → image-provider-routing" },
+    { "q": "create a logo for my company", "trigger": false, "note": "logo creation → logo-generation" },
+    { "q": "how do I write a good prompt for Ideogram?", "trigger": false, "note": "prompt engineering → image-creator" },
+    { "q": "do I need a rights check before using a celebrity's likeness in my image?", "trigger": false, "note": "likeness / rights → media governance rules" }
   ]
 }