Skill UI

This skill guides the architectural definition of complex business domains using Domain-Driven Design (DDD). It helps in defining core subdomains, separating services by bounded contexts, and establishing a unified ubiquitous language. It is essential for decomposing monoliths, structuring microservices, and aligning team ownership with clear domain boundaries.

This tool extracts and formalizes the core business terminology (Ubiquitous Language) from a conversational context. It generates a structured glossary, identifies ambiguities, resolves conflicting terms, and proposes canonical names. It is essential for building consistent and unambiguous domain models, particularly when following Domain-Driven Design (DDD).

A comprehensive skill for systematically building, refining, and documenting a project's domain model. It helps define core terminology, establish a ubiquitous language, and record critical architectural decisions (ADRs). Use this when you need to challenge ambiguous language, invent edge-case scenarios, or maintain architectural consistency throughout the development lifecycle.

Apply Eric Evans-inspired Domain-Driven Design rules for modeling complex domains. Define bounded contexts, protect ubiquitous language, and design aggregates. Use this skill for strategic domain modeling, context mapping, repositories, and domain services before making design or code decisions.

This skill guides the architectural definition of complex business domains using Domain-Driven Design (DDD). It helps in defining core subdomains, separating services by bounded contexts, and establishing a unified ubiquitous language. It is essential for decomposing monoliths, structuring microservices, and aligning team ownership with clear domain boundaries.

A comprehensive skill for systematically building, refining, and documenting a project's domain model. It helps define core terminology, establish a ubiquitous language, and record critical architectural decisions (ADRs). Use this when you need to challenge ambiguous language, invent edge-case scenarios, or maintain architectural consistency throughout the development lifecycle.