Apply clean architecture as a small, explicit flow rather than mirroring every framework folder. Put domain use cases in `app/Domains/<Domain>/Actions`, typed immutable data in `DTOs`, and persistence abstractions in `Contracts`. Keep Eloquent implementations at the outer adapter boundary and bind them in `AppServiceProvider`. The request layer validates input, constructs a DTO, and calls one Action. The Action depends on interfaces and contains the use-case rule. The repository adapter trans...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill laravel-clean-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Laravel Clean Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-laravel-clean-architecture-724a141b)More formats (shields.io, HTML) on the badges page.
Apply clean architecture as a small, explicit flow rather than mirroring every framework folder. Put domain use cases in `app/Domains/<Domain>/Actions`, typed immutable data in `DTOs`, and persistence abstractions in `Contracts`. Keep Eloquent implementations at the outer adapter boundary and bind them in `AppServiceProvider`.
The request layer validates input, constructs a DTO, and calls one Action. The Action depends on interfaces and contains the use-case rule. The repository adapter translates the interface to Eloquent. Keep models in `app/Models/` and keep controllers free of queries. Verify container bindings with `php artisan tinker`, then test the Action with a repository double and the controller at the HTTP boundary.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
