asd-ste100
Skill0 starsChanged 21 days agoMITView on GitHub
Always apply ASD-STE100 Simplified Technical English to all docs, commit messages, code comments and chat replies. Use for any writing task.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- hamzzaqureshi/gravidextheir own version, first seen Nov 8, 2026
- nateslabach/skillstheir own version, first seen Nov 8, 2026
- smartwatermelon/claude-configtheir own version, first seen Nov 3, 2026
- twistedmelonman/claude-configtheir own version, first seen Nov 3, 2026
- gerardbalaoro/skillstheir own version, first seen Nov 1, 2026
- tarrragon/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use handoff, tdd and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 5 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
- GoogleSkill
code-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- humanlayer/humanlayer★ 13ksame name
- danyuchn/asd-ste100-skill★ 6.2ksame name
- filipstrand/mflux★ 2.6ksame name
- nuelcyoung/asd-ste100★ 39same name
- cfcosta/writing-styles★ 32same name
- prithivrajmu/asd-ste100★ 16same name
- parthjshah95/visual-planning-skills★ 14same name
- nateslabach/skills★ 6same name
- The-Utopia-Studio/skills★ 6same name
- A-Ariyanto/ASD-STE100-skill★ 4same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- audit-repoSkill
- audit-uiSkill
- ooga-boggaSkill
- session-endSkill
- ui-uxSkill
- yagniSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 31 edited versions we read keep these.
8
Distinctive
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
- Distinctive: line 13
Put the main fact first. Use "Do not" for prohibitions.
- Distinctive: line 14
Keep the article ("the", "a") and the verb.
- Distinctive: line 20
Use simple verbs: "use", not "utilize".
- Distinctive: line 21
No filler: "basically", "just", "simply", "please note that".
- Distinctive: line 22
No phrasal-verb chains, idioms, or humor.
- Distinctive: line 23
Avoid -ing forms as verbs.
- Distinctive: line 24
Write numbers as digits. Keep units after a space (5 s, 90 fps).
- Distinctive: line 28
Write the current fact. Do not narrate history.
“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ASD-STE100 style
Apply to every text you write: docs, commits, comments, chat.
Sentences
- One idea in each sentence. 20 words or fewer (procedures: 25 max).
- Active voice. Present tense. Use the imperative for instructions.
- Put the main fact first. Use "Do not" for prohibitions.
- Keep the article ("the", "a") and the verb. Do not drop them.
- Paragraphs: 6 sentences or fewer.
Words
- One term for one thing. Do not vary a name for style.
- One word, one meaning, one part of speech. "Test" is a noun or a verb, not both in one doc.
- Use simple verbs: "use", not "utilize". "Start", not "initiate". "Show", not "display" or "illustrate".
- No filler: "basically", "just", "simply", "please note that".
- No phrasal-verb chains, idioms, or humor.
- Avoid -ing forms as verbs. Avoid "may", "might", "could" for facts. Say "can" or state the condition.
- Write numbers as digits. Keep units after a space (5 s, 90 fps).
Facts about the past
- Give a past mistake one line: "Was: X. Is: Y."
- Write the current fact. Do not narrate history.
Check before you send
- Count the words in each sentence.
- Find passive verbs and rewrite them.
- Find a second name for the same thing and use one name.
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
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.