Re:My agent.md to improve LLM-assisted code quality
by wpasc on Sunday August 23, 2026 @04:07PM
(#49412103)
idk who came up with it first, but ASD-STE100 has been floating around more since matt pocock put it in one of his skills
Re:My agent.md to improve LLM-assisted code quality
by mattjoyce on Sunday August 23, 2026 @05:24PM
(#49412795)
This will produce quite verbose prose. STE100 is good for specs and explanations but it works best with a glossary or terms. will burn tokens.
Re:My agent.md to improve LLM-assisted code quality
by hartleybrody on Monday August 24, 2026 @12:23PM
(#49422091)
This has not been my experience at all. I have been using this skill[0] for several weeks and when I ask it to rewrite existing AI slop docstrings to use this convention they are nearly always 10-20% smaller, plus easier to read and mostly free from the traditional "tells" of AI writing.
Re:My agent.md to improve LLM-assisted code quality
by statenjason on Sunday August 23, 2026 @08:29PM
(#49413980)
Agreed. ASD-STE100 makes automated code reviews tolerable.
Re:My agent.md to improve LLM-assisted code quality
by bityard on Sunday August 23, 2026 @08:40PM
(#49414027)
Do you give the model access to the ASD-STE100 spec for reference/review or are you just assuming that enough of it is baked into the model for it to mostly adhere to it?
Re:My agent.md to improve LLM-assisted code quality
by sha-3 on Monday August 24, 2026 @02:28AM
(#49415878)
If we alter the way LLMs talk, will it noticeably affect the quality of code it produces?
Re:My agent.md to improve LLM-assisted code quality
by hartleybrody on Monday August 24, 2026 @12:28PM
(#49422199)
This is probably the skill you remembered: https://github.com/AminBlg/SimpleEnglish
I have been using it for a few weeks, and it significantly improves the quality of the docstrings and code comments, as well as the readability of spec docs.
I have also added a few key bullet points to my AGENTS.md and have found the results to be very effective and generating plans and code that looks like something I would have written:
-----------
## planning, design and spec docs
- the highest design goal is simplicity -- in our systems and our mental model -- even if if means edge cases are unaddressed and could potentially fail
- please practice "ya ain't gunna need it" (YAGNI) do not add unnecessary guardrails
- do not plan to add caching, many layers of unnecessary abstraction or other premature optimizations
- look for places where adding or clarifying an invariant would simplify the code or the overall system
please specifically try to avoid:
- redundant calculations or duplicated work
- duplicated conditionals or state-machine logic
- storing state that can be derived from other state, which could drift and become out of sync over time
- leaky abstractions across layers of the application
- multi-line comments explaining a variable name or a single statement. well chosen names and design should makes these unnecessary, as the code is self-documenting
**Always use ASD-STE100 Simplified Technical English
Disclaimer: I saw this listed in some other HN post that I can' locate right away.