@event4u/agent-config 9.12.0 → 9.14.0

package/dist/agent-src/rules/senior-engineering-discipline.md

@@ -4,8 +4,6 @@ tier: "2b"
 alwaysApply: false
 description: "Writing/generating code — generalize (no overfit/tautological tests), supply the invisible cross-cutting controls, never invent an API/field/package"
 triggers:
-  - intent: "writing or generating code"
-  - intent: "implementing a feature"
   - keyword: "implement"
   - keyword: "endpoint"
   - keyword: "query"

package/dist/agent-src/rules/session-canary.md

@@ -4,8 +4,6 @@ tier: "2a"
 description: "personal.canary_name set — open every new task by name (liveness canary); keep the reply-close markers alive (ONE end-summary, PR URL last)"
 alwaysApply: false
 triggers:
-  - intent: "starting a new task or a new conversation"
-  - intent: "opening the first reply to a request"
   - keyword: "canary"
   - keyword: "canary_name"
   - phrase: "session canary"

package/dist/agent-src/rules/size-enforcement.md

@@ -3,11 +3,6 @@ type: "manual"
 tier: "mechanical-already"
 description: "Creating or editing rules, skills, commands, guidelines, AGENTS.md, or copilot-instructions.md — enforce size and scope limits"
 alwaysApply: false
-triggers:
-  - intent: "create rule"
-  - intent: "create skill"
-  - intent: "create command"
-  - intent: "create guideline"
 workspaces: [agent-config-maintainer]
 packs: [meta]
 ---

package/dist/agent-src/rules/source-confidentiality.md

@@ -10,9 +10,6 @@ triggers:
   - path_prefix: "docs/"
   - path_prefix: "agents/evidence/"
   - path_prefix: "agents/roadmaps/"
-  - intent: "adopt or harvest from an external repo"
-  - intent: "compare against another package"
-  - intent: "attribute an idea to an external source"
 validator_ignore:
   - type: "substring"
     pattern: "external_sources_denylist"

package/dist/agent-src/rules/source-discovery-gate.md

@@ -7,8 +7,6 @@ load_context:
   - ../contexts/execution/evidence-discipline.md
   - ../contexts/execution/project-intelligence.md
 triggers:
-  - intent: "before coding"
-  - intent: "DB-driven work"
   - keyword: "schema"
   - keyword: "endpoint"
   - phrase: "new API"

package/dist/agent-src/rules/think-before-action.md

@@ -6,9 +6,9 @@ alwaysApply: false
 load_context:
   - ../contexts/communication/rules-auto/think-before-action-mechanics.md
 triggers:
-  - intent: "before coding"
-  - intent: "before debugging"
-  - intent: "before modifying"
+  - phrase: "before coding"
+  - phrase: "before debugging"
+  - phrase: "before modifying"
   - keyword: "implement"
   - keyword: "debug"
   - keyword: "refactor"

package/dist/agent-src/rules/token-budget-discipline.md

@@ -5,7 +5,6 @@ description: "rich-class skills are exempt from telegraph + thin-projector trims
 triggers:
   - keyword: "token_budget_class"
   - keyword: "rich skill"
-  - intent: "editing a rich-tagged skill"
 workspaces: [agent-config-maintainer]
 packs: [meta]
 ---

package/dist/agent-src/rules/token-efficiency.md

@@ -6,9 +6,8 @@ alwaysApply: false
 load_context:
   - ../contexts/communication/rules-auto/token-efficiency-mechanics.md
 triggers:
-  - intent: "verbose CLI output"
-  - intent: "fetching logs"
   - keyword: "minimize tool calls"
+  - phrase: "fetching logs"
 workspaces: [agent-config-maintainer, construction, engineering, finance, founder, gtm, legal-review-prep, ops, product, small-business]
 packs: [meta]
 ---

package/dist/agent-src/rules/tool-safety.md

@@ -5,7 +5,6 @@ description: "Skill uses external tools — enforce allowlist, deny-by-default,
 triggers:
   - keyword: "allowed_tools"
   - keyword: "tool registry"
