domain-modeling

Name: domain-modeling
Availability: InStock
Author: onblueroses

Create domain model terms and document architectural decisions as ADRs.

3|Updated Mar 1, 2026

Search Tags:#domain modeling #glossary #ubiquitous language #ADR #bounded contexts

Ready to run

npx skills add https://github.com/onblueroses/strata --skill domain-modeling-onblueroses

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/onblueroses/strata/tree/main/skills/domain-modeling
Command: npx skills add https://github.com/onblueroses/strata --skill domain-modeling-onblueroses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you actively build and refine a project's domain model during the design process, ensuring precise terminology, clear context boundaries, and well-documented decisions.

Core Features & Use Cases

Domain Model Refinement: Enhance the domain model by mapping bounded contexts, creating edge-case scenarios, and cross-referencing behavior against code.
Glossary Creation: Write the glossary inline as terms crystallize to maintain a precise vocabulary.
Decision Documentation: Capture architectural decisions as ADRs (Architectural Decision Records) when they meet specific criteria.
Use Case: When you're designing a complex system, use this Skill to ensure that every term, context, and decision is clearly documented and understood.

Quick Start

Use the domain-modeling skill to create a new term for your project: 'domain-modeling create-term [term-name] [definition]'.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

What is domain modeling and how does it help with ubiquitous language in software design?▼

Domain modeling helps map bounded contexts and cross-reference system behavior against code, ensuring your domain model accurately reflects complex software design requirements and edge-case scenarios.

How do I document architectural decisions using ADRs in domain modeling?▼

You create a glossary inline as terms crystallize during the design process, manually inputting term names and definitions to maintain a precise vocabulary across your bounded contexts.

Can I cross-reference my domain model behavior directly against my codebase?▼

This domain modeling approach is suited for complex systems where you need to map bounded contexts, create edge-case scenarios, and ensure every architectural decision is clearly documented.

What's the best way to define bounded contexts and edge-case scenarios for a complex system?▼

The best way to define bounded contexts is to actively refine the domain model by mapping context boundaries, creating edge-case scenarios, and cross-referencing behavior against your code.