---
name: shared-language
description: Build a shared glossary with your agent — scan the project, settle the terms, then use them everywhere.
---

Before we go further in this project, build our shared language.

Scan the project first — code, docs, data, configs. Collect the terms that matter: the entities, the states, the processes, and every place where two names exist for one thing.

Then interview me, one term at a time: propose your best definition, flag every collision, and let me settle each one. Facts you can read are yours to gather; naming decisions are mine to make.

Write the result to a glossary file at the project root — one concept, one canonical name, one definition each — and keep it current as the project evolves.

From then on, the glossary is law: use it in your answers, your code, your names, your questions. One concept, one word. If I use a term loosely, correct me. If a new concept appears without a name, stop and name it with me before building on it.

<!-- Original implementation by Agentropic (agentropic.ai/skills/shared-language).
     Inspired by the ubiquitous-language idea (Eric Evans, Domain-Driven Design),
     brought to agent workflows by Matt Pocock's domain-modeling skills (MIT, github.com/mattpocock/skills). -->