-  - intent: "external API"
 workspaces: [agent-config-maintainer, engineering]
 packs: [meta]
 enforced_by:

package/dist/agent-src/rules/user-interaction.md

@@ -6,9 +6,6 @@ alwaysApply: false
 load_context:
   - ../contexts/communication/rules-auto/user-interaction-mechanics.md
 triggers:
-  - intent: "ask user a question"
-  - intent: "numbered options"
-  - intent: "summarizing progress"
   - keyword: "option"
   - keyword: "recommendation"
   - phrase: "what do you recommend"

package/dist/agent-src/rules/user-interrupt-priority.md

@@ -4,7 +4,6 @@ tier: "2a"
 description: "New user instruction mid-flight — STOP the current task, run the new one in full, ASK before resuming"
 alwaysApply: false
 triggers:
-  - intent: "new instruction while a task is running"
   - keyword: "weiter"
   - keyword: "resume"
   - keyword: "continue"

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

@@ -237,6 +237,14 @@ numbered options; do NOT auto-rewrite prose without the user's knowledge:
 - Do NOT duplicate content that's already in `AGENTS.md` or `.github/copilot-instructions.md`.
 - Do NOT write docs just to document what you did — only document things others need to know.
 - If unsure whether a doc needs updating, **ask the user**.
+- **Sibling-routing sentences are edited as a set, never alone.** When a skill's
+  `description:` carries a routing clause naming an overlapping sibling
+  (`Animated → pixar-storyteller`), editing it obliges re-reading every sibling
+  it names and every sibling that names it, so no user phrase ends up routed to
+  two skills and none ends up routed to neither. One-sided edits are how a
+  cluster's descriptions drift back into ambiguity between sweeps;
+  `lint_skill_descriptions` catches a *missing* clause, not an *inconsistent*
+  one.
 
 ## Output format
 

package/dist/agent-src/skills/analysis-skill-router/SKILL.md

@@ -11,6 +11,11 @@ packs:
 
 # analysis-skill-router
 
+A chooser, not a worker. It answers exactly one question — *which skill* — and
+then gets out of the way. How to actually carry out the work belongs to
+whichever skill this picks; a chooser that also explains the work reads like
+its own fallback target, which is the defect this file was cut back from.
+
 ## When to use
 
 Use this skill when:
@@ -29,111 +34,75 @@ Do NOT use when:
 
 ## Procedure
 
-### 1. Identify request scope
-
-Classify the request as one of:
-
-* full project analysis
-* architecture review
-* broad multi-layer debugging
-* framework-specific deep analysis
-* narrow root-cause analysis
-* performance/security specialist analysis
-* simple local code issue
-
-### 2. Check whether deep analysis is justified
-
-Use deep analysis only if at least one is true:
-
-* the user explicitly asks for broad analysis
-* the system is unclear or unknown
-* the issue spans multiple layers
-* architecture reconstruction is required
-* the cause is not local and not obvious
-
-If none apply → do NOT route to a broad analysis skill.
-
-### 3. Detect framework or system type
-
-Check whether the request clearly targets:
-
-* Laravel, Symfony, Zend/Laminas, Node/Express, React, Next.js
-* unknown / mixed stack
-
-### 4. Route to the correct skill
+### 1. Classify the scope
 
-#### Broad / unknown system
+Pick one: full project · architecture review · broad multi-layer debugging ·
+framework-specific deep dive · narrow root cause · performance/security
+specialist · simple local issue.
 
-* full project analysis or unclear stack → `universal-project-analysis`
-* unknown system, discovery-focused → `project-analysis-core`
+**Broad scope requires a reason.** At least one must hold, or the answer is a
+narrow specialist: the user asked for breadth · the system is unknown · the
+issue spans layers · architecture must be reconstructed · the cause is
+non-local.
 
-#### Root-cause analysis
+### 2. Detect the framework
 
