@event4u/agent-config 7.1.0 → 7.2.0

package/dist/agent-src/skills/react-shadcn-ui/SKILL.md

@@ -34,9 +34,15 @@ wraps `npx shadcn@latest add <components>` — **the only subprocess+network
 surface in the adopted suite**. Per `runtime-safety` + the `execution`
 block above:
 
-1. **Propose, never silent-run** — show exact `npx` command + component list first (`--dry-run`); user confirms before live run.
-2. **Missing tool** → per `missing-tool-handling`: `npx`/Node absent → STOP and ask (install vs manual copy) — never silently work around.
-3. **Verify after run** — `components/ui/<name>.tsx` exists, `components.json` unchanged or sanely updated, before reporting success.
+1. **Propose, never silent-run** — always show the exact `npx` command +
+   component list first (use `--dry-run`); the user confirms before any
+   live run.
+2. **Missing tool** → per `missing-tool-handling`: if `npx`/Node is
+   absent, STOP and ask (install vs. manual component copy) — never
+   silently work around.
+3. **Verify after run** — confirm the component landed
+   (`components/ui/<name>.tsx` exists, `components.json` unchanged or
+   sanely updated) before reporting success.
 
 ## Compatibility
 
@@ -82,13 +88,19 @@ Do NOT use when:
   the generated primitives but is easy to remove during a refactor.
 - **Anti-AI-slop: shadcn-default look.** The out-of-the-box shadcn
   theme + `Inter`-as-system-fallback + neutral grays reads as
-  template across projects. Unless `state.ui_audit.design_tokens`
-  pins the neutral palette as the project's identity, the polish
-  step should match typography and color tokens to the design
-  brief's `aesthetic:` line (from `fe-design` aesthetic-direction).
-  Theme/font drift within a single audited project breaks
-  consistency — variation lives between projects, not between
+  template across projects (catalog T7/T8 + C5). Unless
+  `state.ui_audit.design_tokens` pins the neutral palette as the
+  project's identity, the polish step should match typography and color
+  tokens to the design brief's `aesthetic:` line (from `fe-design`
+  aesthetic-direction). Theme/font drift within a single audited project
+  breaks consistency — variation lives between projects, not between
   components in the same surface.
+- **Anti-AI-slop catalog + linter.** Pull
+  [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+  before the polish step (Visual V1–V7, Layout L1–L8 are the React-component
+  slop tells); the objective quality floors (WCAG contrast, focus-visible,
+  reduced-motion) are CI-enforced by
+  [`lint_design_quality`](../../../src/scripts/lint_design_quality.ts).
 
 ## Covered primitives
 

package/dist/agent-src/skills/skill-writing/SKILL.md

@@ -121,6 +121,24 @@ Then run the Understand → Research → Draft sequence from the
 rule. Skip only on explicit *"just do it"* bypass or trivial edits
 (typo, link, single-line clarification).
 
+### 0b. Skill-growth gate (new skill only)
+
+The skill count keeps climbing; nothing forces *"should this be a new skill at
+all?"*. Before creating a **new** skill, answer these in the PR body — a new
+skill that cannot answer them is a merge / guideline / no-op in disguise:
+
+1. **Family** — which capability family does it join? (engineering, product, …)
+2. **Capability** — what does it do that no existing skill does? Name the gap.
+3. **Why not extend / merge** — which nearest skill did you consider folding into, and why is a separate skill better?
+4. **Why not a guideline** — is this executable workflow (skill) or reference material (guideline)? Guideline-shaped content does not become a skill.
+5. **Visibility tier** — `core` or `lab`? Which pack?
+
+**Surface overlap before deciding** — run `./scripts-run src/scripts/skill_overlap`
+(or `audit_skill_overlap`) and read the nearest matches; a high-overlap hit is a
+merge signal, not a green light. This gate is the authoring-time companion to the
+[capability-boundary matrix](../../../docs/contracts/capability-boundary.md): the
+matrix governs packs, this governs the skills inside them.
+
 ### 1. Define the trigger
 
 Write "When to use" first. This is the in-body trigger — it documents the

package/dist/agent-src/skills/subagent-orchestration/SKILL.md

@@ -58,17 +58,13 @@ than blocking on each return — intervene only if one goes off track. Engage pe
 
 ### Settings-gated auto-dispatch
 
-"By default" is governed by `.agent-settings.yml`, not unconditional. Before
-auto-dispatch, run the activation gate
+"By default" is governed by the [`delegation-policy`](../../rules/delegation-policy.md)
+rule — the single source of the auto-trigger. It gates on the activation context
 ([`auto-orchestration-activation`](../../contexts/execution/auto-orchestration-activation.md)):
-dispatch only when `subagents.enabled` **and** `subagents.auto != off` **and**
-the [`host-capability-manifest`](../../contexts/execution/host-capability-manifest.md)
-reports `subagent_spawn: true` **and** the task is classified delegable
-([`auto-dispatch-classification`](../../contexts/execution/auto-dispatch-classification.md)).
-`auto: ask` → ask once (per [`user-interaction`](../../rules/user-interaction.md));
-`auto: on` → surface chosen mode + per-subtask tiers in one line. Any gate fails
-→ in-session. Auto-dispatch is the default where host + settings allow, a clean
-no-op elsewhere — never lifts a safety floor.
+dispatch only when `subagents.enabled`, `subagents.auto != off`, the host
+manifest reports `subagent_spawn: true`, and the task is classified delegable.
+`auto: ask` → ask once; `auto: on` → surface mode + per-subtask tiers in one
+line; any gate failing → in-session no-op. Never lifts a safety floor.
 
 ## The seven modes
 
@@ -368,3 +364,4 @@ the judge verdict.
 | Standalone judge on an existing diff | [`/judge`](../../commands/judge.md)  |
 | External / networked second opinion  | [`ai-council`](../ai-council/SKILL.md) |
 | Verifying completeness               | [`verify-before-complete`](../verify-before-complete/SKILL.md) |
+| What a subagent owns vs never owns   | [`subagent-boundary`](../../../docs/contracts/subagent-boundary.md) |

package/dist/agent-src/skills/tailwind-engineer/SKILL.md

@@ -51,11 +51,13 @@ radius, spacing, shadow, font-size to a configured token. If the design hands yo
 (`bg-[#3B82F6]`, `mt-[17px]`) are a smell — accept only with a
 one-line comment naming the design source.
 
-Token authoring (DTCG 3-layer, CSS-var/Tailwind generation):
-[`design-tokens`](../design-tokens/SKILL.md); its `tokens.py validate
---dir <path>` is the **single token-discipline linter** behind this rule.
-Greenfield config: bundled `scripts/tailwind_config_gen.py`
-(Apache-2.0-derived, pure templating) scaffolds `tailwind.config.{js,ts}`.
+Token authoring (DTCG 3-layer model, CSS-var/Tailwind generation) lives
+in [`design-tokens`](../design-tokens/SKILL.md); its
+`tokens.py validate --dir <path>` is the **single token-discipline
+linter** — the mechanical check behind this rule (no hardcoded hex / px /
+rem outside the token files). Greenfield Tailwind config: bundled
+`scripts/tailwind_config_gen.py` (Apache-2.0-derived, pure templating)
+scaffolds `tailwind.config.{js,ts}` per framework.
 
 ### 2. Compose, don't inline
 
@@ -127,10 +129,18 @@ Risks:          <arbitrary values, !important, dark-mode gaps>
   break the design system; they accumulate silently.
 - `@apply` inside component CSS interacts with PurgeCSS — keep it
   in files Tailwind scans, not in vendor CSS.
+- **Anti-AI-slop catalog.** The bullets below are the Tailwind-specific
+  manifestations of the stack-agnostic patterns in
+  [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md)
+  (C1 gradients, T7 fonts, L1/L2 layout, V1 side-stripe). Pull the catalog
+  for the full list; the objective subset (contrast, font-size floor,
+  reduced-motion) is CI-enforced by
+  [`lint_design_quality`](../../../src/scripts/lint_design_quality.ts) for
+  consumer projects.
 - **Anti-AI-slop: gradients.** Unless audit-pinned or brief-explicit,
   avoid the default purple-to-blue / cyan-to-pink gradients on white —
-  they read as auto-generated. Reach for a single accent from the
-  token map, or a duotone built from configured tokens.
+  they read as auto-generated (catalog C1/C2). Reach for a single accent
+  from the token map, or a duotone built from configured tokens.
 - **Anti-AI-slop: typography.** Unless audit-pinned, avoid surfacing
   the system stack (`font-sans` fallback to Arial / Helvetica / Inter
   via system defaults) as the *visible* body face. If `tailwind.config`

package/dist/agent-src/skills/typography-system/SKILL.md

@@ -8,6 +8,7 @@ workspaces:
   - engineering
 packs:
   - frontend-design
+token_budget_class: rich
 trust:
   level: professional
 install:
@@ -136,3 +137,16 @@ brand already registers fonts, use them and skip the filter.
   consumes the token system produced here.
 - [`brand`](../brand/SKILL.md) — supplies the archetype → pairing-filter
   Grounding (`typography` domain) consumed by stage 2.
+
+## Why this skill is rich
+
+Typography is one of the highest-leverage design decisions and one of the
+most commonly mis-applied by AI agents (defaulting to Inter + arbitrary sizes).
+The skill carries 73 curated font pairings (heading + body + mono combinations
+with Google Fonts URLs and Tailwind config), 6 worked-through modular-scale
+examples across different use-cases (marketing, dashboard, docs, e-commerce,
+SaaS, editorial), and per-pairing line-height + weight guidance. Condensing
+to "use a 1.25 modular scale" loses the worked examples that teach agents
+the difference between a 14/17.5/21.8/27.2 rounded scale and an invented
+arbitrary scale. Without the worked examples, agents produce: 16, 20, 24, 28
+(arbitrary) instead of a properly grounded typographic system.

package/dist/agent-src/skills/ui-component-architect/SKILL.md

@@ -144,6 +144,15 @@ Anti-cases:       <combinations the component refuses to support>
   every render, the child re-renders too. Stabilize via
   `useCallback` or hoist.
 
+## Cross-task design memory
+
+Before proposing a component, check the project root for `DESIGN.md`
+(written by `design-system-capture`). If present, apply its captured
+visual conventions (radius/shadow/motion/spacing) to the new component
+rather than deriving them from scratch. Flag any new design decision
+(e.g., a first-use of a new elevation tier) for capture:
+*"Suggest adding to DESIGN.md: [decision]."*
+
 ## Do NOT
 
 - Do NOT design a component without running

package/dist/discovery/deprecation-report.md

@@ -1,6 +1,6 @@
 # Discovery — Deprecation Report
 
-- Generated: `2026-06-24T13:42:39Z`
+- Generated: `2026-06-24T20:56:10Z`
 - Deprecated artefacts: **0**
 
 _None. Tree is clean._