Duster Laravel Package

Product Decisions This Supports

• Standardizing Code Quality: Enables consistent linting and code style enforcement across Laravel projects, reducing technical debt and onboarding friction for new developers.
• Developer Experience (DX): Automates repetitive linting/fixing tasks, allowing engineers to focus on feature development rather than manual code cleanup.
• CI/CD Integration: Streamlines GitHub Actions workflows by consolidating linting tools (TLint, PHP_CodeSniffer, PHP CS Fixer, Pint) into a single command, reducing pipeline complexity.
• Build vs. Buy: Eliminates the need to maintain custom scripts or configure multiple tools individually, saving engineering time.
• Scalability: Supports large codebases by offering granular control over file inclusion/exclusion and parallel processing (e.g., PHP CS Fixer).
• Roadmap Alignment: Aligns with Laravel’s ecosystem (e.g., Pint integration) and modern tooling (e.g., GitHub Actions, Husky hooks).
• Use Cases:
  • Enforcing Tighten’s (or custom) coding standards in new projects.
  • Migrating legacy Laravel apps to standardized practices.
  • Pre-commit hooks (via Husky) to catch issues early.
  • CI pipelines to block non-compliant code merges.

When to Consider This Package

• Adopt if:

  • Your team uses Laravel and needs consistent, automated linting/fixing without manual tool configuration.
  • You prioritize developer productivity by reducing repetitive code reviews or CI failures.
  • Your project requires Tighten’s presets (or similar) for PHP/Blade standards (e.g., PSR1 + custom rules).
  • You want GitHub Actions or Husky integration with minimal setup.
  • Your team lacks dedicated code quality maintainers to manage individual tools (TLint, PHP CS Fixer, etc.).

• Look elsewhere if:

  • You need non-Laravel-specific standards (e.g., Symfony, WordPress).
  • Your project uses custom linting rules incompatible with Tighten’s presets (though Duster supports overrides).
  • You require advanced static analysis (e.g., PHPStan) beyond linting/fixing (Duster supports extensions via duster.json).
  • Your team prefers manual tooling (e.g., running Pint, PHPCS separately).
  • You’re using non-PHP languages in the same repo (Duster focuses on PHP/Blade).

How to Pitch It (Stakeholders)

For Executives:

"Duster automates Laravel code quality enforcement, reducing busywork for engineers and ensuring consistency across our codebase. By integrating linting tools (like Pint and PHP CS Fixer) into a single command, we cut CI/CD complexity and catch issues earlier—saving time and improving onboarding. It’s a low-effort way to enforce best practices without hiring dedicated tooling maintainers."

Key Outcomes:

• Faster developer ramp-up (standardized code style).
• Fewer CI failures due to linting errors.
• Scalable for large teams/projects.

For Engineering:

*"Duster replaces fragmented linting tools with a unified CLI (duster lint/duster fix) that runs Tighten’s optimized presets for Laravel. It supports:

• Pre-commit hooks (Husky) to block bad code early.
• GitHub Actions to gate merges on quality.
• Customization via duster.json (e.g., exclude tests, add PHPStan).
• Parallel processing for faster runs.

No more juggling Pint, PHPCS, and TLint separately—just install, configure once, and let it handle the rest."*

Why Now?

• Aligns with Laravel’s Pint adoption.
• Reduces context-switching during code reviews.
• Future-proofs for team growth.