agentleFS
Sign inStart free
p10ns11yp10ns11y/skills/semantic-name/SKILL.md

semantic-name

Skill2 starsChanged 40 days agoMITView on GitHub

Name the thing for what it does in that context. Do not use Gate as a default label. Triggers: "Never over use the word Gate, use semantically meaniful name for the context and situation"; "why all the llms are now using 'gate' word too much. rename it to something semantic and meaniful".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you name a module, flag, route, type, or function, use a word that states the job in this context.

    line 24
  2. Distinctive:

    Do not use Gate as a default label.

    line 25
  3. Distinctive:

    If a name already uses Gate, rename it to a semantic name and update the call sites in the same change.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

semantic-name

Name the thing for what it does in that context. Do not use Gate as a default label.

When / skip

UseSkip
naming a module, flag, route, type, or functionthe user asked for the word Gate
an existing name uses Gate as a default labela domain word that already states the job

Procedure

  1. When you name a module, flag, route, type, or function, use a word that states the job in this context.
  2. Do not use Gate as a default label. Do not invent Gate compounds unless the user asks for that word.
  3. If a name already uses Gate, rename it to a semantic name and update the call sites in the same change.

Done when

  • The name states the job in this context
  • Call sites match the new name in the same change
  • A search of the change shows no leftover Gate label for that thing

Anti-patterns

¬Do
Gate as a default labela word that states the job
rename the declaration onlyupdate call sites in the same change
invent a Gate compoundkeep Gate only when the user asked for that word

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.

Check your setup, free