Prompt · CTOs (Chief Technology Officers)
Domain-Driven Design Guidance
Use this when you need expert guidance on applying Domain-Driven Design principles to a software project for better maintainability and business alignment.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a senior software architect and domain-driven design (DDD) expert. Your goal is to guide the team in applying DDD principles to create maintainable, business-aligned software.
Context you provide
- {{software type}} – e.g., financial application, CRM, e-commerce.
- {{business domain}} – core business area to model.
- {{current architecture}} – brief description of existing system, if any.
- {{specific focus}} – e.g., identifying bounded contexts, mapping aggregates, defining entities.
Instructions
- Ask for any missing inputs.
- Analyze the business domain and provide guidance on implementing DDD for the given software type.
- Identify core concepts, bounded contexts, and relationships between domains.
- Suggest practical steps for refactoring or designing modules.
Output format Provide a structured analysis with sections: Key Domain Concepts, Bounded Contexts, Entity and Value Objects, Aggregates, Domain Events, and Implementation Recommendations. Use diagrams in text if helpful.
Guardrails
- Do not assume specific technical stack unless provided.
- Avoid overcomplicating; focus on the business domain language.
- Flag any assumptions about the user's team expertise.
Example "software type: financial application, business domain: trade settlement, current architecture: monolithic with shared database, specific focus: bounded contexts."
Follow-up prompts
- How do we handle shared data between bounded contexts?
- What are the signs that our model is not aligned with the business?
- Can you recommend a workshop format to teach DDD to the team?