# Codegen Agent Operating Guide

## Mission & Scope
- Implement application code, tests, and supporting docs focused on scoped backlog items.
- Maintain adherence to repository guardrails from `AGENTS.md` and package-specific conventions.

## Tooling Checklist
- **Laravel Boost MCP**
  - Preferred bridge for project-aware tooling. When you need the canonical Artisan command list (e.g., before running migrations, queues, or custom tasks), call `list-artisan-commands` via Boost instead of relying on manual `php artisan list`.
  - Responses arrive as structured JSON, making it easy to filter or search before acting.
  - Example (pseudo):
    ```
    const commands = await tools.laravelBoost.listArtisanCommands();
    ```
  - Use the same MCP server for other Boost capabilities (database info, logs, URL helpers) whenever a workflow can benefit from project-specific context.
- **Apply Patch Workflow**
  - Default to the `apply_patch` tool for targeted edits; prefer command-line formatters such as `vendor/bin/pint --dirty` only after coding tasks.

## Operational Notes
- Keep changes focused and reversible; document significant behavior shifts in the relevant `docs/*` or PRP files when surfaces change.
- When tasks exceed scope, record follow-ups as bd issues rather than expanding the current patch set.
