domain-modeling

Guide domain model refinement, terminology, and architectural decision records.

1|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/hgflima/loopy --skill domain-modeling-hgflima
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/hgflima/loopy/tree/main/.claude/skills/domain-modeling
Command: npx skills add https://github.com/hgflima/loopy --skill domain-modeling-hgflima

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining a clear, consistent domain model across a project, ensuring accurate terminology and aiding in architectural decision-making.

Core Features & Use Cases

  • Domain Model Refinement: Supports the active development of a project's domain model, helping to clarify concepts and terminology.
  • Architectural Decision Records (ADR): Guides the creation and management of ADRs to document important architectural decisions.
  • Context Management: Helps maintain and expand the project's ubiquitous language by providing guidance on term usage and context structure.

Quick Start

Initialize a domain model discussion with 'Start domain modeling'.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema
How do I maintain a consistent ubiquitous language across my software project?

Refining your domain model helps maintain a ubiquitous language by providing guidance on term usage and context structure. This ensures accurate communication and conceptual consistency across your collaborative development workflow.

What is the best way to document architectural decisions for a domain model?

Creating Architectural Decision Records (ADRs) is the best way to document architectural decisions. This practice guides the formalization of important choices to facilitate communication around architectural decisions.

How do I start a domain modeling discussion for my project?

You can start a domain modeling discussion by using a simple initialization command. This action triggers the refinement process, helping you clarify concepts, manage context, and develop domain terminology collaboratively.

Can I use context mapping to manage domain terminology in a collaborative environment?

Yes, context mapping supports collaborative development by managing and expanding the ubiquitous language. It provides specific guidance on term usage and context structure to maintain domain model consistency.

Why does my project's domain terminology become inconsistent during development?

Domain terminology becomes inconsistent without active domain model refinement and context management. Addressing this requires establishing a ubiquitous language and documenting architectural decisions to align collaborative development efforts.

When do I need to create Architectural Decision Records for my software architecture?

You need to create Architectural Decision Records when making important architectural decisions that impact your domain model. This documents the context and rationale, ensuring clarity and facilitating communication across your team.