What problem does it solve? Teams often lose track of domain terminology and architectural decisions as a project grows, leading to inconsistent naming and misaligned understanding. This Skill provides a structured workflow to pin down domain terminology, record architectural decisions, and keep the domain model current. ## Core Features & Use Cases - Ubiquitous Language Definition: Capture and standardize domain terminology so the whole team speaks the same language. - Architectural Decision Records: Document key design decisions with context and rationale for future reference. - Cross-Skill Maintenance: Other skills can invoke this workflow to keep the domain model synchronized as the codebase evolves. - Use Case: While designing a new billing module, use this Skill to define terms like "invoice", "ledger entry", and "settlement" and record the decision to model payments as immutable events. ## Quick Start Ask the assistant to use the domain-modeling skill to define the core domain terms and record an architectural decision for your project.