@event4u/agent-config 2.25.0 → 2.26.0

package/.agent-src/commands/bug-fix.md

@@ -9,6 +9,7 @@ suggestion:
   eligible: true
   trigger_description: "fix this bug, patch the issue, resolve this error"
   trigger_context: "branch name matches fix/* or bug/*"
+framework: laravel
 ---
 
 # bug-fix

package/.agent-src/commands/feature/roadmap.md

@@ -97,7 +97,7 @@ For each roadmap, work through the phases interactively:
 - [ ] {concrete task with file reference}
 - [ ] {concrete task}
 - [ ] Tests: {what to test}
-- [ ] Quality: PHPStan + Rector
+- [ ] Quality: project's type-checker + auto-fixer (see `quality-tools` skill — e.g. PHPStan + Rector for PHP, tsc + eslint --fix for TS, mypy + ruff for Python)
 ```
 
 ### 4. Generate the roadmap(s)
@@ -206,7 +206,7 @@ What's next?
 - **Always link roadmaps back to the feature** and vice versa.
 - **Use the roadmap template** at `.augment/templates/roadmaps.md`.
 - **Reference specific files** in roadmap tasks — not vague descriptions.
-- **Include quality gates** (PHPStan, Rector, tests) in every phase.
+- **Include quality gates** in every phase — the project's type-checker, auto-fixer, and full test run. Look up the actual commands via `quality-tools` instead of hardcoding stack-specific tool names in the roadmap.
 - **Research the codebase** to make tasks concrete and realistic.
 
 ## See also

package/.agent-src/commands/fix/seeder.md

@@ -10,6 +10,7 @@ suggestion:
   eligible: true
   trigger_description: "the seeder is broken, foreign key errors in seeders"
   trigger_context: "seeder error output or recent edits in database/seeders/"
+framework: laravel
 ---
 
 # /fix seeder
@@ -64,9 +65,9 @@ where the seeder class is NOT the owner of the data file.
 
 ### Known Exceptions
 
-Currently there are **no exceptions**. All circular deps have been resolved.
+Currently there are **no exceptions**. All circular dependencies have been resolved.
 
-**Pattern for resolving circular deps:** Use two-phase seeding. The data file seeds
+**Pattern for resolving circular dependencies:** Use two-phase seeding. The data file seeds
 records with placeholder values (e.g., empty arrays). The Seeder's `run()` method then updates
 records with the real values using `getReference()`. Since `run()` is called after all seeders
 are initialized, the circular dependency is broken.

package/.agent-src/commands/memory/add.md

@@ -137,6 +137,6 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 
 - [`engineering-memory-data-format`](../../docs/guidelines/agent-infra/engineering-memory-data-format.md)
   — full schema
-- [`capture-learnings`](../rules/capture-learnings.md) — when a
-  learning is better captured as an `incident-learnings` entry vs a
-  rule/skill proposal
+- [`skill:learning-to-rule-or-skill`](../skills/learning-to-rule-or-skill/SKILL.md) —
+  when a learning is better captured as an `incident-learnings` entry vs
+  a rule/skill proposal

package/.agent-src/commands/module/create.md

@@ -10,6 +10,7 @@ suggestion:
   eligible: true
   trigger_description: "create a new module, scaffold a module for X"
   trigger_context: "prompt mentions a new domain area without an existing module"
+framework: laravel
 ---
 
 # /module create

package/.agent-src/commands/module/explore.md

@@ -3,7 +3,7 @@ name: module:explore
 tier: 2
 cluster: module
 sub: explore
-skills: [laravel]
+skills: [laravel, symfony-workflow, php-coder]
 description: Explore a module — load its structure, docs, and context into the current conversation
 disable-model-invocation: true
 suggestion:
@@ -17,17 +17,21 @@ suggestion:
 
 ### 1. Check for modules
 
-- **Laravel projects**: Check if `app/Modules/` exists.
-- **Composer projects / packages**: Check `./agents/` or `src/` for domain directories.
-- If neither exists:
+- **Laravel HMVC**: Check `app/Modules/`.
+- **Symfony / DDD-lite**: Check `src/<Domain>/` or `src/Module/<Domain>/`.
+- **Composer packages / libraries**: Check `./agents/` or `src/` for domain directories.
+- **Node / TS monorepo**: Check `packages/`, `apps/`, or `modules/`.
+- **Python**: Check top-level package dirs under `src/<package>/` or flat `<package>/`.
+- **Go**: Check `internal/<domain>/` or `cmd/<service>/`.
+- If none of the above exists:
   ```
