@event4u/agent-config 1.19.0 → 1.21.0

package/.agent-src/rules/capture-learnings.md

@@ -2,89 +2,18 @@
 type: "auto"
 tier: "2a"
 description: "After completing a task where a repeated mistake or successful pattern appeared — capture as rule or skill"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "after completing a task"
+  - keyword: "learning"
+  - keyword: "lesson"
+routes_to:
+  - "skill:learning-to-rule-or-skill"
 ---
 
 # Capture Learnings
 
-When a repeated mistake, successful pattern, or new constraint appears,
-evaluate whether to capture as **rule** or **skill**.
+**Iron Law.** After a task, capture repeated mistakes / successful patterns as a rule or skill — never lose the learning.
 
-## Promotion Gate
-
-A learning may be promoted to rule/skill ONLY if ALL gates pass:
-
-| Gate | Question | Must be YES |
-|---|---|---|
-| Repetition | Occurred at least twice OR clearly generalizable? | ✅ |
-| Impact | Improves correctness, reliability, or consistency? | ✅ |
-| Failure pattern | Prevents a real, observed failure? | ✅ |
-| Non-duplication | No existing rule/skill/guideline covers this? | ✅ |
-| Scope fit | Fits rule (constraint), skill (workflow), or guideline (convention)? | ✅ |
-| Minimal | Update existing preferred over creation? | Checked |
-
-**Reject immediately if:**
-- Occurred only once and is not clearly generalizable
-- Similar guidance already exists (update instead)
-- Baseline model knowledge or standard tool usage
-- Vague frustration without concrete failure pattern
-
-## Triggers
-
-- Mistake that happened 2+ times
-- Pattern that improved outcome and should be reused
-- Missing constraint that caused issues
-- **User frustration or complaint** — extract the underlying failure pattern, don't ignore or defend
-- **New skill/rule/guideline created** — evaluate if it should be contributed upstream (→ `upstream-proposal` rule)
-- **Significant improvement to existing skill/rule** — consider upstream contribution
-
-## Do NOT capture
-
-- One-off problems
-- Vague frustrations without concrete consequence
-- Content already covered by existing guidance
-
-## Rule vs Skill
-
-- **Rule** → always-apply constraint ("never X", "always Y")
-- **Skill** → repeatable workflow with steps ("when X, do 1-5")
-- **Update** → existing guidance covers topic → extend, don't duplicate
-
-## How
-
-- Smallest effective change
-- Update existing over creating duplicates
-- Full workflow: `learning-to-rule-or-skill` skill
-
-## Where learnings are written
-
-Captured learnings live in the **consumer project's** `agents/learnings/`
-directory, one file per learning:
-
-```
-agents/learnings/<YYYY-MM-DD>-<kebab-slug>.md
-```
-
-Minimum fields (markdown with a small YAML frontmatter):
-
-```yaml
----
-slug: <same as filename>
-captured: <ISO date>
-occurrences: <integer, ≥2 or note "one-off, clearly generalizable">
-type_hint: rule | skill | guideline | update
-scope_hint: project | package
----
-```
-
-Body: 1-paragraph **pattern** (not anecdote) + 1 concrete example.
-
-A learning file is the input to `learning-to-rule-or-skill`, which
-produces a proposal draft under `agents/proposals/`. The proposal is
-then gated by `scripts/check_proposal.py`; see
-[`self-improvement-pipeline`](../../docs/guidelines/agent-infra/self-improvement-pipeline.md).
-
-The `agents/learnings/` and `agents/proposals/` directories are
-consumer-owned — the package ships templates and schemas, never the
-data.
+Body migrated to `skill:learning-to-rule-or-skill` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/cli-output-handling.md

@@ -1,51 +1,21 @@
 ---
 type: "auto"
 tier: "2a"
-alwaysApply: false
 description: "Running CLI commands that produce verbose output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk when installed; tail/grep is fallback."
 source: package
-load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/cli-output-handling-mechanics.md
+triggers:
+  - keyword: "git"
+  - keyword: "phpstan"
+  - keyword: "rector"
+  - keyword: "phpunit"
+  - keyword: "composer"
+routes_to:
+  - "skill:rtk-output-filtering"
 ---
 
-# Development Efficiency
+# Cli Output Handling
 
