Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Domain Language Governance

    1

    Resolve terminology drift across specs, APIs, and code into context-specific canonical terms with definitions, invariants, and aliases, while keeping behavior-changing questions open for a domain decision.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Domain Language Governance

    Domain Language Governance

    Example session with this skill installed

    The API, database, and docs use "user," "account," and "member" interchangeably. Based only on the supplied authority and examples, define canonical terms with meaning, context, invariant, and authority; map deprecated aliases and artifacts to align; and identify open domain questions. Do not infer an unverified product rule or claim files changed.

    • Read your context and instructions
    • Compiled the domain language governance

    Illustrative output based on the synthetic example included with the package. These names and findings are not repository evidence; no project files were inspected or changed.

    CANONICAL TERMS

    TERMMEANINGCONTEXTINVARIANTAUTHORITY
    AccountBilling entity that owns a subscriptionbillingExactly one ownerADR-009
    UserA person who can authenticateidentityBelongs to at least one AccountADR-009
    MemberRole of a User within an AccountauthorizationUser and Account pairNew glossary entry

    CONFLICTS / DEPRECATED ALIASES

    • The users table stores Accounts in this synthetic example; route a concept rename and migration to the implementation phase.
    • member_id refers to User in some API uses and to a membership row in others; split the ambiguous reference.

    ARTIFACTS TO ALIGN

    • Glossary
    • OpenAPI schema
    • User and Account tables
    • Authentication middleware

    OPEN DOMAIN QUESTIONS

    • Can a User belong to multiple Accounts simultaneously? UNVERIFIED. A product decision is needed before changing the schema.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Domain Language Governance resolves competing names and overloaded terms across project contexts into canonical records grounded in project authority and representative evidence. Use it when the same concept has different names across specs, APIs, code, or agent instructions, or when one word means different things across services. It is not for style-only renaming of local variables.

    What it does

    • Reads the smallest sufficient glossary, ADR, spec, API, type, test, and implementation evidence, recording each term source and observed meaning.
    • Classifies conflicts as synonym duplication, overloaded term, missing concept, wrong abstraction boundary, or stale artifact.
    • Defines canonical terms from authoritative product or domain evidence, with context, invariant, allowed aliases, and ambiguous usage to avoid.
    • Stops for a domain decision when uncertainty changes behavior or contracts. If only a bounded sample is available, repository-wide terminology coverage remains UNVERIFIED.
    • Maps the glossary, ADR, spec, API/schema, tests, or code that may need alignment, without mass-renaming implementation while meaning is unsettled.

    Output

    A canonical-terms record with each term meaning, context, invariant, and authority, followed by conflicts or deprecated aliases, artifacts to align, and open domain questions.

    Boundaries

    Project governance documents, accepted ADRs, boundaries, glossaries, and approved specs outrank the skill. It does not replace project-specific rules or guarantee model output. Missing evidence, capability, or authority stays explicit instead of being invented. A style-only local variable rename is outside scope.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    The result depends on accessible project authority and representative source evidence. It cannot settle a missing product decision when terminology changes behavior or contracts. When only a bounded sample is available, repository-wide terminology coverage remains UNVERIFIED. It maps artifacts to align but does not claim a mass rename, commit, push, install, or deployment.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    Permissions

    Read Files

    Read Files is required for project glossaries, ADRs, specifications, and representative APIs, types, tests, and implementation evidence. Terminal/Shell is optional only for targeted search when available; use host-native or manual search when it is not, and mark repository-wide coverage UNVERIFIED when evidence is bounded. Write Files, Browser, Network Access, MCP, external accounts, and Environment Variables are not required by the package. Commits, pushes, merges, installs, deployments, and implementation changes are not implied.

    Listed17 days ago

    What's inside

    Frequently Asked Questions

    It identifies the glossary, ADR, spec, API/schema, tests, or code that may need alignment. It does not mass-rename implementation while term meaning is unsettled, and it does not imply code changes were made.

    Start with the project glossary, ADRs, and approved specs, then inspect representative APIs, types, tests, and only enough implementation to identify the drift. Each term should be tied to its source and observed meaning.

    It records the context, invariant, canonical meaning, authority, and aliases to avoid. If the difference changes behavior or contracts, it stops for a domain decision instead of inventing semantics.

    A canonical-terms table with term, meaning, context, invariant, and authority, followed by conflicts or deprecated aliases, artifacts to align, and open domain questions.

    Only for the evidence it can inspect. When it reviews a bounded sample, it marks repository-wide terminology coverage UNVERIFIED rather than claiming complete coverage.

    New in Technical Documentation