-  ⚠️  No module system found (no app/Modules/ directory).
+  ⚠️  No module system found (no Modules/, src/<Domain>/, packages/, internal/, or equivalent directory).
   ```
   Stop.
 
 ### 2. List available modules
 
-Scan `app/Modules/` and show all modules (skip `.module-template` and hidden dirs):
+Scan the detected modules directory (see step 1) and show all modules. Skip `.module-template`, `.example`, and hidden dirs:
 
 ```
 📦 Available modules:

package/.agent-src/commands/onboard.md

@@ -217,7 +217,15 @@ no network call, file-existence only:
 
 ```bash
 stacks=()
-[ -f composer.json ] && stacks+=("php")
+if [ -f composer.json ]; then
+  if grep -q '"laravel/framework"' composer.json 2>/dev/null; then
+    stacks+=("php-laravel")
+  elif grep -q '"symfony/framework-bundle"' composer.json 2>/dev/null; then
+    stacks+=("php-symfony")
+  else
+    stacks+=("php")
+  fi
+fi
 [ -f package.json ] && stacks+=("node")
 [ -f Cargo.toml ] && stacks+=("rust")
 [ -f go.mod ] && stacks+=("go")

package/.agent-src/commands/optimize/augmentignore.md

@@ -31,11 +31,24 @@ and creates/updates `.augmentignore` accordingly. Also identifies irrelevant
 | `go.mod` exists | `go.sum` |
 | `.idea/` exists | `.idea/` |
 | `.vscode/` exists | `.vscode/` |
-| `_ide_helper.php` exists | `_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php` |
+| `_ide_helper.php` exists (Laravel `barryvdh/laravel-ide-helper`) | `_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php` |
 | `public/build/` exists | `public/build/` |
-| `storage/` exists (Laravel) | `storage/logs/`, `storage/framework/cache/`, `storage/framework/sessions/`, `storage/framework/views/` |
+| `storage/` exists AND `artisan` exists (Laravel) | `storage/logs/`, `storage/framework/cache/`, `storage/framework/sessions/`, `storage/framework/views/` |
 | `docker-compose.yml` exists | `.storage/`, `.composer/` |
 | `.env` exists | `.env`, `.env.*` |
+| `pyproject.toml` exists | `__pycache__/`, `*.pyc`, `*.pyo`, `.pytest_cache/`, `.mypy_cache/`, `.ruff_cache/`, `.tox/`, `.nox/`, `dist/`, `build/`, `*.egg-info/` |
+| `Pipfile` or `Pipfile.lock` exists | `Pipfile.lock` |
+| `poetry.lock` exists | `poetry.lock` |
+| `Cargo.toml` exists | `target/`, `Cargo.lock` (binaries only — keep for libraries) |
+| `go.mod` exists | `go.sum`, `vendor/` (if `go mod vendor` is used) |
+| `Gemfile` exists | `.bundle/`, `vendor/bundle/`, `Gemfile.lock` (apps only — keep for gems) |
+| `next.config.js` / `next.config.mjs` / `next.config.ts` exists | `.next/`, `out/` |
+| `nuxt.config.ts` / `nuxt.config.js` exists | `.nuxt/`, `.output/` |
+| `vite.config.*` exists | `dist/`, `.vite/` |
+| `astro.config.*` exists | `.astro/`, `dist/` |
+| `svelte.config.*` exists | `.svelte-kit/`, `build/` |
+| `tsconfig.json` exists | `*.tsbuildinfo`, `.tscache/` |
+| `.terraform/` exists | `.terraform/`, `*.tfstate`, `*.tfstate.backup`, `.terraform.lock.hcl` (debatable — keep if collaborating) |
 
 ### 2. Find large files polluting the index
 
@@ -62,7 +75,9 @@ For each large file, decide: is this **source code** (keep) or **generated/fixtu
 | `**/.docker/**/*.json` | Generated dashboard/config JSONs (Grafana, etc.) |
 | `.github/workflows/` | CI YAML — large, rarely relevant for code context |
 | `.github/actions/` | CI actions — same reason |
-| `lang/*/validation.php` | Translation files — huge, static, rarely needed |
+| `lang/*/validation.php` (Laravel) | Translation files — huge, static, rarely needed |
+| `locales/**/*.json` (i18next / next-intl / vue-i18n) | Translation bundles — large, mostly static |
+| `messages/**/*.{json,po,properties}` (gettext / Java-style) | Same reason |
 
 ### 3. Find duplicate content
 
@@ -88,21 +103,33 @@ If many exist in specific dirs, add the directory pattern.
 
 ### 6. Whitelist own packages
 
-Check `composer.json` for the project's own organization namespace:
-- Look at `name` field (e.g., `your-org/project-name` → org is `your-org`)
-- Look at `repositories` for private packages from the same org
-- Add negation pattern: `!vendor/{org}/` to keep own packages in the retrieval index
+Detect the project's own organization namespace from whichever manifest is present.
+Add a negation pattern after the broad ignore so the agent can still index
+first-party packages via `codebase-retrieval`:
 
-This ensures the agent can find code in own packages via `codebase-retrieval`,
-while still excluding the thousands of third-party vendor files.
+| Manifest         | Where the org lives                                         | Negation pattern                          |
+|------------------|-------------------------------------------------------------|-------------------------------------------|
+| `composer.json`  | `name` (`vendor/pkg`) + `repositories[]` for private repos  | `!vendor/{org}/`                          |
+| `package.json`   | `name` (`@scope/pkg`) — derive `@scope`                     | `!node_modules/@{scope}/`                 |
+| `pyproject.toml` | `[project].name` + `[tool.poetry].repositories`             | `!**/site-packages/{org}*/` (rare — most Python projects don't vendor) |
+| `go.mod`         | `module example.com/{org}/{repo}` — derive `example.com/{org}` | `!vendor/example.com/{org}/` (only if `go mod vendor` is used) |
+| `Cargo.toml`     | `[package].name` / workspace members                        | Not applicable — Cargo does not vendor by default; skip |
+| `Gemfile`        | Git source URLs pointing to the org                         | `!vendor/bundle/ruby/*/gems/{org-prefix}*/` |
+
+Effect: the broad ignore (`vendor/` / `node_modules/` / `vendor/bundle/`) excludes
+thousands of third-party files; the negation keeps first-party packages indexed.
 
 ### 7. Cross-reference with .gitignore
 
 Read `.gitignore` — most entries there should also be in `.augmentignore`.
-But `.augmentignore` should ALSO include:
-- Lock files (`composer.lock`, `package-lock.json`) — tracked in Git but useless for retrieval.
-- IDE helpers (`_ide_helper.php`) — tracked in Git but huge generated files.
-- OpenAPI specs — tracked but too large for context.
+But `.augmentignore` should ALSO include the following — these are typically
+tracked in Git (so absent from `.gitignore`) yet useless for the retrieval
+index because they are large, generated, or duplicate first-class source:
+
+- Lock files (`composer.lock`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `poetry.lock`, `Pipfile.lock`, `Gemfile.lock`, `go.sum`, `Cargo.lock` for binaries) — tracked but useless for code understanding.
+- IDE helpers and codegen artefacts (`_ide_helper.php`, `_ide_helper_models.php`, `.phpstorm.meta.php`, `*.generated.ts`, `*.gen.go`, `__generated__/`) — tracked but huge.
+- API contracts that are generated, not authored (`openapi.{yaml,json}` produced by codegen, `schema.graphql` generated from resolvers, `swagger.json`) — keep the source, drop the generated.
+- Translation bundles when the project ships them in source control (`lang/`, `locales/`, `i18n/` files larger than ~20 KB).
 
 ### 8. Analyze irrelevant agent skills
 
@@ -112,10 +139,16 @@ Each ignored skill saves ~3 lines of system prompt tokens per request.
 **How:**
 
 1. Read `AGENTS.md` — extract tech stack (framework, language, DB, frontend, infra).
-2. Read `composer.json` — extract `require` and `require-dev` packages.
-3. Read `package.json` (if exists) — extract frontend dependencies.
-4. List all skills: `ls .augment/skills/`
-5. For each skill, decide: **is this relevant to the detected stack?**
+2. Read every package manifest present in the project root — extract dependencies:
+   - `composer.json` → `require`, `require-dev`
+   - `package.json` → `dependencies`, `devDependencies`, `peerDependencies`
+   - `pyproject.toml` → `[project].dependencies`, `[tool.poetry.dependencies]`, `[dependency-groups]`
+   - `requirements*.txt` / `Pipfile` → package list
+   - `go.mod` → `require` blocks
+   - `Cargo.toml` → `[dependencies]`, `[dev-dependencies]`, workspace members
+   - `Gemfile` → `gem` lines
+3. List all skills: `ls .augment/skills/`
+4. For each skill, decide: **is this relevant to the detected stack?**
 
 **Decision matrix — ignore when ALL conditions are true:**
 
@@ -165,7 +198,6 @@ Only consider rules with a `description` frontmatter (auto-loaded by topic match
 
 | Rule | Ignore when... |
 |---|---|
-| `e2e-testing.md` | No Playwright / no E2E tests in project |
 | `lang-files.md` | No `lang/` directory in project |
 
 **Conservative approach:**
@@ -262,9 +294,9 @@ echo "Rules ignored: $rules_count"
 - **Lock files are always ignored** — they're huge and provide zero code insight.
 - **IDE helpers are always ignored** — generated, 20k+ lines, stale quickly.
 - **When in doubt, ignore files** — false positive is easy to fix, false negative wastes tokens silently.
-- **When in doubt, keep skills** — ignoring a needed skill → bad output, keeping an unneeded one just wastes ~3 lines.
+- **When in doubt, keep skills** — ignoring a needed skill causes bad output, keeping an unneeded one just wastes ~3 lines.
 - **Never ignore always-active rules** — only auto-loaded rules (those with `description` frontmatter) may be ignored.
-- **Never ignore meta/agent-system skills** — `agent-docs-writing-writing`, `commands`, `context-create`, `override-management`, `guidelines`, `project-docs`, `roadmap-management`, `naming`, `skill-reviewer`, `file-editor`, `copilot-config`, `copilot-agents-optimization`.
+- **Never ignore meta / agent-system skills** — these are framework-independent and used by every project regardless of stack: `agent-docs-writing`, `agents-md-thin-root`, `check-refs`, `command-routing`, `command-writing`, `compress-memory`, `context-authoring`, `copilot-agents-optimization`, `copilot-config`, `description-assist`, `file-editor`, `guideline-writing`, `learning-to-rule-or-skill`, `lint-skills`, `md-language-check`, `override-management`, `persona-writing`, `project-analyzer`, `project-docs`, `project-health`, `roadmap-writing`, `rule-writing`, `skill-improvement-pipeline`, `skill-management`, `skill-reviewer`, `skill-writing`.
 - **Restore previously ignored skills** when the stack changes (e.g., Vue added to project → restore `vue` skill).
 
 ## Cloud Behavior

package/.agent-src/commands/optimize/rtk.md

@@ -26,21 +26,29 @@ which rtk
 
 Scan the project to determine which CLI tools are used:
 
-| Check | Tool detected |
-|---|---|
-| `composer.json` contains `phpstan` or `larastan` | PHPStan |
-| `composer.json` contains `pestphp/pest` or `phpunit/phpunit` | Pest / PHPUnit |
-| `composer.json` contains `symplify/easy-coding-standard` | ECS |
-| `composer.json` contains `rector/rector` | Rector |
-| `composer.json` contains scripts like `quality:phpstan` | Artisan quality commands |
-| `package.json` contains `playwright` | Playwright |
-| `package.json` contains `vitest` or `jest` | JS test runner |
-| `package.json` contains `biome` or `eslint` | JS linter |
-| `package.json` contains `typescript` | TypeScript compiler |
-| `docker-compose.yml` or `docker-compose.yaml` exists | Docker Compose |
-| `Makefile` exists | Make targets |
-| `Cargo.toml` exists | Rust / Cargo |
-| `go.mod` exists | Go |
+| Detection                                                                                      | Tool                       |
+|------------------------------------------------------------------------------------------------|----------------------------|
+| `composer.json` contains `phpstan` or `larastan`                                               | PHPStan                    |
+| `composer.json` contains `pestphp/pest` or `phpunit/phpunit`                                   | Pest / PHPUnit             |
+| `composer.json` contains `symplify/easy-coding-standard`                                       | ECS                        |
+| `composer.json` contains `rector/rector`                                                       | Rector                     |
+| `composer.json` contains scripts like `quality:phpstan`                                        | Artisan / Composer quality wrappers |
+| `package.json` contains `typescript`                                                            | tsc                        |
+| `package.json` contains `eslint`                                                                | ESLint                     |
+| `package.json` contains `prettier`                                                              | Prettier                   |
+| `package.json` contains `@biomejs/biome`                                                        | Biome                      |
+| `package.json` contains `vitest`                                                                | Vitest                     |
+| `package.json` contains `jest`                                                                  | Jest                       |
+| `package.json` contains `playwright` / `@playwright/test`                                       | Playwright                 |
+| `pyproject.toml` / `requirements*.txt` contains `ruff`                                          | Ruff                       |
+| `pyproject.toml` / `requirements*.txt` contains `mypy` / `pyright`                              | mypy / Pyright             |
+| `pyproject.toml` / `requirements*.txt` contains `pytest`                                        | pytest                     |
+| `.golangci.yml` exists OR `golangci-lint` in `go.mod` tool dependencies                         | golangci-lint              |
+| `go.mod` exists                                                                                 | `go test` / `go vet`       |
+| `Cargo.toml` exists                                                                             | cargo (build / test / clippy / fmt) |
+| `Gemfile` contains `rubocop` / `standard`                                                       | RuboCop / Standard         |
+| `docker-compose.yml` or `docker-compose.yaml` exists                                            | Docker Compose             |
+| `Makefile` exists                                                                               | Make targets               |
 
 ### 3. Read existing filters
 
@@ -77,16 +85,24 @@ max_lines = <appropriate limit>
 
 **Common noise patterns per tool:**
 
-| Tool | Noise to strip |
-|---|---|
-| PHPStan | Progress bars (`\d+/\d+`), separator lines (`━`), notes |
-| Pest/PHPUnit | Empty lines, box-drawing chars (`│`, `⇂`) |
-| ECS/Rector | Separator lines, empty lines |
-| Composer | Download progress, "Loading composer" |
-| Docker Compose | Build context lines, pull progress |
-| npm/yarn | Audit warnings, funding messages |
-| Playwright | Browser download progress |
-| cargo | Compiling lines (keep errors), download progress |
+| Tool           | Noise to strip                                                               |
+|----------------|------------------------------------------------------------------------------|
+| PHPStan        | Progress bars (`\d+/\d+`), separator lines (`━`), notes                      |
+| Pest / PHPUnit | Empty lines, box-drawing chars (`│`, `⇂`)                                    |
+| ECS / Rector   | Separator lines, empty lines                                                 |
+| Composer       | Download progress, "Loading composer"                                        |
+| tsc            | Progress dots, repeated cache-hit notes, watch-mode banners                  |
+| ESLint         | Numeric prefix per line (`123:45`), summary divider, `0 errors / 0 warnings` |
+| Prettier       | File-list output when only formatting (`✔ src/foo.ts`)                       |
+| Vitest / Jest  | Spinner frames, watch banner, coverage summary table when not requested      |
+| Playwright     | Browser launch banner, retry notices, trace-file paths repeated per run      |
+| Ruff           | Progress (`Checking N files`), repeated file headers in `--watch`            |
+| mypy / Pyright | `Daemon running` banners, success summary repeated per file                  |
+| golangci-lint  | Progress (`linters`), divider lines between linters                          |
+| `go test`      | `=== RUN` / `--- PASS` per sub-test (suppress in passing runs)               |
+| Cargo          | `   Compiling …` lines for dependencies, `Finished release` banner           |
+| npm / yarn     | Audit warnings, funding messages                                             |
+| Docker Compose | Build-context lines, pull progress                                           |
 
 ### 5. Write the filters file
 
@@ -114,11 +130,21 @@ Read `verbosity.post_action_reports` from `.agent-settings.yml` (default
 - `full` → multi-line summary table:
 
   ```
