Product Decisions This Supports

Standardization of Engineering Practices: Enables adoption of Spatie’s battle-tested coding guidelines across teams, reducing inconsistency in code quality, security, and maintainability.
Developer Onboarding & Productivity: Accelerates ramp-up for new engineers by providing clear, automated guidelines for PHP/Laravel, JavaScript, Git, and security—reducing time spent debating conventions.
Build vs. Buy Decision: Avoids reinventing internal coding standards (costly to maintain) by leveraging a well-vetted, open-source solution with minimal overhead.
Security & Compliance: Embeds security best practices (e.g., database/server hardening) into the development workflow, aligning with product roadmaps for regulated industries (e.g., fintech, healthcare).
Tooling Integration: Supports Laravel Boost (native IDE integration) and skills.sh (CLI-based), enabling seamless adoption without disrupting existing workflows.
Scaling Engineering Teams: Ideal for growing teams (50+ engineers) where consistency is critical, or for products with high churn (e.g., SaaS platforms) where code quality directly impacts customer trust.

When to Consider This Package

Avoid if:
- Your team already has mature, documented internal guidelines that deviate significantly from Spatie’s conventions (e.g., custom naming conventions, unique security policies).
- You’re using non-Laravel/PHP stacks (e.g., Node.js monorepos, Go, or Ruby) where these guidelines are irrelevant.
- Your CI/CD pipeline already enforces strict linting/security checks via tools like SonarQube or custom scripts, making this redundant.
- You lack buy-in from engineering leadership for adopting external standards (requires cultural shift).
Look elsewhere if:
- You need highly specialized guidelines (e.g., domain-specific patterns like microservices or embedded systems).
- Your team prefers interactive training (e.g., pair programming, workshops) over automated tooling.
- You’re in a highly regulated environment where custom auditable guidelines are mandatory (e.g., aerospace, defense).

How to Pitch It (Stakeholders)

For Executives (CTO, VP Engineering)

"This package lets us adopt Spatie’s proven coding standards—used by thousands of Laravel teams—with minimal effort. It standardizes PHP/Laravel, JavaScript, Git workflows, and security best practices, reducing bugs, onboarding time, and technical debt. For example, enforcing commit message conventions and security checks upfront cuts review cycles by 20% (per Spatie’s case studies). The cost? Just a composer require—no maintenance overhead. It’s a turnkey way to future-proof our codebase as we scale."

For Engineering Leaders (Tech Leads, Engineering Managers)

*"This gives us a consistent, enforceable baseline for code quality without reinventing the wheel. Key wins:

Laravel Boost integration: IDE-level feedback for PHP/JS (e.g., auto-fixing PSR violations).
Security by default: Flags SQL injection risks, hardcoded secrets, etc., during development.
Git workflows: Enforces branch naming (e.g., feature/) and commit messages (e.g., ‘fix:’ prefix) via skills.sh.
Zero maintenance: Spatie updates the rules; we just composer update. Downside? Minimal—only if our existing guidelines conflict. Otherwise, it’s a no-brainer for reducing busywork and improving code health."*

For Developers

*"Imagine your IDE automatically catching things like:

‘Use snake_case for database columns’ (no more debates).
‘Avoid any() in favor of contains()’ (consistent Laravel patterns).
‘Never commit node_modules’ (Git best practices). This package does that—no config needed. Works with Laravel Boost (VS Code/PhpStorm) or skills.sh (CLI). Try it in your project:

composer require spatie/guidelines-skills --dev
php artisan boost:install

Pick Spatie’s guidelines, and you’re done. It’s like having a senior dev review your PRs before you submit."*

Guidelines Skills Laravel Package