@event4u/agent-config 7.4.0 → 8.0.0

package/dist/agent-src/skills/blameless-post-mortem/SKILL.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: blameless-post-mortem
 description: "Use after an incident or outage is resolved — blame-free facilitation, root cause, corrective actions, memory write-back — even for a near-miss. Consumes the incident-commander skeleton."
-source: package
 domain: quality
 personas:
   - senior-engineer
@@ -11,11 +10,9 @@ workspaces:
   - engineering
 packs:
   - analysis-workbench
-lifecycle: active
 trust:
   level: professional
   confidence: medium
-  human_review_required: false
 install:
   default: false
   removable: true

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

@@ -52,7 +52,7 @@ Provenance: [`ATTRIBUTION.md`](ATTRIBUTION.md); manifest:
 1. **Ground or search** (paths resolve skill-relative; works from any cwd):
 
    ```bash
-   python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+   ./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
      --manifest <skills-root>/brand/data/manifest.json \
      "<brand brief: sector + intent + audience>" \
      [--domain archetype|voice|naming|color|logo|messaging|typography] \

package/dist/agent-src/skills/brand-identity/SKILL.md

@@ -35,7 +35,7 @@ Grounding + Method skill. Turns a confirmed brand strategy into an identity cons
 2. **Ground the colour story** via the brand corpus:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/brand/data/manifest.json \
   "<archetype + sector>" --domain color --json
 ```
@@ -45,7 +45,7 @@ python3 <skills-root>/corpus-grounding/scripts/ground.py search \
 3. **Ground the type story** via:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/brand/data/manifest.json \
   "<archetype + sector>" --domain typography --json
 ```
@@ -55,7 +55,7 @@ python3 <skills-root>/corpus-grounding/scripts/ground.py search \
 4. **Ground the logo direction** via:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/brand/data/manifest.json \
   "<archetype + sector>" --domain logo --json
 ```

package/dist/agent-src/skills/brand-strategy/SKILL.md

@@ -35,7 +35,7 @@ Grounding skill. Consults the brand corpus to surface archetype, positioning, vo
 2. **Ground via the corpus.** Run the corpus engine for each required domain. Start with archetype, then voice, then messaging:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/brand/data/manifest.json \
   "<sector + audience + intent>" --domain archetype --json
 ```

package/dist/agent-src/skills/brand-to-tokens/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 name: brand-to-tokens
-description: "Derive a DTCG .tokens.json source of truth from confirmed brand decisions, emit CSS vars + Tailwind via design-tokens, and export locked brand deck templates. Use to turn a brand identity into tokens."
+description: "Turn a confirmed brand identity into a DTCG .tokens.json source of truth — emit CSS vars + Tailwind via design-tokens, export locked brand deck templates."
 domain: engineering
 personas: []
 workspaces:
@@ -49,13 +49,13 @@ execution:
 3. **Generate** CSS vars + Tailwind through the toolchain:
 
    ```bash
-   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
-   python3 <skills-root>/design-tokens/scripts/tokens.py generate \
+   ./scripts-run <skills-root>/design-tokens/scripts/tokens generate \
      --config .tokens.json --format tailwind
    ```
 
-4. **Validate** — `python3 <skills-root>/design-tokens/scripts/tokens.py
+4. **Validate** — `./scripts-run <skills-root>/design-tokens/scripts/tokens
    validate --dir src/` until clean (exit 0 is the evidence); convert
    hardcoded values to `var(--token)`.
 5. **Export the deck templates** — emit the locked-variable brand deck
@@ -95,6 +95,7 @@ execution:
 
 ## See also
 
+- [`design-canon.md`](../../../docs/guidelines/design-canon.md) § Colour references — culturally-situated palettes + a11y-contrast grounding when deriving brand colour tokens.
 - [`brand-identity`](../brand-identity/SKILL.md) — supplies the constraint set this skill derives tokens from.
 - [`design-tokens`](../design-tokens/SKILL.md) — the DTCG toolchain that emits CSS/Tailwind from `.tokens.json`.
 - [`typography-system`](../typography-system/SKILL.md) — brand-aware stage-2 supplies the type tokens.

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

@@ -145,3 +145,9 @@ Apply the [Frugality Charter](../../contexts/contracts/frugality-charter.md).
 * Skip the philosophy file — the artifact without it is just an image
 * Skip the refinement pass
 * Write binary artifacts to the repo root or to source-of-truth dirs
