monica-project-unit-development

What problem does it solve?

Provides clear, Monica-aligned guidance to decide which ProjectUnits to create, how to name and place them, and how to keep boundaries correct so teams avoid scattering business rules, misplacing repositories, or breaking discovery conventions.

Core Features & Use Cases

• Unit selection guidance: Maps feature shapes to the smallest correct set of ProjectUnits (ApplicationService, RequestDto, DomainService, Entity, Repository, DomainEvent, handlers, jobs, configuration).
• Naming, placement & boundary rules: Enforces Monica.Framework discovery conventions and folder placement for both microservice and modular-monolith solutions.
• Templates & checklists: Includes handler, domain service, entity, repository, event, job, and configuration templates plus a pre-deployment feature checklist to ensure consistency and scanability.
• Use case: Use when adding a new use case, creating an aggregate, introducing events or background jobs, or deciding where to place repository implementations.

Quick Start

Use this skill to choose the ProjectUnits, their names, and folder placement for a new feature and produce a one-page checklist of files, templates, and registration steps.