Skip to content

borghei/Claude-Skills / engineering/domain-modeling

domain-modeling

Verified

Keep a project glossary of domain terms and lightweight decision records, and catch banned synonyms in docs and code. Use when terms are used inconsistently, writing a GLOSSARY.md, or recording a design decision.

FileKindSize
SKILL.mdskill md13.9 KB
assets/GLOSSARY-template.mdmarkdown2.1 KB
assets/adr-template.mdmarkdown1.1 KB
assets/sample_GLOSSARY.mdmarkdown2.3 KB
assets/sample_adr_set.jsonconfig3.0 KB
assets/sample_conversation.txtmarkdown1.4 KB
assets/sample_feature_notes.mdmarkdown517 B
references/decision-records.mdmarkdown6.3 KB
references/glossary-practice.mdmarkdown7.4 KB
scripts/adr_lint.pyexecutablescript9.3 KB
scripts/glossary_lint.pyexecutablescript8.8 KB
scripts/term_extract.pyexecutablescript9.6 KB

assets/adr-template.md

View on GitHub
# NNNN. <Decision stated as a short sentence>

**Status:** proposed
**Date:** YYYY-MM-DD
**Deciders:** <roles or names>

<!--
File name: docs/adr/NNNN-kebab-slug.md, next free number (adr_lint.py --next-title prints it).
Write a record only if all three hold:
  1. Reversing it later would cost real time or money.
  2. A newcomer reading the code would be surprised without the explanation.
  3. There was a genuine alternative, rejected for a reason.
Statuses: proposed | accepted | rejected | deprecated | superseded by NNNN.
Never delete a record; supersede it, and add "**Supersedes:** NNNN" to the new one.
A short record is fine. Context and Decision are required; the rest only when it helps.
-->

## Context

<The forces at play: the problem, the constraint that is not visible in the code,
and what made this a decision rather than an obvious default. Use glossary terms.>

## Decision

We will <the decision, in one or two decisive sentences>.

## Alternatives considered

- <Option>: rejected because <reason>.

## Consequences

<What becomes easier, what becomes harder, and what follow-up work this creates.>
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall