skill-arch-domain-model

Identify domain boundaries, entities, and relationships to produce Mermaid ERDs.

4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-arch-domain-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-arch-domain-model
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/skills/skill-arch-domain-model
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-arch-domain-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design domain models by identifying bounded contexts, core entities, relationships, and business rules, and producing ERDs (text or Mermaid) to guide implementation.

Core Features & Use Cases

  • Bounded context identification and boundary definition
  • Entity and relationship specification with text or Mermaid ERD
  • Business rules capture and validation
  • Aggregates and value objects guidance
  • Database schema considerations for domain-driven design

Quick Start

Identify the primary domain areas, define bounded contexts, list key entities and their relationships, and draft a Mermaid ERD to guide implementation.

Frequently Asked Questions about skill-arch-domain-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define bounded contexts and model domain boundaries for early-stage system design?

Modeling domain boundaries involves identifying bounded contexts, specifying core entities and relationships, and capturing business rules. This process supports scalable software architecture and produces ERDs to guide implementation.

What is the best way to generate a Mermaid ERD from domain entities and relationships?

Drafting a Mermaid ERD involves listing key entities and defining their relationships to guide implementation. This visual representation clarifies domain-driven design architecture and supports database schema considerations.

How do I identify aggregates and value objects when designing a domain model?

Identify aggregates and value objects by analyzing business rules and grouping core entities within domain boundaries. This ensures consistency and supports clear bounded context separation in domain-driven design.

Does domain-driven design work for capturing complex business rules and database schema considerations?

Domain-driven design captures business rules by defining bounded contexts and specifying entities. It also addresses basic database schema considerations to align implementation with domain logic.

When do I need bounded context identification for architecture reviews?

You need bounded context identification during architecture reviews to define domain boundaries and model core entities. This ensures clear contexts and ERDs support scalable software architecture.