@event4u/agent-config 1.16.0 → 1.17.0

package/.agent-src/skills/test-driven-development/SKILL.md

@@ -9,23 +9,23 @@ source: package
 ## When to use
 
 * Adding a new function, method, or behavior
-* Fixing a bug (bug needs a regression test before the fix)
+* Fixing a bug (the bug needs a regression test before the fix)
 * Refactoring a unit whose current behavior is unclear
 * Any task where expected behavior can be expressed as an assertion
 
 Do NOT use when:
 
-* Throwaway prototype or spike code explicitly marked as exploration
-* Boilerplate generation (migrations, config, scaffolding)
-* Pure documentation (`.md`, `AGENTS.md`, README)
+* Writing throwaway prototype or spike code explicitly marked as exploration
+* Generating boilerplate (migrations, config files, scaffolding)
+* Editing pure documentation (`.md`, `AGENTS.md`, README)
 * Working inside this `agent-config` package on skill/rule markdown
 
 ## Goal
 
-* Drive implementation from a verified-failing test, not the agent's
-  belief that code "should work".
-* Catch edge cases **before** production bugs.
-* Leave every change with a regression test running in CI.
+* Drive implementation from a verified-failing test, not from the agent's
+  belief that the code "should work".
+* Catch edge cases **before** they become production bugs.
+* Leave every change with a regression test that runs in CI.
 
 ## The core discipline
 
@@ -38,7 +38,7 @@ Do NOT use when:
 ```
 
 If step 2 is skipped, the test is not trusted — a test that has never
-failed proves nothing.
+failed proves nothing about the code under test.
 
 ## Procedure
 
@@ -46,21 +46,21 @@ failed proves nothing.
 
 State in one sentence: *"When X happens, the system should do Y."*
 
-Cannot state in one sentence? Scope too big — split into multiple tests,
-one sentence each.
+If you cannot state it in one sentence, the scope is too big — split into
+multiple tests, each covering one sentence.
 
 ### 2. Write the failing test first
 
-Smallest test expressing step-1 sentence.
+Write the smallest test that expresses the sentence from step 1.
 
-* One assertion per behavior (multiple assertions OK only when describing
-  the same single behavior).
+* One assertion per behavior (multiple assertions are OK only when they
+  describe the same single behavior).
 * Real code paths, not mocks — mock only at I/O boundaries (HTTP, DB, time).
-* Descriptive name: `it_rejects_empty_email`, not `test_email_1`.
+* Use a descriptive name: `it_rejects_empty_email`, not `test_email_1`.
 
 ### 3. Run the test and watch it fail
 
-Execute the single test (targeted, not full suite):
+Execute the single test (targeted, not the full suite):
 
 ```bash
 # PHP/Pest
@@ -72,26 +72,27 @@ npx vitest run --testNamePattern "rejects empty email"
 
 Required observations **before proceeding**:
 
-* Test **fails** (not errors).
-* Failure message matches expectation (missing behavior, not typo).
-* Passes immediately → it does not test what you think. Fix the test,
-  do not start writing production code.
+* The test **fails** (not errors).
+* The failure message matches what you expected (missing behavior, not typo).
+* If the test passes immediately → it does not test what you think. Fix
+  the test, do not start writing production code.
 
 ### 4. Write minimum code to pass
 
-**Just enough** production code to make the test green. No extra
+Add **just enough** production code to make the test green. No extra
 features, no unrelated refactoring, no "while I'm here" cleanups.
 
-Urge to add a parameter, edge case, or helper not covered by current
-test → stop. Belongs in the next RED step, not this GREEN step.
+If you feel the urge to add a parameter, edge case, or helper not covered
+by the current test — stop. That belongs in the next RED step, not this
+GREEN step.
 
 ### 5. Run again and watch it pass
 
 Re-run the same targeted command. Required:
 
-* New test passes.
-* No previously green tests turned red.
-* Output clean (no new warnings, deprecations, or noise).
+* The new test passes.
+* No previously green tests have turned red.
+* Test output is clean (no new warnings, deprecations, or noise).
 
 ### 6. Refactor (only if green)
 
