Evaluate, introduce, or refactor persistence abstractions when direct Eloquent is insufficient. Use for repository requests, complex aggregate reconstruction, or multiple persistence implementations; reject CRUD wrappers without a concrete benefit.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Direct Eloquent is the default in Domain and Application. Loading an order and calling $order->save() from CancelOrder does not require a repository, interface, or separate persistence entity.
Introduce a repository only for an actual persistence problem, such as complex aggregate reconstruction, multiple implementations, or a meaningful boundary hiding specialized storage.
When the implementation lives in Infrastructure, put the contract with its consumer in App\Domain\<Capability>\Contracts or App\Application\<Capability>\Contracts. Infrastructure implements it; a Laravel service provider binds it. The consumer receives the contract rather than the concrete implementation.
Name the contract for the capability it provides and use consumer-owned types in its API. Avoid generic RepositoryInterface, BaseRepository, or CRUD forwarding methods around Eloquent. Do not introduce a repository solely to mock a model in an Action test.
Keep transaction coordination in the Action. A repository should not silently commit the caller's unit of work. Reusing an existing suitable abstraction is preferable to building a parallel one.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create, modify, or refactor application use cases into Laravel-native DDD Actions. Use for business operations such as placing or cancelling orders, extracting controller orchestration, and fixing use-case behavior.
The English summary is being prepared. Showing the original description.
Create or change structured input for application use cases, including extracting HTTP request data for Actions invoked from controllers, jobs, or commands. Avoid DTOs for trivial scalar input.
The English summary is being prepared. Showing the original description.
Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.
The English summary is being prepared. Showing the original description.
Create, extend, or fix Eloquent business models and their state transitions. Use when moving business rules out of controllers or Actions, or explicitly migrating a model into a DDD capability.
The English summary is being prepared. Showing the original description.
Create or refactor business calculations and rules spanning multiple domain objects when no single entity or value object naturally owns the behavior. Use when assessing a growing service class.
The English summary is being prepared. Showing the original description.
Add, change, or debug external API integrations, vendor SDK adapters, and bridges to legacy business workflows. Use when an Action or domain service needs an outer technical dependency.
The English summary is being prepared. Showing the original description.