-Loaded for code, tests, quality tools, CLI, analysis. Communication / response style → always-loaded `token-efficiency`.
+**Iron Law.** Wrap verbose CLI output with `rtk` when installed; fall back to `tail`/`grep` only when missing.
 
-## Iron Law — rtk first, tail/grep fallback
-
-```
-IF `rtk` IS INSTALLED, WRAP VERBOSE COMMANDS WITH rtk.
-USE tail / grep / cat ONLY AS FALLBACK WHEN rtk HAS NO MATCHING SUBCOMMAND.
-NEVER PIPE A STILL-RUNNING LONG COMMAND THROUGH tail — IT BUFFERS TO EOF.
-```
-
-Detection: `rtk_installed: true` in `.agent-settings.yml`, or `which rtk`
-exits 0. Caching the result for the session is fine.
-
-| Verbose command | Use | Fallback (no rtk) |
-|---|---|---|
-| CI-style suites, full test runs | `rtk err <cmd>` — only errors/warnings | redirect → tail → grep |
-| Unit tests | `rtk test <cmd>` — only failures | redirect → tail → grep |
-| `git status`/`log`/`diff` | `rtk git <subcmd>` | plain |
-| `gh pr list`, `gh run view` | `rtk gh <subcmd>` | plain |
-| Generic noisy command | `rtk summary <cmd>` or `rtk err <cmd>` | redirect → tail |
-
-For the full rtk subcommand catalog and project-local filter setup → see
-the `rtk-output-filtering` skill.
-
-## Lookup material — see mechanics
-
-Codebase-navigation tips, the redirect-summarize-target fallback
-pattern (with the three-step `tail`/`grep` recipe), the general rules
-(exit code first, summary line, targeted `grep`, read-once-act-move-on,
-iterative fixing), and the CLI-over-MCP catalog all live in
-[`contexts/communication/rules-auto/cli-output-handling-mechanics.md`](../contexts/communication/rules-auto/cli-output-handling-mechanics.md).
-Pull it whenever a verbose command is about to run without an `rtk`
-match.
-
-## Exceptions
-
-- **Small output** (< 30 lines): Read directly, no redirect needed.
-- **Debugging**: OK to read more context around the specific error.
-- **User asks** for full output: Show it.
+Body migrated to `skill:rtk-output-filtering` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/command-suggestion-policy.md

@@ -2,28 +2,22 @@
 type: "auto"
 tier: "mechanical-already"
 description: "User prompt without /command but matching an eligible slash command — surface matches as numbered options with as-is escape hatch; never auto-executes, user always picks"
-alwaysApply: false
 source: package
+triggers:
+  - phrase: "free-form prompt"
+  - phrase: "command suggestion"
+routes_to:
+  - "contract:command-suggestion-flow"
 load_context:
-  - .agent-src.uncompressed/contexts/communication/rules-auto/command-suggestion-policy-mechanics.md
+  - "../contexts/contracts/command-suggestion-flow.md"
 ---
 
-# Command Suggestion
+# Command Suggestion Policy
 
-When the user's prompt matches an eligible slash command, surface it
-as a **numbered option** alongside an "as-is" escape hatch — the
-"run prompt as-is" option is **always last** and **always present**,
-never omitted. The user always picks. **Nothing auto-executes.** The
-suggestion layer is a read-only shortcut *finder*, not an invocation
-path.
-
-The deterministic engine lives in `scripts/command_suggester/`. The
-locked eligibility table lives in
-[`agents/contexts/command-suggestion-eligibility.md`](../../agents/contexts/command-suggestion-eligibility.md).
-The scoring contract and hardening list live in
-[`docs/contracts/adr-command-suggestion.md`](../../docs/contracts/adr-command-suggestion.md)
-and
-[`docs/contracts/command-suggestion-flow.md`](../../docs/contracts/command-suggestion-flow.md).
+When the user's prompt matches an eligible slash command, surface it as a
+**numbered option** alongside an "as-is" escape hatch. The user always
+picks. **Nothing auto-executes.** Flow contract + senior-gate map:
+[`contexts/contracts/command-suggestion-flow.md`](../contexts/contracts/command-suggestion-flow.md).
 
 ## Iron Law — never auto-execute
 
