add-or-update-domain

Create or update domains with command, query, and repository interfaces.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-or-update-domain
Source: https://github.com/GrowWeek/GrowWeek-Backend/tree/main/.claude/skills/domain
Command: npx skills add https://github.com/GrowWeek/GrowWeek-Backend --skill add-or-update-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the challenge of adding or updating a domain within a bounded context.

Core Features & Use Cases

  • Standardized workflow for creating or updating domain models within a bounded context.
  • Clear separation of concerns: command for write operations, query for reads, and a repository interface for persistence.
  • Guidance for implementing common domain primitives and ensuring cross-context references remain controlled.

Quick Start

Solve domain evolution by creating or updating a domain following the model (command and query), repository, and service conventions described above.

Frequently Asked Questions about add-or-update-domain

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

FAQPage Schema
How do I add a domain to an existing bounded context in DDD?

To add a domain within a bounded context, you create standardized domain models, separate command and query operations, define repository interfaces with saveAll and findAll signatures, and optionally implement domain services following frontmatter-driven discovery contracts.

What is the command-query separation pattern for domain management?

Command-query separation for domain management splits write operations into commands and read operations into queries, maintaining clear boundaries within a bounded context while enforcing repository interface contracts for persistence layer consistency.

Can I update an existing domain model without breaking cross-context references?

Updating a domain model within a bounded context enforces controlled cross-context references through standardized domain primitives, repository interface contracts, and frontmatter-driven discovery, ensuring modifications maintain separation of concerns across bounded contexts.

Do I need a repository interface to manage domains in a bounded context?

A repository interface is required for domain management in a bounded context, enforcing saveAll and findAll signatures for persistence operations while maintaining clean separation between domain models, commands, queries, and optional services.

What's the best way to structure domain commands and queries in DDD?

Structuring domain commands and queries in DDD involves clear separation of concerns: commands handle write operations, queries manage reads, and repository interfaces with saveAll and findAll signatures handle persistence within bounded context boundaries.

When should I use a domain service versus a repository interface in DDD?

Use domain services for complex domain logic that doesn't naturally belong to a single entity, while repository interfaces with saveAll and findAll signatures handle persistence concerns within a bounded context's standardized domain management workflow.