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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.