domain-driven-design
Design and review backend APIs using Routes→Handlers→Services→Repositories with clear Domain Model vs DTO boundaries. Use PROACTIVELY when creating/refactoring endpoints, moving logic out of handlers, defining service use-cases, or implementing repositories. Triggers: DDD, domain-driven design, layered architecture, clean architecture, hexagonal, ports and adapters, repository pattern, service layer, handler, endpoint, API design, refactor backend, business logic, use-case, aggregate, entity, value object, DTO
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Fonctions et usage
Design and review backend APIs using Routes→Handlers→Services→Repositories with clear Domain Model vs DTO boundaries. Use PROACTIVELY when creating/refactoring endpoints, moving logic out of handlers, defining service use-cases, or implementing repositories. Triggers: DDD, domain-driven design, layered architecture, clean architecture, hexagonal, ports and adapters, repository pattern, service layer, handler, endpoint, API design, refactor backend, business logic, use-case, aggregate, entity, value object, DTO
Démarrage rapide
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Guides ↗Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-26
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!