-* concrete multi-cause problem → `project-analysis-hypothesis-driven`
-* bug-focused but not full-project → `bug-analyzer`
+Laravel · Symfony · Zend/Laminas · Node/Express · React · Next.js · unknown or
+mixed.
 
-#### Backend framework analysis
+### 3. Read the decision table
 
-* Laravel → `project-analysis-laravel`
-* Symfony → `project-analysis-symfony`
-* Zend/Laminas → `project-analysis-zend-laminas`
-* Node/Express → `project-analysis-node-express`
+| Signal | Route to |
+|---|---|
+| Full audit, or unclear stack | `universal-project-analysis` |
+| Unknown system, discovery-focused | `project-analysis-core` |
+| Concrete problem, several plausible causes | `project-analysis-hypothesis-driven` |
+| Bug-focused, not full-project | `bug-analyzer` |
+| Laravel | `project-analysis-laravel` |
+| Symfony | `project-analysis-symfony` |
+| Zend/Laminas | `project-analysis-zend-laminas` |
+| Node/Express | `project-analysis-node-express` |
+| React state / render / hooks | `project-analysis-react` |
+| Next.js SSR / cache / hydration | `project-analysis-nextjs` |
+| Bottleneck | `performance-analysis` |
+| Security concern | `security-audit` |
 
-#### Frontend / rendering analysis
-
-* React state/render/hooks issues → `project-analysis-react`
-* Next.js SSR/client/cache/hydration issues → `project-analysis-nextjs`
-
-#### Specialist follow-up routing
-
-* performance bottleneck → `performance-analysis`
-* security concern → `security-audit`
-
-### 5. Validate routing quality
-
-Check:
-
-* the chosen skill is narrower than the broadest possible option
-* full-project analysis is actually justified if selected
-* framework-specific skill matches the explicit framework
-* no simpler specialist skill was skipped
+Tie-break: **the narrowest row that still covers the request wins.**
 
 ## Output format
 
-1. Selected skill
-2. Reason for selection
-3. Why broader alternatives were not chosen
-4. Optional chained specialist skills
-
-## Routing heuristics
-
-**Choose `universal-project-analysis` only if:** user explicitly wants full audit, architecture must be reconstructed, stack is unclear, multiple subsystems involved.
-
-**Choose `project-analysis-core` if:** broad discovery needed, framework deep-dive not yet justified.
-
-**Choose `project-analysis-hypothesis-driven` if:** problem is concrete, multiple causes plausible, main job is explanation not discovery.
-
-**Choose framework-specific analysis if:** framework is explicit, failure pattern is framework-shaped.
+1. The selected skill.
+2. The signal from step 1–2 that selected it.
+3. Why the next-broader row lost, when one was plausible.
+4. Any skill to chain afterwards — or "none".
 
-**Do NOT route broadly if:** one component or file is enough, fix is obvious and local, task is implementation not investigation.
+One or two lines total. A routing verdict longer than the request it routes is
+itself a routing failure.
 
 ## Examples
 
-**"Analyze this whole Laravel project"** → `universal-project-analysis` → chain `project-analysis-laravel`
-**"Hydration mismatch in Next.js"** → `project-analysis-nextjs` (no full-project needed)
-**"Bug could be cache, queue, or version mismatch"** → `project-analysis-hypothesis-driven`
-**"Change one React component"** → no analysis skill, use implementation skill
+| Request | Route |
+|---|---|
+| "Analyze this whole Laravel project" | `universal-project-analysis`, chain `project-analysis-laravel` |
+| "Hydration mismatch in Next.js" | `project-analysis-nextjs` — no full-project step |
+| "Could be cache, queue, or a version mismatch" | `project-analysis-hypothesis-driven` |
+| "Change one React component" | none — implementation skill |
 
 ## Gotcha
 
