Common Laravel architecture anti-patterns include: - Fat controllers containing validation, business rules, Eloquent queries, and serialization. - Inline `$request->validate()` everywhere instead of reusable Form Requests. - Passing `$request->all()` into `Model::create()`. - Manually constructing services instead of letting the container inject them. - Depending directly on concrete repositories when an interface is the boundary. - One God Service that owns unrelated use cases. - Business lo...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill laravel-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Laravel Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-laravel-architecture-0d78b90a)More formats (shields.io, HTML) on the badges page.
Common Laravel architecture anti-patterns include:
- Fat controllers containing validation, business rules, Eloquent queries, and serialization.
- Inline `$request->validate()` everywhere instead of reusable Form Requests.
- Passing `$request->all()` into `Model::create()`.
- Manually constructing services instead of letting the container inject them.
- Depending directly on concrete repositories when an interface is the boundary.
- One God Service that owns unrelated use cases.
- Business logic hidden in global helpers or model callbacks without a clear use-case owner.
Prefer a Form Request → single-responsibility Action → repository interface → Eloquent flow. Bind implementations in `AppServiceProvider`, use `$request->validated()`, and keep controllers responsible for HTTP orchestration only. This makes boundaries visible and keeps tests focused.
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!
