Composer-01

Overview AI coding agents are shifting from simple autocomplete helpers to sophisticated architectural assistants. This transition demands a new set of workflows that prioritize context over raw syntax. For Laravel developers, this means moving beyond basic copilot functionality and embracing tools that understand the framework's specific conventions. By utilizing Laravel Boost and high-level agents like Cursor, Claude Code, and Codex CLI, developers can automate the repetitive scaffolding of CRUD operations, validation logic, and API resources while maintaining strict control over the code quality. Prerequisites To follow this guide effectively, you should possess a baseline understanding of the following: * **PHP & Laravel**: Familiarity with Eloquent models, migrations, and API resource structures. * **Terminal Proficiency**: Ability to run composer commands and navigate CLI interfaces. * **Git Basics**: Understanding of branching and commits, as AI-generated code should always be tracked for easy rollback. * **Node/NPM**: Required for installing various CLI-based agents. Key Libraries & Tools * **Laravel Boost**: A specialized package that generates `.mdc` and `.md` guideline files to ensure AI models follow modern Laravel conventions. * **Cursor**: A fork of VS Code that integrates AI deep into the editor's UI for "tab-tab-tab" workflows. * **Claude Code**: An agent from Anthropic that operates entirely within the terminal, focusing on agentic task completion. * **Codex CLI**: OpenAI's command-line interface powered by GPT-4o (and later versions) for high-accuracy code generation. * **Laravel Idea**: A powerful plugin for PHPStorm that provides deep framework integration. Solving the Context Problem with Laravel Boost The primary failure point for AI is "stale knowledge." Models trained on Laravel 11 might hallucinate syntax when working in a Laravel 12 environment. Laravel Boost solves this by injecting your specific project context into the AI's prompts. When you run the installation command, the package scans your `composer.json` to detect exactly which versions of Livewire, Tailwind, or Pest you are using. It then generates specific guideline files for your IDE of choice. This ensures the AI doesn't suggest outdated patterns like `DB::table()` when your team prefers modern Eloquent query builders. ```bash composer require laravel-boost php artisan boost:install ``` Code Walkthrough: Generating a CRUD API When using an agent like Cursor, the most efficient path is a combination of manual scaffolding and AI refinement. Instead of asking the AI to build everything from scratch, start with the core model and migration. 1. Scaffolding the Core Run the standard Artisan command to ensure the foundation is deterministic. ```bash php artisan make:model Post -m ``` 2. Defining the Migration with AI Autocomplete Open the migration file and let the AI suggest fields. By simply hitting `Tab`, the AI recognizes common Laravel patterns like `user_id` foreign keys and `string` title fields based on the model name. 3. Agentic Resource Generation Open the Agent window (`Cmd+I`) and provide a high-context prompt. Specifying the use of Form Requests is critical to avoid bloated controllers. ```markdown Generate a CRUD API for the Post model. - Use API Resources for the response. - Place validation in separate Form Request classes. - Ensure the controller is in the API namespace. ``` 4. Refining the Resource If the generated PostResource includes sensitive data like timestamps, you can use Claude Code to refine it without leaving the terminal: ```bash Inside Claude Code CLI In @app/Http/Resources/PostResource.php, remove the created_at and updated_at fields from the return array. ``` Syntax Notes * **Slash Commands**: Agents like Claude Code use commands like `/usage` to monitor token limits or `/clear` to reset the context window. * **Markdown Guidelines**: Most agents look for a `.cursorrules` or `claude.md` file. These are standard Markdown files that dictate coding style, such as "Use Pest for testing" or "Prefer constructor injection." * **MCP (Model Context Protocol)**: Some tools use MCP to allow the AI to search documentation or run local commands directly. Practical Examples * **Test-Driven Scaffolding**: Use Codex CLI to generate both the controller and a corresponding Pest test suite. The agent will run the tests automatically and fix the code until they pass. * **Plan Mode Execution**: For complex features like a multi-step checkout, enter "Plan Mode." This allows you to verify the AI's architectural logic (e.g., service classes vs. jobs) before any files are actually modified. Tips & Gotchas * **Vibe Coding vs. Precision**: Avoid long-running chat sessions. As the conversation grows, the "context pollution" increases, leading to hallucinations and higher token costs. Use the `/new` command or open a new chat window for every distinct task. * **Pricing Horror Stories**: Cursor pricing can be volatile if you use expensive models like Claude 3.5 Sonnet for small tasks. Monitor your dashboard frequently. For minor refactors, switch to cheaper models like Grok Code or Composer-01. * **Git Integration**: Always commit your work before triggering an agent. While Cursor offers an "Undo" button, it only reverts the most recent block of changes. A Git rollback is the only reliable way to recover from an AI that has accidentally modified 20 different files.