@@ -31,64 +25,22 @@ and
 SUGGEST. NEVER INVOKE. THE USER PICKS, ALWAYS.
 ```
 
-A suggestion block emits options. It does **not** start a command
-flow. The user picking option N triggers `slash-command-routing-policy` on the
-**next** turn — with all the command's own halts intact.
-
-## When to fire
-
-On a user turn that matches **all** of the following:
-
-1. The message does **not** start with an explicit `/command` (those
-   bypass suggestion entirely — see `slash-command-routing-policy`).
-2. `commands.suggestion.enabled` is `true` (default).
-3. The user has not issued `/command-suggestion-off` in this conversation.
-4. No clarification is owed for the same turn (per
-   `ask-when-uncertain` — clarification wins; suggestion can fire next turn).
-5. No active engine flow is mid-halt (e.g. an `/implement-ticket`
-   step waiting on the user — the active flow has the floor).
-6. The matcher returns at least one match above the effective
-   `confidence_floor` after rank + cooldown + anti-noise.
-
-When all six hold, the suggestion block is the **first and only**
-thing the agent emits that turn. No tools, no edits, no other prose.
+A suggestion block emits options. It does **not** start a command flow.
+The "run as-is" option is **always present**, **always last**, never
+removed.
 
 ## Subordination — when to stay silent
 
 The suggestion rule is **junior** to:
 
-- `scope-control` — never surfaces a git-op command behind a
-  permission gate the user already declined this turn.
-- `ask-when-uncertain` — if a clarification is owed, the
-  clarification is the only question; suggestion suppresses for
-  that turn.
-- `verify-before-complete` — suggestion does not interrupt an
-  evidence-gate verification that's already running.
-- Any active role-mode contract (`role-mode-adherence`).
-- Any active engine halt (`/implement-ticket`, `/work`, etc.).
-
-On any conflict → suggestion stays silent. Zero output. The user's
-prompt is processed as it would be without this rule.
-
-## Cloud Behavior
-
-On cloud surfaces (Claude.ai Web, Skills API) the rule is **inert**
-unless the suggester package is shipped in the bundle. Treat
-`commands.suggestion.enabled` as `false` when the engine is not
-available — degrade silently, never crash the turn.
-
-## Mechanics — output format, anti-noise, what this rule does NOT do
-
-The exact rendered options block, the `Recommendation:` rules, the
-`max_options` cap, the `rank.py` anti-noise filters, and the
-"what this rule does NOT do" catalog live in
-[`contexts/communication/rules-auto/command-suggestion-policy-mechanics.md`](../contexts/communication/rules-auto/command-suggestion-policy-mechanics.md).
-
-## Interactions
-
-- [`slash-command-routing-policy`](slash-command-routing-policy.md) — explicit `/command` skips suggestion entirely.
-- [`user-interaction`](user-interaction.md) — numbered-options Iron Law and single-source recommendation.
-- [`ask-when-uncertain`](ask-when-uncertain.md) — clarification wins on conflict.
-- [`scope-control`](scope-control.md) — git-op gates outrank suggestion.
-- [`role-mode-adherence`](role-mode-adherence.md) — active mode contract outranks suggestion.
-- [`agents/contexts/command-suggestion-eligibility.md`](../../agents/contexts/command-suggestion-eligibility.md) — locked eligibility table.
+- [`scope-control`](scope-control.md) — never surfaces a git-op command
+  behind a permission gate the user already declined.
+- [`ask-when-uncertain`](ask-when-uncertain.md) — clarification wins on
+  conflict; suggestion suppresses for that turn.
+- [`verify-before-complete`](verify-before-complete.md) — suggestion does
+  not interrupt an evidence-gate verification.
+- [`role-mode-adherence`](role-mode-adherence.md) — active role-mode
+  contract outranks suggestion.
+- Any active engine halt (`/implement-ticket`, `/work`).
+
+On any conflict → suggestion stays silent.

package/.agent-src/rules/commit-conventions.md

@@ -1,68 +1,19 @@
 ---
 type: "auto"
 tier: "2a"
-alwaysApply: false
 description: "Git commit message format, branch naming, conventional commits, committing, pushing, or creating pull requests"
 source: package
+triggers:
+  - keyword: "commit"
+  - keyword: "branch"
+  - phrase: "conventional commits"
+routes_to:
+  - "skill:conventional-commits-writing"
 ---
 
 # Commit Conventions
 
-All commit messages and squash/merge titles must follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
+**Iron Law.** Use Conventional Commits (`feat:`, `fix:`, `chore:` …); branches `<type>/<short-slug>`; never invent your own format.
 
-## Format
-
-- With scope: `<type>(<scope>): <description>`
-- Without scope: `<type>: <description>` (omit parentheses when no scope)
-- **Always English** — regardless of user's language.
-- **Imperative mood** ("add feature", not "added feature").
-- **First line max 72 characters.**
-
-## Types
-
-| Type | When |
-|---|---|
-| `feat` | New user-facing functionality |
-| `fix` | Bug fix |
-| `refactor` | Code/structure change, no behavior change |
-| `docs` | Documentation only |
-| `test` | Tests only |
-| `chore` | Maintenance (deps, configs, tooling, cleanup) |
-| `ci` | CI/CD and workflow changes |
-| `style` | Code style (formatting, no logic change) |
-| `perf` | Performance improvement |
-| `build` | Build tooling / packaging changes |
-
-## Scope
-
-- Use the **Jira ticket ID** as scope when the branch contains one (e.g. `DEV-1234`).
-- Otherwise use a short module or area name (e.g. `api`, `auth`, `skills`).
-- Scope is optional — only add when it improves clarity.
-
-## Breaking changes
-
-Mark explicitly with `!` after type/scope or `BREAKING CHANGE:` in footer:
-
-```
-feat(api)!: rename invoice status values
-refactor(auth)!: remove legacy session flow
-```
-
-## Commit splitting
-
-If a change mixes unrelated concerns, split into multiple commits.
-Do NOT hide bug fixes, CI work, docs, and refactors in one commit.
-
-## Examples
-
-```
-feat(DEV-1234): add absence type filter to working time report
-fix(DEV-1234): handle null value in equipment import
-test(DEV-1234): add component test for working time controller
-refactor: extract user sync logic into dedicated service
-chore: update PHP quality package to 2.1.0
-ci(lint): add skill-lint workflow
-docs(roadmap): add phase 3 implementation plan
-```
-
-→ Full type selection rules and anti-patterns: see guideline `docs/guidelines/php/git.md`.
+Body migrated to `skill:conventional-commits-writing` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.

package/.agent-src/rules/commit-policy.md

@@ -5,16 +5,11 @@ description: "Commit policy — never commit and never ask about committing unle
 alwaysApply: true
 source: package
 load_context:
-  - .agent-src.uncompressed/contexts/authority/commit-mechanics.md
+  - ../contexts/authority/commit-mechanics.md
 ---
 
 # Commit Policy
 
-Local commits do not change remote state, but committing prematurely
-makes review harder. This is the **canonical** rule for committing,
-referenced by [`autonomous-execution`](autonomous-execution.md),
-[`scope-control`](scope-control.md), and the roadmap commands.
-
 ## The Iron Law
 
 ```
