laravel-claude

Run common Laravel Artisan commands quickly. Use /artisan make:model, /artisan migrate, etc.

Review code for Laravel best practices, security issues, and performance problems.

Run Laravel tests. Use /test to run all tests, /test --filter=name for specific tests.

Use this agent when designing, building, or improving APIs in Laravel applications. This includes designing RESTful endpoints, creating API resources and collections, implementing authentication (Sanctum/Passport), handling versioning, designing GraphQL schemas, and ensuring API best practices. The agent helps create consistent, well-documented, and developer-friendly APIs. Examples: <example> Context: User needs to design a new API. user: "I need to build a REST API for our mobile app" assistant: "I'll use the api-designer agent to design a comprehensive RESTful API with proper authentication, resource structure, and documentation." <Task tool invocation to launch api-designer agent> </example> <example> Context: User wants to add authentication to their API. user: "How should I secure my API endpoints?" assistant: "I'll use the api-designer agent to implement proper API authentication using Laravel Sanctum or Passport, depending on your requirements." <Task tool invocation to launch api-designer agent> </example> <example> Context: User needs API versioning. user: "We need to release v2 of our API without breaking existing clients" assistant: "I'll use the api-designer agent to implement a versioning strategy that maintains backward compatibility while allowing new features." <Task tool invocation to launch api-designer agent> </example> <example> Context: User wants to improve API responses. user: "Our API responses are inconsistent and hard to work with" assistant: "I'll use the api-designer agent to standardize your API responses using Laravel Resources and establish consistent response patterns." <Task tool invocation to launch api-designer agent> </example>

Use this agent for thorough code reviews of Laravel applications. It analyzes code for security vulnerabilities, performance issues, Laravel best practices, SOLID principles, and maintainability concerns. The agent provides actionable feedback with specific suggestions for improvement. Examples: <example> Context: User wants a pull request reviewed. user: "Can you review the changes in my feature branch?" assistant: "I'll use the code-reviewer agent to perform a comprehensive review of your changes, checking for security issues, performance problems, and adherence to Laravel best practices." <Task tool invocation to launch code-reviewer agent> </example> <example> Context: User wants a specific file reviewed. user: "Review my OrderController for any issues" assistant: "I'll use the code-reviewer agent to thoroughly analyze your OrderController for potential improvements." <Task tool invocation to launch code-reviewer agent> </example> <example> Context: User is preparing for production deployment. user: "We're about to deploy to production, can you check for any critical issues?" assistant: "I'll use the code-reviewer agent to perform a pre-deployment review focusing on security, error handling, and production readiness." <Task tool invocation to launch code-reviewer agent> </example> <example> Context: User inherited legacy code. user: "I inherited this codebase and want to understand what needs fixing" assistant: "I'll use the code-reviewer agent to audit the codebase and identify technical debt, security concerns, and areas needing improvement." <Task tool invocation to launch code-reviewer agent> </example>

Use this agent for database-related tasks in Laravel applications. This includes designing schemas, writing migrations, optimizing queries, planning indexes, analyzing slow queries, setting up relationships, and resolving database performance issues. The agent understands MySQL, PostgreSQL, and SQLite. Examples: <example> Context: User needs to design a database schema. user: "I need to design the database for an e-commerce platform" assistant: "I'll use the database-expert agent to design a normalized schema with proper relationships, indexes, and migrations for your e-commerce platform." <Task tool invocation to launch database-expert agent> </example> <example> Context: User has slow database queries. user: "My product listing page takes 5 seconds to load" assistant: "I'll use the database-expert agent to analyze your queries, identify missing indexes, and optimize the slow queries." <Task tool invocation to launch database-expert agent> </example> <example> Context: User needs complex migrations. user: "I need to split the users table into users and profiles without losing data" assistant: "I'll use the database-expert agent to plan a safe migration strategy that preserves all data while restructuring your tables." <Task tool invocation to launch database-expert agent> </example> <example> Context: User has N+1 query issues. user: "Laravel Debugbar shows I'm making 200 queries on one page" assistant: "I'll use the database-expert agent to identify the N+1 problems and implement proper eager loading." <Task tool invocation to launch database-expert agent> </example>

Use this agent when troubleshooting errors, unexpected behavior, or bugs in Laravel applications. The agent analyzes error messages, stack traces, logs, and code to identify root causes and suggest fixes. It can help with HTTP errors, database issues, queue failures, authentication problems, and general debugging. Examples: <example> Context: User encounters an error. user: "I'm getting a 500 error on the checkout page" assistant: "I'll use the debugger agent to investigate the 500 error by checking your logs, examining the checkout code, and identifying the root cause." <Task tool invocation to launch debugger agent> </example> <example> Context: User has a stack trace to analyze. user: "Can you help me understand this error? [pastes stack trace]" assistant: "I'll use the debugger agent to analyze this stack trace and explain what's happening and how to fix it." <Task tool invocation to launch debugger agent> </example> <example> Context: User has unexpected behavior. user: "My form submission works locally but fails in production" assistant: "I'll use the debugger agent to investigate environment-specific issues that could cause this discrepancy." <Task tool invocation to launch debugger agent> </example> <example> Context: User has queue job failures. user: "My jobs keep failing after a few seconds" assistant: "I'll use the debugger agent to examine your job code, check for timeout issues, and identify why the jobs are failing." <Task tool invocation to launch debugger agent> </example>

Use this agent when documentation needs to be created, reviewed, or improved. This includes README.md files, CHANGELOG.md files, inline code documentation for phpDocumentor compatibility, API documentation, and any other technical documentation. Also use this agent to audit existing documentation for accuracy and completeness, or to provide guidance on documentation best practices.\n\n<example>\nContext: The user has just completed a new feature and needs documentation.\nuser: "I just finished implementing the user authentication module"\nassistant: "Great work on the authentication module! Let me use the documentation expert to help create proper documentation for this feature."\n<commentary>\nSince a significant feature was completed, use the Task tool to launch the docs-expert agent to review the code and create appropriate documentation including README updates and phpDocumentor-compatible inline comments.\n</commentary>\nassistant: "Now let me use the docs-expert agent to document this authentication module"\n</example>\n\n<example>\nContext: The user wants to ensure their project documentation is accurate.\nuser: "Can you check if my README accurately describes the project?"\nassistant: "I'll use the documentation expert to audit your README against the actual codebase."\n<commentary>\nSince the user wants documentation verification, use the Task tool to launch the docs-expert agent to cross-reference the README with the actual code and identify any discrepancies.\n</commentary>\n</example>\n\n<example>\nContext: The user is preparing a release and needs changelog updates.\nuser: "I'm about to release version 2.1.0"\nassistant: "Let me bring in the documentation expert to help prepare the CHANGELOG.md for this release."\n<commentary>\nSince a release is being prepared, use the Task tool to launch the docs-expert agent to review recent changes and create accurate changelog entries following proper conventions.\n</commentary>\n</example>\n\n<example>\nContext: The user has PHP code that needs proper docblocks.\nuser: "My PHP classes need better documentation for phpDocumentor"\nassistant: "I'll use the documentation expert to analyze your PHP classes and provide guidance on proper phpDocumentor-compatible documentation."\n<commentary>\nSince the user needs phpDocumentor-compatible documentation, use the Task tool to launch the docs-expert agent to review the code structure and provide specific docblock recommendations.\n</commentary>\n</example>