systematic-debugging-laravel

10 Laravel-Specific Agents

Development:

• laravel-architect - Application architecture and design patterns expert
• eloquent-specialist - Database design, models, relationships, and query optimization
• laravel-api-developer - RESTful API development with Sanctum/Passport

Quality & Testing:

• laravel-testing-expert - Pest PHP, PHPUnit, and comprehensive testing strategies
• laravel-code-reviewer - Code quality, Laravel best practices, and PR reviews
• laravel-architecture-reviewer - Architecture evaluation and design validation

Debugging & Performance:

• laravel-debugger - Systematic debugging and issue diagnosis
• laravel-performance-optimizer - Performance optimization, caching, and scaling

Security & Documentation:

• laravel-security-auditor - Security best practices and vulnerability detection
• laravel-documentation-engineer - API documentation and technical guides

5 Laravel Development Skills

Development Workflows:

• laravel-tdd - Test-driven development for Laravel with Pest PHP
• brainstorming - Collaborative feature design and planning for Laravel
• systematic-debugging - Systematic debugging process for Laravel applications

Best Practices:

• eloquent-best-practices - Eloquent ORM patterns and optimization
• api-resource-patterns - API resource and collection best practices

• PHP 8.1 or higher
• Laravel 10.0 or 11.0
• Claude Code

Install the package via Composer:

```bash

composer require iserter/laravel-claude-agents

```

Publish the Claude AI agents and skills to your project root:

```bash

php artisan claude-agents:publish

```

This will create a .claude directory in your project root containing all agents and skills.

Merging with Existing Files

If a .claude directory already exists in your project:

• Without --force: New files from the package will be added, but existing files will be preserved (not overwritten). This allows you to keep your custom modifications.

```bash

php artisan claude-agents:publish

```

• With --force: New files will be added and existing files will be updated to match the package versions, while your custom agent/skill files remain untouched.

```bash

php artisan claude-agents:publish --force

```

After running the publish command, you'll have:

```

your-project/

├── .claude/

│ ├── agents/

│ │ ├── laravel-debugger.md

│ │ ├── laravel-architect.md

│ │ ├── laravel-code-reviewer.md

│ │ ├── eloquent-specialist.md

│ │ ├── laravel-documentation-engineer.md

│ │ ├── laravel-api-developer.md

│ │ ├── laravel-security-auditor.md

│ │ ├── laravel-performance-optimizer.md

│ │ ├── laravel-testing-expert.md

│ │ └── laravel-architecture-reviewer.md

│ └── skills/

│ ├── systematic-debugging/

│ ├── eloquent-best-practices/

│ ├── api-resource-patterns/

│ ├── laravel-tdd/

│ └── brainstorming/

```

Once published, Claude Code automatically detects and loads the subagents. You can:

Invoke them explicitly:

```

> Ask the laravel-architect to design the authentication system

> Have eloquent-specialist optimize the user queries

> Get laravel-security-auditor to review the API endpoints

```

Let Claude decide automatically:

```

> Create a RESTful API for blog posts with authentication

(Claude will automatically use laravel-api-developer)

> Optimize the dashboard query performance

(Claude will automatically use eloquent-specialist and laravel-performance-optimiz