Coding Standard Laravel Package

Product Decisions This Supports

• Enforcing consistency in PHP/Laravel codebases to reduce onboarding friction and merge conflicts.
• Accelerating onboarding by standardizing formatting, reducing cognitive load for new developers.
• Automating code quality as part of CI/CD pipelines (e.g., pre-commit hooks, GitHub Actions) to catch formatting issues early.
• Roadmap alignment: Justifying investment in developer tooling to improve team velocity and reduce technical debt.
• Build vs. buy: Opting for a lightweight, customizable alternative to proprietary tools like PHPStorm’s built-in formatter or paid static analysis suites.
• Use cases:
  • Open-source projects needing standardized contributions.
  • Internal Laravel monorepos with multiple teams.
  • Projects adopting PHP 8+ features where legacy formatting varies.

When to Consider This Package

• Avoid if:
  • Your team already uses a mature standard (e.g., PSR-12, Laravel’s built-in php-cs-fixer presets) with no custom needs.
  • You lack PHP/Laravel expertise to configure or maintain custom rules (low maturity signals risk).
  • The package’s niche focus (Innmind’s internal rules) conflicts with your existing style (e.g., strict PSR compliance).
  • You prioritize analysis (e.g., security, performance) over formatting—consider tools like phpstan or pint instead.
• Look elsewhere if:
  • You need interactive fixes (e.g., IDE integration) → Use pint or PHPStorm’s formatter.
  • You require team-specific customization beyond basic PHP-CS-Fixer rules → Build a wrapper or extend php-cs-fixer directly.
  • The project’s 0 stars/dependents raises concerns about long-term maintenance (evaluate Innmind’s commitment).

How to Pitch It (Stakeholders)

For Executives: "This package lets us automate PHP/Laravel code formatting to a single standard—reducing merge conflicts, speeding up reviews, and cutting onboarding time. It’s a lightweight, open-source alternative to paid tools, with minimal setup. For a one-time effort, it’ll save hours weekly in manual formatting debates and CI failures. We’ll pilot it in [Project X] to measure impact on developer velocity."

For Engineering: "This wraps php-cs-fixer with Innmind’s custom rules (e.g., [hypothetical: strict type hints, modern array syntax]). It’s a drop-in replacement for .php_cs.dist—just add it to composer.json, configure paths, and run php-cs-fixer fix. The tradeoff? We inherit Innmind’s opinions (which may need tweaking), but it’s easier than maintaining our own rules. Let’s compare it to our current setup in a PR."

For Developers: "No more ‘style wars’—this tool auto-fixes indentation, braces, and naming conventions so we can focus on logic. It integrates with Git hooks or CI to block messy commits. Try it on your branch: composer require innmind/coding-standard --dev and update .php_cs.dist."