ddd-context-generator

Generate DDD bounded contexts with four layers for Bun.js and Express backends.

5|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/moasadi/ddd-bun-api-boilerplate --skill ddd-context-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-context-generator
Source: https://github.com/moasadi/ddd-bun-api-boilerplate/tree/main/.claude/skills/ddd-context-generator
Command: npx skills add https://github.com/moasadi/ddd-bun-api-boilerplate --skill ddd-context-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a complete bounded context following DDD and Clean Architecture, including Domain, Application, Infrastructure, and Presentation layers.

Core Features & Use Cases

  • Domain Layer: Entities, Value Objects, Domain Repositories, Domain Events, Domain Errors
  • Application Layer: Use cases and event listeners
  • Infrastructure Layer: Persistence models, repositories, mappers
  • Presentation Layer: DTOs, serializers, controllers with Swagger docs

Quick Start

Request generation for a Product context with full CRUD and inventory management.

Frequently Asked Questions about ddd-context-generator

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

FAQPage Schema
How do I generate a complete DDD bounded context with all layers?

DDD bounded context generation creates a full Domain-Driven Design structure with Domain, Application, Infrastructure, and Presentation layers in one operation. This Skill scaffolds entities, value objects, repositories, use cases, DTOs, controllers, and Swagger documentation for Bun.js and Express backends automatically.

Can I use DDD scaffolding for Express and routing-controllers?

Yes. This Skill generates complete DDD contexts specifically for Bun.js plus Express with routing-controllers, including controller wiring, dependency injection setup, and OpenAPI documentation integration out of the box.

What layers does a generated DDD context include?

The generated context includes four layers: Domain (entities, value objects, domain events, errors), Application (use cases, event listeners), Infrastructure (persistence models, repositories, mappers), and Presentation (DTOs, serializers, controllers with Swagger docs).

How do I scaffold a new business capability using DDD architecture?

Request context generation for your capability—for example, Order or Product context. The Skill produces a complete bounded context with CRUD operations, full-layer structure, domain logic separation, and integration wiring ready to extend.

Does DDD scaffolding include API documentation?

Yes. Generated contexts include Swagger and OpenAPI documentation for all controller endpoints, automatically derived from DTOs and request/response structures.

What's the difference between DDD scaffolding and manual layered architecture?

DDD scaffolding generates all four layers with consistent structure, repository patterns, domain event wiring, and DTO mappers in minutes. Manual setup requires building each layer separately and integrating them without automated consistency checks.