skills.rest
hohai99
hohai99COMMUNITY
Explore all skills by this author →
WebsiteGitHub

workspace-domain-glossary

Extract and enforce canonical domain terms across specifications and code.

1|Updated Jan 22, 2026
Search Tags:#consistency#glossary#code-review#terminology#spec-writing#domain-terms
One-click install
npx skills add https://github.com/hohai99/antigravity-skills --skill workspace-domain-glossary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace-domain-glossary
Source: https://github.com/hohai99/antigravity-skills/tree/main/.agent/skills/workspace-domain-glossary
Command: npx skills add https://github.com/hohai99/antigravity-skills --skill workspace-domain-glossary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill builds and enforces a single source of truth for business terminology to prevent drift and ambiguity across specifications, code, and documents.

Core Features & Use Cases

  • Canonical Term Definitions: Create and maintain canonical meanings for domain terms to ensure consistent usage.
  • Conflict Detection: Identify and reconcile conflicting terminology across specs, code, and communications.
  • Terminology Alignment: Update artifacts to reflect canonical terms across teams and projects.

Quick Start

  1. Audit current terminology across specifications and code.
  2. Define canonical meanings for the top terms.
  3. Apply the glossary to new and existing artifacts.

Frequently Asked Questions about workspace-domain-glossary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent terminology drift across specifications and code?▼

To prevent terminology drift, you must consolidate and enforce a domain glossary that defines canonical meanings. This ensures consistent usage across specifications, code reviews, and migration tasks.

What is the best way to maintain consistent domain terms during spec-writing?▼

Maintaining consistent domain terms during spec-writing requires creating canonical term definitions and applying them to new and existing artifacts. This aligns terminology across teams and projects.

How do I detect conflicting terminology across project artifacts?▼

Detecting conflicting terminology requires auditing current terms across specifications and code. By extracting terms and defining canonical meanings, you can identify and reconcile inconsistencies.

Can I use a glossary to update artifacts across multiple projects?▼

Yes, you can use a glossary to update artifacts across multiple projects. Terminology alignment applies canonical terms to ensure consistency across teams during migration tasks and code reviews.

What are the limitations of manually aligning domain terms?▼

Manually aligning domain terms often leads to ambiguity and drift across documents and code. Without a single source of truth for business terminology, conflicting usage persists across teams and projects.

Related Skills

Explore More Content & Communication Skills→
raphaelmansraphaelmans

ubiquitous-language

Extract domain terminology from conversations into a structured glossary file.

Community
Intermediate
ruskibeatsruskibeats

ubiquitous-language

Extract domain-specific terminology and propose canonical terms from text.

Community
Intermediate
docs-plusdocs-plus
88

ubiquitous-language

Extract domain terms from conversations and generate a markdown glossary with flagged ambiguities.

Official
Intermediate
OneWave-AIOneWave-AI
245

conversation-archaeologist

Extract writing style, goals, and preferences from past Claude conversations.

Official
Advanced