skills.rest
Tairitsua
TairitsuaCOMMUNITY
Explore all skills by this author →
GitHub

monica-business-microservice

Define DDD microservice solution layouts and project reference chains for Monica projects.

13|6|Updated Feb 19, 2025
Search Tags:#architecture#ddd#microservice#service-boundaries#monica#platform-protocol#solution-layout
One-click install
npx skills add https://github.com/Tairitsua/Monica --skill monica-business-microservice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monica-business-microservice
Source: https://github.com/Tairitsua/Monica/tree/main/.claude/skills/monica-business-microservice
Command: npx skills add https://github.com/Tairitsua/Monica --skill monica-business-microservice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides architects and developers to correctly structure Monica DDD microservices, decide where each subdomain and contract belongs, and prevent dependency leakage or collapsing service boundaries.

Core Features & Use Cases

  • Solution layout guidance: Prescribes a canonical src/ layout with AppHost, Shared platform layers, Services, and Migrations to keep ownership clear.
  • Project reference rules: Enforces the strict chain API -> Domain -> Platform.Infrastructure -> Platform.Protocol -> Platform.BuildingBlocks and where to place project-common versus service-only libraries.
  • Contract and collaboration patterns: Advises what belongs in PublishedLanguages, when to prefer events vs synchronous calls, and how to keep APIs as adapters.
  • Operational checklist: Provides a step-by-step workflow for creating new subdomains, wiring migrations, and final delivery checks to ensure migration ownership and host registration order.

Quick Start

Design a new subdomain service named Ordering and ask for a solution layout, the required PublishedLanguages entries, the API/Domain/migration project scaffolding, and a migration ownership checklist.

Frequently Asked Questions about monica-business-microservice

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

FAQPage Schema
How do I structure DDD microservices to prevent dependency leakage?▼

To structure DDD microservices and prevent dependency leakage, enforce a strict project reference chain from API to Domain, then to Platform.Infrastructure, Platform.Protocol, and Platform.BuildingBlocks, ensuring clear ownership for project-common versus service-only libraries.

What is the correct solution layout for Monica microservice projects?▼

The correct solution layout for Monica microservice projects uses a canonical src/ structure containing AppHost, shared platform layers, Services, and Migrations directories to keep subdomain ownership and boundaries clear.

Where should PublishedLanguages contracts be placed in a DDD microservice architecture?▼

PublishedLanguages contracts belong in the Platform.Protocol layer to ensure stable cross-service collaboration, defining events versus synchronous calls while keeping APIs acting merely as adapters.

How do I scaffold a new subdomain service with API, Domain, and migration projects?▼

To scaffold a new subdomain service, follow an operational checklist that defines the solution layout, places API and Domain projects, wires migrations with correct ownership, and sequences host registration for final delivery.

When should I split project-common libraries from service-only libraries in microservices?▼

You should split project-common libraries from service-only libraries when establishing the solution-project reference chain, placing shared code in Platform.BuildingBlocks while isolating service-specific logic within the Domain layer to prevent boundary collapse.

Does Monica platform-protocol support event-driven collaboration over synchronous calls?▼

Monica platform-protocol supports event-driven collaboration by advising what contracts belong in PublishedLanguages, guiding architects on when to prefer events over synchronous calls to maintain stable service boundaries.

Related Skills

Explore More Software Engineering Skills→
TairitsuaTairitsua
13

monica-business-modular-monolith

Structure Monica solutions into a DDD modular monolith with bounded contexts.

Community
Advanced
0xdsgnrd0xdsgnrd
1

agentic-orchestration

Define a three-layer architecture for agentic systems across Framework, Skills, and Application layers.

Community
Advanced
yonatangrossyonatangross
217

testing-integration

Validate API boundaries and cross-service contracts with Pact, Supertest, httpx, and Hypothesis.

Community
Advanced
iCesofTiCesofT
1

architecture-patterns

Apply Clean Architecture, Hexagonal Architecture, and DDD to backend service designs.

Community
Advanced