Weave Code
Guidelines Skills Laravel Package
spatie/guidelines-skills
Spatie’s battle-tested coding guidelines packaged as AI skills for Laravel Boost and skills.sh. Includes skills for Laravel/PHP, JavaScript, version control, and security, helping teams apply consistent conventions and best practices.
At a glance
Frequently asked questions about Guidelines Skills
- How do I integrate Spatie’s coding guidelines into my Laravel 12+ project?
- Install via Composer (`composer require spatie/guidelines-skills --dev`) and run `php artisan boost:install` to select Spatie’s guidelines for Laravel Boost. For CLI-only workflows, use `npx skills add spatie/guidelines-skills` with skills.sh. Both methods require no core app changes.
- Will this package conflict with my existing team coding standards?
- Spatie’s guidelines are modular—override specific rules via `.boost/skills.json` or use `skills.sh --ignore` for conflicts. Audit your current conventions first to minimize friction. The package prioritizes PSR-12 and OWASP Top 10 but allows customization.
- Does this work with Laravel Boost’s early access release?
- Yes, but test thoroughly. Laravel Boost is Laravel 12+ only and may have instability. Start with `skills.sh` (more mature) before committing to Boost. Monitor Spatie’s GitHub and Boost’s changelog for updates.
- How does this improve my CI/CD pipeline?
- Add `skills.sh lint` to your pipeline to enforce guidelines pre-merge. Use `--fix` for auto-corrections and `--parallel` to speed up checks. Begin with warning-only mode to avoid blocking merges, then enforce gradually.
- Can I use this for JavaScript/TypeScript alongside Laravel?
- Yes, the `spatie-javascript` skill enforces Prettier and modern JS conventions. It integrates seamlessly with Laravel’s frontend assets (Vite, Mix) and works in both Boost and skills.sh environments.
- What Laravel versions are supported?
- Officially supports Laravel 12+. For older versions, use `skills.sh` (no Boost dependency) but expect limited AI-driven feedback. Spatie recommends upgrading to Laravel 12+ for full compatibility.
- How do I handle false positives in security checks?
- Configure whitelists in your skills config (e.g., `allowed_functions`) or use `skills.sh audit --verbose` to review flags. Document exceptions in `CONTRIBUTING.md` and train your team to recognize legitimate edge cases.
- Is this package suitable for small teams or startups?
- Absolutely. The modular design lets you adopt only relevant skills (e.g., skip `spatie-security` if your stack is simple). It’s non-invasive, reducing overhead for smaller teams while still enforcing best practices.
- How often should I update this package?
- Schedule quarterly updates aligned with Spatie’s release cycle. Use `composer update spatie/guidelines-skills` and `boost:update` to sync. Monitor the [changelog](https://github.com/spatie/guidelines-skills/blob/main/CHANGELOG.md) for breaking changes.
- What alternatives exist for Laravel coding standards?
- Alternatives include PHP-CS-Fixer (PSR-12 only), Laravel Pint (built-in formatter), or custom ESLint/PHPStan rules. However, Spatie’s package uniquely combines AI-driven feedback (via Boost), security, and Git conventions in one tool—ideal for teams wanting end-to-end standardization.
Weaver
How can I help you explore Laravel packages today?