Domain Modeling
vinvcn/mattpocock-skills-zh-CN
构建并打磨项目的领域模型。适用于讨论 codebase 术语、编写或编辑 GLOSSARY.md，或记录或编辑 ADR。
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Install Domain Modeling
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brim-borium/spotify_sdk domain-modeling --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/domain-modeling .claude/skills/domain-modeling && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .claude/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modelingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brim-borium/spotify_sdk domain-modeling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/domain-modeling .agents/skills/domain-modeling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .agents/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brim-borium/spotify_sdk domain-modeling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/domain-modeling .cursor/skills/domain-modeling && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .cursor/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brim-borium/spotify_sdk.git --path .agents/skills/domain-modeling--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brim-borium/spotify_sdk domain-modeling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/domain-modeling .gemini/skills/domain-modeling && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .gemini/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brim-borium/spotify_sdk domain-modelingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/domain-modeling .github/skills/domain-modeling && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .github/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brim-borium/spotify_sdk --skill domain-modeling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brim-borium/spotify_sdk domain-modeling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brim-borium/spotify_sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/domain-modeling .opencode/skills/domain-modeling && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "domain-modeling" agent skill from https://github.com/brim-borium/spotify_sdk/tree/main/.agents/skills/domain-modeling into .opencode/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
domain-modeling- GitHub stars
- 166
- Used in
- 5 other repos
- Token cost
- ~806 tokens
- SKILL.md length
- 400 words
- Files
- 4
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
- Works in 3 steps: Hard to reverse: the cost of changing… → Surprising without context: a future… → The result of a real trade-off: there…
- Discussing codebase terminology
- SKILL.md covers File structure and During the session
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Domain Modeling is an agent skill from brim-borium/spotify_sdk. Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `ADR-FORMAT.md`, `GLOSSARY-FORMAT.md` and `agents/openai.yaml`).
It sits in Development, covering Domain-driven design and Architecture decision records. The repository describes itself as: Flutter Package to connect the spotify sdk. The licence is Apache-2.0.
When your agent uses it
- Discussing codebase terminology
- Editing a GLOSSARY.md
Example prompts
- “/domain-modeling”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Hard to reverse: the cost of changing your mind later is meaningful
- Surprising without context: a future reader will wonder "why did they do it this way?"
- The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons
What it can do on your machine
Read from SKILL.md and the folder at commit 2622fc0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Domain Modeling loads about 806 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 400 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brim-borium/spotify_sdk at commit 2622fc0, republished under its Apache-2.0 licence (© brim-borium). 400 words, ~806 tokens.
Download SKILL.mdSave it as
.claude/skills/domain-modeling/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- domain-modeling
- description
- Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Domain Modeling
Actively build and sharpen the project's domain model as you design. This is the active discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading GLOSSARY.md for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)
File structure
Most repos have a single context:
/
├── GLOSSARY.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/If a GLOSSARY-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:
/
├── GLOSSARY-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── GLOSSARY.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── GLOSSARY.md
│ └── docs/adr/Create files lazily: only when you have something to write. If no GLOSSARY.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in GLOSSARY.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y. Which is it?"
Sharpen fuzzy language
When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things."
Discuss concrete scenarios
When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
Show full SKILL.md (171 more words)Show less
Cross-reference with code
When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible. Which is right?"
Update GLOSSARY.md inline
When a term is resolved, update GLOSSARY.md right there. Don't batch these up: capture them as they happen. Use the format in GLOSSARY-FORMAT.md.
GLOSSARY.md should be totally devoid of implementation details. Do not treat GLOSSARY.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.
Offer ADRs sparingly
Only offer to create an ADR when all three are true:
- Hard to reverse: the cost of changing your mind later is meaningful
- Surprising without context: a future reader will wonder "why did they do it this way?"
- The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons
If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.
© brim-borium, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in .agents/skills/domain-modeling of brim-borium/spotify_sdk.
- SKILL.md
- ADR-FORMAT.md
- GLOSSARY-FORMAT.md
- agents/openai.yaml
Open the folder on GitHubat commit 2622fc0
Used in 5 other repositories
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in brim-borium/spotify_sdk, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Domain Modeling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Domain Modeling this skillbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Domain Modelingvinvcn/mattpocock-skills-zh-CN | 4.7k | — | ~477 | Automated safety check: Pass | MIT | |
| Domain Modelingdevcxl/mattpocock-skills-zh | 440 | — | ~412 | Automated safety check: Pass | MIT | |
| Domain Modelingiurysza/module-graph | 420 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Expectationscitypaul/.dotfiles | 740 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Domain Modelingromiluz13/cc10x | 164 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Domain Modeling
devcxl/mattpocock-skills-zh
构建和完善项目的领域模型。当讨论代码库术语、编写或编辑 GLOSSARY.md，或记录或编辑 ADR 时使用. An agent skill from devcxl/mattpocock-skills-zh.
Domain Modeling
iurysza/module-graph
Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.
Expectations
citypaul/.dotfiles
Decide where a learning, gotcha, or decision should live so it is not lost, and capture it there while context is fresh.
Domain Modeling
romiluz13/cc10x
A skill your agent uses when changing or sharpening a project's domain model: challenge terms against the glossary, sharpen fuzzy language, stress-test with edge-case scenarios, update CONTEXT.md…
Domain Model
sammcj/agentic-coding
Actively build and sharpen a project's domain model - challenge terms against the glossary, stress-test boundaries with scenarios, cross-reference against the code, and record the glossary…
More from brim-borium/spotify_sdk
All 9 skills in this repoRetro
brim-borium/spotify_sdk
Conduct a retrospective on a coding session. An agent skill from brim-borium/spotify_sdk.
Implement Spec
brim-borium/spotify_sdk
Implement the result of /to-spec and /to-tickets in code. An agent skill from brim-borium/spotify_sdk.
Android Setup
brim-borium/spotify_sdk
Configure or clean Spotify App Remote SDK AAR resolution on Android.
Build Runner
brim-borium/spotify_sdk
Generate Dart JSON models and .g.dart files using buildrunner.
PR
brim-borium/spotify_sdk
Use when writing a PR body.
Platform Sync
brim-borium/spotify_sdk
Synchronize method channels and event streams across Dart, Android (Kotlin), iOS (Swift), and Web.
Related
Categories
Questions about Domain Modeling
What does Domain Modeling do?
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk. Domain Modeling is an agent skill from brim-borium/spotify_sdk. Build and sharpen a project's domain model.
When should I use Domain Modeling?
Domain Modeling fits situations like: discussing codebase terminology; editing a GLOSSARY.md.
How do I install Domain Modeling in Claude Code?
Run `npx skills add brim-borium/spotify_sdk --skill domain-modeling -a claude-code`. Or copy the skill folder (.agents/skills/domain-modeling in brim-borium/spotify_sdk) into .claude/skills/domain-modeling in your project. Claude Code loads it when a task matches its description.
How do I install Domain Modeling in Codex?
Run `npx skills add brim-borium/spotify_sdk --skill domain-modeling -a codex`. Or copy the skill folder (.agents/skills/domain-modeling in brim-borium/spotify_sdk) into .agents/skills/domain-modeling in your project. Codex loads it when a task matches its description.
Can I use Domain Modeling in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brim-borium/spotify_sdk --skill domain-modeling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain-modeling, .gemini/skills/domain-modeling, .github/skills/domain-modeling and .opencode/skills/domain-modeling in your project.
What does Domain Modeling need to run?
SKILL.md names no scripts, command-line tools or credentials: Domain Modeling is instructions for the agent only.
Does Domain Modeling access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Domain Modeling safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Domain Modeling use?
Domain Modeling is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Domain Modeling use?
About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Domain Modeling?
Skills that share tags, products or a category with Domain Modeling: Domain Modeling (vinvcn/mattpocock-skills-zh-CN, 4.7k stars), Domain Modeling (devcxl/mattpocock-skills-zh, 440 stars), Domain Modeling (iurysza/module-graph, 420 stars) and Expectations (citypaul/.dotfiles, 740 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Domain Modeling?
brim-borium (a GitHub user) maintains it in brim-borium/spotify_sdk, which has 166 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.
Source: brim-borium/spotify_sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.