agentleFS
45ck45ck/hci-review-skill/.agents/skills/vocabulary-audit/SKILL.md

vocabulary-audit

Skill19 starsChanged 6 days agoMITView on GitHub

Normalize UI terminology by creating a canonical glossary of nouns, verbs, statuses, and labels used across the system.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use ultrathink. Use the current prototype, components, routes, docs, and visible copy.

    line 11
  2. Very specific:

    Write docs/hci/glossary.md unless the user asked for another path.

    line 14
  3. Distinctive:

    Create the directory if it does not exist.

    line 15
  4. Distinctive:

    Prefer language that is:

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit and normalize interface language for this scope:

$ARGUMENTS

Use ultrathink. Use the current prototype, components, routes, docs, and visible copy. Extract all important terms that affect understanding.

Output

Write docs/hci/glossary.md unless the user asked for another path. Create the directory if it does not exist.

Required sections

  1. Canonical glossary
  2. Terms to merge or ban
  3. Status vocabulary
  4. Action vocabulary
  5. Naming problems and recommendations

Tables to include

Canonical terms

| Term | Type (noun/verb/status) | Exact meaning | Where used | Notes |

Terms to avoid

| Avoid this term | Use instead | Reason |

Status model

| Status | Meaning | Entered when | Exited when |

What to look for

  • same concept with multiple names
  • vague verbs like "handle", "manage", "process"
  • inconsistent status labels
  • labels that require domain knowledge the user may not have
  • UI copy that does not match the underlying conceptual model

Synthesis

End with:

  • the five most damaging terminology inconsistencies
  • concepts that are overloaded or ambiguous across the system
  • priority terms to standardize before next implementation cycle

Quality bar

Prefer language that is:

  • concrete
  • consistent
  • distinguishable from nearby concepts
  • aligned with the user’s mental model

Deliverable style

  • Clear headings
  • Markdown tables
  • Mermaid diagrams where useful
  • Direct language
  • No filler

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.