This project uses codebar-ag/coding-guidelines (Composer dev dependency). Laravel Boost indexes the app and syncs editor/MCP assets; the guidelines supply shared rules and skills for assistants.
Git: .claude/, .cursor/, .junie/, root .mcp.json, and CLAUDE.md are gitignored (regenerated by Boost). This file stays in the repo as the project index; run php artisan boost:install and php artisan boost:update after composer install on a fresh clone so your editor and Claude Code receive skills and MCP config.
| What | Where |
|---|---|
| Rule index | vendor/codebar-ag/coding-guidelines/RULES.md |
| Skill playbooks | vendor/codebar-ag/coding-guidelines/resources/boost/skills/**/SKILL.md |
| Project overrides | .ai/skills/{skill-name}/SKILL.md (optional; overrides package skills) |
After composer install, vendor/codebar-ag/coding-guidelines resolves from this repo’s path package under packages/coding-guidelines.
Use the same role set as upstream: ArchitectAgent, BackendImplementationAgent, FrontendImplementationAgent, ImplementationAgent, RefactorAgent, TestAgent, ReviewAgent, DocumentationAgent. Full descriptions and example prompts live in the package’s AGENTS.md (same paths as above, under vendor/.../AGENTS.md).
Ask your assistant:
Act as ReviewAgent. Using
RULES.mdand all skills underresources/boost/skills/**/SKILL.mdfrom codebar-ag/coding-guidelines, review this diff and produce: (1) a short assessment, (2) a file-grouped refactor plan, (3) a few copy-pasteable suggestions.
Register and refresh Boost’s guidelines/skills (from a local app environment—Boost does not load when APP_ENV=testing):
php artisan boost:install
php artisan boost:updateSee the coding-guidelines README for Boost, MCP, and CI options.