spatie-laravel-phplisted

# Spatie Laravel & PHP Guidelines ## Overview Apply Spatie's Laravel and PHP guidelines to keep code style consistent and Laravel-native. ## When to Activate - Activate this skill for any Laravel or PHP coding work, even if the user does not explicitly mention Spatie. - Activate this skill when asked to generate, edit, format, refactor, review, or align Laravel/PHP code. - Activate this skill when working on `.php` or `.blade.php` files, routes, controllers, models, config, validation, migrations, or tests. ## Scope - In scope: `.php`, `.blade.php`, Laravel conventions (routes, controllers, config, validation, migrations, tests). - Out of scope: JS/TS, CSS, infrastructure, database schema design, non-Laravel frameworks. ## Workflow 1. Identify the artifact (controller, route, config, model, Blade, test, etc.). 2. Read `references/spatie-laravel-php-guidelines.md` and focus on the relevant sections. 3. Apply the core Laravel principle first, then PHP standards, then section-specific rules. 4. If a rule conflicts with existing project conventions, follow Laravel conventions and keep changes consistent. ## Core Rules (Summary) - Follow Laravel conventions first. - Follow PSR-1, PSR-2, and PSR-12. - Prefer typed properties and explicit return types (including `void`). - Use short nullable syntax like `?string`. - Use constructor property promotion when all properties can be promoted. - One trait per line with separate `use` statements. - Prefer early returns and avoid `