-  | # | Filter | Match | Max Lines |
-  |---|---|---|---|
-  | 1 | phpstan | phpstan\|quality:phpstan\|vendor/bin/phpstan | 80 |
-  | 2 | pest | pest\|phpunit\|artisan test | 60 |
-  | ... | ... | ... | ... |
+  | #   | Filter       | Match                                                         | Max  |
+  |-----|--------------|---------------------------------------------------------------|------|
+  | 1   | phpstan      | phpstan\|quality:phpstan\|vendor/bin/phpstan                  | 80   |
+  | 2   | pest         | pest\|phpunit\|artisan test                                   | 60   |
+  | 3   | tsc          | tsc\|tsc --noEmit                                             | 60   |
+  | 4   | eslint       | eslint\|next lint                                             | 50   |
+  | 5   | vitest       | vitest\|jest                                                  | 50   |
+  | 6   | playwright   | playwright\|@playwright/test                                  | 40   |
+  | 7   | ruff         | ruff check\|ruff format                                       | 60   |
+  | 8   | mypy         | mypy\|pyright                                                 | 50   |
+  | 9   | pytest       | pytest\|python -m pytest                                      | 50   |
+  | 10  | golangci     | golangci-lint\|go vet                                         | 50   |
+  | 11  | gotest       | go test                                                       | 40   |
+  | 12  | cargo        | cargo build\|cargo check\|cargo clippy\|cargo test\|cargo fmt | 50   |
+  | ... | ...          | (add per project as the toolchain grows)                      | ...  |
   ```
 
 ### Rules

package/.agent-src/commands/package-test.md

@@ -1,7 +1,7 @@
 ---
 name: package-test
 tier: 2
-skills: [composer, npm]
+skills: [composer, npm, python-packages, go-modules, cargo-packages]
 description: /package-test
 disable-model-invocation: true
 suggestion:
@@ -17,15 +17,28 @@ Test a local package in the current project by linking it via Composer or npm.
 
 ### 1. Detect or ask for package manager
 
-Check the project root for `composer.json` and `package.json`.
+Check the project root for a package manifest. Supported (try in this order, take the first match — the project can have several):
 
-- **Both exist** → ask:
+| Manifest                                                          | Ecosystem        | Link mechanism                                           |
+|-------------------------------------------------------------------|------------------|----------------------------------------------------------|
+| `composer.json`                                                   | PHP / Composer   | `repositories[].type: path` + `composer require @dev`    |
+| `package.json`                                                    | JS / TS / Node   | `npm link` / `pnpm link` / `yarn link` / `file:../path`  |
+| `pyproject.toml`, `setup.py`, or `setup.cfg`                      | Python           | `pip install -e <path>` / `uv pip install -e <path>` / `poetry add --editable <path>` |
+| `go.mod`                                                          | Go               | `go mod edit -replace example.com/pkg=<path>`            |
+| `Cargo.toml`                                                      | Rust             | `cargo add --path <path>` or `[patch.crates-io]` block   |
+| `Gemfile`                                                         | Ruby             | `bundle config local.<gem> <path>`                       |
+
+- **Multiple manifests exist** → ask:
 
 ```
 Which package manager?
 
 1. Composer (PHP)
