Laravel software architect following Taylor Otwell's philosophy. Use when designing features, reviewing architecture decisions, creating models/controllers, or when the user asks about Laravel patterns, services, repositories, or "the Laravel way." Activates for questions about Filament, Spatie packages, or Inertia+React architecture.
Expert Laravel security auditor. Use proactively after code changes in PHP/Laravel files.
Use this agent when the user needs to write, run, or debug browser tests using Pest's browser testing (Pest) plugin. This includes end-to-end testing, UI interaction testing, form submissions, navigation flows, JavaScript-dependent features, and any test that requires a real browser environment.
TDD and Pest PHP expert for Laravel. Use PROACTIVELY when writing tests, implementing features with TDD, running test suites, doing arch testing, mutation testing, or following RED-GREEN-REFACTOR cycle. Delegates automatically for any testing-related task in Laravel/PHP projects.
Review code against project rules. Use when reviewing code quality or ensuring compliance with conventions.
Copies rules from skill to the project. Use it when user asks you to copy the rules into the project.
Creates a new Laravel project from scratch. Use when the user ask to create a new project.
Initializes project with necessary files and structure. Use it when user asks to setup the project.
Conducts in-depth technical interviews about implementation plans. Use when the user wants to be interviewed about a plan, spec, or feature before implementation, or when they say "interview me" or "let's discuss the plan".
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for PHP and Laravel developers. This plugin provides agents, skills, and coding rules tailored for Laravel development.
# Add the marketplace
/plugin marketplace add guetteman/claude-code
# Install the plugin
/plugin install laravel@guetteman
A senior Laravel software architect following Taylor Otwell's philosophy: "Code should be like Kenny from South Park, not T1000 from Terminator—disposable, easy to change."
Use when designing features, reviewing architecture decisions, or when you need guidance on "the Laravel way."
An elite TDD specialist using Pest PHP. Activates for writing tests, implementing features with TDD, running test suites, architecture testing, and mutation testing. Follows the sacred RED-GREEN-REFACTOR cycle.
Reviews Laravel code for security vulnerabilities and best practices.
Reviews code against all project rules. Spawns parallel agents to check each rule file and provides a summary of violations with fix suggestions.
Creates a new Laravel project from scratch with Herd integration. Guides you through project setup including authentication preferences and Herd configuration.
Starts a new feature in a dedicated branch following the feature/<feature-name> convention. Activates plan mode, conducts an interview, validates the plan with architect, TDD, and security agents, then saves the spec to specs/.
Conducts in-depth technical interviews about implementation plans before coding begins. Helps refine and validate your approach by exploring edge cases, failure modes, and tradeoffs.
Copies the plugin's rules to your project's .claude/rules directory. A convenient alternative to manually copying or symlinking rules.
Initializes your Laravel project with a Makefile, PHPStan (via Larastan), Pint, and Rector configuration files. Runs formatting and static analysis after setup.
This plugin includes opinionated coding rules organized by category:
accessors-mutators - Prefer attribute casting over accessors/mutatorsapi-resource-resolution - API resource resolution patternsarrayable-iterations - Iterating over Arrayable objectsclass-imports - Import conventionscollection-higher-order-messages - Use higher-order messages for simple operationsdatabase-transactions - Database transaction best practicesform-request-authorization - Form request authorization patternslocal-scopes - Eloquent local scope conventionsresource-collections - API resource collection patternssingle-action-controllers - When to use invokable controllersassert-database-empty - Database emptiness assertionsavoid-and-modifier - Avoid the and() modifierchained-higher-order-expectations - Chain expectations elegantlydatabase-assertions-use-models - Use models in database assertionsfactory-count-syntax - Factory count syntax preferencesfactory-relationships - Factory relationship patternshigher-order-expectations - Use higher-order expectationsmagic-factory-relationships - Magic factory relationship methodsminimize-refresh-usage - Minimize model refresh callsmocking - Mocking best practicestest-file-location - Test file organizationuse-pest-functions - Use Pest standalone functions instead of $this-> method callsuse-test-function - Use test() over it()array-destructuring - Array destructuring conventionsenum-options - Enum options in Filament formscommits - Commit message conventionsCurrent Limitation: Claude Code plugins do not yet support automatic distribution of rules. The rules included in this plugin will not be automatically applied to your projects.
To use the rules, you need to manually copy them to your project's .claude/rules directory:
# Copy all rules to your project
cp -r ~/.claude/plugins/marketplaces/guetteman/plugins/laravel/rules/* /path/to/your/project/.claude/rules/
# Or copy specific categories
cp -r ~/.claude/plugins/marketplaces/guetteman/plugins/laravel/rules/laravel/* /path/to/your/project/.claude/rules/laravel/
cp -r ~/.claude/plugins/marketplaces/guetteman/plugins/laravel/rules/pest/* /path/to/your/project/.claude/rules/pest/
Alternatively, you can symlink the rules directory if you want to keep them in sync:
ln -s ~/.claude/plugins/marketplaces/guetteman/plugins/laravel/rules /path/to/your/project/.claude/rules
npx claudepluginhub guetteman/claude-code --plugin laravelLaravel-focused skills for Claude Code: TDD (Pest/PHPUnit), migrations, queues, quality checks (Pint/Insights), and pragmatic architecture patterns — Sail and non-Sail compatible.
Expert Laravel 12 + PHP 8.5 with SOLID principles, Eloquent, Livewire, and comprehensive documentation
Production-grade rules and workflows for Laravel REST APIs built with essa/api-tool-kit. 21 rule files and 8 guided workflows covering every layer of a Laravel API including DDD support.
Claude Code plugin channeling Taylor Otwell's Laravel philosophy
Specialized Claude Code subagents and skills for Laravel development — architecture, Eloquent, API, testing, security, performance, debugging, and more.
Proactive Pest 4 testing for PHP, Laravel, Livewire, and Filament apps. Auto-generates tests for models, controllers, policies, and Livewire components. Analyzes coverage gaps and runs test suites with detailed reporting.