domain-modeling

Use when a project needs shared terminology, glossary updates, ADRs, clearer domain language, or when user language conflicts with existing code, ticket…

Skill by tensology

IndexedMIT★ 17

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tensology-domain-modeling

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when a project needs shared terminology, glossary updates, ADRs, clearer domain language, or when user language conflicts with existing code, ticket, board, project, workflow, or CONTEXT.md terms.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/domain-modeling

What's inside

Skill name: domain-modeling
Description: Use when a project needs shared terminology, glossary updates, ADRs, clearer domain language, or when user language conflicts with existing code, ticket, board, project, workflow, or CONTEXT.md terms.
License: MIT
Instructions: 20 lines in SKILL.md · view on GitHub

Files (3)

SKILL.md
adr-format.md · references/
context-format.md · references/

SKILL.md (first lines)

# Domain Modeling

Use this to keep the project language sharp while planning or implementing.

## Workflow

1. Look for `CONTEXT.md`, `CONTEXT-MAP.md`, and nearby ADRs.
2. When a term is fuzzy, propose one canonical term and test it with a concrete scenario.
3. When user language conflicts with code or docs, surface the conflict and resolve it before implementation.
4. Update the glossary only when a term is settled.
5. Create an ADR only when the choice is hard to reverse, surprising without context, and the result of a real tradeoff.

## DecisionsAI Fit

- Use board/ticket/workflow names as evidence, not as the glossary by themselves.
- Keep glossary entries free of implementation detail.
- Put implementation decisions in ADRs or workflow artifacts, not in `CONTEXT.md`.
- Prefer project memory sync when the active workflow needs the term later.

From tensology/decisionsai, MIT.

Signals

Stars: 17
Forks: 2
Open issues: 0
Last commit (this folder): Oct 2, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/tensology/decisionsai
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from tensology

Cite this page

domain-modeling skill. Agent Mart. https://agentmart.dev/skills/tensology-domain-modeling (last updated 2026-10-24)