Coding Standard Laravel Package

Product Decisions This Supports

• Enforce consistent code quality across PHP/Laravel projects by standardizing coding conventions (e.g., PSR-12, Slevomat rules, Doctrine rules).
• Reduce technical debt by automating code review checks via CI/CD pipelines (e.g., GitHub Actions, GitLab CI).
• Accelerate onboarding for new developers by eliminating ambiguity in style/structure (e.g., naming conventions, docblocks, array syntax).
• Build vs. Buy Decision: Opt for this package over custom rulesets if:
  • Your team lacks time/resources to maintain a bespoke coding standard.
  • You need a pre-configured, opinionated standard (e.g., WyriHaximus’ custom rules like @api annotation bans).
  • You’re already using PHP-CS-Fixer or PHP_CodeSniffer and want a drop-in replacement.
• Roadmap Use Cases:
  • Pre-merge hooks: Block PRs with violations (e.g., via GitHub Branch Protection).
  • Onboarding tool: Require new hires to pass a coding standard check before accessing the codebase.
  • Legacy refactoring: Gradually enforce standards in older codebases with --allow-risky=... flags.

When to Consider This Package

Adopt this package if:

• Your team uses PHP 8.2+ (minimum supported version).
• You’re already invested in PHP_CodeSniffer or Slevomat’s tools (this is a wrapper).
• You need custom rules (e.g., banning @api, enforcing specific docblock formats) without writing them from scratch.
• Your project is Laravel-based or uses Symfony components (common dependencies).
• You prioritize maintainability over flexibility (e.g., no need to tweak rules frequently).

Look elsewhere if:

• You require JavaScript/TypeScript standards (this is PHP-only).
• Your team prefers strict PSR-12 only (this includes Slevomat/Doctrine rules by default).
• You need real-time IDE feedback (pair with PHPStan or Psalm instead).
• Your project uses PHP < 8.2 (requires downgrading dependencies manually).
• You want active community support (this package has 0 stars/contributors; rely on underlying libraries like Slevomat).

How to Pitch It (Stakeholders)

For Executives: "This package lets us enforce consistent, high-quality PHP code automatically—reducing bugs, speeding up reviews, and lowering onboarding time. It’s like a ‘linter on steroids’ for our Laravel apps, built on top of industry-standard tools. The upfront cost is minimal (MIT license, no vendor lock-in), and the long-term ROI comes from fewer merge conflicts and cleaner code. We’re not reinventing the wheel; we’re leveraging battle-tested rules from the PHP ecosystem."

For Engineering: "WyriHaximus’ coding standard gives us a pre-configured, opinionated set of rules (PSR-12 + Slevomat + Doctrine) with custom tweaks (e.g., banning @api annotations). It integrates seamlessly with our existing CI (GitHub Actions/GitLab CI) and can block PRs with violations. Since it’s a wrapper for PHP_CodeSniffer, we get all the familiar tooling (e.g., --diff, --fix) but with less maintenance overhead. Zero stars? True, but the underlying libraries (Slevomat, Doctrine) are rock-solid. We can fork it later if we need customizations."

For Developers: *"This means:

• No more ‘style nitpicks’ in code reviews—violations are caught automatically.
• Faster onboarding—new devs see consistent formatting from day one.
• Less context-switching—your IDE can highlight issues before you commit.
• Easy to run locally: ./vendor/bin/php-cs-fixer fix or add it to your pre-commit hooks. We’re not adding complexity; we’re reducing busywork."*