Does this skill generate the database implementation or SQL?

No, this skill is specifically for generating the domain-layer interface (the port). To generate the implementation with SQL or ORM mapping, you should use the infra-bc-repository-generator.

Can I use this for external API integrations?

Yes, while it defaults to Repository for persistence, the skill also supports creating Gateway interfaces for external system contracts.

Why does it prevent using Page or QueryWrapper types?

These types are usually specific to frameworks like Spring Data or MyBatis Plus. Including them in domain ports would leak infrastructure details into your core business logic, violating DDD principles.

Where are the generated interfaces located?

The skill places interfaces in the domain module under the {{basePackage}}.domain.{{bcName}}.repository package.

Domain Repository Port Generator

Name: Domain Repository Port Generator
Author: ryan-alexander-zhang

byryan-alexander-zhang

0•

Gestión de Bases de Datos

Generates pure domain repository interfaces to define persistence contracts without infrastructure or framework dependencies.

The Domain Repository Port Generator is a specialized tool for developers following Domain-Driven Design (DDD) principles. It automates the creation of clean Java repository interfaces within the domain layer, ensuring that persistence logic is expressed in business terms rather than database operations. By strictly excluding infrastructure-specific types and framework annotations, this skill helps maintain a decoupled architecture where the core domain remains isolated from implementation details like SQL, MyBatis, or Spring Data.

Características Principales

01Enforces strict DDD separation between domain ports and infrastructure adapters.

02Generates framework-agnostic Java interfaces for domain persistence.

03Translates business intent into standardized repository methods like save and find.

04Prevents leakage of SQL concepts, pagination wrappers, and ORM types into the domain.

05Standardizes repository packaging within the Persimmon scaffold structure.

060 GitHub stars

Casos de Uso

01Establishing consistent interface patterns across multiple bounded contexts.

02Refactoring legacy monoliths into clean DDD modules by decoupling data access.

03Defining persistence contracts for new domain aggregates during initial modeling.

Características Principales

01Enforces strict DDD separation between domain ports and infrastructure adapters.

02Generates framework-agnostic Java interfaces for domain persistence.

03Translates business intent into standardized repository methods like save and find.

04Prevents leakage of SQL concepts, pagination wrappers, and ORM types into the domain.

05Standardizes repository packaging within the Persimmon scaffold structure.

060 GitHub stars

Casos de Uso

01Establishing consistent interface patterns across multiple bounded contexts.

02Refactoring legacy monoliths into clean DDD modules by decoupling data access.

03Defining persistence contracts for new domain aggregates during initial modeling.