When to use it

Use project-vocabulary when a domain term keeps changing meaning: account might describe a person, a billing relationship, or an organization. A shared definition helps prevent those differences from becoming design or implementation mistakes.

How it works

Figure 01

Resolve the meaning before changing the glossary.

  1. Notice

    Identify a term with conflicting or unclear meanings.

  2. Propose

    Show the exact definition or alias change.

  3. Update

    Write only after an explicit request or approval.

ResultCONCEPTS.md at the repository root
Reading a glossary and proposing a definition do not authorize a write. The update checks that the file has not changed underneath it.

The skill reads the repository-root CONCEPTS.md glossary and applies its terms in conversation. Entries define concepts, retain aliases for retired names, and flag meanings that are still disputed.

When it notices an ambiguity, it can propose an exact change. An explicit add or update request, or approval of that proposal, allows the glossary helper to write the change atomically after checking that the file has not changed underneath it.

An example request

Ask your agent

“Add workspace to CONCEPTS.md: it owns projects and memberships; a user can belong to several workspaces. Keep organization as a retired alias.”

This illustrates a request you can adapt; it is not a transcript of a completed run.

A small, reviewable glossary that both people and agents can use while discussing the domain and naming code.

Install and use

The skill’s identifier is project-vocabulary. It ships in the project-vocabulary plugin. In Claude Code, first add the Overclock marketplace, then install the package:

/plugin install project-vocabulary@overclock

For a standalone installation, keep the skill directory and its bundled resources together. The repository also includes per-skill Codex metadata. Read the full skill instructions for its exact workflow and supporting files.

What to keep in mind

Automatic selection may inspect the glossary and suggest changes, but it does not authorize writes. Conflicting definitions remain visible until resolved.

Workflow expectations belong in lessons-learned. This skill should stay quiet when the task has no meaningful domain vocabulary to maintain.

  • Lessons learned — Turn a correction into a reusable lesson, and keep repeated lessons up to date.
  • Groundwork — Resolve the decisions that matter before planning a substantial change.