Coding Standard Laravel Package

Product Decisions This Supports

• Standardization of Code Quality: Enables consistent coding standards across PHP/Laravel projects, reducing technical debt and improving maintainability.
• Developer Onboarding: Accelerates new developer ramp-up by enforcing a shared, documented standard (BitBag Coding Bible).
• Build vs. Buy Decision: Justifies adopting a pre-built solution over custom rulesets, saving engineering time.
• Scalability: Supports long-term maintainability for projects leveraging Symfony/Sylius or PHP-heavy stacks.
• Compliance & Audits: Aligns with security and best-practice requirements (e.g., PHPStan levels, ECS fixers).
• Roadmap for Open-Source Contributions: Facilitates collaboration with BitBag’s ecosystem (e.g., Sylius plugins).

When to Consider This Package

• Adopt if:

  • Your team uses Laravel/Symfony/PHP and lacks a unified coding standard.
  • You prioritize consistency over customization (BitBag’s rules are opinionated but battle-tested).
  • Your project involves Sylius or BitBag’s plugins (optimized compatibility).
  • You need PHPStan + ECS integration without configuring rules manually.
  • Executives demand reduced code review cycles and lower technical debt.

• Look Elsewhere if:

  • Your team requires highly custom rules beyond BitBag’s standards.
  • You’re not using PHP 8.1+ (compatibility may vary).
  • Your stack is non-PHP (e.g., Node.js, Python).
  • You prefer lightweight tools (this package bundles ECS/PHPStan dependencies).
  • Your organization already has an entrenched coding standard (e.g., PSR-12 only).

How to Pitch It (Stakeholders)

For Executives: "This package enforces BitBag’s proven coding standards—used across 120+ Sylius projects—to reduce bugs, speed up reviews, and cut onboarding time. By adopting it, we align with industry best practices (PHPStan, ECS) while leveraging BitBag’s expertise. Minimal setup; immediate ROI in code quality."

For Engineering: *"BitBag’s coding standard gives us:

• Pre-configured PHPStan/ECS (no manual rule setup).
• BitBag’s open-source header (compliance with their licensing).
• Fixers for common issues (e.g., type hints, final methods).
• Sylius-specific optimizations (if applicable). Just run composer require bitbag/coding-standard --dev and integrate in 10 minutes. Supports PHP 8.1+ and modern ECS/PHPStan."*

For Developers: *"This is a drop-in coding standard that:

1. Enforces BitBag’s Coding Bible (strict but practical).
2. Integrates PHPStan (static analysis) and ECS (autofix) out of the box.
3. Works with Laravel/Symfony/Sylius—just configure ecs.php and phpstan.neon. Run ./vendor/bin/ecs check src to validate, or --fix to auto-correct. Customize rules later if needed."*

Key Ask: "Should we adopt this as our team’s standard to improve consistency and reduce technical debt?"