agentleFS
DonaldMurilloDonaldMurillo/gofastr/.claude/skills/plain-words/SKILL.md

plain-words

Skill24 starsChanged yesterdayMITView on GitHub

Write GoFastr-facing copy in plain, concrete words. Auto-load before writing or editing ANY user-facing sentence: taglines, README prose, site/UI text, headlines, docs, changelogs, marketing. Kills jargon, marketing adjectives, abstract nouns, and AI-slop phrasing. Triggers on writing/editing copy, tagline, hero, headline, lede, positioning, README prose, landing page, UI microcopy.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Very specific:

    Run every user-facing sentence through this filter before it ships: GoFastr copy states what the code does, in the words a Go developer …

    line 8
  2. Distinctive:

    Before you write or keep a user-facing sentence, ask:

    line 12
  3. Distinctive:

    If it sounds like a landing page, a keynote, or a pitch deck, delete it and write what the thing actually does.

    line 16
  4. Distinctive:

    If one shows up, delete the sentence and start over with the concrete thing.

    line 22
  5. Distinctive:

    Every claim must be checkable: If you can't point to a file, route, or behavior, don't write it.

    line 32

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

Plain words

Run every user-facing sentence through this filter before it ships: GoFastr copy states what the code does, in the words a Go developer uses.

The one test

Before you write or keep a user-facing sentence, ask:

Would a working Go developer say this out loud to a coworker?

If it sounds like a landing page, a keynote, or a pitch deck, delete it and write what the thing actually does. If you can't say it at a desk with a straight face, it's wrong.

Banned: never use these words or phrases

first-class, first-party, bolt-on, add-on, seamless(ly), powerful, robust, blazing(ly), lightning-fast, unlock, leverage, empower, enable (as filler), elevate, delight, craft(ed), journey, world-class, battle-tested, enterprise-grade, cutting-edge, next-gen, revolutionary, game-changer, supercharge, effortless, "out of the box" (as praise), "under the hood", "at the table", "wired for", "runs through", "baked in", introspect, surface (as a noun meaning API/tools/pages), projection, authoritative, paradigm, ecosystem, holistic, turnkey, native (as buzzword), rich (as praise), "just works", "so you can focus on what matters", "the way X should be", "not a bolt-on / not an afterthought".

If one shows up, delete the sentence and start over with the concrete thing.

Rules

  1. Name the real thing. "an agent can call posts_list", not "agents get a tool surface".
  2. Plain verbs: get, write, read, run, call, add, change, delete. Not: leverage, enable, empower, provide, deliver.
  3. Show it. A command, a file path, a route, a flag beats any adjective. Prefer a two-line code block over a sentence praising the code.
  4. One idea per sentence. Cut every word that isn't load-bearing. Long, comma-spliced sentences are where jargon hides.
  5. No praise adjectives. Facts don't need selling. Delete "powerful", "simple", "elegant", "clean".
  6. No metaphors. Say the literal thing. Cut "on-ramp", "batteries", "at the table".
  7. Every claim must be checkable. If you can't point to a file, route, or behavior, don't write it.

After you write

Re-read once. Strike every banned word. Replace every abstraction with the concrete thing it stands for. If the sentence still reads like copywriting, it is. Say it the boring way instead. Boring and true beats clever and vague, every time.

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.