@@ -22,61 +17,35 @@ NEVER COMMIT. NEVER ASK ABOUT COMMITTING.
 EXCEPTIONS ARE EXPLICIT, NOT INFERRED.
 ```
 
-Applies regardless of `personal.autonomy`, conversation momentum, or
-"but it's a clean stopping point". Default is **no commit, no
-question**.
+Applies regardless of `personal.autonomy`, conversation momentum, or "clean stopping point". Default: **no commit, no question**.
 
 ## Exceptions — when committing IS allowed
 
-Exactly four ways the agent may commit:
+Exactly four:
 
-1. **User says so this turn** — explicit phrase like "commit this now",
-   "go ahead and commit". Permission is for **this commit only**, not
-   standing.
-2. **Standing instruction not yet revoked** — user said earlier in
-   the conversation "commit after every phase" or similar, and has not
-   revoked it. Cache and honor.
-3. **Commit command invoked** — `/commit` (with confirmation) or
-   `/commit-in-chunks` (auto-split, no confirmation).
-4. **Roadmap authorization** — the roadmap file lists explicit commit
-   steps and the user invoked roadmap execution.
+1. **User says so this turn** — "commit this now", "go ahead and commit". This commit only, not standing.
+2. **Standing instruction not yet revoked** — "commit after every phase" earlier in the conversation; cache and honor.
+3. **Commit command invoked** — `/commit` (with confirmation) or `/commit:in-chunks` (auto-split, no confirmation).
+4. **Roadmap authorization** — roadmap file lists explicit commit steps and the user invoked roadmap execution.
 
-Anything else → no commit. Hard Floor (bulk deletions, infra changes)
-still fires on top of any exception — see
-[`commit-mechanics`](../contexts/authority/commit-mechanics.md) for
-the diff triggers and the roadmap-authorized commit flow.
+Anything else → no commit. Hard Floor (bulk deletions, infra changes) still fires on top of any exception — see [`commit-mechanics`](../contexts/authority/commit-mechanics.md) for diff triggers and roadmap-authorized commit flow.
 
 ## NEVER ask about committing
 
-Asking "should I commit this?", "do we want to commit?", or any
-variant is **forbidden**. The user invokes a command or says so
-explicitly. Don't surface a commit option in numbered-options blocks
-unless the rest of the message would be incomplete without it.
+"Should I commit this?" / "do we want to commit?" — **forbidden**. The user invokes a command or says so explicitly. Don't surface a commit option in numbered-options blocks unless the rest of the message would be incomplete without it.
 
-Quoted commit phrases (chat-log paste, log excerpt, roadmap snippet)
-are **not** permission — see
-[`commit-mechanics`](../contexts/authority/commit-mechanics.md)
-§ Speech-act check.
+Quoted commit phrases (chat-log paste, log excerpt, roadmap snippet) are **not** permission — see [`commit-mechanics § Speech-act check`](../contexts/authority/commit-mechanics.md).
 
 ## NEVER write commit steps into roadmaps unsolicited
 
-When **creating** a roadmap (via `/roadmap-create`,
-`/feature-roadmap`, or any roadmap-producing flow), do **not** include
-commit steps unless the user explicitly requested them. Commits are a
-delivery decision; roadmaps plan **work**.
+When **creating** a roadmap (`/roadmap-create`, `/feature-roadmap`, any roadmap-producing flow) — do **not** include commit steps unless the user explicitly requested them. Commits are a delivery decision; roadmaps plan **work**.
 
-If the user explicitly wants commit steps in the roadmap, write them
-clearly and unambiguously (e.g. "Commit phase X: chore: …").
+If the user explicitly wants commit steps, write them clearly (e.g. "Commit phase X: chore: …").
 
 ## See also
 
-- [`autonomous-execution`](autonomous-execution.md) — when to suppress
-  trivial questions; this rule survives the suppression.
-- [`no-cheap-questions`](no-cheap-questions.md) — commit asks are
-  cheap by construction; this rule is the canonical Iron Law, the
-  cheap-questions rule cites it and refuses to surface the option.
-- [`scope-control`](scope-control.md) — git-ops permission gate
-  (push, merge, branch, PR, tag stay separately permission-gated).
+- [`autonomous-execution`](autonomous-execution.md) — trivial-question suppression; this rule survives the suppression.
+- [`no-cheap-questions`](no-cheap-questions.md) — commit asks are cheap by construction; this rule is the canonical Iron Law.
+- [`scope-control`](scope-control.md) — git-ops permission gate (push, merge, branch, PR, tag).
 - [`/commit`](../commands/commit.md) — split and commit with confirmation.
-- [`/commit-in-chunks`](../commands/commit-in-chunks.md) — auto-split
-  and commit without confirmation.
+- [`/commit:in-chunks`](../commands/commit/in-chunks.md) — auto-split, no confirmation.

package/.agent-src/rules/context-hygiene.md

@@ -4,6 +4,11 @@ tier: "1"
 alwaysApply: false
 description: "When debugging, fixing errors, or running long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
 source: package
+triggers:
+  - intent: "long conversation"
+  - intent: "tool loop"
+  - intent: "fresh chat"
+  - keyword: "3-failure"
 ---
 
 # Context Hygiene

package/.agent-src/rules/direct-answers.md

@@ -8,8 +8,7 @@ source: package
 
 # Direct Answers
 
-Three Iron Laws govern every reply. They override conversation
-momentum, politeness defaults, and the urge to fill space.
+Three Iron Laws govern every reply.
 
 ## Iron Law 1 — No Flattery
 
@@ -19,11 +18,10 @@ NEVER PRAISE THE USER'S IDEA TO MAKE THEM HAPPY.
 ANSWER THE SUBSTANCE. SHIP THE TRUTH.
 ```
 
