skills.rest
ian-pascoe
ian-pascoeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

domain-modeling

Clarify project terminology, context boundaries, and architectural decisions in Markdown CONTEXT files and ADR notes.

1|Updated Mar 19, 2026
Search Tags:#architecture#domain modeling#adr#glossary#context map#ubiquitous language
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill domain-modeling-ian-pascoe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/domain-modeling
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill domain-modeling-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams keep domain language, context boundaries, and architectural decisions consistent so the codebase and documentation tell the same story.

Core Features & Use Cases

  • Defines canonical terms with clear avoid lists for ambiguous project vocabulary.
  • Maintains a context map for single-context or multi-context repositories.
  • Captures durable architectural decisions in lightweight ADRs when trade-offs matter.
  • Use it when a term like "account" could mean multiple things and the team needs one precise meaning.

Quick Start

Ask the skill to review the repository terms and draft the appropriate CONTEXT.md entries for the concepts you want to standardize.

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 ubiquitous language when a term like 'account' means multiple things in my codebase?▼

Domain modeling clarifies ambiguous project vocabulary by defining canonical terms with clear avoid lists in a CONTEXT.md file. This ensures your team adopts one precise meaning for each concept, keeping documentation and code aligned.

What is the best way to document architectural decisions when trade-offs are ambiguous?▼

Recording architectural decisions in lightweight ADRs captures durable trade-offs when they matter. This approach keeps your architectural choices precise, reversible, and discoverable for future reference.

How do I create a context map for a multi-context repository?▼

Context mapping maintains boundaries for single-context or multi-context repositories by defining relationships within a CONTEXT.md file. This clarifies how different domain areas interact and separates distinct conceptual models.

When do I need to standardize domain terminology versus just writing inline code comments?▼

You need domain terminology standardization when project terms become ambiguous and the team requires one precise meaning. It supports Markdown-based glossary curation to keep definitions precise and discoverable across the entire codebase.

Can I use Markdown files to manage both glossary curation and architectural decision records?▼

Yes, domain modeling supports Markdown-based CONTEXT files and ADR notes. This format keeps your glossary definitions and architectural decisions precise, reversible, and discoverable directly alongside your codebase.

Related Skills

Explore More Software Engineering Skills→
AshenDulsankaAshenDulsanka
4

grill-with-docs

Validate project plans against domain models and update documentation inline.

Community
Intermediate
JFrangelJFrangel

documentation

Generate ADRs, runbooks, and README files in markdown, mdx, and github-flavored-markdown.

Community
Advanced
yongwoonyongwoon
8

ywc-commit

Stage, split, and commit session-relevant file changes using conventional commit standards.

Community
Advanced
plastikawebplastikaweb
1

code-documentation

Generate Markdown documentation, API references, and architecture guides from codebases.

Community
Basic