-* The most expensive skill is often not the best skill.
-* Broad analysis feels safe but reduces sharpness when the problem is already localized.
-* Framework-specific routing should happen as early as possible once the framework is explicit.
+* **Size adjectives read as scope.** "Our *whole* Laravel app is slow" picks the
+  broad row on the word "whole", and the audit then spends its passes
+  rediscovering a stack the request already named. The step-2 framework signal
+  outranks size words — those are how frustration sounds, not scope.
+* **Breadth feels safe and costs sharpness.** The most expensive choice is
+  rarely the best one once the problem is already localised.
+* **Steps 1 and 2 disagreeing is a question, not a tie-break.** Ask which the
+  user meant instead of picking the broader row to be safe.
 
 ## Do NOT
 
 * Do NOT default to `universal-project-analysis`
-* Do NOT use full-project analysis for normal feature work
-* Do NOT choose a generic skill when a framework-specific one clearly fits
-* Do NOT route to deep analysis when a simple specialist skill is enough
+* Do NOT choose a generic skill when a framework-specific row fits
 * Do NOT confuse discovery with root-cause investigation
+* Do NOT re-import procedure, validation checklists, or output contracts from
+  the skills in the table — that is what this file was cut back from

package/dist/agent-src/skills/character-consistency/SKILL.md

@@ -181,12 +181,15 @@ Worked example — `creature`:
 
 ## Policies
 
+Paths, enforcement model, and the full set: the
+[media policy preamble](../../../agents/settings/policies/media/README.md).
+
 When a character lock would identify or render a real person, consult before emitting the JSON:
 
-- [`agents/settings/policies/media/likeness.md`](../../../agents/settings/policies/media/likeness.md) — real-person identity tokens require a cited likeness release.
-- [`agents/settings/policies/media/public-figures.md`](../../../agents/settings/policies/media/public-figures.md) — recognised public figures carry the harder gate (publicity rights + transformative-intent).
-- [`agents/settings/policies/media/voice-cloning.md`](../../../agents/settings/policies/media/voice-cloning.md) — when `voice_note` references a real person's voice.
-- [`agents/settings/policies/media/disclosure.md`](../../../agents/settings/policies/media/disclosure.md) — outputs carrying a real-person lock require the non-removable AI-generation disclosure downstream.
+- **`likeness`** — real-person identity tokens require a cited likeness release.
+- **`public-figures`** — recognised public figures carry the harder gate (publicity rights + transformative-intent).
+- **`voice-cloning`** — when `voice_note` references a real person's voice.
+- **`disclosure`** — outputs carrying a real-person lock require the non-removable AI-generation disclosure downstream.
 
 Refuse-and-surface the file path; do not silently sanitise the prompt.
 

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

@@ -58,6 +58,14 @@ Do NOT use when:
   get a one-page record; one-way doors get the full options +
   consequences + supersession chain. The reversibility row of the
   matrix decides which template fires. See `mental-models.md` § 10.
