domain-driven-development
Domain-Driven Development (DDD) Architecture
Layers
Our DDD architecture has three layers.
Domain (domain/[domain name]/)
This layer contains all domain-related code, including domain objects, business logic, APIs.
Interface of this layer must be technology-agnostic and have no dependencies on any third-party libraries, specific storage or UI technologies. Internally you can use any third-party libraries, but the interface must be clean and technology-agnostic to ensure that the core domain logic is reusable and testable without any specific technologies.
This layer must not have any dependencies on the other layers.
Read rules/domain.md for details on Domain Objects, Factories, Repositories, and Services.
External Services (external/)
More from geb-algebra/geb-agent-skills
react-router-route-module-patterns
How to implement Route Modules for React Router. Use when you implement any page or component using React Router Framework Mode.
5ui-components
Implement React components in maintainable, effortless and consistent way. Use when you implement React components for your application.
4principles-of-coding-with-geb
Principles of coding tasks I prefer. Use this skill for EVERY code-related task (e.g., implementation planning, coding, writing documentations).
4impl-pad
Implement following your Pad (a markdown file named `pad.md`). Use When the user instructs you to implement something, specifying pad.md.
1write-pad
Write your Pad (a markdown file named `pad.md` in this repository). Use when the user instructs you to write a pad.md.
1