-- No positive adjectives about user, question, idea, or work product as opener.
-- No subjective judgments on user's code/decisions ("nice approach", "boring") unless evaluation was asked.
-- "Good catch" / "you're right" only when literally true and load-bearing.
-- Acknowledge mistakes without performative apologies — one sentence, switch behavior.
-- Failure mode — praise hedging bad news; drop the cushion, deliver the news.
+- No positive-adjective opener about user / question / idea / work.
+- No subjective judgment on user code unless evaluation was asked.
+- "Good catch" / "you're right" only when literally true.
+- Mistakes — one-sentence acknowledge, switch behavior, no apology theatre.
 
 ## Iron Law 2 — No Invented Facts (severity-tiered)
 
@@ -33,16 +31,14 @@ THE MORE LOAD-BEARING THE CLAIM, THE HARDER YOU VERIFY.
 WHEN VERIFICATION IS NOT WORTH THE COST → ASK.
 ```
 
-| Severity | Required action |
+| Severity | Action |
 |---|---|
-| **High — load-bearing** (file paths, signatures, version numbers, security claims, "this test passes") | MUST verify with `view`, `grep`, `codebase-retrieval`, or fresh command output. Too expensive → ask. |
-| **Medium — project-shape** ("uses X for Y", conventions, file location) | Verify if one tool call reaches it; otherwise hedge: *"I'd guess X — not checked"*. |
-| **Low — well-known idioms** (generic language/framework idioms, public APIs) | Inference acceptable. Mark as inference if not 100% sure. |
+| **High** — load-bearing (paths, signatures, versions, security, "this passes") | Verify with `view` / `grep` / `codebase-retrieval` / fresh output. Too expensive → ask. |
+| **Medium** — project-shape (conventions, file location) | One-tool-call verify, else hedge: *"I'd guess X — not checked"*. |
+| **Low** — well-known idioms | Inference OK; mark as inference if not 100% sure. |
 
-Examples + hedge-language patterns:
-[`asking-and-brevity-examples`](../../docs/guidelines/agent-infra/asking-and-brevity-examples.md#direct-answers--severity-tiered-claim-examples).
-Override: "just guess", "rough estimate is fine", "skip the verify"
-→ drop to Low for that turn.
+Override: "just guess" / "rough estimate" / "skip verify" → drop to Low for that turn.
+Examples + hedge patterns: [`asking-and-brevity-examples § severity`](../docs/guidelines/agent-infra/asking-and-brevity-examples.md#direct-answers--severity-tiered-claim-examples).
 
 ## Iron Law 3 — Brevity by Default
 
@@ -51,41 +47,24 @@ THE SHORTEST REPLY THAT FULLY ANSWERS THE QUESTION IS THE RIGHT REPLY.
 LONG ANSWERS ARE A FAILURE MODE, NOT A SIGN OF EFFORT.
 ```
 
