Laravel toolkit

Copy this plugin's path-scoped rules into the current project's .claude/rules/

Use this agent when writing, modifying, or refactoring PHP/Laravel backend code in this project, including controllers, models, migrations, services, form requests, API resources, Eloquent queries, jobs, events, listeners, and related backend infrastructure. This agent should be invoked proactively whenever backend work is needed to ensure code adheres to project standards, leverages installed Laravel skills, and follows separation of concerns principles.\n\n<example>\nContext: User needs a new endpoint to manage partner discounts.\nuser: "I need an API endpoint to let partners update their discount tiers"\nassistant: "I'm going to use the Agent tool to launch the laravel-backend-specialist agent to design and implement this endpoint following the project's Laravel conventions."\n<commentary>\nThis is a backend task involving routes, controllers, validation, and Eloquent models. The laravel-backend-specialist should handle it to ensure proper separation of concerns and adherence to project standards.\n</commentary>\n</example>\n\n<example>\nContext: User is adding a new feature that requires database changes.\nuser: "Add a 'verified_at' timestamp to partners and a scope to filter verified ones"\nassistant: "Let me use the Agent tool to launch the laravel-backend-specialist agent to create the migration, update the model, and add the scope properly."\n<commentary>\nMigration and model changes are backend Laravel work. The specialist agent will use proper artisan commands and follow project conventions.\n</commentary>\n</example>\n\n<example>\nContext: User has just described a frontend change that also requires backend support.\nuser: "The dashboard needs to display the partner's monthly revenue"\nassistant: "I'll start with the backend work first. Let me use the Agent tool to launch the laravel-backend-specialist agent to build the data layer and Inertia props."\n<commentary>\nProactively delegate the backend portion to the specialist to ensure proper data shaping, query optimization, and adherence to project patterns before frontend work begins.\n</commentary>\n</example>

Use when adding an audit trail, recording who did what, logging login or model events, or tracking changes with spatie/laravel-activitylog v5 — keywords spatie activitylog, activity log, LogsActivity trait, causedBy, performedOn, withProperties, activity_log table, getActivitylogOptions, logOnlyDirty, ActivityEvent, beforeLogging, custom column grouping, organisation scoping.

Thin HTTP-layer controllers with zero domain logic. Use when creating or modifying controllers, handling HTTP concerns, or structuring web vs API layers.

Laravel database optimization patterns. Use when writing Eloquent queries, creating migrations, configuring caching, debugging slow queries, or optimizing database performance. Triggers on tasks involving N+1 queries, indexing, Redis caching, pagination, or database transactions.

Data Transfer Objects using Spatie Laravel Data. Use when creating or modifying DTOs, data objects, formatters, transformers, or structured data handling.

Backed enums with labels and business logic. Use when defining or modifying enums, status values, or fixed option sets.