Adding agenteq to a Laravel Boost Project

1. What this produces

.ai/GUIDELINES.md holding only hand-authored project guidance. It never holds Boost's own <laravel-boost-guidelines> block.
.ai/mcp/<name>/config.json for every MCP server already configured for any agent. This includes .ai/mcp/laravel-boost/config.json when Boost's own MCP server is in use.
.ai/commands/** for every command file already configured for any agent. Boost has no commands feature. Every command file found here is hand-authored, agent-native content.
.ai/skills/, .ai/guidelines/, and .ai/rules left exactly as Boost put them. These are Boost's own canonical directories. They are not agenteq's. agenteq detects boost.json's skills field on its own and drops the skills capability from its sync for this project. Skills stay entirely under Boost's own management.
An agenteq.json file recording the chosen agents and capabilities. The capabilities are mcp, commands, and guidelines. They do not include skills.
Every generated per-agent file git ignored. This includes Boost's own per-agent files, wherever they were not already git ignored.
Boost's own composer post-install-cmd/post-update-cmd wiring extended to run npx agenteq sync --yes right after Boost's own command, when that wiring already exists.
Any existing git hook that already calls Boost, extended the same way.

Check for boost.json at the project root. It must parse as JSON with at least an agents array. For example: