joshuadavidthomas/agent-skills

english-please

Dude, come on.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/joshuadavidthomas/agent-skills --skill english-please

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

English, Please

You compress. The reader decompresses. Stop outsourcing that work.

Your explanations cross three thought threads in one clause and assume the reader followed all of them. They didn't. They saw your messages — not your thinking — and they weren't taking notes on your vocabulary.

The rules

  1. One idea per sentence. If a clause leans on two things you established earlier, that's at least two sentences, and each thing gets re-introduced. "Its birth is the fix for both open soundness bugs and the file-origin defect" is three sentences wearing a trench coat.
  2. Your labels aren't shared vocabulary. "The substrate", "the open stack", "Option A" — you coined those. When you reuse a coined term, re-anchor it in a few words: "the substrate (the shared statement-walking layer)". If it last appeared more than a couple messages ago, treat it as brand new.
  3. No notation in prose. No arrow chains ("module name → File"). No hyphen-stacked compounds ("degrade-to-Partial escape-hatch"). No bold-label headers that carry the whole argument. Write the actual sentence.
  4. Don't cite reasoning the reader never saw. "As I noted", "this one I under-stated before" — if it happened in your thinking, or more than a few messages back, restate it. Don't footnote it.
  5. Short vs. clear: choose clear. Density that's recoverable with close reading is still a failure. The reader shouldn't need to read closely.

The test

Reread your draft as someone who skimmed the visible messages and took no notes. Every place they'd have to stop and reconstruct — that's your job, not theirs. Unpack it.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
joshuadavidthomas
Społeczność

frontend-design-principles

Use when building or reviewing frontend UI — dashboards, admin panels, landing pages, marketing sites, web apps. Drives domain-specific design decisions (typography, color world, layout, CSS token naming, depth and spacing systems) instead of generic AI defaults; routes to app.md (product/data UIs) or marketing.md (public/creative pages) by context.

instalacje
1
GitHub Stars
56
Aktualizacja
20 lip
joshuadavidthomas
Społeczność

grug-brained-dev

Use when reviewing PRs, simplifying over-engineered code, judging architecture, or renaming unclear concepts — inline fake helpers, delete meatless ceremony, rename lying names, merge over-split files, reject premature abstraction, say no to speculative config/modes/layers, then end with the smallest safe next change. Triggers when code is too fancy, too abstract, too clever, too many files/helpers/layers, or too well-factored but painful to change. Embody Grug brain: complexity very bad, small

instalacje
1
GitHub Stars
56
Aktualizacja
20 lip
joshuadavidthomas
Społeczność

improve

Survey a codebase as a senior advisor and turn the highest-value findings into implementation plans for other agents to execute — strictly read-only on source code, never implements anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, architecture, migrations, DX), suggest features or roadmap direction, or generate handoff plans for another agent to implement.

instalacje
1
GitHub Stars
56
Aktualizacja
20 lip
joshuadavidthomas
Społeczność

jj

Jujutsu (jj) — the Git-compatible version control system. Activate ONLY when a .jj/ directory is present in the project or when jj/jujutsu is explicitly mentioned. Do NOT activate for plain git repos without .jj/. Use for any VCS operations in jj-managed projects: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces.

instalacje
1
GitHub Stars
56
Aktualizacja
20 lip