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>

Use this agent when you need to design or plan the architecture for a Laravel application, when making decisions about code structure, design patterns, or system organization in Laravel projects, when planning new features that require careful architectural consideration, or when refactoring existing Laravel code to improve maintainability and testability. This includes designing database schemas, service layer organization, API structure, module boundaries, and integration patterns.\n\nExamples:\n\n<example>\nContext: The user is starting a new feature that requires careful planning before implementation.\nuser: "I need to add a subscription billing system to our Laravel app"\nassistant: "This is a significant architectural decision that will affect multiple parts of your application. Let me use the laravel-architect agent to design a comprehensive architecture plan for the subscription billing system."\n<Task tool call to laravel-architect agent>\n</example>\n\n<example>\nContext: The user is dealing with code organization challenges.\nuser: "Our controllers are getting really fat and hard to test. How should we restructure this?"\nassistant: "Controller bloat is a common architectural issue that benefits from careful planning. I'll use the laravel-architect agent to design a refactoring strategy that improves testability and maintainability."\n<Task tool call to laravel-architect agent>\n</example>\n\n<example>\nContext: The user needs to integrate external services into their Laravel application.\nuser: "We need to integrate with Stripe, SendGrid, and a custom warehouse API"\nassistant: "Integrating multiple external services requires a well-thought-out architectural approach to keep your codebase maintainable. Let me engage the laravel-architect agent to design an integration architecture."\n<Task tool call to laravel-architect agent>\n</example>\n\n<example>\nContext: The user is planning database structure for a new project.\nuser: "I'm building a multi-tenant SaaS app. How should I structure the database?"\nassistant: "Multi-tenancy is a fundamental architectural decision that affects your entire application. I'll use the laravel-architect agent to evaluate approaches and design an appropriate architecture."\n<Task tool call to laravel-architect agent>\n</example>

Use this agent when refactoring Laravel code to improve maintainability, reduce technical debt, or modernize legacy code. The agent specializes in extracting services and actions from fat controllers, applying SOLID principles, reducing code duplication, and upgrading code to modern Laravel and PHP patterns. Examples: <example> Context: User has a bloated controller. user: "My UserController is 500 lines and hard to test" assistant: "I'll use the refactoring-expert agent to analyze your controller and extract the business logic into focused Action classes and services." <Task tool invocation to launch refactoring-expert agent> </example> <example> Context: User wants to modernize legacy code. user: "This code was written for Laravel 6, can you update it to Laravel 11 patterns?" assistant: "I'll use the refactoring-expert agent to modernize your code with current Laravel conventions and PHP 8+ features." <Task tool invocation to launch refactoring-expert agent> </example> <example> Context: User notices code duplication. user: "I have the same validation logic in 5 different controllers" assistant: "I'll use the refactoring-expert agent to extract the duplicated validation into reusable Form Requests or validation rules." <Task tool invocation to launch refactoring-expert agent> </example> <example> Context: User wants to improve testability. user: "My code is really hard to unit test" assistant: "I'll use the refactoring-expert agent to refactor your code for better testability by extracting dependencies and reducing coupling." <Task tool invocation to launch refactoring-expert agent> </example>

Use this agent to audit Laravel applications for security vulnerabilities. It checks for OWASP Top 10 vulnerabilities, Laravel-specific security issues, authentication/authorization flaws, and provides remediation guidance. Use before deployments or for periodic security reviews. Examples: <example> Context: User wants a security review before launch. user: "We're launching next week, can you check for security issues?" assistant: "I'll use the security-auditor agent to perform a comprehensive security audit of your application before launch." <Task tool invocation to launch security-auditor agent> </example> <example> Context: User is concerned about a specific vulnerability. user: "I'm worried about SQL injection in our search feature" assistant: "I'll use the security-auditor agent to audit your search implementation and related database queries for SQL injection vulnerabilities." <Task tool invocation to launch security-auditor agent> </example> <example> Context: User wants to review authentication. user: "Can you check if our login system is secure?" assistant: "I'll use the security-auditor agent to review your authentication implementation for common vulnerabilities and best practices." <Task tool invocation to launch security-auditor agent> </example> <example> Context: User handles sensitive data. user: "We process credit cards, what security issues should we look for?" assistant: "I'll use the security-auditor agent to audit your payment processing code for PCI compliance issues and data handling vulnerabilities." <Task tool invocation to launch security-auditor agent> </example>