@@ -101,8 +102,8 @@ With all tests green, you may:
 * Extract duplication into helpers
 * Tighten types
 
-Do **not** add new behavior during refactor — needs its own failing test
-first. Re-run tests after refactor to confirm still-green.
+Do **not** add new behavior during refactor — that needs its own failing
+test first. Re-run tests after the refactor to confirm still-green.
 
 ### 7. Repeat for the next behavior
 
@@ -110,25 +111,25 @@ Back to step 1 with the next single-sentence behavior.
 
 ## Output format
 
-1. Failing test (file + test name) with captured failure output
-2. Minimum-code diff that makes it pass
+1. The failing test (file + test name) with captured failure output
+2. The minimum-code diff that makes it pass
 3. Captured green-run output
-4. Refactor diff (optional)
+4. Any refactor diff (optional)
 
 ## Anti-rationalizations table
 
-The urge to skip TDD is strongest when TDD matters most. Name the
-rationalization and reject it:
+The urge to skip TDD is strongest on tasks where TDD matters most. Name
+the rationalization and reject it:
 
 | Thought | Reality |
 |---|---|
-| "Too simple to need a test" | Simple code still breaks. A test costs less than one debug cycle. |
-| "I'll add the test after the code works" | A test written after code passes on first run — never failed. Proves nothing. |
-| "I already ran it manually" | Manual runs not repeatable. Next edit breaks it silently. |
-| "Deleting code I just wrote is wasteful" | Sunk cost. Cheap path: delete, write test, reimplement minimally. |
-| "I'll keep the code as reference while I write the test" | You will adapt it. That is test-after-the-fact with extra steps. Delete it. |
-| "I just need to explore the API first" | Spike on a throwaway branch. Then delete and restart with TDD. |
-| "The test is too hard to write" | Signals a design problem in the code, not the test. Listen. |
+| "This is too simple to need a test" | Simple code still breaks. A test takes less time than one debug cycle. |
+| "I'll add the test after the code works" | A test written after code passes on the first run — it has never failed. It does not prove the code is correct. |
+| "I already ran it manually" | Manual runs are not repeatable. The next edit breaks it silently. |
+| "Deleting this code I just wrote is wasteful" | Sunk cost. The cheap path is: delete, write the test, reimplement minimally. |
+| "I'll keep the code as reference while I write the test" | You will read it and adapt it. That is test-after-the-fact with extra steps. Delete it. |
+| "I just need to explore the API first" | Spike it on a throwaway branch. Then delete it and restart with TDD. |
+| "The test is too hard to write" | That signals a design problem in the code, not in the test. Listen to it. |
 | "This bug is urgent, no time for a test" | The test **is** the fastest path to a verified fix. Guessing takes longer. |
 
 
@@ -162,7 +163,7 @@ final class EmailValidator
 }
 ```
 
-Run filter again → passes. No additional rules (format, MX, length)
+Run the filter again → passes. No additional rules (format, MX, length)
 until a next failing test drives them.
 
 ### JS / Vitest
@@ -184,7 +185,7 @@ it('retries a failing operation up to 3 times', async () => {
 ```
 
 Run: `npx vitest run --testNamePattern "retries a failing"` → fails
-(`retry` undefined).
+(`retry` is undefined).
 
 ```ts
 // src/retry.ts — GREEN (minimum)
@@ -197,21 +198,22 @@ export async function retry<T>(op: () => Promise<T>): Promise<T> {
 }
 ```
 
-Run again → passes. Configurable attempt count, backoff, jitter all
+Run again → passes. Configurable attempt count, backoff, and jitter all
 wait for their own failing tests.
 
 ## Gotchas
 
 * Running the full suite instead of a filtered test hides the RED→GREEN
   signal in noise. Always target first.
