domain-modeling

Manage project domain terminology in CONTEXT.md and record architectural decisions as ADRs.

Updated Jul 9, 2026

Search Tags:#software development #domain modeling #ubiquitous language #architectural decision #terminology management

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of defining and maintaining a consistent, clear domain model for your project, ensuring terminology alignment and architectural coherence.

Core Features & Use Cases

Domain Terminology Management: Establish and manage a project-specific terminology in CONTEXT.md.
Architectural Decision Recording: Record architectural decisions as ADRs for traceability and review.
Use Case: As you develop your software, this Skill helps define the terms "Customer", "Order", and "Payment", ensuring everyone involved in the project speaks the same language and follows a unified architectural approach.

Quick Start

Utilize the domain-modeling skill to define the term 'Customer' in your project's domain model.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I establish a consistent domain model for my software development project?▼

To establish a consistent domain model, you need to manage project terminology and record architectural decisions. This ensures terminology alignment and architectural coherence across the development team by defining terms in a shared context file.

What is the best way to manage ubiquitous language and domain terminology?▼

Managing ubiquitous language requires establishing a project-specific terminology set in a shared context file. This ensures all team members speak the same language and maintains a unified domain understanding for effective implementation.

How do I record architectural decisions for traceability and review?▼

You record architectural decisions by creating Architecture Decision Records (ADRs). This practice captures decisions for traceability and review, ensuring the project maintains architectural coherence throughout its lifecycle.

When do I need domain terminology management in software development?▼

You need domain terminology management when clear, unified domain understanding is critical for communication. It solves the challenge of defining and maintaining consistent terms like "Customer" or "Order" across the project.

Does this domain modeling approach work without external dependencies?▼

Yes, this domain modeling approach works without external dependencies. It relies on internal scripts and reference components to maintain the domain model, requiring no prior environment setup beyond the project itself.