Standards Laravel Package

Product Decisions This Supports

• Standardization Across Projects: Enables consistent coding practices for all Laravel/PHP projects under a single umbrella, reducing technical debt and improving maintainability. Aligns with company-wide initiatives to unify tooling and reduce fragmentation.
• Developer Productivity: Accelerates onboarding by providing pre-configured, opinionated tooling (PHP-CS-Fixer, PHPStan, PHPUnit) that eliminates manual setup. Reduces context-switching for developers working across multiple repositories.
• Scalability for Growth: Supports teams scaling from small projects to large portfolios (e.g., Rollerscapes’ ecosystem) by enforcing best practices out-of-the-box. Reduces the need for custom tooling as projects grow.
• Roadmap Alignment: Fits a "build vs. buy" strategy where off-the-shelf standards are preferred over bespoke solutions. Ideal for teams adopting Laravel or PHP 8.1+ and prioritizing maintainability.
• Use Cases:
  • New Laravel Projects: Provides a zero-configuration QA pipeline for greenfield development.
  • Legacy Modernization: Standardizes existing codebases with minimal disruption (e.g., incremental PHPStan rule adoption).
  • Open-Source Collaboration: Ensures consistency for distributed teams or public repositories.
  • CI/CD Optimization: Reduces flaky tests and false positives by unifying linting/analysis tools.

When to Consider This Package

• Adopt if:

  • Your team uses Laravel or PHP 8.1+ and lacks standardized coding guidelines.
  • You prioritize developer velocity over custom tooling (e.g., no time to configure PHP-CS-Fixer/PHPStan from scratch).
  • Your project involves multiple contributors or open-source collaboration requiring unified rules.
  • You’re managing a portfolio of PHP projects (like Rollerscapes) and want consistency across them.
  • Your CI/CD pipeline needs lightweight, pre-configured static analysis without heavy customization.

• Look elsewhere if:

  • Your team requires highly custom static analysis rules beyond PHPStan’s defaults (e.g., domain-specific logic).
  • You’re using PHP <8.1 (package drops support for older versions).
  • Your project has unique architectural constraints (e.g., microservices with divergent standards).
  • You already have a mature internal QA toolchain (e.g., custom PHPCS rules or proprietary linting).
  • You need Laravel-specific rules (e.g., Blade templates, Eloquent) that aren’t covered by the package’s Symfony-focused PHPStan extensions.

How to Pitch It (Stakeholders)

For Executives: "This package standardizes our PHP/Laravel code quality with zero upfront cost—leveraging industry-proven tools like PHPStan and PHP-CS-Fixer to catch bugs early, reduce technical debt, and improve developer productivity. Used by Rollerscapes’ portfolio of projects, it’s battle-tested for scalability and integrates seamlessly with Laravel. Implementation is as simple as a one-line Composer install, saving engineering time while ensuring consistency across all our PHP projects. The long-term ROI comes from reduced bug rates, faster onboarding, and lower maintenance costs."

For Engineering: *"Rollerscapes/standards gives us a pre-configured, opinionated QA pipeline for Laravel/PHP projects:

• PHPStan for static analysis (type safety, Symfony/Laravel integration) with auto-fixable rules.
• PHP-CS-Fixer for consistent code style (PSR-12 compliant) with zero manual configuration.
• PHPUnit best practices baked in (e.g., internal test marking).
• Artisan commands (standards:check, standards:fix) for seamless integration into workflows. It’s lightweight, MIT-licensed, and actively maintained, with a Makefile for common tasks. Perfect for new projects or adding to CI/CD pipelines—just install and go. No more reinventing the wheel for linting and analysis."*

For Technical Leads/TPMs: *"This package addresses three critical pain points:

1. Tooling Fragmentation: Unifies PHP-CS-Fixer, PHPStan, and PHPUnit under one dependency, reducing maintenance overhead.
2. Onboarding Friction: Standardized rules mean new devs don’t need to learn custom configs—they just follow the package’s defaults.
3. Scalability: Works out-of-the-box for small to large projects, with incremental adoption (e.g., start with PHP-CS-Fixer, then add PHPStan). Caveats:

• Laravel-specific gaps: The Symfony-focused PHPStan rules may need tweaking for Eloquent/Blade. We’ll need to baseline errors and customize.
• PHPStan strictness: Upgrading to level max may break legacy code. Phase in rules to avoid disruption. Recommendation: Pilot in one Laravel project, measure impact on CI/CD time and developer productivity, then roll out company-wide."*