repository-pattern-gate

name

repository-pattern-gate

description

Place or check logic in ack-nestjs-boilerplate's Controller → Service → Repository shape — deciding which role owns a rule, a query, a throw, a DTO boundary, or a module registration. Use this whenever you are about to put business logic in a controller, inject DatabaseService into a service, throw a module exception from a repository, register a controller or processor inside its own feature module, add forwardRef between feature modules, or decide whether a util, decorator, guard, or processor is the right home. The failure modes here are services owning Prisma, controllers owning rules, repositories owning module exceptions, and wiring cycles that only fail at boot.

rules/architecture.md holds the obligations — what each role may do, module wiring, path aliases, and YAGNI; this skill holds the procedure for placing logic and the traps at each decision. When they appear to disagree, the rule file governs and the skill is stale — fix the skill. Related surfaces also live in rules/http.md, rules/database.md, rules/validation.md, rules/null-safety.md, and rules/queue.md.

Repository pattern gate — place, wire, trap

Dispatch to

coder — this skill governs feature code (controllers, services, repositories, guards, processors, module files). It is a REFERENCE skill: the coder agent invokes it from inside its own rule set when it is about to place logic, and the workflow skill coding invokes it at its gate step when the feature touched those surfaces. It dispatches nobody — workflow skills are the only things that dispatch agents.

The three roles

Controller ──▶ Service ──▶ Repository ──▶ DatabaseService (Prisma)

Role	Owns	Must not