SkillsAdd

fudesign2008/open-skills

domain-language-discipline

Hard discipline for project domain language: maintain a pure glossary in CONTEXT.md (no implementation details), challenge fuzzy or conflicting terms in-session, create files lazily, keep orthogonal to OpenSpec behavioral contracts.

First seen Jul 29, 2026

Installation

$ npx skills add fudesign2008/open-skills --skill domain-language-discipline
View on skills.sh ↗ GitHub repository ↗

Summary

  • Hard discipline for project domain language: maintain a pure glossary in CONTEXT.md (no implementation details), challenge fuzzy or conflicting terms in-session, create files lazily, keep orthogonal to OpenSpec behavioral contracts.
  • Referenced by PDCA hosts during clarify/analyze when domain terms matter.
  • Triggers — 「领域语言」「CONTEXT.md」「术语表」「统一语言」「领域词汇」 / domain language discipline, project glossary, CONTEXT.md.
  • Do NOT use as a substitute for OpenSpec specs.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from fudesign2008/open-skills · top by installs.

npx skills add fudesign2008/open-skills
jira-fix-workflow 73 solve-workflow 71 opsx-solve-workflow 69 opsx-jira-fix-workflow 68 typescript-check 67 android-webview-debug 67 jira-read 66 git-commit 66 opsx-jira-fix-batch 65 think-big 64

Browse all from fudesign2008/open-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,026 B
  • docs SUMMARY.md 546 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 31 installs

SKILL.md

Domain Language Discipline

Internal shared skill. Single source of truth for project ubiquitous language as a glossary, orthogonal to OpenSpec. Hosts declare it in dependencies and abort if missing — no silent fallback.

Name note: intentionally not named domain-modeling (external skills repo). Use this name only.

What CONTEXT.md is (and is not)

Is Is not
Canonical terms and boundaries (glossary) Spec, ticket, or task list
Pure domain language Implementation details, APIs, schemas, file paths
Orthogonal companion to OpenSpec Replacement for openspec/ proposal/specs/design/tasks

If a root CONTEXT-MAP.md exists, treat it as a pointer to multiple context-local CONTEXT.md files; otherwise use a single root CONTEXT.md.

Required behavior

  1. Read when domain language is in play — if CONTEXT.md (or mapped files) exists, load relevant terms before sharpening analysis or solutions that hinge on vocabulary.
  2. Challenge conflicts — when the user (or session) uses a term that conflicts with the glossary, surface the conflict and resolve which meaning is canonical before continuing as if both were fine.
  3. Sharpen fuzzy language — propose a precise canonical term when language is vague or overloaded; confirm with the user when it is a decision (per clarifying-question-discipline if asking).
  4. Update lazily, inline — when a term is resolved, update CONTEXT.md immediately. Create the file only when the first term is recorded. Keep entries free of implementation detail.
  5. ADRs sparingly — offer an ADR only when hard-to-reverse and surprising without context and the result of a real trade-off; otherwise skip. ADRs are optional companions, not required by this skill's core loop.

Forbidden

  • Writing OpenSpec requirements, code designs, or API contracts into CONTEXT.md
  • Treating the glossary as the behavioral source of truth instead of OpenSpec / host sinks
  • Renaming this skill to domain-modeling inside this repository

Integration guide

  • Hosts: one-line pointer at clarify/analyze when domain terms matter — load this skill; do not paste glossary format tables into hosts.
  • Prefer user-invocable: false; users reach it through PDCA hosts or explicit load.
  • Behavior changes still go to OpenSpec (or the host's artifact sink), not into CONTEXT.md.