
laravel-event-driven-architecture
Best practices for Laravel events and listeners including event discovery, queued listeners, subscribers, and model events for decoupled architecture.
- Installs
- 85
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/iserter/laravel-claude-agents --skill laravel-event-driven-architecture- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads laravel-event-driven-architecture automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Laravel Event-Driven Architecture
Event Class Structure
<?php
namespace App\Events;
use App\Models\Order;
use Illuminate\Broadcasting\InteractsWithSockets;
use Illuminate\Foundation\Events\Dispatchable;
use Illuminate\Queue\SerializesModels;
class OrderPlaced
{
use Dispatchable, InteractsWithSockets, SerializesModels;
public function __construct(
public readonly Order $order,
) {}
}
Listener Class Structure
<?php
namespace App\Listeners;
use App\Events\OrderPlaced;
class SendOrderConfirmation
{
public function handle(OrderPlaced $event): void
{
$event->order->user->notify(
new OrderConfirmationNotification($event->order)
);
}
}
Automatic Listener Discovery
Laravel auto-discovers listeners when they are in the App\Listeners directory and have a handle method type-hinting an event. No manual registration needed.
// ✅ Auto-discovered - just create the class with a typed handle method
class SendOrderConfirmation
{
public function handle(OrderPlaced $event): void { /* ... */ }
}
// ✅ One listener handling multiple events
class AuditLogger
{
public function handleOrderPlaced(OrderPlaced $event): void { /* ... */ }
public function handleOrderCancelled(OrderCancelled $event): void { /* ... */ }
}
// ❌ Won't be discovered - missing type hint
class SendOrderConfirmation
{
public function handle($event): void { /* ... */ }
}
Dispatching Events
// ✅ Using static dispatch
OrderPlaced::dispatch($order);
// ✅ Using event helper
event(new OrderPlaced($order));
// ❌ Calling listeners directly instead of dispatching events
(new SendOrderConfirmation)->handle($order); // Tight coupling
Queued Listeners
use Illuminate\Contracts\Queue\ShouldQueue;
// ✅ Listener runs asynchronously on the queue
class GenerateInvoicePdf implements ShouldQueue
{
public string $queue = 'invoices';
public int $tries = 3;
public array $backoff = [10, 60];
public function handle(OrderPlaced $event): void
{
$pdf = PdfGenerator::fromOrder($event->order);
Storage::put("invoices/{$event->order->id}.pdf", $pdf);
}
public function failed(OrderPlaced $event, \Throwable $exception): void
{
// Handle failure
}
// Conditionally handle
public function shouldQueue(OrderPlaced $event): bool
{
return $event->order->total > 0;
}
}
ShouldQueueAfterCommit
use Illuminate\Contracts\Queue\ShouldQueueAfterCommit;
// ✅ Only dispatched to queue after the database transaction commits
class UpdateSearchIndex implements ShouldQueueAfterCommit
{
public function handle(OrderPlaced $event): void
{
SearchIndex::update('orders', $event->order);
}
}
ShouldDispatchAfterCommit for Transaction Safety
// ✅ Event only dispatches after the surrounding transaction commits
class OrderPlaced
{
use Dispatchable, InteractsWithSockets, SerializesModels;
public $afterCommit = true;
public function __construct(
public readonly Order $order,
) {}
}
// This prevents listeners from running on data that might be rolled back
DB::transaction(function () {
$order = Order::create($data);
OrderPlaced::dispatch($order); // Dispatched only after commit
});
Event Subscribers
<?php
namespace App\Listeners;
use Illuminate\Events\Dispatcher;
class OrderEventSubscriber
{
public function handleOrderPlaced(OrderPlaced $event): void
{
// Log order creation
}
public function handleOrderShipped(OrderShipped $event): void
{
// Send shipping notification
}
public function handleOrderCancelled(OrderCancelled $event): void
{
// Process refund
}
public function subscribe(Dispatcher $events): array
{
return [
OrderPlaced::class => 'handleOrderPlaced',
OrderShipped::class => 'handleOrderShipped',
OrderCancelled::class => 'handleOrderCancelled',
];
}
}
// Register in EventServiceProvider
protected $subscribe = [
OrderEventSubscriber::class,
];
Model Events and Observers
<?php
namespace App\Observers;
use App\Models\Order;
class OrderObserver
{
public function creating(Order $order): void
{
$order->reference = Order::generateReference();
}
public function created(Order $order): void
{
OrderPlaced::dispatch($order);
}
public function updating(Order $order): void
{
if ($order->isDirty('status') && $order->status === 'cancelled') {
$order->cancelled_at = now();
}
}
public function deleted(Order $order): void
{
Storage::deleteDirectory("orders/{$order->id}");
}
}
// Register via model attribute (Laravel 11+)
use Illuminate\Database\Eloquent\Attributes\ObservedBy;
#[ObservedBy(OrderObserver::class)]
class Order extends Model
{
// ...
}
When to Use Events vs Direct Calls
// ✅ USE EVENTS when:
// - Multiple side effects from one action
// - Side effects may change independently
// - Side effects can be async
class OrderService
{
public function place(Order $order): void
{
$order->save();
// Multiple listeners handle: email, invoice, inventory, analytics
OrderPlaced::dispatch($order);
}
}
// ✅ USE DIRECT CALLS when:
// - Core business logic that must succeed together
// - Single clear responsibility
// - Synchronous transactional requirement
class OrderService
{
public function place(Order $order): void
{
DB::transaction(function () use ($order) {
$order->save();
$this->inventoryService->reserve($order); // Must succeed together
});
OrderPlaced::dispatch($order); // Side effects via events
}
}
// ❌ Don't use events for core logic that must not fail silently
// ❌ Don't use events when you need the return value
Testing Events
use Illuminate\Support\Facades\Event;
// ✅ Assert events were dispatched
public function test_placing_order_fires_event(): void
{
Event::fake();
$order = Order::factory()->create();
$this->orderService->place($order);
Event::assertDispatched(OrderPlaced::class, function ($event) use ($order) {
return $event->order->id === $order->id;
});
}
// ✅ Assert event not dispatched
public function test_cancelled_order_does_not_fire_placed(): void
{
Event::fake();
$order = Order::factory()->cancelled()->create();
$this->orderService->place($order);
Event::assertNotDispatched(OrderPlaced::class);
}
// ✅ Fake only specific events, let others run normally
public function test_order_with_real_listeners(): void
{
Event::fake([OrderShipped::class]);
// OrderPlaced listeners will run, OrderShipped will be faked
}
// ✅ Test listener directly
public function test_send_confirmation_listener(): void
{
Notification::fake();
$event = new OrderPlaced(Order::factory()->create());
(new SendOrderConfirmation)->handle($event);
Notification::assertSentTo($event->order->user, OrderConfirmationNotification::class);
}
Checklist
- Events are simple data-carrying objects (no business logic)
- Listeners have a single responsibility each
- Queued listeners used for slow operations (email, PDF, API calls)
- ShouldQueueAfterCommit or $afterCommit used for transaction safety
- Auto-discovery relied on instead of manual registration where possible
- Observers used sparingly and only for model lifecycle hooks
- Core business logic not hidden inside event listeners
- Events tested with Event::fake and assertDispatched
- Listeners tested in isolation with direct handle() calls
- shouldQueue() used to conditionally skip queuing
FAQ
What does the laravel-event-driven-architecture skill do?
Best practices for Laravel events and listeners including event discovery, queued listeners, subscribers, and model events for decoupled architecture.
How do I install laravel-event-driven-architecture?
Run npx skills add https://github.com/iserter/laravel-claude-agents --skill laravel-event-driven-architecture in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/laravel-event-driven-architecture/ (personal) or .claude/skills/laravel-event-driven-architecture/ (project).
Which AI agents can use laravel-event-driven-architecture?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is laravel-event-driven-architecture safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains laravel-event-driven-architecture?
It is published by iserter in iserter/laravel-claude-agents. It has 85 recorded installs.
More from iserter/laravel-claude-agents
eloquent-best-practices
iserter/laravel-claude-agents
Best practices for Laravel Eloquent ORM including query optimization, relationship management, and avoiding common pitfalls like N+1 queries.
laravel-tdd
iserter/laravel-claude-agents
Open the skill to read its SKILL.md instructions.
laravel-blade-component-patterns
iserter/laravel-claude-agents
Best practices for Laravel Blade components including class-based and anonymous components, slots, attribute bags, and reusable UI patterns.
api-resource-patterns
iserter/laravel-claude-agents
Open the skill to read its SKILL.md instructions.
laravel-systematic-debugging
iserter/laravel-claude-agents
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
laravel-validation-patterns
iserter/laravel-claude-agents
Best practices for Laravel validation including Form Requests, custom rules, conditional validation, and input sanitization.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.