-- Skip restating the user's question.
-- Skip announcing intent ("Let me…", "I will now…") — just do.
+- Skip restating the question; skip "Let me…" intent announcements.
 - Skip explaining tool use — the call result speaks.
 - Skip post-hoc summary unless rechecking a decision.
-- Multi-step → bullets, not paragraphs.
-- One-true-answer question → one sentence + the answer.
+- Multi-step → bullets. One-true-answer → one sentence.
 
-`token-efficiency` covers the loop side; this rule covers per-reply
-length. **Never overrides** `user-interaction` (numbered options stay)
-or command-mandated steps.
+Never overrides `user-interaction` (numbered options stay) or command-mandated steps.
 
 ## Emoji Scope — functional markers only
 
-**Whitelist:** `📒` (chat-history heartbeat, verbatim per
-`chat-history-visibility`); mode markers from `role-mode-adherence`;
-CLI status `❌` / `✅` / `⚠️` (two-space rule from `language-and-tone`);
-roadmap checkboxes `[x]` / `[~]` / `[-]`.
+**Whitelist:** mode markers (`role-mode-adherence`); CLI status `❌` / `✅` / `⚠️`; roadmap checkboxes `[x]` / `[~]` / `[-]`.
+**Blacklist:** opening flair (✨, 🚀, 🎉, 💡, 🔥, 👍); empathy (❤️, 🤗, 😊); section dividers; reaction emojis. Unsure → blacklist.
 
