DDD Repository Placement Guidance

Trust Score 88/100

Guidance on where to place repository interfaces in Clean Architecture — recommends defining repository interfaces in the use-case layer to avoid domain couplin

triggers:repository placementwhere to put repositoryddd repositoryclean architecturerepository interface

GitHub SKILL.md

What it does

This skill provides concrete guidance and review checks for placing repository interfaces within a layered architecture. It argues for defining repository interfaces in the use-case (application) layer rather than the domain layer to prevent accidental coupling, enforce ID-based references between aggregates, and keep domain models focused on business rules. The content includes detection patterns and recommended project layouts.

When to use it

Invoke this skill when reviewing code or repos for architecture hygiene, when deciding where to define repository interfaces, or when preparing a PR that touches persistence/adapter boundaries. It's useful during design reviews, refactors, and code audits focused on DDD and clean architecture.

What's included

Scripts: none (has_scripts=false).
References: examples, code snippets, and a checklist for reviewers covering placement, coupling, and ID-reference rules.
Instructions: clear examples showing anti-patterns (repositories in domain) and recommended structures (usecases/application layer for interfaces, adapters/infra for implementations).

Compatible agents

Best used with developer-focused agents and tooling that can read code structure and produce architecture review notes (codex-cli, claude-code, cursor, gemini-cli).

Audit Summary

A guidance-only skill with no scripts that advises on where to place repository interfaces in DDD/Clean Architecture projects. Well-structured SKILL.md with clear triggers, placement rules, and progressive disclosure via references/. Purely instructional — no executable code, no security concerns.

Watch Out

Niche topic — only useful for teams actively working on DDD/Clean Architecture repository placement questions

Notes

No scripts to evaluate. Static analysis only. Clean, well-organized skill following the spec conventions.

Information

Repository: ai-tools
Stars: 24

Trust Score

Overall88

Security100

Code Quality72

Architecture80

Usefulness42

Related Skills

BK-CI Design Patterns Guide

Practical guide to design patterns used in the BK-CI project (Kotlin/Spring). Covers factory, strategy, singleton, decorator, observer, template method, chain-o

Node.js Best Practices

Guidelines and decision-making for Node.js architecture, runtime, async patterns, security, validation, and testing to inform framework and system choices.

Ubiquitous Language Glossary

Extract a DDD-style ubiquitous language glossary from conversation: identify domain terms, flag ambiguities, propose canonical terms, and write the result to UB

React Development Expert

Provides authoritative React guidance on hooks, state patterns, Server Components, performance optimization, and common architectural patterns.

Cellar

CLI to inspect public APIs of JVM artifacts (Scala/Java): signatures, members, docs and source code from terminal or project classpath.

draw.io Diagram Skill

Create, edit, lint, and export draw.io diagrams; includes export helpers, SVG linting, and repository QA for clean architecture and icon-based diagrams.

Microsoft Foundry Classic — Expert Guidance

Comprehensive guidance for building, configuring, troubleshooting, and deploying Microsoft Foundry Classic agents and integrations.

Arcana (Technical Mechanism Analysis)

Explain how systems, protocols, or architectures actually work under the hood and surface non-obvious implications and failure modes.

Back to Skills