Part

Shared vocabulary

You might say: glossary, ubiquitous language, domain language, primitives catalog

A short file of the project's terms, each with one meaning, that agents and people both use. It can also list the building blocks of the code and the words to avoid.

What it does
Saves each agent from guessing the jargon, so tickets, prompts, code and reviews use the same short names.
Ask
Does each important concept have one written name, and does the code use it?

What to look for

  1. A glossary or primitives file in the repository
  2. Entries with a term, a one-line meaning and words to avoid
  3. Code, tickets and review comments that use the glossary's terms

Connections

Sources

  1. Matt Pocock, Skills For Real Engineers, #2: The Agent Is Way Too VerboseAgents are usually dropped into a project and asked to figure out the jargon as they go. So they use 20 words where 1 will do.
  2. Matt Pocock, Skills For Real Engineers, #2: The Agent Is Way Too VerboseThe Fix for this is a shared language. It's a document that helps agents decode the jargon used in the project.
  3. Kent C. Dodds, kcd-skills, autopilot skillPrimitives catalog: building blocks and code roots, kept short.
  4. Kody, kody-hq/kody repository, docs/contributing/architecture/primitives.yamlStable vocabulary for the visual-recap skill

Use it on your project

teardown-apply: hold "Shared vocabulary" (shared-vocabulary) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal