create-repository

Estrelas13

Forks1

Atualizado10 de fevereiro de 2026 às 01:24

Create repository adapter with MongoDB schema following the ports & adapters pattern. Use when adding persistence for domain entities.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

jovicon

jovicon/nestjs-clean-architecture-event-driven-template

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	create-repository
description	Create repository adapter with MongoDB schema following the ports & adapters pattern. Use when adding persistence for domain entities.

Create repository infrastructure for "$1" entity in the $0 module.

Create these files in src/modules/$0/adapters/repository/:

$1.schema.ts - Mongoose schema definition
$1.adapter.ts - Repository adapter implementing IRepository
$1.service.ts - Service implementing the port interface
$1.module.ts - Adapter module for DI

Also create the port interface: 5. src/modules/$0/application/ports/$1.port.ts

Requirements:

Schema: Use Mongoose decorators (@Schema, @Prop) from @nestjs/mongoose
Adapter: Implement generic IRepository interface
Service: Implement the port interface defined in application layer
Follow Repository pattern from shared/adapters/repository/
Map between domain entities and database models
Handle persistence concerns (MongoDB)
Return domain entities, not database models
Use proper error handling with Result pattern

Layer responsibilities:

Port (application): Interface definition
Adapter (adapters): Repository implementation
Schema (adapters): Database mapping
Module (adapters): DI configuration for adapters only

Mais deste repositório

mesmo repositório

analyze-architecture

jovicon/nestjs-clean-architecture-event-driven-template

Analyze NestJS project architecture against Clean Architecture, DDD, and best practices. Use when reviewing code structure, checking layer boundaries, validating architectural patterns, or auditing module compliance.

2026-02-1013

analyze-code-quality

jovicon/nestjs-clean-architecture-event-driven-template

Analyze code quality including ESLint, Prettier, tests, TypeScript, and NestJS best practices. Use when reviewing code quality, checking test coverage, or auditing for best practices.

2026-02-1013

architecture-guide

jovicon/nestjs-clean-architecture-event-driven-template

Quick reference guide for architectural decisions and patterns in Clean Architecture + DDD + Event-Driven systems. Use for learning or when making architectural decisions.

2026-02-1013

create-domain-event

jovicon/nestjs-clean-architecture-event-driven-template

Create a domain event and its handler following DDD patterns. Use when you need to publish domain events for asynchronous reactions.

2026-02-1013

create-entity

jovicon/nestjs-clean-architecture-event-driven-template

Create a new domain entity or aggregate root following DDD patterns. Use when modeling business entities with identity and lifecycle.

2026-02-1013

create-module

jovicon/nestjs-clean-architecture-event-driven-template

Create a new feature module following Clean Architecture structure. Use when adding a new business domain or feature module to the project.

2026-02-1013

name	create-repository
description	Create repository adapter with MongoDB schema following the ports & adapters pattern. Use when adding persistence for domain entities.

Create repository infrastructure for "$1" entity in the $0 module.

Create these files in src/modules/$0/adapters/repository/:

$1.schema.ts - Mongoose schema definition
$1.adapter.ts - Repository adapter implementing IRepository
$1.service.ts - Service implementing the port interface
$1.module.ts - Adapter module for DI

Also create the port interface: 5. src/modules/$0/application/ports/$1.port.ts

Requirements:

Schema: Use Mongoose decorators (@Schema, @Prop) from @nestjs/mongoose
Adapter: Implement generic IRepository interface
Service: Implement the port interface defined in application layer
Follow Repository pattern from shared/adapters/repository/
Map between domain entities and database models
Handle persistence concerns (MongoDB)
Return domain entities, not database models
Use proper error handling with Result pattern

Layer responsibilities:

Port (application): Interface definition
Adapter (adapters): Repository implementation
Schema (adapters): Database mapping
Module (adapters): DI configuration for adapters only