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.
See how to installReview the instructions the agent will receive before you install.
First look for a model or Value Object that naturally owns the behavior. Create App\Domain\<Capability>\Services only when a cohesive business operation has no such owner.
For example, OrderCancellationFee may calculate a fee using an order and a cancellation policy. It computes a business result; CancelOrder authorizes, coordinates, saves, and handles follow-up work.
Avoid generic OrderService, UserService, or PaymentService containers. Do not extract a service merely because a method is long or used twice.
Domain services must not depend on Application, Infrastructure, or delivery code. If a business calculation genuinely needs an external capability, define its contract under App\Domain\<Capability>\Contracts, implement it in Infrastructure, and bind it in a Laravel service provider. Do not hide an adapter lookup behind a facade or container call.
Use domain exceptions for rejected rules. Leave persistence coordination and transactions to Application. Direct collaboration with models in other capabilities is allowed within the same bounded context.
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.
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.
Create or change immutable business values with meaningful invariants, equality, or behavior, such as order numbers and money. Use when primitive values obscure domain rules; avoid wrapping every scalar.
The English summary is being prepared. Showing the original description.