-2. npm (JavaScript/TypeScript)
+2. npm / pnpm / yarn (JavaScript / TypeScript)
+3. Python (pip / poetry / uv)
+4. Go modules
+5. Cargo (Rust)
+6. Bundler (Ruby)
 ```
 
 - **Only one exists** → use that one automatically, confirm:
@@ -37,7 +50,7 @@ Detected: {manager}. Proceeding.
 - **Neither exists** → abort:
 
 ```
-❌  No composer.json or package.json found in project root. Cannot link a local package.
+❌  No supported package manifest (composer.json / package.json / pyproject.toml / setup.py / go.mod / Cargo.toml / Gemfile) found in project root. Cannot link a local package.
 ```
 
 ### 2. Ask for the local package path
@@ -51,15 +64,19 @@ Example: ../my-package or /Users/me/projects/my-package
 
 Validate:
 - Path exists and is a directory
-- For Composer: directory contains `composer.json`
-- For npm: directory contains `package.json`
+- The directory contains a manifest matching the ecosystem chosen in the detection step (`composer.json`, `package.json`, `pyproject.toml` / `setup.py`, `go.mod`, `Cargo.toml`, or `Gemfile`)
+- If the directory has multiple manifests, ask the user which one to link (rare but possible — e.g. a Composer package that also ships a JS bundle)
 
 If invalid, show error and ask again.
 
 ### 3. Read the package name
 
-- **Composer:** Read `name` from the package's `composer.json`
-- **npm:** Read `name` from the package's `package.json`
+- **Composer:** Read `name` from the package's `composer.json` (e.g. `vendor/package`)
+- **npm / pnpm / yarn:** Read `name` from the package's `package.json` (e.g. `@scope/package`)
+- **Python:** Read `[project].name` from `pyproject.toml`, or `setup(name=...)` from `setup.py`
+- **Go:** Read `module` from `go.mod` (e.g. `example.com/vendor/package`)
+- **Rust:** Read `[package].name` from `Cargo.toml`
+- **Ruby:** Read the gem name from the `*.gemspec` file in the package directory
 
 Confirm:
 
@@ -118,10 +135,69 @@ Or for workspaces, add to `package.json`:
 
 Then: `npm install`
 
+#### Python
+
+Editable install (preferred):
+
+```bash
+pip install -e {package-path}
+# or, if the project uses uv:
+uv pip install -e {package-path}
+# or, if the project uses poetry:
+cd {project-root} && poetry add --editable {package-path}
+```
+
+Re-sync after upstream changes:
+
+```bash
+pip install -e {package-path} --force-reinstall --no-deps
+```
+
+#### Go
+
+Edit `go.mod` in the **project** root to add a `replace` directive:
+
+```
+replace example.com/vendor/package => ../my-package
+```
+
+Then run `go mod tidy` so the lockfile picks up the local path. Remove the `replace` line before publishing.
+
+#### Rust / Cargo
+
+Add as a path dependency in the **project's** `Cargo.toml`:
+
+```toml
+[dependencies]
+vendor_package = { path = "../my-package" }
+```
+
+Or, to override a published crate without rewriting the dependency line, use `[patch.crates-io]`:
+
+```toml
+[patch.crates-io]
+vendor_package = { path = "../my-package" }
+```
+
+Run `cargo build` to re-resolve.
+
+#### Ruby / Bundler
+
+```bash
+bundle config local.{gem-name} {package-path}
+bundle install
+```
+
+Remove with `bundle config --delete local.{gem-name}`.
+
 ### 5. Verify
 
 - **Composer:** Check that `vendor/{package-name}` is a symlink → the local path
-- **npm:** Check that `node_modules/{package-name}` is a symlink → the local path
+- **npm / pnpm / yarn:** Check that `node_modules/{package-name}` is a symlink → the local path
+- **Python:** `pip show {package-name}` → `Location` should point inside `{package-path}` (editable installs show the source dir, not site-packages)
+- **Go:** `go list -m {module-path}` → resolved path should match the `replace` target
+- **Rust:** `cargo metadata --format-version 1 | jq '.packages[] | select(.name=="{package-name}") | .manifest_path'` → should point inside `{package-path}`
+- **Ruby:** `bundle config get local.{gem-name}` → should return the linked path
 
 Report result:
 

package/.agent-src/commands/quality-fix.md

@@ -6,8 +6,8 @@ description: Run quality pipeline (PHP and/or JS/TS) and fix all errors — auto
 disable-model-invocation: true
 suggestion:
   eligible: true
-  trigger_description: "fix the quality errors, run PHPStan and fix issues, fix code style"
-  trigger_context: "PHPStan/Rector/ECS output in recent tool results"
+  trigger_description: "fix the quality errors — run the project's type-checker / linter / formatter and resolve every issue (PHPStan / tsc / mypy / golangci-lint / clippy / …)"
+  trigger_context: "type-checker / linter / formatter output in recent tool results (PHPStan, Rector, ECS, tsc, eslint, prettier, ruff, mypy, golangci-lint, clippy)"
 ---
 
 # quality-fix
@@ -33,34 +33,56 @@ git diff --name-only origin/{default}..HEAD
 ### Prerequisites
 
 - All commands run **inside the PHP container** (e.g. `docker compose exec -T <service> ...`).
-- Detect the project type:
-  - Project ships a `quality:*` wrapper (Artisan or Composer script) → prefer `php artisan quality:phpstan` / `php artisan quality:rector --fix`
-  - `phpstan/phpstan` installed → `vendor/bin/phpstan analyse`
-  - `rector/rector` installed → `vendor/bin/rector process`
-  - `symplify/easy-coding-standard` installed → `vendor/bin/ecs check --fix`
-
-### Step 1: PHPStan — fix all errors
-
-1. Run PHPStan and capture the full output.
+- Detect the project's quality toolchain **before** doing anything else. Pick the first match:
+  1. Project ships a wrapper script — prefer the wrapper over invoking tools directly:
+     - PHP: `php artisan quality:*` (Laravel), `composer run quality`, `composer run lint`
+     - JS / TS: `npm run lint`, `npm run typecheck`, `pnpm lint`, `pnpm typecheck`, `yarn lint`, `yarn typecheck`
+     - Python: `make lint`, `nox -s lint`, `tox -e lint`
+     - Polyglot: `Taskfile.yml`, `Makefile`, or `justfile` with a `quality` / `lint` / `check` target
+  2. No wrapper — invoke tools directly based on which are installed:
+     - PHP: `vendor/bin/phpstan analyse`, `vendor/bin/rector process`, `vendor/bin/ecs check --fix`
+     - JS / TS: `npx tsc --noEmit`, `npx eslint . --fix`, `npx prettier . --write`, `npx biome check --apply`
+     - Python: `ruff check . --fix`, `ruff format .`, `mypy .`, `pyright`
+     - Go: `golangci-lint run --fix`, `go vet ./...`, `gofmt -w .`
+     - Rust: `cargo clippy --fix --allow-dirty`, `cargo fmt`
+  3. Nothing detected → ask the user which command runs the project's quality pipeline. Do not invent one.
+
+### Step 1: Type-checker — fix all errors
+
+Run the project's type-checker (chosen in the detection step):
+- PHP → PHPStan
+- JS / TS → `tsc --noEmit`
+- Python → mypy / pyright
+- Go → `go vet` + `go build`
+- Rust → `cargo check`
+
+1. Run the type-checker and capture the full output.
 2. For each error, **fix it in code**. Resolve the root cause.
-3. **Do NOT add errors to the baseline or phpstan.neon ignore lists.**
-4. If truly impossible (confirmed false positive), use inline ignore with reason.
-5. After fixing, run PHPStan again.
+3. **Do NOT add errors to the baseline or ignore list** (`phpstan-baseline.neon`, `tsconfig.json` `exclude`, `# type: ignore`, `// @ts-ignore`, `#[allow(...)]`, `//nolint`).
+4. If truly impossible (confirmed false positive), use the language-native inline ignore with a one-line reason: `@phpstan-ignore`, `// @ts-expect-error: <reason>`, `# type: ignore[<code>]  # <reason>`, `//nolint:<linter> // <reason>`, `#[allow(<lint>)] // <reason>`.
+5. After fixing, re-run the type-checker.
 6. Repeat until **0 errors**.
 
