Coding Standard Laravel Package

Product Decisions This Supports

• Standardization Across Teams: Enables consistent PHP coding standards for Laravel projects, reducing onboarding time and code review friction, especially in distributed teams or open-source contributions.
• Security and Quality Gates: Acts as a pre-commit/pre-merge guard for security-sensitive projects (e.g., financial, healthcare) by enforcing stricter naming, docblock, and structural rules beyond PSR-12.
• Laravel Ecosystem Expansion: Justifies adoption of Respect’s validation/HTTP libraries by aligning codebases with their conventions, reducing integration friction.
• Tooling Consolidation: Replaces fragmented custom PHP_CodeSniffer rules with a maintained, opinionated standard, lowering DevOps overhead for linting pipelines.
• Legacy Code Modernization: Provides a structured refactoring path for older Laravel codebases by enforcing modern conventions incrementally (e.g., via CI warnings → blocking).
• Open-Source Contribution: Critical for teams contributing to Respect’s ecosystem or Laravel packages, ensuring compliance with upstream standards.

When to Consider This Package

• Adopt if:
  • Your Laravel project prioritizes strict code quality (e.g., enterprise, security-critical, or open-source).
  • You’re already using Respect libraries (e.g., respect/validation, respect/http) and want consistency.
  • Your team lacks custom PHP_CodeSniffer rules but needs enforceable standards without reinventing the wheel.
  • You’re migrating from PSR-12 to stricter conventions (e.g., Respect’s SnakeCase methods) and want a pre-built ruleet.
  • You need CI/CD integration for linting with minimal maintenance (no active rule updates required).
• Look elsewhere if:
  • Your project relies on PSR-12 or Symfony standards and Respect’s rules introduce too many conflicts.
  • You prefer modern static analysis (e.g., PHPStan, Psalm) over PHP_CodeSniffer for type/quality checks.
  • Your team values speed over strictness (e.g., startups, MVPs) and would find the rules too restrictive.
  • You don’t use Respect libraries and the niche focus doesn’t align with your roadmap.
  • You need Blade template linting (this package doesn’t support Blade files natively).

How to Pitch It (Stakeholders)

For Executives: "The Respect Coding Standard is a lightweight, MIT-licensed PHP_CodeSniffer ruleet that enforces Respect’s strict coding conventions—critical for projects where code quality directly impacts security, scalability, and developer productivity. By adopting this, we standardize our Laravel codebase to enterprise-grade consistency, reducing technical debt and onboarding time. It integrates seamlessly with CI/CD and requires no runtime overhead, making it a low-risk, high-reward tool for long-term maintainability. Ideal for projects adopting Respect’s validation or HTTP libraries, or for teams prioritizing strict linting as a quality gate."

For Engineering: "This package gives us Respect’s pre-configured PHP_CodeSniffer rules—strict but practical—for enforcing consistent coding standards across our Laravel project. It’s a drop-in replacement for custom rules, saving time while catching issues early (e.g., naming conventions, docblocks). Works alongside Laravel’s tooling (Pest, Pint) and can be customized to exclude Blade files or override conflicting rules. Low maintenance: just install, integrate into CI, and let it catch violations pre-merge. Perfect if we’re using Respect libraries or want stricter standards than PSR-12."

For Developers: *"Respect’s coding standard adds real-time feedback in your IDE (PHPStorm/VSCode) and blocks PRs with violations in CI. It catches things like:

• Inconsistent naming (camelCase vs. snake_case methods).
• Missing or incorrect docblocks.
• Security-sensitive structural issues. Think of it as PHP’s equivalent of ESLint—but for Laravel. We can tweak rules to fit our needs (e.g., ignore Blade files) and auto-fix some issues. No flaky tests or runtime impact—just cleaner code."*