@event4u/agent-config 2.25.0 → 3.0.0

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

@@ -3,6 +3,18 @@ name: openapi
 description: "Use when documenting APIs — OpenAPI/Swagger, PHP attributes, Redocly validation, versioned specs — even when the user just says 'document this endpoint' without naming OpenAPI."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # openapi
@@ -13,7 +25,7 @@ Use this skill when adding or updating API documentation, writing OpenAPI annota
 
 ## Procedure: Add OpenAPI documentation
 
-1. **Gather context** — read `agents/docs/controller.md` for OpenAPI patterns, `agents/contexts/api-versioning.md` for versioning, and check 2-3 existing controllers for annotation style.
+1. **Gather context** — read `agents/reference/docs/controller.md` for OpenAPI patterns, `agents/settings/contexts/api-versioning.md` for versioning, and check 2-3 existing controllers for annotation style.
 2. **Detect tooling** — check `composer.json` for `l5-swagger` or `laravel-openapi`, look for `@OA\` vs `#[OA\` syntax in existing controllers, find the config file.
 3. **Write annotations** — add `#[OA\...]` attributes to the controller method. Include path, summary, tags, all parameters, and all response codes (200, 401, 403, 404, 422).
 4. **Define schemas** — create or reuse `#[OA\Schema]` for request/response types. Use `$ref` for shared types.

package/.agent-src/skills/org-design/SKILL.md

@@ -6,6 +6,18 @@ tier: senior
 source: package
 domain: process
 context_spine: [org-stage, product, customer-segment]
+workspaces:
+  - ops
+packs:
+  - ops-people
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # org-design

package/.agent-src/skills/override-management/SKILL.md

@@ -7,6 +7,18 @@ execution:
   type: assisted
   handler: internal
   allowed_tools: []
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Override Skill

package/.agent-src/skills/perf-feedback-craft/SKILL.md

@@ -6,6 +6,18 @@ tier: senior
 source: package
 domain: process
 context_spine: [org-stage, customer-segment, product]
+workspaces:
+  - ops
+packs:
+  - ops-people
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # perf-feedback-craft

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

@@ -3,6 +3,18 @@ name: performance
 description: "Use when optimizing application performance — caching strategies, eager loading, query optimization, Redis patterns, or background job design."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # performance

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

@@ -3,6 +3,18 @@ name: performance-analysis
 description: "ONLY when user explicitly requests: performance audit, bottleneck analysis, or N+1 query detection. NOT for regular feature work."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # performance-analysis

package/.agent-src/skills/persona-writing/SKILL.md

@@ -3,6 +3,18 @@ name: persona-writing
 description: "Use when creating or editing a persona in .agent-src.uncompressed/personas/ — voice / focus / unique questions / output expectations — even when the user just says 'add a reviewer voice for X'."
 source: package
 domain: process
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 <!-- cloud_safe: degrade -->

package/.agent-src/skills/pest-testing/SKILL.md

@@ -3,6 +3,18 @@ name: pest-testing
 description: "Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions."
 source: package
 domain: quality
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # pest-testing
@@ -283,6 +295,24 @@ When generating Pest tests:
 - keep tests readable, isolated, and maintainable
 
 
+### Filter Pest output
+
+When triaging a verbose run, narrow the output with `--filter` (Pest)
+plus targeted `grep`/`rg` instead of re-running the whole suite or
+echoing all logs:
+
+```bash
+# Only run failing tests in one file
+vendor/bin/pest tests/Feature/InvoiceTest.php --filter='creates invoice'
+
+# Scan the test log for failures only
+rg --color=never '^FAIL|Tests:' storage/logs/pest.log
+
+# Inspect JSON output from data-driven tests
+vendor/bin/pest --log-junit=pest.xml && rg '<failure' pest.xml
+```
+
+
 ## Output format
 
 1. Pest test file with descriptive test names and clear assertions

package/.agent-src/skills/php-coder/SKILL.md

@@ -3,6 +3,18 @@ name: php-coder
 description: "Writes or edits PHP code — controllers, classes, type hints, SOLID refactors, modern idioms — even without naming PHP. NOT for writing tests (use pest-testing) or explaining PHP concepts."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - php
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # coder

package/.agent-src/skills/php-debugging/SKILL.md

@@ -3,6 +3,18 @@ name: php-debugging
 description: "Use when debugging PHP with Xdebug — breakpoints, step-through, dual-container setup, IDE configuration, header-based routing — even when the user just says 'why does this blow up on request X'."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - php
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # php-debugging
@@ -130,6 +142,20 @@ make console-xdebug    # Enter Xdebug container
 php artisan your:command   # Xdebug connects to IDE automatically
 ```
 
+### Verifying CLI fixes
+
+After a fix, verify the command without re-attaching the debugger:
+
+```bash
+# Run the command, capture exit code + command output
+php artisan your:command; echo "exit code: $?"
+
+# Pest CLI assertion — expectsOutput / artisan test
+vendor/bin/pest --filter='ProcessInvoicesCommand'
+```
+
+Assert on the **exit code** and **command output**; never trust "looks fine" from breakpoint inspection alone.
+
 ## Troubleshooting
 
 | Problem | Solution |
@@ -151,6 +177,20 @@ make rebuild-php-xdebug   # Rebuild Xdebug container only
 make rebuild-php-all      # Rebuild both PHP containers
 ```
 
+### Filter noisy debug output
+
+`tail -f /tmp/xdebug.log` and `docker logs` produce far too much
+data to read line-by-line. Filter with `rg`/`grep` for the relevant
+event:
+
+```bash
+# Only connection / breakpoint events
+rg --color=never 'Connect|Step|breakpoint' /tmp/xdebug.log
+
+# Only this request's frames in the laravel log
+docker compose logs php-xdebug | rg --color=never "$REQUEST_ID"
+```
+
 ## What NOT to do
 
 - Do not leave Xdebug enabled in production containers.

package/.agent-src/skills/php-service/SKILL.md

@@ -3,6 +3,18 @@ name: php-service
 description: "Use when the user says 'create service', 'new service class', or needs a PHP service following SOLID principles with proper DI and repository usage."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - php
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # php-service
@@ -13,7 +25,7 @@ Use when creating a new service, extracting business logic from a controller, or
 
 Do NOT use when:
 - Controllers (use `laravel` skill)
-- DTOs (use `dto-creator` skill)
+- DTOs (use `laravel-dto` skill for Laravel/PHP; framework-native skill for other stacks)
 - Models (use `eloquent` skill)
 
 ## When to create a service
@@ -39,7 +51,7 @@ Do NOT use when:
 1. Location: `app/Services/{Domain}/` or `app/Modules/{Module}/App/Services/`.
 2. `declare(strict_types=1)`, proper namespace.
 3. Constructor inject dependencies (repositories, other services).
-4. Max 4 constructor deps — if more, split the service.
+4. Max 4 constructor dependencies — if more, split the service.
 
 ### Step 2: Implement methods
 
@@ -70,7 +82,7 @@ public function __invoke(
 
 - Run PHPStan on the service — must pass at level 9.
 - Verify single responsibility: service does one thing, no mixed concerns.
-- Confirm all deps are constructor-injected (no `app()` or facades in service).
+- Confirm all dependencies are constructor-injected (no `app()` or facades in service).
 - Run affected tests — must pass.
 
 ## Output format

package/.agent-src/skills/pipeline-strategy/SKILL.md

@@ -7,8 +7,18 @@ source: package
 domain: product
 context_spine: [product, customer-segment, channel-stage]
 recommended_for_user_types: [gtm]
-
-
+workspaces:
+  - gtm
+packs:
+  - gtm-sales
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # pipeline-strategy

package/.agent-src/skills/pixar-storyteller/SKILL.md

@@ -3,6 +3,18 @@ name: pixar-storyteller
 description: "Use when turning an idea into a Pixar-style animation prompt — character sheet, scene, image, video — anchored in emotional beat, want, obstacle. Triggers 'Pixar prompt', 'animated scene'."
 source: package
 domain: product
+workspaces:
+  - small-business
+packs:
+  - ai-video
+lifecycle: experimental
+trust:
+  level: experimental
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # pixar-storyteller
@@ -37,7 +49,7 @@ Do NOT use when:
 ### Step 0: Inspect
 
 1. Confirm the input is an animated / stylized beat.
-2. If `character.json` exists under `agents/ai-video/<project>/characters/`,
+2. If `character.json` exists under `agents/reference/ai-video/<project>/characters/`,
    read identity tokens — reused verbatim in CHARACTER SHEET.
 3. Read the beat once. Name the *want* and the *obstacle* in one
    sentence each before drafting.
@@ -111,10 +123,10 @@ Any "no" → revise that block.
 
 The Pixar-storyteller skill anchors prompts to named films and studios by design — the policy surface is the largest in the video cluster:
 
-- [`agents/policies/media/style.md`](../../../agents/policies/media/style.md) — naming a film + year as the *primary* anchor crosses the "in the style of [STUDIO]" trigger; surface and refuse without a transformative-intent rationale.
-- [`agents/policies/media/likeness.md`](../../../agents/policies/media/likeness.md) — when a beat references a named animator's signature character (real-person extension of style).
-- [`agents/policies/media/public-figures.md`](../../../agents/policies/media/public-figures.md) — when the storyteller's character is a recognised public figure rendered in Pixar shape.
-- [`agents/policies/media/disclosure.md`](../../../agents/policies/media/disclosure.md) — every Pixar-style output ships with the AI-generation disclosure; parody / commentary cases are flagged for human review.
+- [`agents/settings/policies/media/style.md`](../../../agents/settings/policies/media/style.md) — naming a film + year as the *primary* anchor crosses the "in the style of [STUDIO]" trigger; surface and refuse without a transformative-intent rationale.
+- [`agents/settings/policies/media/likeness.md`](../../../agents/settings/policies/media/likeness.md) — when a beat references a named animator's signature character (real-person extension of style).
+- [`agents/settings/policies/media/public-figures.md`](../../../agents/settings/policies/media/public-figures.md) — when the storyteller's character is a recognised public figure rendered in Pixar shape.
+- [`agents/settings/policies/media/disclosure.md`](../../../agents/settings/policies/media/disclosure.md) — every Pixar-style output ships with the AI-generation disclosure; parody / commentary cases are flagged for human review.
 
 Refuse-and-surface when style ⇒ primary signature, not one influence among several.
 

package/.agent-src/skills/playwright-architect/SKILL.md

@@ -6,8 +6,18 @@ personas:
 source: package
 domain: quality
 recommended_for_user_types: [developer]
-
-
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # playwright-architect

package/.agent-src/skills/playwright-testing/SKILL.md

@@ -3,6 +3,18 @@ name: playwright-testing
 description: "Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns."
 source: package
 domain: quality
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # playwright-testing
@@ -18,7 +30,6 @@ Use this skill when:
 - Configuring Playwright for CI/CD
 
 **Guideline:** `../../../docs/guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
-**Rule:** `.augment/rules/e2e-testing.md` — constraints enforced during E2E test work.
 **Mobile:** for native iOS/Android or React Native E2E, do NOT reuse Playwright — see the `mobile-e2e-strategy` skill for framework selection.
 
 ## Procedure: Write Playwright tests
@@ -164,6 +175,22 @@ npx playwright show-report
 npx playwright test -g "should login"
 ```
 
+### Filter noisy Playwright output
+
+Use `--grep`, `--reporter=json`, plus `jq`/`rg` to keep diagnosis scoped:
+
+```bash
+# Targeted run — only matching specs
+npx playwright test --grep '@smoke'
+
+# JSON report, narrowed to failures via jq
+npx playwright test --reporter=json > pw.json
+jq '.suites[].specs[] | select(.tests[].results[].status=="failed")' pw.json
+
+# Scan trace logs for one selector
+rg --color=never 'getByRole.*Submit' test-results/
+```
+
 ## Avoiding flaky tests
 
 | Problem | Solution |

package/.agent-src/skills/po-discovery/SKILL.md

@@ -6,6 +6,18 @@ personas:
   - stakeholder
 source: package
 domain: product
+workspaces:
+  - product
+packs:
+  - product-basic
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # po-discovery

package/.agent-src/skills/positioning-strategy/SKILL.md

@@ -6,6 +6,18 @@ tier: senior
 source: package
 domain: product
 context_spine: [product, customer-segment]
+workspaces:
+  - gtm
+packs:
+  - gtm-marketing
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # positioning-strategy

package/.agent-src/skills/privacy-review/SKILL.md

@@ -7,8 +7,18 @@ source: package
 domain: process
 context_spine: [regulatory-regime, customer-segment, product]
 recommended_for_user_types: [ops, finance, creator]
-
-
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # privacy-review

package/.agent-src/skills/project-analysis-core/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-core
 description: "Raw discovery primitives — project discovery, version resolution, docs loading, architecture mapping, execution flow. Called by `universal-project-analysis`. Single-pass scan → `project-analyzer`."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analysis-core

package/.agent-src/skills/project-analysis-hypothesis-driven/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-hypothesis-driven
 description: "Use when a bug has multiple plausible causes across layers — competing hypotheses, validation loops, evidence-based conclusions — even when the user just says 'why is this happening?'."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # project-analysis-hypothesis-driven

package/.agent-src/skills/project-analysis-laravel/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-laravel
 description: "Use for deep Laravel project analysis: boot flow, request lifecycle, container usage, Eloquent/data flow, async systems, and Laravel-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-laravel

package/.agent-src/skills/project-analysis-nextjs/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-nextjs
 description: "Use for deep Next.js analysis: server vs client boundaries, routing, data fetching, caching, rendering modes, and hydration/runtime issues."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - nextjs
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-nextjs

package/.agent-src/skills/project-analysis-node-express/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-node-express
 description: "Use for deep Node.js / Express project analysis: boot flow, middleware order, async behavior, data layer, auth/security, and Node-specific runtime failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - typescript
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-node-express

package/.agent-src/skills/project-analysis-react/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-react
 description: "Use for deep React analysis: component tree, state flow, props flow, hooks usage, rendering behavior, and React-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - react
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-react

package/.agent-src/skills/project-analysis-symfony/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-symfony
 description: "Use for deep Symfony project analysis: kernel/bootstrap, container wiring, routing/request flow, Doctrine, security, Messenger, and Symfony-specific failure patterns."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - symfony
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-symfony

package/.agent-src/skills/project-analysis-zend-laminas/SKILL.md

@@ -3,6 +3,18 @@ name: project-analysis-zend-laminas
 description: "Use for deep Zend Framework or Laminas project analysis: bootstrap, config merge order, service manager, MVC flow, data layer, and migration-specific risks."
 source: package
 domain: discovery
+workspaces:
+  - engineering
+packs:
+  - php
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # project-analysis-zend-laminas