+
+## See also
+
+- [`html-deck`](../html-deck/SKILL.md) — multi-slide HTML presentations
+  (fixed-canvas deck with navigation); this skill owns single-frame static
+  art, not decks.

package/dist/agent-src/skills/check-refs/SKILL.md

@@ -9,12 +9,15 @@ execution:
   timeout_seconds: 60
   allowed_tools: []
   command:
-    - python3
-    - src/scripts/check_references.ts
+    - ./scripts-run
+    - src/scripts/check_references
 workspaces:
   - agent-config-maintainer
 packs:
   - meta
+gaps:
+  - description: "Only validates references to known-root paths (docs/, skills/, rules/, commands/, contexts/, personas/, …). A relative-path link such as `./sibling.md` or `../foo.md` is not matched, so a broken relative link is never reported."
+    witness: tests/scripts/witness/check_refs_relative_gap.test.ts
 ---
 
 # check-refs
@@ -52,7 +55,7 @@ this skill's frontmatter governs the call:
 ```
 
 The dispatcher resolves the request, the shell handler runs
-`python3 src/scripts/check_references.ts`, captures stdout/stderr, and returns a
+`./scripts-run src/scripts/check_references`, captures stdout/stderr, and returns a
 typed `ExecutionResult`.
 
 ### 3. Verify the result
@@ -63,7 +66,7 @@ Check the returned `ExecutionResult`:
 - `exit_code: 1` → at least one broken reference — read `stdout` for file,
   line, and the offending ref, then fix the source or update the target
 - `status: timeout` → the checker exceeded `timeout_seconds` — investigate
-- `status: error` → interpreter or script missing — confirm `python3` and
+- `status: error` → runner or script missing — confirm `./scripts-run` and
   `src/scripts/check_references.ts` are available at the repository root
 
 ## Output format

package/dist/agent-src/skills/code-review/SKILL.md

@@ -3,6 +3,7 @@ model_tier: high
 name: code-review
 description: "Use when the user says \"review this\", \"check my code\", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards."
 domain: quality
+parallelizable: files
 workspaces:
   - engineering
 packs:
@@ -162,6 +163,10 @@ gh api repos/{owner}/{repo}/pulls/comments/{comment_id}/replies \
   -f body="Fixed in latest commit."
 ```
 
+## Rubric pass (optional, surfacing-only)
+
+After completing review, run [`judge-artifact-completeness`](../judge-artifact-completeness/SKILL.md) with rubric `pr-review-score` to verify evidence-fit, risk/blast-radius, migration/rollback completeness. Invoke for high-risk or when user asks — not by default.
+
 ## Output format
 
 1. Structure every finding by severity (Blocker / Suggestion / Nit) using the block below; never mix severities in one block.

package/dist/agent-src/skills/complexity-first-planning/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: complexity-first-planning
 description: "Use when staging multi-component or uncertain work — tackle the load-bearing unknown first (risk-first decomposition), not the easy parts first."
-source: package
 domain: engineering
 status: active
 model_tier: medium
@@ -43,10 +42,12 @@ unknown to resolve), or when the user has already fixed the sequence.
 
 ## Procedure
 
-1. **Inspect and name the unknowns.** Read the affected components first, then
-   list which carry real uncertainty (technical feasibility, an unverified
-   integration, an ambiguous requirement) — analyze the existing system before
-   planning any change.
+1. **Inspect and name the unknowns.** Read the affected components first
+   (start from the **repo** slot of the
+   [context-spine](../../../docs/contracts/context-spine.md) when present),
+   then list which carry real uncertainty (technical feasibility, an
+   unverified integration, an ambiguous requirement) — analyze the existing
+   system before planning any change.
 2. **Assess and rank by load-bearing risk.** The load-bearing unknown is the one
    whose failure invalidates the most dependent work — not the one that is merely hard.
 3. **Resolve it first.** Spike / probe / prototype the load-bearing unknown

package/dist/agent-src/skills/condense-memory/SKILL.md

