- How do I install and use sandermuller/boost-skills in a Laravel project?
- Install via Composer with `composer require sandermuller/boost-skills`, then configure a sync engine like `laravel/boost` or `boost-core` to push the Markdown skills to your AI agent (e.g., Claude, Cursor). No PHP code changes are needed—skills are static files consumed by the sync engine.
- Does this package work with Laravel 10/11, or only newer versions?
- The package itself is framework-agnostic and requires no Laravel-specific runtime code, so it works with any Laravel version. However, the sync engines (`laravel/boost` or `boost-core`) may have version requirements—check their docs for compatibility with your Laravel install.
- Can I customize or extend the skills without breaking the sync?
- Yes, skills are modular and tag-gated (e.g., `laravel`, `phpunit`). You can fork the package, modify Markdown files, or add your own `.ai/skills/` folder. The sync engine will merge them if configured to scan local directories or allowed vendors.
- What AI agents does this package support out of the box?
- The package itself doesn’t enforce agent support—it provides Markdown skills for AI tools like Claude, Cursor, Copilot, or Gemini. However, you’ll need a sync engine (`boost-core` or `laravel/boost`) to push skills to your specific agent, which may require additional configuration for authentication or API access.
- Are there performance concerns with syncing skills to AI agents?
- Syncing Markdown skills adds minimal overhead, but latency depends on the sync engine and AI agent’s API. Test in a non-production environment first, especially if skills include large workflows (e.g., deployment checklists). Monitor response times and costs if using paid AI services.
- How do I handle conflicts if my team already uses GitHub Copilot or another AI tool?
- Skills are agent-agnostic but may conflict with existing plugins (e.g., Copilot extensions). Audit your current AI tooling before integrating. Use `withAllowedVendors()` in `boost-core` to restrict skills to specific packages, or manually curate a subset to avoid overlaps.
- What happens if boost-core or laravel/boost stops being maintained?
- The package is zero-runtime, so you can fork `boost-core` or `laravel/boost` to maintain compatibility. Alternatively, treat the skills as reference documentation and manually integrate them into your workflows. The Markdown format ensures portability.
- Can I use this package without Laravel, e.g., in a Symfony or plain PHP project?
- Yes, the package is Composer-based and framework-agnostic. However, some skills are tagged for Laravel (e.g., Artisan commands, migrations). Prune or ignore those tags if you’re not using Laravel, or use the generic skills (e.g., code review, testing) for any PHP project.
- How do I test if the skills improve my AI agent’s responses in Laravel?
- Start with a small pilot: install `sandermuller/boost-skills` and `laravel/boost`, sync skills to one AI agent (e.g., Claude), and test responses for Laravel-specific tasks (e.g., debugging migrations, optimizing queries). Compare results with and without skills to measure impact.
- Are there alternatives to boost-skills for Laravel AI integration?
- For Laravel-native AI integration, consider `laravel/boost` (bundled skills) or custom solutions like GitHub Copilot plugins. For generic AI skills, explore other Composer packages with `resources/boost/skills/` or build your own Markdown catalog. Evaluate based on your AI agent’s compatibility and maintenance needs.