HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AminBlg
SimpleEnglish
Python2026–2026
AminBlg / SimpleEnglish

SimpleEnglish

Agent skill: make LLMs write docs in ASD-STE100 Simplified Technical

6Distinct people
6Mentions
0Explicit recommenders
4.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Agent skill: make LLMs write docs in ASD-STE100 Simplified Technical

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:34:31 PM UTC.

Show HN: STE80 Humanizer – de-AI text by writing 80% of the way to ASD-STE100 direct repository linkDebated

The discussion centers on whether the STE80 Humanizer effectively reduces AI-generated text patterns to improve readability or merely obfuscates machine output without adding genuine human voice. Participants strongly disagree on the value of the tool's implementation, with some praising its utility for clarity while others criticize the 'slop' quality of the skill file and the ethical implications of deceiving readers.

43 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by week6 dated mentions

Observed mentions: 2026-07-30 19:34:27 UTC to 2026-09-22 16:59:41 UTC. Weeks start Monday, UTC.

0122026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 272026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 242026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-21 00:00:00 UTC to 2026-09-28 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 21

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC110
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC101
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC101
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC101
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC000
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC000
Sep 212026-09-21 00:00:00 UTC2026-09-28 00:00:00 UTC202

What Hacker News says

1 sources
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
Read the rest
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
In My agent.md to improve LLM-assisted code quality

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.