-* A test that passes on the very first run is not TDD — written against
-  existing code.
+* A test that passes on the very first run is not TDD — it was written
+  against code that already exists.
 * `expect()` with three or four assertions on unrelated fields describes
   multiple behaviors. Split them.
-* Snapshot tests invert the discipline — they generate the expected
-  value from the code. Only use where human-readable output is the
-  contract (CLI, SQL strings).
-* Mocking the thing under test (instead of its I/O) tests the mock.
+* Snapshot tests invert the discipline — they generate the expected value
+  from the code. Only use snapshots where human-readable output is the
+  contract (CLI output, SQL strings).
+* Mocking the thing under test (instead of its I/O) tests the mock, not
+  the code.
 
 ## Do NOT
 
@@ -219,22 +221,22 @@ wait for their own failing tests.
   and has been observed to fail
 * Do NOT accept a test that never failed as evidence the code works
 * Do NOT bundle refactors into the GREEN step
-* Do NOT silence a flaky test — diagnose or delete it
-* Do NOT skip the targeted RED-run because "I know it fails"
+* Do NOT silence a flaky test — diagnose it, or delete it
+* Do NOT skip the targeted RED-run because "I just wrote it, I know it fails"
 
 ## Anti-patterns
 
 * `it('works')` — no behavior described
 * One test covering "and/and/and" — split per behavior
-* Test reaching into private state instead of observable behavior
-* Test duplicating the production code's algorithm (tautology)
+* Test that reaches into private state instead of testing observable behavior
+* Test that duplicates the production code's algorithm (tautology)
 
 ## When to hand over to another skill
 
 * Quality tools, PHPStan, ECS, Rector → [`quality-tools`](../quality-tools/SKILL.md)
 * Full Pest conventions, Laravel testing helpers → [`pest-testing`](../pest-testing/SKILL.md)
 * Running tests inside Docker → [`tests-execute`](../tests-execute/SKILL.md)
-* Investigating why a test fails for non-obvious reasons →
+* Investigating why a test is failing for non-obvious reasons →
   [`systematic-debugging`](../systematic-debugging/SKILL.md)
 
 ## Validation checklist
@@ -243,10 +245,10 @@ Before marking TDD work complete:
 
 * [ ] Every new behavior has a test
 * [ ] Each test was observed to fail first, with a matching failure message
-* [ ] Minimum code was written to turn each RED into GREEN
+* [ ] The minimum code was written to turn each RED into GREEN
 * [ ] All targeted tests pass
-* [ ] No adjacent test turned red
-* [ ] Output clean (no new warnings or deprecations)
+* [ ] No adjacent test has turned red
+* [ ] Test output is clean (no new warnings or deprecations)
 
 See also [`developer-like-execution`](../developer-like-execution/SKILL.md)
 for the broader think → analyze → verify loop this skill plugs into.

package/.agent-src/skills/test-performance/SKILL.md

@@ -148,7 +148,6 @@ Replace dynamic `getPdo()` probing with explicit config:
 
 ## Related project docs
 
-- `agents/roadmaps/test-performance-refactor.md` — active roadmap for this project
 - `agents/docs/seeders.md` — seeder conventions (if exists)
 
 ## Output format

package/.agent-src/skills/traefik/SKILL.md

@@ -18,11 +18,11 @@ Use this skill when:
 
 ### 0. Understand current setup
 
-Before changing routing:
+Before changing any routing configuration:
 
-1. Check existing proxy — `docker ps | grep traefik`
-2. Review docker-compose for existing labels and network config
-3. Check `/etc/hosts` or dnsmasq for existing domain mappings
+1. **Check existing proxy setup** — is Traefik already running? Check `docker ps | grep traefik`.
+2. **Review docker-compose** — read `docker-compose.yml` for existing labels and network config.
+3. **Check DNS/hosts** — review `/etc/hosts` or dnsmasq for existing domain mappings.
 
 ### Architecture
 

package/.agent-src/skills/verify-completion-evidence/SKILL.md

