add-bounded-context

Create bounded context scaffolding with DDD, Clean Architecture, and CQRS layers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the process of adding a new bounded context, reducing manual setup errors and inconsistencies.

Core Features & Use Cases

  • Structured directory scaffolding across presentation, application, domain, and infrastructure layers.
  • Enforces naming conventions for bounded context modules.
  • Simple, repeatable starting point for new bounded contexts like user, task, or order.

Quick Start

Create the new bounded context directory structure under server/src/main/kotlin/xyz/robinjoon/growweek/{bounded-context} following the naming and layering rules.

Frequently Asked Questions about add-bounded-context

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

FAQPage Schema
How do I scaffold a new bounded context in Kotlin using DDD and Clean Architecture?

To scaffold a bounded context in Kotlin, this tool automates the creation of a multi-layer directory structure that follows DDD, Clean Architecture, and CQRS conventions. It builds presentation, application, domain, and infrastructure layers to enforce a consistent layout.

What is the best way to structure a CQRS bounded context with separate Command and Query models?

The best way to structure a CQRS bounded context is by enforcing a conventional layout across presentation, application, domain, and infrastructure layers. This approach directly separates Command and Query models within the generated module to maintain clean architecture boundaries.

How do I set up a domain module directory structure for domain-driven design in Kotlin?

Setting up a domain module directory structure for DDD involves creating a consistent multi-layer layout under your main Kotlin source path. This tool generates the required presentation, application, domain, and infrastructure folders automatically when starting a new module.

Do I need to manually configure naming conventions when adding a new DDD bounded context?

You do not need to manually configure naming conventions when adding a DDD bounded context. The scaffolding process enforces naming conventions for bounded context modules automatically, reducing manual setup errors and inconsistencies.

Can I use this bounded context scaffolding for any type of domain module like user or order?

Yes, you can use this bounded context scaffolding for any new domain module. It provides a simple, repeatable starting point for common contexts like user, task, or order by applying a standardized directory structure across all architectural layers.

When do I need to generate a new bounded context with CQRS and Clean Architecture?

You need to generate a new bounded context with CQRS and Clean Architecture when starting a new domain module that requires a consistent multi-layer directory structure. This ensures proper separation of Command and Query models from the beginning of your project.