Laravel Best Practices Laravel Package

Product Decisions This Supports

• Enforcing Consistency & Quality: Aligns development teams with standardized Laravel best practices, reducing technical debt and onboarding friction for new engineers. Critical for scaling teams or maintaining legacy codebases.
• Accelerating Onboarding: Reduces ramp-up time for junior developers by providing pre-configured, opinionated defaults (e.g., naming conventions, security checks, testing structures).
• Build vs. Buy: Justifies not building custom tooling for enforcing Laravel conventions (e.g., no need to reinvent static analysis or linting for PHP). Saves engineering time for higher-impact work.
• Security & Compliance: Enables automated checks for vulnerabilities (e.g., SQL injection, CSRF) or compliance gaps (e.g., GDPR data handling) via Boost integration.
• Roadmap Prioritization: Validates investment in Laravel as a long-term stack by ensuring adherence to modern patterns (e.g., dependency injection, service containers).
• Use Cases:
  • Greenfield Projects: Start with a "batteries-included" setup to avoid retrofitting best practices later.
  • Legacy Refactoring: Audit existing codebases for violations (e.g., hardcoded routes, missing type hints) and prioritize fixes.
  • Agency/Client Work: Deliver "premium" Laravel implementations with built-in quality gates.

When to Consider This Package

• Avoid If:
  • Your team rejects opinionated tooling (e.g., prefers custom rules over predefined conventions).
  • You’re using non-Laravel PHP frameworks (Symfony, Lumen) or a non-PHP stack.
  • Your project is prototype-only with no long-term maintenance plans.
  • You lack Laravel Boost (this package is an additive overlay; core functionality depends on Boost).
  • Your team already has mature custom solutions (e.g., in-house PSR-12 linters, custom PHPStan rules).
• Look Elsewhere If:
  • You need deep IDE integration (e.g., PHPStorm templates) → Consider laravel-shift or laravel-ide-helper.
  • You require performance optimization → Focus on laravel-debugbar or tightenco/ziggy.
  • Your priority is API-first development → Evaluate spatie/laravel-api or fractal/zf2.

How to Pitch It (Stakeholders)

For Executives: "This package lets us bake Laravel best practices into our development workflow—like a ‘PMD for PHP’ but tailored for Laravel. It catches critical issues early (e.g., security flaws, inconsistent code) and speeds up hiring by reducing the ‘Laravel learning curve.’ Think of it as insurance: small upfront cost to avoid costly refactoring later. MIT-licensed, so no vendor lock-in."

For Engineering: "Laravel Boost already gives us a solid foundation, but this package fills gaps Boost ignores—like enforcing type safety, naming conventions, and security checks. It’s like having a senior dev review every PR automatically. We’d integrate it via Boost’s skill system, so zero extra tooling to maintain. Tradeoff: slight opinionatedness, but the tradeoffs are documented and configurable."

For Developers: "No more arguing about whether User::find() should be User::firstWhere(). This package enforces a consistent style and catches bugs (e.g., missing CSRF tokens) before they hit production. It’s additive—won’t break existing code—but will nag you in Slack if you violate rules. Think of it as a strict but helpful teammate."