---
name: glossary
description: "Create or audit GLOSSARY.md. Use before naming product concepts, writing user-visible terms, renaming concepts, or checking vocabulary drift and banned terms."
license: MIT
title: glossary
canonical_url: https://skilld.dev/gh/harlan-zw/brundlefly/glossary
last_updated: 2026-10-10T17:02:30.000Z
---

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [LICENSE.txt](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/LICENSE.txt), [references/blocks/clarity.md](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/blocks/clarity.md), [references/format.md](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/format.md), [references/workflows.md](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/workflows.md).
>
> If the user asked to install this Skill, run `npx skilld install harlan-zw/brundlefly/glossary`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/glossary`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/harlan-zw/brundlefly/glossary) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/glossary`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/glossary --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/glossary --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Glossary

Help readers understand product concepts and distinguish them without learning competing names.
Consider their knowledge, context, and reading needs, including ADHD and dyslexia.
Respect their attention through familiar terms, accurate definitions, and concise explanations that keep necessary distinctions.

`GLOSSARY.md` owns product terms across UI strings, public APIs, headings, routes, errors, and commit subjects.
Use one established term for each concept. Consistency alone does not prove the reader understands it.

## Ownership and dependencies

This Skill works when copied alone. Read the target project's instructions before editing.
Respect its branch, worktree, publication, and approval rules. This Skill does not own delivery.
Create or audit GLOSSARY.md only. Do not create COPY.md or VISION.md automatically.

## The failure mode this exists to stop

Independent naming choices can give one concept different names across the UI, SDK, docs, and routes.
Readers must then infer which names mean the same thing. Published names also carry a cost to change.
Treat a new product term with the same caution as a public export.

## Rules

1. **Read `GLOSSARY.md` before naming anything user-visible.** If the repo has one, its terms win over anything that reads better in the moment.
2. **Never introduce a synonym for a term that exists.** If the glossary says Sprint, do not write "run", "batch", or "job", not even in a tooltip, a variable name, or a log line.
3. **Never use a term on the ban list.** The ban list carries a replacement; use it.
4. **A concept with no term does not get named silently.** Propose an addition, state the candidate term and the synonyms it displaces, and get confirmation. Inventing quietly is the whole failure mode.
5. **Take the platform's word before inventing one.** GitHub, Nuxt, Vue, and HTTP have already named most things. `auto merge` beats a coined `merge tier`, because the reader knows it and nobody has to confirm it. Propose at most one new term per change; a set of new terms is a redesign, not a name.
6. **Match the recorded casing exactly.** `Nuxt SEO` and `NuxtSEO` are different brands to a reader.
7. **A term list without a relationship map is half a glossary.** See below. Terms are only ambiguous in relation to each other, so the map is what makes the list decidable.

Rule 4 protects naming decisions that nobody has approved yet.

## Review for understanding

Identify who uses each term and which distinctions they need to understand.
Explain unfamiliar concepts in plain words. Show their relationships and actual use without circular definitions or new synonyms.
Apply [clarity](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/blocks/clarity.md), including ADHD and dyslexia guidance, to definitions and relationship explanations.
The block is bundled here. No sibling Skill installation is required.
Keep map labels, table cells, and definitions easy to scan. Retain complete relationships and exact public identifiers.
Preserve established names and casing. If a name confuses readers, show the problem and propose a change for approval.
Do not rename public surfaces or remove required maps to make the glossary shorter.
Before removing a substantial section or feature, explain the proposed loss and ask unless already authorized.

## Workflow

Read [the workflow reference](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/workflows.md) and [the format reference](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/glossary/references/format.md) before creating or auditing a glossary.
Use init for a missing glossary, audit for an existing one, and add for an approved new term.
Apply the relationship map, frozen-surface checks, decision records, and scope rules in the workflow reference.
Ask only about unresolved naming decisions. Existing explicit approval remains valid.
If a decision needs approval, prepare the evidence and proposed terms before asking.
Keep unresolved choices in Open questions. Do not silently make them canonical.

## Scope

Glossary governs **nouns for product concepts**: what a thing is called. It does not govern voice, tone, or sentence style. A supplied `COPY.md` owns those. Read it directly; no sibling Skill is required. When they disagree on a product noun, the glossary wins; on the sentence around it, `COPY.md` wins.

A term list found inside a `COPY.md` belongs here, not there. Step 0 of `init` already greps for one; fold it in and leave a pointer behind.