@@ -11,9 +11,9 @@ source: package
 * Just before claiming a task, feature, fix, or refactor is complete
 * Just before proposing `/commit`, `/create-pr`, or pushing
 * Before answering "is it ready?", "can I merge?", "does it work?"
-* After a sequence of edits, when next step is reporting to the user
-* Whenever "should work", "looks good", "probably fine" is about to
-  appear in a reply
+* After a sequence of edits, when next step would be reporting to the user
+* Whenever the wording "should work", "looks good", "probably fine" is
+  about to appear in a reply
 
 Do NOT use when:
 
@@ -40,11 +40,11 @@ runs are stale the moment another edit lands.
 
 ### 1. Identify the claim you are about to make
 
-Examples: *"all tests pass"*, *"ready for PR"*, *"refactor is done"*,
-*"bug is fixed"*.
+Examples: *"all tests pass"*, *"this is ready for PR"*, *"the refactor
+is done"*, *"the bug is fixed"*.
 
-Each claim maps to a specific verification command. Write the mapping
-before running anything:
+Each claim maps to a specific verification command. Write down the
+mapping before running anything:
 
 | Claim | Evidence command |
 |---|---|
@@ -58,11 +58,11 @@ before running anything:
 
 ### 2. Run the command fresh
 
-* Run against current working tree, not a cached summary.
-* PHP projects inside Docker: run inside the container (see
+* Run against the current working tree, not a cached summary.
+* For PHP projects inside Docker: run inside the container (see
   [`docker`](../docker/SKILL.md) and [`tests-execute`](../tests-execute/SKILL.md)).
 * Use targeted runs during iteration (`--filter=`, `--testNamePattern`).
-  Run full suite only in the final verification pass.
+  Run the full suite only in the final verification pass.
 
 ### 3. Read the full output
 
@@ -87,20 +87,20 @@ errors on `app/Services/`."* — not *"everything looks good"*.
 
 ## The end-of-work sequence (PHP projects)
 
-When all code changes are done and ready to report completion:
+When all code changes are done and you are ready to report completion:
 
-1. **Targeted tests** — test(s) covering the changed code pass
+1. **Targeted tests** — the test(s) covering the changed code pass
 2. **Full test suite** — only after targeted pass is green
 3. **PHPStan** → **Rector --dry-run** → **ECS** → **PHPStan** (second pass
-   catches issues Rector / ECS introduced)
+   catches issues Rector / ECS may have introduced)
 4. Fix any output from steps 1–3 and restart the sequence
 5. Only then: claim completion or suggest `/commit`, push, or PR
 
-Do not run the full quality pipeline between intermediate edits — burns
-time and tokens. Use it once, at the end.
+Do not run the full quality pipeline between intermediate edits — it
+burns time and tokens. Use it once, at the end.
 
-See [`quality-tools`](../quality-tools/SKILL.md) for exact commands per
-tool.
+See [`quality-tools`](../quality-tools/SKILL.md) for the exact commands
+per tool.
 
 ## Minimum evidence per task type
 
@@ -124,7 +124,7 @@ is sound", "compiles" (unless compilation itself is the contract).
 When reporting completion to the user:
 
 1. **What was changed** — one line summary per changed file / component
-2. **Verification run** — exact command and its exit code
+2. **Verification run** — the exact command and its exit code
 3. **Result** — numeric breakdown (tests passed/failed/skipped, errors,
    warnings)
 4. **Caveats** — anything the output flagged but you chose to accept
@@ -132,14 +132,16 @@ When reporting completion to the user:
 
 ## Gotchas
 
-* "No output" from a linter is not proof it ran — check exit code and
-  analyzed-file count.
+* A "no output" result from a linter is not proof it ran — check the
+  exit code and the analyzed-file count.
 * Silencing a warning with `@phpstan-ignore-next-line` or `// @ts-expect-error`
   without a reason code passes the linter but defers the real problem.
-* Running tests with `--stop-on-failure` then reporting "passed" — only
-  ran until the first failure; the green streak after is unexamined.
+* Running tests with `--stop-on-failure` then reporting "passed" — it
+  only ran until the first failure; the green streak after it is
+  unexamined.
 * Cached static-analysis results (`--cache` directories) can report