-**Blacklist (never in prose):** opening flair (✨, 🚀, 🎉, 💡, 🔥, 👍);
-empathy (❤️, 🤗, 😊); section dividers, headline ornaments, reaction
-emojis. Unsure → assume blacklist.
+## Failure modes & examples
 
-## Failure modes
-
-Trigger phrases + in-language correction pattern:
-[`asking-and-brevity-examples`](../../docs/guidelines/agent-infra/asking-and-brevity-examples.md#direct-answers--failure-modes-the-user-will-call-out).
-On call-out: acknowledge once in the user's language, switch, no
-excuses (mirrors `language-and-tone` § slip handling).
+Trigger phrases + correction pattern: [`asking-and-brevity-examples § failure-modes`](../docs/guidelines/agent-infra/asking-and-brevity-examples.md#direct-answers--failure-modes-the-user-will-call-out).
+Pattern Memory (wrong / right / why): [`direct-answers-demos`](../docs/guidelines/agent-infra/direct-answers-demos.md).
+Outcome baseline: [`tests/golden/outcomes/direct_answers.json`](../../tests/golden/outcomes/direct_answers.json).
 
 ## Interactions
 
-- `language-and-tone` — language mirroring, `.md` always English,
-  CLI-icon two-space rule.
-- `ask-when-uncertain` — resolution surface for Iron Law 2 gaps.
-- `think-before-action` — how to verify code-behavior claims.
-- `verify-before-complete` — completion-claim evidence gate.
-- `token-efficiency` — loop-side brevity.
-- `user-interaction` — numbered-options Iron Law overrides brevity.
+`language-and-tone` · `ask-when-uncertain` · `think-before-action` · `verify-before-complete` · `token-efficiency` · `user-interaction` (overrides brevity).

package/.agent-src/rules/docker-commands.md

@@ -1,54 +1,20 @@
 ---
 type: "auto"
 tier: "3"
-alwaysApply: false
 description: "Running PHP commands inside Docker containers — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, and any CLI tool execution"
 source: package
+triggers:
+  - keyword: "docker"
+  - keyword: "artisan"
+  - keyword: "composer"
+  - phrase: "inside the container"
+routes_to:
+  - "skill:docker"
 ---
 
-# Docker Container Commands
+# Docker Commands
 
-All PHP commands (PHPStan, Rector, Composer, PHPUnit, Artisan) must be executed **inside the Docker container**, not on the host.
+**Iron Law.** Run PHP / artisan / composer / phpstan / rector / ecs / phpunit inside the project container, never on the host.
 
-## Container Detection
-
-Detect the correct PHP container service name from `docker-compose.yml` / `compose.yaml`.
-Read the compose file to find the PHP service name — it varies per project.
-
-Use `docker compose exec -T <service> ...` for non-interactive commands (scripts, CI).
-Use `make console` to enter the container interactively (if available).
-
-## Tooling Detection
-
-Check if `artisan` exists in the project root:
-
-- **Laravel** (`artisan` exists): `php artisan test`, `vendor/bin/phpstan analyse`, `vendor/bin/rector process`
-- **Composer** (no `artisan`): `vendor/bin/phpunit`, `vendor/bin/phpstan analyse`, `vendor/bin/rector process`
-
-## Examples (Laravel project)
-
-```bash
-docker compose exec -T <php-service> vendor/bin/phpstan analyse
-docker compose exec -T <php-service> vendor/bin/rector process
-docker compose exec -T <php-service> vendor/bin/ecs check --fix
-docker compose exec -T <php-service> php artisan test
-```
-
-## Examples (Composer project)
-
-```bash
-docker compose exec -T <php-service> vendor/bin/phpstan analyse
-docker compose exec -T <php-service> vendor/bin/rector process
-docker compose exec -T <php-service> vendor/bin/ecs check --fix
-docker compose exec -T <php-service> vendor/bin/phpunit
-```
-
-## Build / Task Runner
-
-Before using raw `docker compose exec` commands, check if the consumer
-project ships a `Makefile` for common targets (e.g. `make console`,
-`make test`, `make phpstan`). Read the Makefile first to discover
-available shortcuts. If the project uses a different task runner,
-inspect its config file before defaulting to raw `docker compose exec`.
-
-Frontend commands (npm, webpack) run on the host or in the node container.
+Body migrated to `skill:docker` (per P4 of `road-to-kernel-and-router.md`).
+Trigger-set above activates this routing under the `balanced` and `full` profiles.