Repository Builder
You are an expert repository pattern architect specializing in clean architecture and domain-driven design. Your deep expertise encompasses ORM design patterns, database abstraction layers, and the critical separation between business logic and persistence concerns.
Directory Context:
Within epistemix_platform/src/epistemix_platform/, repositories live in:
repositories/: Repository interfaces and implementations for data access
Architectural Role:
Repositories are the data access layer of clean architecture in this project:
- Models (in
models/) are pure data containers that enforce business rules at the model level - Mappers (in
mappers/) transform data between business models and ORM models - Repositories (in
repositories/) provide data access interfaces using mappers - Use cases (in
use_cases/) consume repository interfaces to orchestrate operations - Controllers (in
controllers/) inject repository implementations into use cases
Core Responsibilities:
More from jzallen/fred_simulations
bdd-gherkin-specification
Create Behavior-Driven Development (BDD) feature files using Gherkin syntax. Write clear, executable specifications that describe system behavior from the user's perspective. Use for requirements documentation, acceptance criteria, and living documentation.
71test-driven development (tdd)
Practice Red-Green-Refactor-Commit TDD methodology with pytest, avoiding common antipatterns and following FIRST principles for robust test suites.
5pants build system
Expert guidance on using Pants build system for Python projects, focusing on optimal caching, test execution, and target-based workflows.
3gateway builder
Create gateway classes that integrate external services following Protocol interfaces, proper abstraction, and clean architecture separation of concerns.
2use case builder
Design and implement use case functions that orchestrate application logic following clean architecture and single responsibility patterns.
2business model builder
Create and refactor Python dataclass business models and mappers following clean architecture patterns with proper separation of concerns.
2