-  clean after you broke something; clear the cache for large changes.
+  clean after you have broken something; clear the cache when the
+  change is large.
 * Running the test suite on the wrong branch (forgot to switch or
   rebase) — verify `git status` and `git log -1` before the final gate.
 * A previously green PHPStan run in the same conversation is stale as
@@ -165,13 +167,13 @@ When reporting completion to the user:
 * Do NOT suppress warnings or skip tests to pass the gate
 * Do NOT report only the last line of output — read the whole thing
 * Do NOT run the full quality pipeline between intermediate edits —
-  run once at the end
+  run it once at the end
 
 ## When to hand over to another skill
 
 * Exact PHPStan / Rector / ECS commands → [`quality-tools`](../quality-tools/SKILL.md)
 * Running tests inside Docker → [`tests-execute`](../tests-execute/SKILL.md)
-* Writing the regression test the gate requires →
+* Writing the regression test that the gate requires →
   [`test-driven-development`](../test-driven-development/SKILL.md)
 * Diagnosing why the gate failed → [`systematic-debugging`](../systematic-debugging/SKILL.md)
 * Committing once the gate is green → [`git-workflow`](../git-workflow/SKILL.md)
@@ -180,7 +182,7 @@ When reporting completion to the user:
 
 Before sending a completion message:
 
