Duster Laravel Package

Product Decisions This Supports

• Standardization of Code Quality: Enables adoption of Tighten’s proven Laravel/PHP coding standards (linting, formatting, and sniffs) across teams, reducing inconsistencies and onboarding friction.
• Developer Experience (DX) Improvements: Automates repetitive code quality checks (e.g., lint/fix commands) via CLI, GitHub Actions, or Husky hooks, freeing developers from manual tooling setup.
• CI/CD Integration: Simplifies CI pipelines by consolidating multiple tools (PHP_CodeSniffer, Pint, TLint, PHP CS Fixer) into a single workflow, reducing flaky builds and false positives.
• Build vs. Buy: Buy—avoids reinventing wheel for teams already using Laravel/PHP. Build only if custom tooling is needed beyond Tighten’s standards.
• Use Cases:
  • New Laravel projects needing standardized quality gates.
  • Legacy projects migrating to modern tooling (replaces ad-hoc php-cs-fixer/pint setups).
  • Teams prioritizing DX (e.g., auto-fixing issues pre-commit via Husky).
  • Enforcing consistency in open-source contributions or multi-team repos.

When to Consider This Package

Adopt if:

• Your team uses Laravel/PHP and lacks standardized code quality tools.
• You want pre-configured, opinionated linting/formatting (Tighten’s presets) without customizing rules from scratch.
• You need seamless CI/CD integration (GitHub Actions, Husky) with minimal setup.
• Your project includes multiple developers or contributors who need consistent standards.

Look elsewhere if:

• You require custom rules beyond Tighten’s presets (e.g., company-specific PSR extensions).
• Your team prefers alternative tools (e.g., Laravel Pint alone, custom PHPStan setups).
• You’re not using Laravel (though PHP support exists, Laravel-specific rules may not apply).
• Your project is small/solo and doesn’t need automated enforcement.

How to Pitch It (Stakeholders)

For Executives: "Duster standardizes our Laravel codebase using Tighten’s battle-tested rules, reducing bugs and onboarding time. It automates linting/formatting via CI or pre-commit hooks—saving devs hours weekly while ensuring consistency. Low maintenance (MIT-licensed, actively updated) and integrates with our existing GitHub Actions."

For Engineering: *"This replaces fragmented tooling (PHP CS Fixer, Pint, etc.) with a single CLI (./vendor/bin/duster lint/fix) that:

• Fixes issues automatically (e.g., class ordering, PSR compliance).
• Works in CI/CD (GitHub Action included) or locally (Husky hooks).
• Extends easily—add custom scripts (e.g., PHPStan) via duster.json.
• No config bloat: Uses Tighten’s defaults but lets us override rules per project. Example: Run composer require tightenco/duster --dev and ./vendor/bin/duster fix to auto-correct 80% of style issues pre-commit."*