@@ -36,13 +36,13 @@ Use when:
 ## Procedure
 
 1. **Analyse target first.** Before any write, **inspect** target with `view` or `wc -l` to confirm it is always-loaded memory file (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`, `GEMINI.md`, `.windsurfrules`), not generated, and has prose paragraphs to condense (pointer-only Thin-Root file may net near-zero). Skip rest of procedure if any check fails.
-2. **Check denylist gate.** Run `python3 scripts/condense_memory.py <path> --check` — exit 0 = safe; exit 2 = denylist hit, stop and surface refusal.
+2. **Check denylist gate.** Run `./scripts-run src/scripts/condense_memory <path> --check` — exit 0 = safe; exit 2 = denylist hit, stop and surface refusal.
 3. **Record baseline.** `wc -c <path>` — capture pre-condensation char count for commit message.
-4. **Condense.** `python3 scripts/condense_memory.py <path>`. Script writes `<path>.original.md` (verbatim backup) and rewrites `<path>` with `original_sha256:` + `condensed_at:` frontmatter.
+4. **Condense.** `./scripts-run src/scripts/condense_memory <path>`. Script writes `<path>.original.md` (verbatim backup) and rewrites `<path>` with `original_sha256:` + `condensed_at:` frontmatter.
 5. **Inspect diff.** Eyeball every Iron-Law fence, numbered-options block, code fence, backtick span, `❌`/`⚠️`/`✅` line, and frontmatter pair — all must be byte-identical. Body prose may have lost articles (`the`/`a`/`an`) and auxiliaries (`is`/`are`/`was`/`be`/`that`/`which`).
-6. **Validate idempotency.** Re-run `python3 scripts/condense_memory.py <path>` — clean re-run is no-op (body hash matches). Non-zero exit = stop, escalate.
+6. **Validate idempotency.** Re-run `./scripts-run src/scripts/condense_memory <path>` — clean re-run is no-op (body hash matches). Non-zero exit = stop, escalate.
 7. **Commit both files together.** `<path>` and `<path>.original.md` ship as pair. Backup is rollback path; never commit one without other.
-8. **Rollback path.** If readability fails review at step 5: `python3 scripts/condense_memory.py <path> --decondense` restores backup and deletes `.original.md`.
+8. **Rollback path.** If readability fails review at step 5: `./scripts-run src/scripts/condense_memory <path> --decondense` restores backup and deletes `.original.md`.
 
 ## Output format
 
@@ -57,7 +57,7 @@ Do **not** narrate algorithm, grammar rules, or carve-out theory — rule and th
 
 ## Carve-outs — byte-for-byte preserved
 
-Mirrors seven carve-out classes in [`telegraph-speak`](../../rules/telegraph-speak.md). Condensation engine in [`scripts/condense_memory.py`](../../../scripts/condense_memory.py) preserves:
+Mirrors seven carve-out classes in [`telegraph-speak`](../../rules/telegraph-speak.md). Condensation engine in [`src/scripts/condense_memory.ts`](../../../src/scripts/condense_memory.ts) preserves:
 
 1. **Triple-backtick fences** — any language, any depth.
 2. **Numbered-options lines** — `^>?\s*\d+\.\s` plus `**Recommendation:**` / `**Empfehlung:**` label.
@@ -67,7 +67,7 @@ Mirrors seven carve-out classes in [`telegraph-speak`](../../rules/telegraph-spe
 6. **Frontmatter blocks** — `---` fence pairs at head of file.
 7. **Mode markers** per [`role-mode-adherence`](../../rules/role-mode-adherence.md).
 
-Mangling any of these breaks Iron-Law surface host tool reads. Unit tests in `tests/test_condense_memory.py` lock each carve-out class as regression case.
+Mangling any of these breaks Iron-Law surface host tool reads. Unit tests in `tests/scripts/condense_memory.test.ts` lock each carve-out class as regression case.
 
 ## Idempotency contract — Step 9 guard
 
@@ -83,7 +83,7 @@ If you need to edit condensed memory file, run `--decondense` first, edit restor
 
 ## Sensitive-path gate
 
-Every read path passes through [`scripts/validate_safe_paths.py`](../../../scripts/validate_safe_paths.py) `assert_safe()` before bytes leave disk. Gate is security floor for Phase 2 (input-side condensation) per `step-16-telegraph-substance.md` Phase 0; rollback of gate is rollback of this skill.
+Every read path passes through [`src/scripts/validate_safe_paths.ts`](../../../src/scripts/validate_safe_paths.ts) `assert_safe()` before bytes leave disk. Gate is security floor for Phase 2 (input-side condensation) per `step-16-telegraph-substance.md` Phase 0; rollback of gate is rollback of this skill.
 
 CLI exit codes:
 
@@ -106,7 +106,7 @@ CLI exit codes:
 No published `telegraph-v2` baseline for input-side savings yet (Step 11 of `step-16-telegraph-substance.md` ships that). Until then, maintainer judges per-target whether condensation pays its readability cost. Suggested workflow:
 
 1. `wc -c <path>` before — record baseline char count.
-2. `python3 scripts/condense_memory.py <path>` — condense + back up.
+2. `./scripts-run src/scripts/condense_memory <path>` — condense + back up.
 3. `wc -c <path>` after — record post-condensation char count.
 4. Eyeball diff: does prose stay legible? Are all Iron-Law fences intact?
 5. If yes → commit both `<path>` and `<path>.original.md`. If no → `--decondense`.
@@ -116,8 +116,8 @@ Future `telegraph-v2.md` will tabulate realised input-token saving against `agen
 ## Cross-references
 
 - [`telegraph-speak`](../../rules/telegraph-speak.md) — runtime rule script mirrors for input-side targets; `telegraph.speak_scope` does **not** gate this script (input-side runs regardless).
-- [`scripts/validate_safe_paths.py`](../../../scripts/validate_safe_paths.py) — Phase 0 gate; ported from upstream Telegraph `63a91ec`.
-- [`scripts/condense_memory.py`](../../../scripts/condense_memory.py) — implementation.
-- [`tests/test_condense_memory.py`](../../../tests/test_condense_memory.py) — regression locks for each carve-out + idempotency + denylist.
+- [`src/scripts/validate_safe_paths.ts`](../../../src/scripts/validate_safe_paths.ts) — Phase 0 gate; ported from upstream Telegraph `63a91ec`.
+- [`src/scripts/condense_memory.ts`](../../../src/scripts/condense_memory.ts) — implementation.
+- [`tests/scripts/condense_memory.test.ts`](../../../tests/scripts/condense_memory.test.ts) — regression locks for each carve-out + idempotency + denylist.
 - [`docs/contracts/condensation-default-kill-criterion.md`](../../../docs/contracts/condensation-default-kill-criterion.md) — v1 verdict (output-side; informs but does not gate this skill).
 - [`agents-md-thin-root`](../agents-md-thin-root/SKILL.md) — caps consumer-shipped `templates/AGENTS.md`; this skill is one tool to land under cap.

package/dist/agent-src/skills/context-authoring/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 name: context-authoring
-description: "Use when filling in knowledge-layer context files — auth-model, tenant-boundaries, data-sensitivity, deployment-order, observability — interactive walkthrough that turns templates into reviewer fuel."
+description: "Use when filling knowledge-layer context files — auth-model, tenant-boundaries, data-sensitivity, deployment-order, observability — interactive template walkthrough."
 domain: process
 workspaces:
   - agent-config-maintainer

package/dist/agent-src/skills/context-document/SKILL.md

@@ -72,6 +72,7 @@ agents/settings/contexts/                                # Project-wide contexts
 | **Knowledge card** | Trust-tiered cache of *expensive* (remote) structural evidence — negative facts + pointers durable, positive structure a hypothesis | `lodash.md`, `stripe-api.md` |
 | **Standards card (Class A)** | Coding standards **derived from real tooling config** — pointer + digest, `trust: high (config-derived)`, auto-refreshed when config changes; never a flattened claim | `coding-standards.md` (points at `ruff.toml`, `.editorconfig`) |
 | **Lesson card (Class C)** | Learned lesson — `symptom` (fact) split from `hypothesis` (decaying theory), `trust: low`, subject-not-person, anti-calcification decay; promoted only via human gate (accumulation layer is eval-gated) | `agents/memory/curated/lessons/<slug>.md` |
+| **Knowledge page (typed)** | Team-shared, lifecycle-typed knowledge grown while working the project — episodic sessions, semantic concepts, procedures on the way to a skill, small decisions | `agents/knowledge/concepts/api-response-shape.md` |
 
 ## Where to store contexts
 
@@ -81,6 +82,7 @@ agents/settings/contexts/                                # Project-wide contexts
 | Project-wide or cross-module | `agents/settings/contexts/` |
 | Module-specific | `{module_root}/{Module}/{agent_folder}/settings/contexts/` (resolved via `modules.root_paths` + `modules.agent_folder`; Laravel example: `app/Modules/{Module}/agents/settings/contexts/`) |
 | **Knowledge card** (committed) | `agents/knowledge/<source>.md` — fill from the `knowledge-card` template |
+| **Knowledge page (typed, committed)** | `agents/knowledge/{sessions,concepts,procedures,decisions}/<slug>.md` — fill from the `knowledge-pages` template |
 | **Evidence Report / probe dumps / absence log** (ephemeral) | `agents/memory/knowledge/session/` (gitignored, overwritten each task) |
 | If unsure | Ask the user |
 
@@ -112,6 +114,21 @@ pointer, trust tagging, multi-evidence consistency). See
 card-worthy and [`evidence-discipline`](../../agent-src/contexts/execution/evidence-discipline.md)
 for the full model.
 
