skills.rest
flowel
flowelCOMMUNITY
Explore all skills by this author →
GitHub

domain-modeling

Create and manage domain models with terminology, ubiquitous language, and architectural decisions.

Updated Jun 12, 2026
Search Tags:#context management#software design#domain modeling#ubiquitous language#architectural decisions
One-click install
npx skills add https://github.com/flowel/AiSkills --skill domain-modeling-flowel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/flowel/AiSkills/tree/main/skills/codex/domain-modeling
Command: npx skills add https://github.com/flowel/AiSkills --skill domain-modeling-flowel

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps to clarify and maintain a project's domain model by facilitating the definition of terminology and ubiquitous language, and by recording architectural decisions.

Core Features & Use Cases

  • Domain Modeling Support: Offers guidance for defining and refining project-specific terms and relationships.
  • Architectural Decision Records (ADRs): Assists in creating and managing ADRs for significant architectural decisions.
  • Context Management: Helps establish and maintain a consistent language for different contexts within a project.

Quick Start

Use the domain-modeling skill to create a new context in your project by executing the command 'create-context "Ordering" in "./src/ordering/"'.

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 different bounded contexts?▼

To maintain a consistent ubiquitous language, you can establish and manage distinct contexts within your project, ensuring that terminology and relationships are clearly defined and refined for each specific context.

What is the best way to document architectural decisions in a software project?▼

The best way to document architectural decisions is by creating and managing Architectural Decision Records, which capture significant design choices to maintain clarity and consistent communication around system functionality.

How do I start defining a domain model for a new software module?▼

You can start defining a domain model by creating a new context in your project directory, such as executing 'create-context' with a specific name and path to initiate terminology and relationship guidance.

When do I need formal domain modeling support for my software design process?▼

You need formal domain modeling support when your software development project requires consistent and clear communication around system design, particularly to clarify terminology and record architectural decisions within your workflow.

Can I manage domain terminology and architectural decisions without a dedicated context tool?▼

Without a dedicated context tool, managing domain terminology and architectural decisions relies on manual tracking, which risks inconsistent ubiquitous language and fragmented architectural records across different project contexts.

Related Skills

Explore More Software Engineering Skills→
hwj123hwjhwj123hwj
4

domain-modeling

Shape project domain models and document architectural decisions.

Community
Advanced
caobingshengcaobingsheng
1

domain-driven-design

Plan domain-driven design decisions across strategic modeling and bounded contexts.

Community
Advanced
yongwoonyongwoon
8

ywc-ubiquitous-language

Extract domain terms from source code and create glossary documents.

Community
Intermediate
TheycallmehollaTheycallmeholla

connotation-cop

Audit terminology against a CONTEXT.md glossary and enforce ADR documentation.

Community
Intermediate