Enforce modern Laravel 11+ coding conventions with Pint linting.
npx skills add https://github.com/The-Rabak/naysmith --skill laravel-conventions
Please help me install this Agent Skill. Skill: laravel-conventions Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/laravel-conventions Command: npx skills add https://github.com/The-Rabak/naysmith --skill laravel-conventions
This reference helps developers adopt and enforce modern Laravel coding conventions for Laravel 11+ and PHP 8.3+ projects.
Refactor a Laravel 11+ project to follow the Controller -> FormRequest -> Action/Service -> Model pattern and enforce PSR-12 with Pint linting.
High-intent search queries and answers about installing and using this skill.
Modern Laravel coding conventions enforce a Controller -> FormRequest -> Action/Service -> Model pattern to promote thin controllers and clear separation of concerns. This architecture uses DTOs, Enums, typed properties, and PSR-12 compliance to improve readability and maintainability.
To refactor legacy Laravel apps, align your codebase to the Controller -> FormRequest -> Action/Service -> Model pattern and enforce PSR-12 with Pint linting. This reduces technical debt and speeds up onboarding by ensuring convention compliance across all project files.
Yes, these Laravel coding conventions require strict types, typed properties, readonly DTOs, and PSR-12-compliant structure. Pint linting is used to maintain consistency and ensure convention compliance across Controllers, FormRequests, Actions, Models, Migrations, and Tests.
No, these conventions are specifically designed for Laravel 11+ projects running PHP 8.3+. They enforce the Laravel 11+ directory structure and specific framework components like FormRequests and Eloquent Models, which are not applicable to non-Laravel PHP applications.
Laravel code reviews fail Pint linting when the code lacks strict types, typed properties, or violates PSR-12 structure. Enforcing the Controller -> FormRequest -> Action/Service -> Model pattern with readonly DTOs and Enums ensures compliance and resolves linting inconsistencies.
The best way to enforce separation of concerns in Laravel 11 is by adopting a thin controller architecture. Route requests through FormRequests for validation, delegate business logic to Action/Service classes, and interact with Models, ensuring PSR-12 compliance through Pint linting.
modu-aiDevelop PHP 8.3+ applications for Laravel 11 and Symfony 7.
idiaz01Run environment checks, linting, static analysis, tests, and security scans on Laravel projects.
JCETools-PetraGuide PHP development with framework selection, type safety, and verification workflows.
aronpcEnforce Laravel coding standards and Pint formatting in PHP projects.
