@event4u/agent-config 2.25.0 → 3.0.0

package/.agent-src/skills/laravel-api-endpoint/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: laravel-api-endpoint
+description: "Use when creating a new Laravel API endpoint — Controller, FormRequest, Resource, route, Policy, OpenAPI annotations — versioned route layout, single-action `__invoke` controllers."
+source: package
+domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
+---
+
+# laravel-api-endpoint
+
+## When to use
+
+Use this skill when the project is **Laravel** (detected via `artisan` + `composer.json` with `laravel/framework`) and the user asks to create a new API endpoint, REST route, or controller action.
+
+Routed in from [`api-endpoint`](../api-endpoint/SKILL.md) once the stack is detected as Laravel.
+
+Do NOT use when:
+- Modifying existing endpoints — use the code-refactoring skill.
+- API design decisions — use [`api-design`](../api-design/SKILL.md).
+- The project is Symfony / Next.js / FastAPI / etc. — go back to [`api-endpoint`](../api-endpoint/SKILL.md) and pick the right carve-out.
+
+## Procedure: Create a Laravel API endpoint
+
+1. **Read project docs** — Check `./agents/` and `AGENTS.md` for controller conventions, resource patterns, routing.
+2. **Create route** — Add to the correct `routes/api.php` or module route file (`routes/api/v{N}/{domain}.php`).
+3. **Create controller** — Single-action invokable controller, thin, delegate logic to a service.
+4. **Create FormRequest** — Validate all input at the boundary; authorize via Policy in `authorize()`.
+5. **Create Resource** — Transform model output via API Resource (never raw arrays / models / `response()->json()`).
+6. **Create Policy** — If authorization is needed and no Policy exists yet.
+7. **Verify** — Run PHPStan, run tests, confirm response shape matches conventions.
+
+## What to generate
+
+1. **Controller** — Single Action (invokable). Read `agents/reference/docs/controller.md` and `../../../docs/guidelines/php/controllers.md`.
+2. **FormRequest** — Validation rules, `authorize()` via policies. Read `../../../docs/guidelines/php/validations.md`.
+3. **Resource** — JSON response transformation. Read `agents/reference/docs/api-resources.md`.
+4. **Route** — Add to the correct versioned route file.
+5. **Policy** — If authorization is needed.
+6. **Filter classes** — If it's a list endpoint with filtering. Read `agents/reference/docs/query-filter.md` (if it exists).
+
+## Conventions
+
+- Controllers are thin — delegate to Services.
+- **Every controller MUST return an API Resource** — never raw arrays, models, or `response()->json()`.
+- Controllers type-hint the return value as the Resource class (e.g. `): ProjectResource`).
+- Use `Resource::make()` for single items, `Resource::collection()` for lists.
+- Use method injection on `__invoke()` for new controllers.
+- Use DTOs for data transfer between layers.
+
+## Show endpoint example
+
+```php
+declare(strict_types=1);
+
+namespace App\Http\Controllers\v1\Project;
+
+use App\Http\Controllers\Controller;
+use App\Http\Requests\v1\Projects\ShowProjectRequest;
+use App\Http\Resources\v1\Project\ProjectResource;
+use App\Models\ExternalCustomerDatabase\Project\Project;
+use App\OpenApi\Schema\Request\ShowResourceRequestSchema;
+use App\OpenApi\Schema\Response\ResourceNotFoundResponse;
+use App\OpenApi\Schema\Response\ShowResourceResponseSchema;
+
+class ShowProjectController extends Controller
+{
+    #[ShowResourceRequestSchema(path: '/projects/{id}', version: '1', resource: ProjectResource::class)]
+    #[ShowResourceResponseSchema(ProjectResource::class, wrapInDataObject: false)]
+    #[ResourceNotFoundResponse(ProjectResource::class)]
+    public function __invoke(ShowProjectRequest $request, Project $project): ProjectResource
+    {
+        return ProjectResource::make($project);
+    }
+}
+```
+
+## Create endpoint with service injection
+
+```php
+class CreateCustomerController extends Controller
+{
+    #[CreateCustomerRequestSchema(path: '/customers', version: '1', resource: CustomerResource::class)]
+    #[CreateResourceResponseSchema(resource: CreatedCustomerResource::class, wrapInDataObject: false)]
+    #[ValidationErrorResponse]
+    public function __invoke(
+        CreateCustomerRequest $request,
+        CustomerModelService $customerService,
+    ): CustomerResource {
+        $result = $customerService->create(CreateCustomerDTO::fromRequest($request));
+
+        return CreatedCustomerResource::make($result);
+    }
+}
+```
+
+## FormRequest example
+
+```php
+declare(strict_types=1);
+
+namespace App\Http\Requests\v1\Projects;
+
+use Illuminate\Foundation\Http\FormRequest;
+
+class ShowProjectRequest extends FormRequest
+{
+    public function authorize(): bool
+    {
+        return $this->user()->can('view', $this->route('project'));
+    }
+
+    /** @return array<string, mixed> */
+    public function rules(): array
+    {
+        return [];
+    }
+}
+```
+
+## List endpoint with CollectionFormRequest
+
+For list endpoints, extend `CollectionFormRequest` which provides `perPage`, `page`, and `orderBy` rules:
+
+```php
+use App\Contracts\Http\Requests\CollectionFormRequest;
+
+class ListProjectsRequest extends CollectionFormRequest
+{
+    public string $model = Project::class;
+
+    /** @return array<string, mixed> */
+    public function rules(): array
+    {
+        return [
+            ...parent::rules(),
+            'status' => ['sometimes', 'string'],
+        ];
+    }
+}
+```
+
+## File locations
+
+| Component | Path |
+|---|---|
+| Controller | `app/Http/Controllers/v{N}/{Domain}/{Action}{Entity}Controller.php` |
+| FormRequest | `app/Http/Requests/v{N}/{Domain}/{Action}{Entity}Request.php` |
+| Resource | `app/Http/Resources/v{N}/{Domain}/{Entity}Resource.php` |
+| Route | `routes/api/v{N}/{domain}.php` |
+| Policy | `app/Policies/{Entity}Policy.php` |
+
+## OpenAPI documentation
+
+Controllers use PHP 8 attributes for OpenAPI spec generation from `App\OpenApi\Schema\`:
+
+- `ShowResourceRequestSchema`, `ListResourceRequestSchema`, `CreateResourceRequestSchema`
+- `ShowResourceResponseSchema`, `ListResourceResponseSchema`, `CreateResourceResponseSchema`
+- `ResourceNotFoundResponse`, `ValidationErrorResponse`
+
+## Output format
+
+1. Generated files — controller, route registration, FormRequest, Resource, Policy.
+2. Test file with happy path and validation error cases.
+3. Summary of created files and their locations.
+
+## Gotcha
+
+- Don't forget to register the route — creating the controller without the route is a common miss.
+- Always check if a similar endpoint already exists — duplicates cause confusion.
+- FormRequest validation rules must match the OpenAPI schema — keep them in sync.
+- The model tends to forget the `return` type on Resource `toArray()` methods.
+
+## Do NOT
+
+- Do NOT put business logic in controllers — delegate to services.
+- Do NOT skip FormRequest validation — every controller needs a FormRequest.
+- Do NOT return raw Eloquent models — always use API Resources.
+- Do NOT create routes without proper authorization (Policy in FormRequest or middleware).
+- Do NOT create multi-action controllers — only single-action with `__invoke()`.
+- Do NOT use `response()->json()` — use `Resource::make()`.
+
+## Auto-trigger keywords
+
+- laravel endpoint
+- laravel controller
+- form request
+- API resource
+- laravel api route

package/.agent-src/skills/{dto-creator → laravel-dto}/SKILL.md

@@ -1,11 +1,24 @@
 ---
-name: dto-creator
-description: "Use when the user says "create a DTO", "new data transfer object", or needs to convert request/response data into a typed PHP class. Creates DTOs with SimpleDto base class and attribute mapping."
+name: laravel-dto
+description: "Use when creating a Laravel/PHP DTO with the SimpleDto base class and attribute mapping. For DTOs in other stacks, use the stack-native skill (TypeScript, Python, Rust, Go)."
 source: package
 domain: engineering
+framework: laravel
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
-# dto-creator
+# laravel-dto
 
 ## When to use
 
@@ -13,7 +26,7 @@ Use this skill when creating a new DTO for data transfer between layers (DB ↔
 
 ## Procedure: Create a DTO
 
-1. **Read the project's DTO docs** — check `agents/docs/dto.md` (if it exists) for project-specific conventions.
+1. **Read the project's DTO docs** — check `agents/reference/docs/dto.md` (if it exists) for project-specific conventions.
 2. **Check the base class** — search for the DTO base class in the project (e.g., `SimpleDto`, `LiteDto`, or a custom base).
    Check `composer.json` for DTO-related packages.
 3. **Check existing DTOs** — look at neighboring DTOs in the same directory to match the style.
@@ -79,7 +92,7 @@ class MyModelDto extends SimpleDto
 The DTO pattern varies by project:
 
 - **Projects with a DTO package**: Use the package's base class with attribute mapping.
-  Read `agents/docs/dto.md` for full details (if it exists).
+  Read `agents/reference/docs/dto.md` for full details (if it exists).
 - **Projects without a DTO package**: Check existing DTOs for the local pattern.
   Some projects use plain `readonly` classes, others have custom base classes.
 
@@ -102,7 +115,7 @@ Always check `composer.json` for DTO-related packages before choosing the approa
 
 - DTOs must extend `SimpleDto` — don't create plain PHP classes as DTOs.
 - The model forgets to add the model linkage (`$modelClass`) when the DTO maps to an Eloquent model.
-- Attribute names in the DTO must match the DB column names (snake_case), not the PHP property names.
+- Attribute names in the DTO must match the database column names (snake_case), not the PHP property names.
 
 ## Do NOT
 

package/.agent-src/skills/laravel-horizon/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-horizon
 description: "Use when working with Laravel queues in production — Horizon dashboard, worker supervision, job metrics, balancing strategies — even when the user just says 'my jobs are piling up'."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-horizon

package/.agent-src/skills/laravel-mail/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-mail
 description: "Use when building Laravel emails — Mailables, Markdown templates, queued sending, attachments, previews — even when the user says 'send this as an email' without naming Mailables."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-mail

package/.agent-src/skills/laravel-middleware/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-middleware
 description: "Use when creating or modifying Laravel middleware — request/response filtering, groups, priority, terminable middleware, or route-level assignment."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-middleware

package/.agent-src/skills/{migration-creator → laravel-migration}/SKILL.md

@@ -1,11 +1,24 @@
 ---
-name: migration-creator
-description: "Use when the user says "create migration", "add column", or "new table". Creates migrations with correct table prefixes, column naming, and multi-tenant awareness."
+name: laravel-migration
+description: "Use when creating a Laravel migration — table prefixes, column naming, multi-tenant awareness, php artisan make:migration. Other stacks: use stack-native migration tooling."
 source: package
 domain: engineering
+framework: laravel
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
-# migration-creator
+# laravel-migration
 
 ## When to use
 
@@ -27,9 +40,9 @@ Use this skill when the user asks to create a database migration, add a column,
 
 ## Laravel projects
 
-### Multi-DB architecture
+### Multi-database architecture
 
-Some projects use multiple DB connections. Check `config/database.php` for connections.
+Some projects use multiple database connections. Check `config/database.php` for connections.
 
 | Check | How |
 |---|---|
@@ -37,9 +50,9 @@ Some projects use multiple DB connections. Check `config/database.php` for conne
 | Migration directories | `database/migrations/` (default), check for additional directories |
 | Custom migrate commands | `php artisan list migrate` — look for project-specific commands |
 
-**Always determine which DB the table belongs to before creating a migration.**
+**Always determine which database the table belongs to before creating a migration.**
 
-### API DB migration
+### API database migration
 
 ```bash
 php artisan make:migration create_example_table
@@ -73,13 +86,13 @@ return new class extends Migration {
 };
 ```
 
-### Customer DB migration
+### Customer database migration
 
 ```bash
 php artisan make:migration:customer AddWeatherColumn --table=cl_lv_weather
 ```
 
-Customer DB tables use the `cl_` prefix (e.g. `cl_user`, `cl_lv_weather`).
+Customer database tables use the `cl_` prefix (e.g. `cl_user`, `cl_lv_weather`).
 
 ### Adding a column (with explicit connection)
 
@@ -153,7 +166,7 @@ Focus on the "Database migrations" attack questions: Can this destroy data? Is r
 
 ## Auto-trigger keywords
 
-- DB migration
+- database migration
 - create migration
 - table prefix
 - column naming

package/.agent-src/skills/laravel-notifications/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-notifications
 description: "Use when sending notifications via mail, Slack, database, or custom channels — with queuing, on-demand recipients, and notification preferences."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-notifications

package/.agent-src/skills/laravel-pennant/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-pennant
 description: "Use when working with feature flags — Laravel Pennant, gradual rollouts, A/B testing, scope-based flags — even when the user just says 'hide this behind a flag' without naming Pennant."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-pennant

package/.agent-src/skills/laravel-pulse/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-pulse
 description: "Use when setting up Laravel Pulse — real-time dashboard, built-in cards, custom recorders, performance insights — even when the user just says 'I need app monitoring' without naming Pulse."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-pulse

package/.agent-src/skills/laravel-reverb/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-reverb
 description: "Use when configuring Laravel Reverb — the first-party WebSocket server with Pusher protocol compatibility, horizontal scaling, and Pulse monitoring."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-reverb
@@ -16,12 +28,12 @@ Use this skill for anything specific to **Laravel Reverb** as the WebSocket serv
 - Pusher protocol compatibility questions
 
 For **general WebSocket patterns**, broadcasting events, channel authorization,
-and Laravel Echo client setup, see the [websocket](../websocket/SKILL.md) skill.
+and Laravel Echo client setup, see the [laravel-websocket](../laravel-websocket/SKILL.md) skill.
 
 ## Procedure: Set up Reverb
 
 1. **Install** — `php artisan install:broadcasting` or manual setup (see below).
-2. **Configure** — Set env variables for Reverb host, port, app credentials.
+2. **Configure** — Set environment variables for Reverb host, port, app credentials.
 3. **Start server** — `php artisan reverb:start`.
 4. **Connect client** — Configure Laravel Echo with Reverb credentials.
 5. **Verify** — Confirm WebSocket connection in browser console, test event delivery.
@@ -195,7 +207,7 @@ location /app {
 ## Gotcha
 
 - Reverb requires a persistent process — it's not compatible with serverless deployments.
-- The model forgets to configure the `REVERB_HOST` and `REVERB_PORT` env variables.
+- The model forgets to configure the `REVERB_HOST` and `REVERB_PORT` environment variables.
 - WebSocket connections bypass middleware — don't rely on session auth for channel authorization.
 
 ## Do NOT

package/.agent-src/skills/laravel-scheduling/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-scheduling
 description: "Use when configuring Laravel task scheduling — cron expressions, frequency helpers, overlap prevention, maintenance mode, or output handling."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-scheduling

package/.agent-src/skills/laravel-validation/SKILL.md

@@ -3,6 +3,18 @@ name: laravel-validation
 description: "Use when writing validation — Form Requests, rules, custom rule objects, request-boundary design — even when the user just says 'validate this input' or 'check the request' without naming it."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # laravel-validation

package/.agent-src/skills/{websocket → laravel-websocket}/SKILL.md

@@ -1,11 +1,24 @@
 ---
-name: websocket
-description: "Use when building real-time features — WebSocket broadcasting, live updates, presence channels, connection state — even when the user just says 'push this to the client live'."
+name: laravel-websocket
+description: "Use when building Laravel real-time features — Broadcasting events, ShouldBroadcast, private/presence channels, Echo client. For non-Laravel WebSockets, use the stack-native skill."
 source: package
 domain: engineering
+framework: laravel
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
-# websocket
+# laravel-websocket
 
 ## When to use
 

package/.agent-src/skills/launch-readiness/SKILL.md

@@ -7,8 +7,18 @@ source: package
 domain: process
 context_spine: [team, product]
 recommended_for_user_types: [ops, developer, founder]
-
-
+workspaces:
+  - founder
+packs:
+  - founder-strategy
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: true
 ---
 
 # launch-readiness

package/.agent-src/skills/learning-to-rule-or-skill/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
 ---
 
 # learning-to-rule-or-skill
@@ -21,7 +33,7 @@ Use this skill when:
 * Reviewing post-task learnings or retrospectives
 * Deciding whether a learning belongs in a rule or a skill
 * After completing a task — reflecting on what worked or caused friction
-* Mining the audit log (`agents/state/audit/<YYYY-MM>.jsonl`,
+* Mining the audit log (`agents/runtime/state/audit/<YYYY-MM>.jsonl`,
   [`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)) surfaced
   a repeated phase pattern via
   [`extract_audit_patterns.py`](../../../scripts/extract_audit_patterns.py)
@@ -79,7 +91,7 @@ Before proceeding, the learning MUST pass all gates:
 | Minimal | Update existing preferred over creation? |
 
 If ANY gate fails → **stop**. Do not create or update anything.
-→ See `capture-learnings` rule for rejection criteria.
+Memory-entry rejection criteria live in `/memory:add` (see § "When to skip").
 
 ### 1. State the learning clearly
 
@@ -306,7 +318,7 @@ the gap is documented in its skill body.
 
 When the input is a pattern surfaced by
 [`extract_audit_patterns.py`](../../../scripts/extract_audit_patterns.py)
-mining `agents/state/audit/<YYYY-MM>.jsonl`
+mining `agents/runtime/state/audit/<YYYY-MM>.jsonl`
 ([`audit-log-v1`](../../../docs/contracts/audit-log-v1.md)):
 
 1. Treat the script's pattern record as the **State the learning**
@@ -319,7 +331,7 @@ mining `agents/state/audit/<YYYY-MM>.jsonl`
    `run_id` count as **one** piece of evidence. The mining script
    already de-duplicates by `run_id`; the gate trusts that output.
 4. Audit-derived proposals MUST set
-   `source_learning: agents/state/audit/<YYYY-MM>.jsonl#<line_ids>`
+   `source_learning: agents/runtime/state/audit/<YYYY-MM>.jsonl#<line_ids>`
    and link the mining-script run id, so the human reviewer can
    reproduce the pattern from the raw audit log.
 

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

@@ -12,6 +12,18 @@ execution:
     - python3
     - scripts/skill_linter.py
     - "--all"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # lint-skills

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

@@ -3,6 +3,18 @@ name: livewire
 description: "Use when the project's frontend stack is Livewire — dispatched by `directives/ui/{apply,review,polish}.py`. Covers reactive state, events, lifecycle hooks, and component/view separation."
 source: package
 domain: engineering
+workspaces:
+  - engineering
+packs:
+  - laravel
+lifecycle: active
+trust:
+  level: professional
+  confidence: high
+  human_review_required: false
+install:
+  default: false
+  removable: true
 ---
 
 # livewire