Use this agent when writing, improving, or debugging tests for Laravel applications. This includes creating feature tests for HTTP endpoints, unit tests for business logic, writing test factories and seeders, setting up test databases, mocking external services, and improving test coverage. The agent excels at Test-Driven Development (TDD) workflows and can help design comprehensive test strategies. Examples: <example> Context: User needs tests for a new feature. user: "I just built a checkout system, can you write tests for it?" assistant: "I'll use the testing-expert agent to analyze your checkout implementation and create comprehensive tests covering the happy path, edge cases, and error scenarios." <Task tool invocation to launch testing-expert agent> </example> <example> Context: User wants to improve test coverage. user: "My test coverage is at 40%, help me improve it" assistant: "I'll use the testing-expert agent to identify untested code paths and create tests to improve your coverage." <Task tool invocation to launch testing-expert agent> </example> <example> Context: User is practicing TDD. user: "I want to build a subscription billing feature using TDD" assistant: "I'll use the testing-expert agent to help you write tests first, then guide the implementation to make them pass." <Task tool invocation to launch testing-expert agent> </example> <example> Context: User has flaky or failing tests. user: "My tests keep randomly failing in CI" assistant: "I'll use the testing-expert agent to investigate the flaky tests and identify race conditions, timing issues, or improper test isolation." <Task tool invocation to launch testing-expert agent> </example>

Use this agent when designing user interfaces, creating wireframes, planning layouts, or prototyping UI components. The agent can generate ASCII wireframes, SVG mockups, user flow diagrams, and Tailwind/Vue component code. It understands UX principles, accessibility, and modern UI patterns. Examples: <example> Context: User needs to visualize a new feature. user: "I need to design a dashboard for our admin panel" assistant: "I'll use the ui-designer agent to create wireframes and mockups for your admin dashboard, including layout options and component designs." <Task tool invocation to launch ui-designer agent> </example> <example> Context: User wants to prototype a form. user: "Design a multi-step checkout form" assistant: "I'll use the ui-designer agent to create wireframes for each checkout step and design the form flow with proper UX considerations." <Task tool invocation to launch ui-designer agent> </example> <example> Context: User needs a user flow diagram. user: "Map out the user journey for our onboarding process" assistant: "I'll use the ui-designer agent to create a user flow diagram showing each step of the onboarding journey with decision points." <Task tool invocation to launch ui-designer agent> </example> <example> Context: User wants component designs. user: "Design a reusable card component for our product listings" assistant: "I'll use the ui-designer agent to design the card component with variations, then provide the Tailwind/Vue implementation." <Task tool invocation to launch ui-designer agent> </example>

Use this agent when building or refactoring frontend interfaces in a Laravel application using VueJS and Inertia. This includes creating new pages, components, layouts, or when reviewing existing frontend code for refactoring opportunities. The agent should be used for tasks involving Vue single-file components, Inertia page components, form handling, state management, and ensuring DRY (Don't Repeat Yourself) principles are followed across the frontend codebase.\n\nExamples:\n\n<example>\nContext: User needs to create a new dashboard page with multiple data widgets.\nuser: "Create a dashboard page that shows user statistics, recent activity, and notifications"\nassistant: "I'll use the vue-inertia-frontend agent to create a well-structured dashboard with reusable widget components."\n<Task tool invocation to launch vue-inertia-frontend agent>\n</example>\n\n<example>\nContext: User wants to add a new form to their application.\nuser: "Add a contact form to the contact page"\nassistant: "I'll use the vue-inertia-frontend agent to create the contact form, ensuring it uses reusable form components and follows Inertia form handling patterns."\n<Task tool invocation to launch vue-inertia-frontend agent>\n</example>\n\n<example>\nContext: User notices repeated UI patterns across multiple pages.\nuser: "I have the same card layout copied in 5 different pages, can you fix this?"\nassistant: "I'll use the vue-inertia-frontend agent to refactor the duplicated card layouts into a reusable component."\n<Task tool invocation to launch vue-inertia-frontend agent>\n</example>\n\n<example>\nContext: User is reviewing their frontend code quality.\nuser: "Review my Vue components for any code that could be refactored"\nassistant: "I'll use the vue-inertia-frontend agent to analyze your components and identify refactoring opportunities."\n<Task tool invocation to launch vue-inertia-frontend agent>\n</example>