-### Step 2: Rector — apply automated refactoring
+### Step 2: Auto-fixer / refactoring tool — apply transforms
+
+Run the project's auto-fixer / refactoring tool (skip the step entirely if the project does not ship one):
+- PHP → `vendor/bin/rector process`
+- JS / TS → `npx eslint . --fix` (rule auto-fixes), `npx biome check --apply-unsafe` (safe transforms only)
+- Python → `ruff check . --fix` (lint auto-fixes), `ruff check . --fix --unsafe-fixes` (broader)
+- Go → `golangci-lint run --fix`, `gofmt -w .`, `goimports -w .`
+- Rust → `cargo clippy --fix --allow-dirty --allow-staged`, `cargo fmt`
 
-1. Run Rector with the fix flag.
-2. Review what Rector changed — it may introduce new PHPStan errors.
-3. Run Rector again to verify no further changes are applied.
-4. Repeat until Rector produces no more changes.
+1. Run the auto-fixer with the apply / fix flag.
+2. Review the diff — auto-fixes may introduce new type-checker errors or change semantics on edge cases.
+3. Re-run the auto-fixer to verify it produces no further changes.
+4. Repeat until the auto-fixer is idempotent.
 
-### Step 3: Final PHPStan verification
+### Step 3: Final type-checker verification
 
-1. Run PHPStan one more time.
-2. If new errors appeared (e.g. from Rector changes), fix them as in Step 1.
+1. Run the type-checker (from Step 1) one more time.
+2. If new errors appeared (e.g. from auto-fixer changes), fix them as in Step 1.
 3. If fixes were needed, go back to Step 2.
-4. Done when PHPStan reports **0 errors** and Rector has **no changes**.
+4. Done when the type-checker reports **0 errors** **and** the auto-fixer is idempotent. Also run the formatter once at the very end (`vendor/bin/ecs check --fix` / `prettier --write` / `ruff format` / `cargo fmt`) to normalise whitespace.
 
 ---
 
@@ -105,7 +127,7 @@ git diff --name-only origin/{default}..HEAD
 ## Rules
 
 - **Do NOT commit or push.** Only apply local changes.
-- **Do NOT modify baseline files** (`phpstan-baseline.neon`) or config files (`biome.json`, `tsconfig.json`).
-- **Do NOT add entries to `ignoreErrors`** in `phpstan.neon`.
-- Inline ignores (`@phpstan-ignore`, `@ts-expect-error`, `biome-ignore`) are a last resort.
-- Run `php -l` on modified PHP files if you made significant structural changes.
+- **Do NOT modify baseline files** (`phpstan-baseline.neon`, `tsconfig.json` `exclude`, `.mypy.ini` ignore list, `.eslintrc` `ignorePatterns`, `clippy.toml` `allow` list).
+- **Do NOT widen ignore lists** in the config (`ignoreErrors`, `exclude`, `# type: ignore` blanket, `eslint-disable` file-wide).
+- Inline ignores (`@phpstan-ignore`, `@ts-expect-error`, `# type: ignore[code]`, `biome-ignore`, `eslint-disable-next-line`, `//nolint:`, `#[allow(...)]`) are a last resort and must carry a one-line reason.
+- After significant structural changes, run a language-level syntax check (`php -l <file>`, `node --check <file>`, `python -m py_compile <file>`, `go build ./...`, `cargo check`) before claiming the file is fixed.

package/.agent-src/commands/update-form-request-messages.md

@@ -1,8 +1,9 @@
 ---
 name: update-form-request-messages
 tier: 2
+framework: laravel
 skills: [laravel-validation]
-description: Sync the messages() method of a FormRequest class — add missing entries, link them to language keys, and clean up stale ones
+description: "Sync the messages() method of a FormRequest class — add missing entries, link them to language keys, and clean up stale ones."
 disable-model-invocation: true
 suggestion:
   eligible: true