+  **Corollary — a shortcut through a one-way door is a decision, not a
+  defer.** The cheap-and-simple option is *preferred* where the choice can
+  be walked back later. Where it cannot — a public API shape, a DB schema,
+  a migration, a wire format, a published identifier — "we can simplify
+  this later" is false, so it never ships as a deferred note; it lands
+  here as a recorded decision with its consequences named. The one-way
+  categories are enumerated so the call is not left to a judgement about
+  what feels important.
 - **Team context-spine slot.** Read the **team** slot of the
   [context-spine](../../../docs/contracts/context-spine.md) to
   capture who is bound by the decision (review groups, on-call

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

@@ -352,6 +352,17 @@ structured review phases, add an explicit **Anti-Slop Check** section:
 3. Run the AI-slop originality self-test on the overall aesthetic direction.
    Report the result (pass / flag / fail) with one sentence of evidence — this
    is the human judgment the detector deliberately does not make.
+4. **Mark the findings a provided artifact already answers.** When the run is a
+   port (`state.ui_design.provided_artifact` is set), a finding about a
+   decision the artifact makes is correct about the pattern and wrong about the
+   action. Keep it in the output, cite it as **"matches provided spec"**, and
+   set `artifact_covered: true` on it — the polish gate drops those from the
+   round-driving set, so an unmarked finding will send a round at the user's
+   own design. The flag is scoped to decisions the artifact actually covers;
+   anything it leaves open (a state it never showed) is generative work and
+   keeps the full scan. Precedence + scope:
+   [`design-fidelity-mechanics`](../../../docs/guidelines/design-fidelity-mechanics.md)
+   § Provided-artifact precedence. Regression witness: `daf-slop-vs-provided`.
 
 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/reference/design-system-json.md

@@ -42,6 +42,14 @@
 - **`bundled_local`** on a font family is a flag, not an instruction: the
   package never downloads or bundles fonts (out of scope) — it records that the
   source did.
+- **`motion` has a consumer.** It sits outside the DTCG mapping above, and for
+  a long time that meant nothing read it at all: the block was written by
+  capture and consumed by nobody, so easing and duration were re-derived from
+  taste on every port. On the **Port a provided artifact** branch
+  ([`design-artifact-lifecycle`](../../../../../docs/contracts/design-artifact-lifecycle.md))
+  the audit reads `motion.durations` and `motion.easings` as the answer. The
+  extraction-only marking above still holds: `motion._meta.detected_libs`
+  informs the human and never becomes a token.
 
 ## Trust posture (mandatory)
 

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

@@ -104,9 +104,25 @@ Write into `state.ui_audit.design_tokens` (object, never null — empty object i
 | `:root { --... }` blocks in `resources/css/`, `app/globals.css`, `src/app/globals.css` | every `--token-name: value` pair |
 | `theme.json` / `tokens.json` (any depth) | flat or nested token tree |
 | `app/css/variables.css`, `assets/scss/_tokens.scss` | SCSS `$var: value` and CSS custom properties |
+| **A supplied `design-system.json`** (handed over with a provided artifact) | `colors`, `typography`, `spacing`, `radius`, `shadow`, **and `motion`** (`durations`, `easings`) — read as the answer, never re-derived |
+| **A supplied artifact's own `:root { --… }` / inline `<style>`** (the handover file itself, e.g. `design.html`) | every `--token-name: value` pair, when no `design-system.json` accompanies it |
 
 Group output by category: `colors`, `spacing`, `radius`, `font`, `shadow`, `breakpoint`, `other`.
 
+**Artifact-sourced tokens stay distinguishable from project tokens.** Every
+group carries a `source` — `project` for the first four rows, `artifact` for the
+last two — because the mapping between them is the thing a port has to keep
+visible. Collapsing them loses the answer to "did this value come from what the
+user handed me, or from what the repo already had?", and that is exactly the
+question the apply coverage report has to answer per item. The two sets may
+disagree; when they do, surface the conflict rather than merging it (a supplied
+spec outranks house taste, but not a registered brand token — see
+[`brand-source-of-truth`](../../rules/brand-source-of-truth.md)).
+
+`motion` is new here: the block has existed in the `design-system.json` schema
+since capture shipped and **nothing consumed it**. On the port branch it is
+read, so easing and duration stop being values the brief silently regenerates.
+
 ### 4. Detect shadcn inventory (only when `state.stack.frontend == "react-shadcn"`)
 
 Read `components.json` for the registered style + base color, then read `package.json` for `@radix-ui/*` and any locally vendored `components/ui/*.tsx` files. Write into `state.ui_audit.shadcn_inventory`:
@@ -265,9 +281,24 @@ scheme, border-radius convention, motion patterns), cross-check the findings
 against
 [`docs/guidelines/design-antipatterns.md`](../../../docs/guidelines/design-antipatterns.md).
 If the existing UI already uses a listed anti-pattern, surface it as a design-debt
-finding (separate from the reuse inventory) — flag by entry ID and severity. The
-next design step can then decide whether to continue the existing pattern (for
-consistency) or introduce a corrective direction change.
+finding (separate from the reuse inventory) — flag by entry ID and severity.
+
+**What the design step may then do depends on whose aesthetic it is.** These
+are two different situations and the sentence that used to cover both was
+wrong about one of them:
+
+| The anti-pattern lives in… | The design step may… |
+|---|---|
+| **The consumer's own legacy UI** (inventoried from the repo) | continue it for consistency, **or** propose a corrective direction change. Both are legitimate; it is their codebase and their debt. |
+| **A supplied spec** (a handed-over artifact, a `design-system.json`, a registered brand token) | **neither.** Build it as given. The finding is recorded as informational, marked `artifact_covered`, and no polish round acts on it. |
+
+A corrective direction change against a supplied spec is not a design
+improvement, it is overriding a decision the user already made — the failure
+[`design-fidelity`](../../rules/design-fidelity.md) exists to prevent, arriving
+through the audit's side door. Precedence and its exact scope:
+[`design-fidelity-mechanics`](../../../docs/guidelines/design-fidelity-mechanics.md)
+§ Provided-artifact precedence. Where the two sources disagree, surface the
+conflict rather than picking (fixture `daf-slop-vs-provided`).
 
 ## Do NOT
 

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

@@ -340,6 +340,16 @@ If a tell was the first impulse, choose a different approach or explicitly
 justify why this brief calls for it. (The full pre-proposal scan is under
 *Anti-slop discipline* below.)
 
+**Carve-out — a supplied artifact is the spec, not a first impulse.** This
+discipline governs what *you* reach for. When the user hands over a finished
+artifact, the choices it makes are not your impulses and the justify-or-change
+burden does not apply to them: build them as given. The carve-out is scoped to
+decisions the artifact actually covers — anything it leaves open (a state it
+never shows, a surface it never had) is your first impulse again and gets the
+full scan. See
+[`design-fidelity-mechanics`](../../../docs/guidelines/design-fidelity-mechanics.md)
+§ Provided-artifact precedence.
+
 ## Aesthetic direction
 
 Audit-pinned tokens and components always take precedence (see `existing-ui-audit`). When the audit pins an aesthetic, honor it without deviation. When the audit shows **no pinned aesthetic** — greenfield surface, marketing landing page, brand-new feature without design-system precedent — the design brief is allowed (and expected) to commit to a deliberate direction instead of defaulting to safe centered hero + 3-column features + CTA.

package/dist/agent-src/skills/motion-choreographer/SKILL.md

@@ -186,12 +186,15 @@ stdin shape. The orchestrator pipes this into the video adapter's
 
 ## Policies
 
+Paths, enforcement model, and the full set: the
+[media policy preamble](../../../agents/settings/policies/media/README.md).
+
 Motion prompts inherit every constraint the upstream blueprint carries. Before emitting provider-tuned prose:
 
-- [`agents/settings/policies/media/disclosure.md`](../../../agents/settings/policies/media/disclosure.md) — every distributed clip carries the non-removable AI-generation disclosure; refuse adapter flags that would suppress it.
-- [`agents/settings/policies/media/transparency.md`](../../../agents/settings/policies/media/transparency.md) — provider provenance (C2PA / SynthID) is preserved; refuse re-encode flags whose effect is to strip provenance.
-- [`agents/settings/policies/media/voice-cloning.md`](../../../agents/settings/policies/media/voice-cloning.md) — when the motion prompt requests `audio: native` narration in a named voice.
-- [`agents/settings/policies/media/brand-impersonation.md`](../../../agents/settings/policies/media/brand-impersonation.md) — when the motion prompt copies a recognised brand's chyron / mascot / signature transition.
+- **`disclosure`** — every distributed clip carries the non-removable AI-generation disclosure; refuse adapter flags that would suppress it.
+- **`transparency`** — provider provenance (C2PA / SynthID) is preserved; refuse re-encode flags whose effect is to strip provenance.
+- **`voice-cloning`** — when the motion prompt requests `audio: native` narration in a named voice.
+- **`brand-impersonation`** — when the motion prompt copies a recognised brand's chyron / mascot / signature transition.
 
 Refuse-and-surface; the motion prompt cannot launder a policy gap upstream skills should have caught.