Skill UI

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.

This skill guides authors on how to position their manuscript within the complex, multidisciplinary literature of Agricultural Systems (AgSy). It ensures that the paper advances the conversation by engaging both the domain knowledge and the core modeling/systems methodologies. The process focuses on identifying unresolved systemic trade-offs, pinpointing the exact research gap, and clearly articulating the unique contribution among established alternatives.

This detailed guide helps authors assess the scientific rigor and scope fit for manuscripts targeting Composites Part B: Engineering. It covers advanced domains like composite mechanics, manufacturing processes, multiscale modeling, and multifunctional materials. It emphasizes that a strong contribution must demonstrate a clear, mechanism-driven advance from material science to structural application, supported by rigorous, quantitative experimental evidence and model validation.

This guide ensures that the chosen research methodology genres (e.g., behavioral empirical, analytical modeling, design science) are correctly aligned with the core research claim or phenomenon. It helps researchers identify the necessary design rigor, appropriate identification strategies (like DiD or IV), and the level of analysis required to ensure the study can genuinely support its contribution in the IS domain.

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.

Apply lightweight Domain-Driven Design rules for bounded contexts, subdomains, and tactical modeling without unnecessary ceremony. Ideal for practical software architecture guidance and design decisions in complex systems.

Orchestrate complex multi-phase objectives into guided sequences of skill invocations. Use for shipping SaaS MVPs, web security audits, AI agent systems, browser QA, and DDD domain modeling with verified checkpoints.

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.

Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use for systems requiring audit trails, complex domain modeling, or temporal queries.

Actively build and sharpen a project's domain model by challenging terminology, recording glossary terms, and writing ADRs when decisions are hard to reverse and surprising.