+### Knowledge pages — the typed sibling directories
+
+Alongside knowledge cards, `agents/knowledge/{sessions,concepts,procedures,decisions}/`
+holds team-shared knowledge grown **while working the project** — coding
+standards observed, module structure, API endpoint shapes, recurring
+mistakes, small decisions not big enough for an ADR. Fill new pages from the
+[`knowledge-pages`](../../agent-src/templates/contexts/knowledge-pages.md)
+template.
+
+**Retrieval protocol — index-first, then grep, then read.** Read
+`agents/knowledge/INDEX.md` first (one line per page, regenerated by
+`src/scripts/generate_knowledge_index.ts`); `grep` keywords second; read the
+specific file third. Never enumerate every knowledge file directly — no
+search infrastructure by design.
+
 ### Shared vs. project-specific contexts
 
 **`.augment/contexts/`** — Part of the shared package. Describes the agent infrastructure:

package/dist/agent-src/skills/corpus-grounding/SKILL.md

@@ -63,16 +63,16 @@ Scripts resolve all paths **skill-relative** (per
 — they work from any cwd:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/<domain-skill>/data/manifest.json \
   "fintech dashboard" [--domain style] [--stack react] \
   [--filter "Severity=HIGH"] [--max-results 3] [--json]
 
-python3 <skills-root>/corpus-grounding/scripts/ground.py ground \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground ground \
   --manifest <skills-root>/<domain-skill>/data/manifest.json \
   "luxury e-commerce" [--context '{"data_heavy": true}'] [--persist DIR]
 
-python3 <skills-root>/corpus-grounding/scripts/ground.py validate --manifest …
+./scripts-run <skills-root>/corpus-grounding/scripts/ground validate --manifest …
 ```
 
 `<skills-root>` is wherever skills are deployed (`~/.claude/skills/` for

package/dist/agent-src/skills/decision-record/SKILL.md

@@ -105,6 +105,12 @@ Write:
 - **Consequences:** what becomes true, what becomes harder, what
   becomes impossible. At least one of each, or admit that nothing
   becomes harder (rare; verify).
+- **Revisit-if:** the condition that would reopen this decision — new
+  evidence class, a changed constraint the decision assumed, or an
+  age threshold. A lock recorded without this line reads as permanent
+  law instead of a decision under current conditions; see
+  [`decision-revisit-gate`](../../rules/decision-revisit-gate.md) for
+  what happens when a later change is blocked by it without one.
 
 ### 5. Wire the supersession chain (if any)
 

package/dist/agent-src/skills/decision-review/SKILL.md

@@ -2,17 +2,14 @@
 model_tier: high
 name: decision-review
 description: "Use to audit a past architectural decision — did the chosen option hold up, what assumptions drifted, should the ADR be superseded? Backward review only; does not lock new choices."
-source: package
 domain: process
 workspaces:
   - engineering
 packs:
   - analysis-workbench
-lifecycle: active
 trust:
   level: professional
   confidence: medium
-  human_review_required: false
 install:
   default: false
   removable: true
@@ -40,6 +37,11 @@ install:
   have contributed to problems.
 - Preparation for a supersession: confirm the old decision actually
   needs replacing before writing a new ADR.
+- Routed here by [`decision-revisit-gate`](../../rules/decision-revisit-gate.md)
+  when a beneficial change is blocked by a recorded lock (honest-null
+  verdict, "don't relitigate" memory, budget canon, or ADR) — this skill
+  supplies the backward-audit procedure that rule's re-evaluation offer
+  points to.
 
 Do NOT use when:
 

package/dist/agent-src/skills/deep-reading-analyst/SKILL.md

@@ -170,13 +170,16 @@ Regardless of goal, close with three fixed blocks:
 ## Do NOT
 
 - Do NOT force-apply all frameworks at the user's chosen depth — drop ones that add no insight.
-- Do NOT copy text verbatim from the source — always reword for the user's understanding.
+- Do NOT copy text verbatim from the source — always reword for the user's understanding; any exact quote follows `content-quoting-floor` (≤15 words, one quote per source).
+- Do NOT restate a fresh-lookup-class claim (current status, version, price, date) from model memory — verify against a live source or flag it as unverified, per `asking-and-brevity-examples § Volatile-fact freshness`.
 - Do NOT use academic jargon without one-line definitions in the "key concepts" block.
 - Do NOT skip Step 5 — the takeaways + quick win are the load-bearing output, not optional decoration.
 - Do NOT route code reviews, diff stress-tests, or incident debugging through this skill.
 
 ## Reference modules
 
+All 8 framework modules are project-local guidelines under `docs/guidelines/agent-infra/` (full text adopted under the Reference-Guideline Sunset Policy). Each carries an `## ADOPT citation` footer pinning its MIT upstream origin.
+
 - [`scqa-framework`](../../../docs/guidelines/agent-infra/scqa-framework.md) — situation / complication / question / answer decomposition.
 - [`5w2h-analysis`](../../../docs/guidelines/agent-infra/5w2h-analysis.md) — completeness check (7 questions).
 - [`critical-thinking`](../../../docs/guidelines/agent-infra/critical-thinking.md) — argument quality / fallacy detection.
@@ -186,3 +189,5 @@ Regardless of goal, close with three fixed blocks:
 - [`systems-thinking`](../../../docs/guidelines/agent-infra/systems-thinking.md) — feedback loops + leverage points.
 - [`six-hats`](../../../docs/guidelines/agent-infra/six-hats.md) — White / Red / Black / Yellow / Green / Blue protocol.
 - [`comparison-matrix`](../../../docs/guidelines/agent-infra/comparison-matrix.md) — cross-source synthesis (L4 only).
+
+> **Deprecated — on-demand upstream loading.** Earlier revisions of this skill described loading some modules "on demand from a SHA-pinned URL", backed by an `external_source` frontmatter pin. That capability was **never wired** (no fetcher ever consumed the pin; it was schema-only metadata), so the pin and its `refresh_trigger` / `sunset_criterion` bundle have been **removed** — every module is local, no runtime fetch is needed. If a future revision genuinely needs live upstream content, build an explicit fetch step; do not reintroduce a non-functional metadata pin.

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

@@ -97,6 +97,35 @@ Examples:
 
 **If context is incomplete:** state so and proceed exploratory — *"Design context incomplete: no audience defined; proposing exploratory direction, expect revision after audience is clarified."* Do NOT block on missing context; do NOT prompt the user with a gate; state the gap and continue.
 
+### Taste Dials — quantify, infer, emit
+
+If `DESIGN.md` declares `## Taste Dials`, use those values. Otherwise infer
+three 1–10 dials from the brief and append them to the Design Read line
+(`… · dials V/M/D = 6/3/4`) so the user can correct them; on confirmation,
+suggest persisting to `DESIGN.md` (via `design-system-capture`). Dials are a
+config, not a vibe — never re-infer when `DESIGN.md` already sets them.
+
+**Dial Inference Table** (brief signal → Variance / Motion / Density, 1–10):
+
+| Brief signal | V | M | D |
+|---|---|---|---|
+| minimal / calm / editorial / clean | 3–5 | 2–4 | 2–4 |
+| trust / regulated / public-sector / fintech | 3–4 | 2–3 | 4–6 |
+| default / unstated | 5–6 | 3–4 | 4–5 |
+| data-dense / dashboard / admin / cockpit | 4–6 | 2–3 | 7–9 |
+| bold / playful / expressive / awards / Dribbble | 8–10 | 7–10 | 3–5 |
+
+**Dial → downstream levers:**
+
+| Dial | Low (1–3) | High (8–10) |
+|---|---|---|
+| Variance | symmetric grids, one layout family | asymmetry, varied layout families, off-grid accents |
+| Motion | static / reduced-motion-first, opacity-only | choreographed scroll/stagger (GPU-only, reduced-motion alt) |
+| Density | generous whitespace, large spacing scale | tight spacing scale, more info per viewport |
+
+Dials persist in `DESIGN.md`; stack executors (`tailwind-engineer`,
+`react-shadcn-ui`, `blade-ui`, `flux`) read `DESIGN.md` and honour them.
+
 **Anti-Default Discipline — first-impulse check:** Before committing to any design direction, verify you are NOT defaulting to:
 - Purple/violet + cyan-on-dark gradient palette (AI color cliché)
 - Centered hero over a dark gradient mesh with a single CTA
@@ -111,6 +140,12 @@ If any of these was the first impulse, name a different direction or explicitly
 When the brief maps to an official design system (Material Design, Fluent,
 Carbon, Polaris, GOV.UK, shadcn, Tailwind UI, Radix, etc.):
 
+0. **Canon grounding first.** Brief names a system OR `components.json`/deps
+   signal one (`@mui/material`, `antd`, `@fluentui/*`, `@carbon/*`,
+   `@atlaskit/*`) → pull
+   [`docs/guidelines/design-canon.md`](../../../docs/guidelines/design-canon.md),
+   surface the matching one-liner, **offer to fetch the live spec** before
+   committing to the system's conventions. Thin + lazy: skip for a generic brief.
 1. **Install the real package** — do not hand-recreate its CSS or components.
    Surface the install command for the project's package manager (the
    system's official package, e.g. the shadcn CLI or the `@mui/material`
@@ -123,13 +158,18 @@ Carbon, Polaris, GOV.UK, shadcn, Tailwind UI, Radix, etc.):
    (see Design Read above); never fall back to an unnamed generic aesthetic
    (per `source-discovery-gate`: real source before guessing).
 