-* [ ] Every claim maps to a command run in this turn
+* [ ] Every claim in the message maps to a command run in this turn
 * [ ] Exit code of each command is read and matches the claim
 * [ ] Output is quoted with numeric counts, not paraphrased
 * [ ] No warnings or skips are hidden

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Shared agent configuration \u2014 skills for AI coding tools (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI).",
-    "version": "1.16.0"
+    "version": "1.17.0"
   },
   "plugins": [
     {
@@ -19,6 +19,7 @@
         "./.claude/skills/agent-docs-writing",
         "./.claude/skills/agent-handoff",
         "./.claude/skills/agent-status",
+        "./.claude/skills/agents",
         "./.claude/skills/agents-audit",
         "./.claude/skills/agents-cleanup",
         "./.claude/skills/agents-prepare",
@@ -41,6 +42,7 @@
         "./.claude/skills/chat-history-checkpoint",
         "./.claude/skills/chat-history-clear",
         "./.claude/skills/chat-history-resume",
+        "./.claude/skills/chat-history-show",
         "./.claude/skills/check-current-md",
         "./.claude/skills/check-refs",
         "./.claude/skills/code-refactoring",
@@ -51,21 +53,24 @@
         "./.claude/skills/commit-in-chunks",
         "./.claude/skills/composer-packages",
         "./.claude/skills/compress",
+        "./.claude/skills/context",
         "./.claude/skills/context-authoring",
         "./.claude/skills/context-create",
         "./.claude/skills/context-document",
         "./.claude/skills/context-refactor",
         "./.claude/skills/conventional-commits-writing",
+        "./.claude/skills/copilot-agents",
         "./.claude/skills/copilot-agents-init",
         "./.claude/skills/copilot-agents-optimization",
         "./.claude/skills/copilot-agents-optimize",
         "./.claude/skills/copilot-config",
         "./.claude/skills/council",
+        "./.claude/skills/council-default",
         "./.claude/skills/council-design",
         "./.claude/skills/council-optimize",
         "./.claude/skills/council-pr",
         "./.claude/skills/create-pr",
-        "./.claude/skills/create-pr-description",
+        "./.claude/skills/create-pr-description-only",
         "./.claude/skills/dashboard-design",
         "./.claude/skills/data-flow-mapper",
         "./.claude/skills/database",
@@ -74,8 +79,6 @@
         "./.claude/skills/design-review",
         "./.claude/skills/devcontainer",
         "./.claude/skills/developer-like-execution",
-        "./.claude/skills/do-and-judge",
-        "./.claude/skills/do-in-steps",
         "./.claude/skills/docker",
         "./.claude/skills/dto-creator",
         "./.claude/skills/e2e-heal",
@@ -96,10 +99,10 @@
         "./.claude/skills/fix",
         "./.claude/skills/fix-ci",
         "./.claude/skills/fix-portability",
-        "./.claude/skills/fix-pr-bot-comments",
-        "./.claude/skills/fix-pr-comments",
-        "./.claude/skills/fix-pr-developer-comments",
-        "./.claude/skills/fix-references",
+        "./.claude/skills/fix-pr",
+        "./.claude/skills/fix-pr-bots",
+        "./.claude/skills/fix-pr-developers",
+        "./.claude/skills/fix-refs",
         "./.claude/skills/fix-seeder",
         "./.claude/skills/flux",
         "./.claude/skills/git-workflow",
@@ -113,7 +116,10 @@
         "./.claude/skills/judge",
         "./.claude/skills/judge-bug-hunter",
         "./.claude/skills/judge-code-quality",
+        "./.claude/skills/judge-on-diff",
         "./.claude/skills/judge-security-auditor",
+        "./.claude/skills/judge-solo",
+        "./.claude/skills/judge-steps",
         "./.claude/skills/judge-test-coverage",
         "./.claude/skills/laravel",
         "./.claude/skills/laravel-horizon",
@@ -131,12 +137,15 @@
         "./.claude/skills/logging-monitoring",
         "./.claude/skills/mcp",
         "./.claude/skills/md-language-check",
+        "./.claude/skills/memory",
         "./.claude/skills/memory-add",
-        "./.claude/skills/memory-full",
+        "./.claude/skills/memory-load",
         "./.claude/skills/memory-promote",
+        "./.claude/skills/memory-propose",
         "./.claude/skills/merge-conflicts",
         "./.claude/skills/migration-creator",
         "./.claude/skills/mode",
+        "./.claude/skills/module",
         "./.claude/skills/module-create",
         "./.claude/skills/module-explore",
         "./.claude/skills/module-management",
@@ -146,8 +155,9 @@
         "./.claude/skills/optimize",
         "./.claude/skills/optimize-agents",
         "./.claude/skills/optimize-augmentignore",
-        "./.claude/skills/optimize-rtk-filters",
+        "./.claude/skills/optimize-rtk",
         "./.claude/skills/optimize-skills",
+        "./.claude/skills/override",
         "./.claude/skills/override-create",
         "./.claude/skills/override-manage",
         "./.claude/skills/override-management",
@@ -173,7 +183,6 @@
         "./.claude/skills/project-analyzer",
         "./.claude/skills/project-docs",
         "./.claude/skills/project-health",
-        "./.claude/skills/propose-memory",
         "./.claude/skills/quality-fix",
         "./.claude/skills/quality-tools",
         "./.claude/skills/react-shadcn-ui",
@@ -186,6 +195,7 @@
         "./.claude/skills/requesting-code-review",
         "./.claude/skills/review-changes",
         "./.claude/skills/review-routing",
+        "./.claude/skills/roadmap",
         "./.claude/skills/roadmap-create",
         "./.claude/skills/roadmap-execute",
         "./.claude/skills/roadmap-management",
@@ -211,6 +221,7 @@
         "./.claude/skills/terragrunt",
         "./.claude/skills/test-driven-development",
         "./.claude/skills/test-performance",
+        "./.claude/skills/tests",
         "./.claude/skills/tests-create",
         "./.claude/skills/tests-execute",
         "./.claude/skills/threat-model",

package/AGENTS.md

@@ -103,8 +103,8 @@ and
 ```
 .agent-src.uncompressed/      ← edit here
   skills/       (129 skills)
-  rules/        (57 rules)
-  commands/     (84 files — 69 active + 15 deprecation shims)
+  rules/        (58 rules)
+  commands/     (95 commands)
   personas/     (7 personas)
   templates/    (AGENTS.md, copilot-instructions.md, skill.md, …)
   contexts/