glossary

Manage a project's shared vocabulary as version-controlled YAML files. The glossary bridges the gap between what developers call things in code (cartitem), what users see in the UI ("Shopping Bag"), and what the team says in meetings ("basket"). It's the single source of truth for terminology — consumable by humans, AI tools, CI pipelines, and future web frontends alike.

Inspired by Domain-Driven Design's Ubiquitous Language and compatible with Contextive.

The glossary can live anywhere in the project. Users may choose a custom path (e.g. docs/terminology/, content/glossary/). Always resolve the glossary root before reading or writing.

Create and manage a project-wide ubiquitous language glossary — a shared vocabulary that developers, product managers, UX designers, QA engineers, and business analysts all use consistently. Use this skill whenever the user mentions "glossary", "terminology", "ubiquitous language", "what does X mean", "define a term", "add a term", "look up term", "glossary health", "stale terms", or wants to establish, query, or maintain shared project vocabulary. Also use when writing code, tests, or specs and consistent terminology matters — the glossary is the single source of truth for what terms mean in this project. Source: tsipotu/glossary-skill.