+**Grounding precedence** (per `brand-source-of-truth`): consumer brand tokens >
+confirmed session decisions > named canon
+([`design-canon.md`](../../../docs/guidelines/design-canon.md)) > generated
+corpus. Canon is a gap-filler, never an override of a registered brand value.
+
 ## Procedure: Produce a grounded design brief (`ui-design-brief` rebound)
 
 1. **Ground** (one call — engine runs the manifest's plan
    product → style → color → landing → typography with decision rules):
 
    ```bash
-   python3 <skills-root>/corpus-grounding/scripts/ground.py ground \
+   ./scripts-run <skills-root>/corpus-grounding/scripts/ground ground \
      --manifest <skills-root>/design-intelligence/data/manifest.json \
      "<product type + mood + platform>" --json
    ```
@@ -195,7 +235,7 @@ finding classes instead of ad-hoc judgment:
 Per-framework Do/Don't corpora (16 stacks) ride the same manifest:
 
 ```bash
-python3 <skills-root>/corpus-grounding/scripts/ground.py search \
+./scripts-run <skills-root>/corpus-grounding/scripts/ground search \
   --manifest <skills-root>/design-intelligence/data/manifest.json \
   --stack react "list rerender memo" [--filter "Severity=HIGH"]
 ```
@@ -236,6 +276,9 @@ guidance + docs URLs from here instead of memory.
 | Orchestration gates + locks | `directives/ui/{design,review,polish}.py` — never import the engine |
 | WCAG audit method | [`accessibility-auditor`](../accessibility-auditor/SKILL.md) |
 | Token authoring | [`design-tokens`](../design-tokens/SKILL.md) |
+| Lo-fi structure exploration (pre-selection) | [`wireframe`](../wireframe/SKILL.md) — disposable greyscale variants |
+| Multiple hi-fi options (post-selection) | [`design-variations`](../design-variations/SKILL.md) — grounds each variation via this skill |
+| Fixed-canvas slide decks | [`html-deck`](../html-deck/SKILL.md) — own medium, still corpus-grounded |
 
 ## Gotchas
 

package/dist/agent-src/skills/design-intelligence/references/design-languages.md

@@ -36,7 +36,7 @@
 ## How to use
 
 1. Select the style through the grounding engine first:
-   `python3 <skills-root>/corpus-grounding/scripts/ground.py search
+   `./scripts-run <skills-root>/corpus-grounding/scripts/ground search
    --manifest <skills-root>/design-intelligence/data/manifest.json
    --domain style "<product + mood>"`.
 2. Open the matching spec file and lift its token system (colors,

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

@@ -287,17 +287,29 @@ This is especially useful when the user provides a screenshot or Figma export as
 
 ## Anti-slop scan
 
-During any design review, load
-[`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
-as a reference. After the structured review phases, add an explicit
-**Anti-Slop Check** section to the review output:
-
-1. List any patterns from the catalog that appear in the reviewed UI (cite by
-   entry ID, e.g. V1, T2, C1).
-2. For each finding: note whether an override condition is in effect (if yes,
-   verify it is stated in the design brief; if not, flag as a finding).
-3. Run the AI-slop originality self-test on the overall aesthetic direction.
-   Report the result (pass / flag / fail) with one sentence of evidence.
+Hybrid: a deterministic detector does the mechanical pattern-matching (zero
+token cost, no catalog reload); you do the judgment it cannot. After the
+structured phases, add an **Anti-Slop Check** section:
+
+1. **Run the detector first** — catches pattern-detectable tells so you don't
+   eyeball or re-derive:
+   ```
+   npx tsx src/scripts/lint_design_slop.ts --dir <consumer-ui-path> --json
+   ```
+   Each finding: `rule` (`slop-v1-side-stripe`), `catalogId` (`V1`), `severity`
+   (`P0`–`P3`), `file:line`, `message`. **Cite verbatim** — don't re-describe
+   from the catalog. Findings are *rebuttable presumptions*: a `DESIGN.md`-gated
+   finding is already filtered; a remaining one means intent not declared.
+   `lint_design_slop` is **flags, never a block** (default exit 0; CI opts in via
+   `--fail-on`).
+2. **Judge what the detector cannot** — load
+   [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+   for tells needing structural/aesthetic judgment (T3 icon-tile stack, L2
+   three-identical-card grid, V2 glassmorphism intent). List any, cite by entry
+   ID, check the override.
+3. Run the AI-slop originality self-test on the overall direction. Report
+   pass / flag / fail + one sentence of evidence — the judgment the detector
+   does not make.
 
 For the **objective quality floors** (WCAG contrast, font-size, line-length,
 reduced-motion, heading hierarchy, focus indicator), do NOT eyeball them —

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

@@ -98,6 +98,20 @@ Example: "Information-dense dashboard; optimize for power users, not casual expl
 - Destructive: [token name]
 - Surface hierarchy: [primary bg → secondary bg → elevated bg]
 
+## Taste Dials
+Three 1–10 dials that tune generation. Absent = unset (design-intelligence
+infers from the brief via its Dial Inference Table). One-line rationale each.
+- Variance: [1–10] — [why; 1 = perfectly symmetric, 10 = expressive/asymmetric]
+- Motion: [1–10] — [why; 1 = static, 10 = cinematic]
+- Density: [1–10] — [why; 1 = airy, 10 = packed/data-dense]
+
+## Consistency Locks
+Within-project invariants (derived from the confirmed system). A value outside
+a declared Lock is off-system; the anti-slop detector flags it (rebuttable).
+- Theme Lock: [single | light+dark via prefers-color-scheme] — no mid-surface inversion
+- Colour Lock: [one accent family] — [the accent hue]
+- Shape Lock: [one corner-radius scale] — [the radius set, e.g. 6/12/16px]
+
 ## Stack and conventions
 - CSS approach: [Tailwind / CSS modules / styled-components / etc.]
 - Component primitives: [shadcn / Radix / Headless UI / custom]
@@ -178,6 +192,33 @@ Example: "Dashboard = control panel for power users, not an exploration space."
 4. Update the "Last updated" date.
 5. Output a diff summary: what changed and why.
 
+## Importing an extracted design system
+
+A consumer reverse-engineers an existing site/repo with any external static tool
+and hands the result here as a `design-system.json`. We own the **import
+contract**, not the crawler — the package never ships the Playwright runtime, a
+font-bundler, or a `.skill` auto-installer (out of scope). Full schema lazy from
+[`reference/design-system-json.md`](reference/design-system-json.md); read only
+on import.
+
+Import procedure:
+
+1. Read `design-system.json`; reject if `source` (kind + ref + captured_at) is
+   missing — no provenance, no import.
+2. Diff every field vs the current `DESIGN.md`.
+3. **Per-field confirm/merge proposal** — observed, not authoritative (mirrors
+   `source-discovery`); never write silently.
+4. Conflict with a registered brand value (confirmed `.tokens.json` / brand
+   token) → **flag, never auto-apply** (`brand-source-of-truth`). Precedence:
+   brand tokens > confirmed `DESIGN.md` > imported observation.
+5. On accept, persist chosen fields; hand mapped DTCG fields to
+   [`brand-to-tokens`](../brand-to-tokens/SKILL.md) / `design-tokens` for
+   `.tokens.json` — no parallel token format.
+
+Two sources, one shape: external target → external tool emits the artifact;
+current repo → prefer [`existing-ui-audit`](../existing-ui-audit/SKILL.md), which
+emits the same shape.
+
 ## How the design skills consume these documents
 
 When `DESIGN.md` or `PRODUCT.md` is present in the project root: