| name | php-laravel-core |
| description | Shared reference for the Laravel cluster: the layered request flow (controller → service → action → model), typed Eloquent + Form Request validation, the standard JSON response envelope, the test/CI matrix, and the version/tooling baseline. USE WHEN structuring controllers, writing validation, wiring the test/verify pipeline, or choosing tooling — the conventions every Laravel spoke shares. |
| cluster | php-laravel |
| version | 1.0.0 |
PHP / Laravel Core
Shared model for the php-laravel cluster. The patterns, TDD, verification, and security spokes
all lean on these conventions — keep them consistent here so no spoke contradicts another.
1. The decision this cluster turns on: thin controllers, layered flow
Every request crosses the same one-way pipeline. Each layer has exactly one job, and logic
flows down, never back up:
HTTP Request ─> Route (model-bound) ─> Form Request (validate + authorize)
─> Controller (thin: translate I/O) ─> Service (orchestrate)
─> Action (single use case) ─> Model / Repository (persist)
─> API Resource (shape) ─> JSON envelope
- Controller — thin. Receives the validated request, calls one service/action, returns a
resource. No business logic, no queries. →
laravel-patterns
- Service — coordinates a multi-step use case across actions/models.
- Action — a single-purpose use case (); the smallest reusable unit.
