Where are the generated interfaces stored?

Repositories are generated in the BC/Entities/Repository/ directory, while Finders are located in BC/UseCases/Gateway/Finder/.

Which programming language is this skill optimized for?

Based on the directory structures and validation tools like PHPStan, this skill is primarily optimized for PHP projects following Clean Architecture.

Does this skill support custom templates?

Yes, it utilizes .claude/templates/repository.php.tpl and finder.php.tpl to ensure all generated code follows your project's specific coding standards.

What is the difference between a Repository and a Finder in this skill?

The Repository is designed for write operations (commands) and must throw exceptions if data is not found. The Finder is for read operations (queries) and returns null or arrays instead of throwing exceptions.

Repository & Finder Architect

Name: Repository & Finder Architect
Author: Dev-Int

byDev-Int

Database Management

Generates standardized Repository and Finder interfaces to implement clean, CQRS-compliant data persistence layers.

About

This skill automates the creation of a decoupled persistence layer by generating two distinct interfaces: a Repository for state-modifying commands (which throw exceptions on missing data) and a Finder for read-only queries (which return nulls or arrays). By following strict architectural patterns and automated directory placement, it ensures that your domain logic remains cleanly separated from data access implementation details, facilitating consistent CQRS and Port/Adapter pattern implementation.

Key Features

Automates directory placement for domain entities and gateways
Enforces standardized 'get-throw' vs 'find-null' error handling patterns
0 GitHub stars
Generates CQRS-compliant Repository and Finder interfaces
Includes automated validation via CS-Fixer and PHPStan
Integrates with PHP template files for consistent boilerplate

Use Cases

Implementing a new domain entity that requires a robust persistence layer
Refactoring legacy code to follow clean architecture and CQRS principles
Standardizing data access patterns across a large PHP backend project

About

Key Features

Automates directory placement for domain entities and gateways
Enforces standardized 'get-throw' vs 'find-null' error handling patterns
0 GitHub stars
Generates CQRS-compliant Repository and Finder interfaces
Includes automated validation via CS-Fixer and PHPStan
Integrates with PHP template files for consistent boilerplate

Use Cases

Implementing a new domain entity that requires a robust persistence layer
Refactoring legacy code to follow clean architecture and CQRS principles
Standardizing data access patterns across a large PHP backend project