The slop backlash arrives as tooling, not think-pieces. Everyone agrees agent output trends generic and agent users trend deskilled; today the fixes are installable things instead of essays — a tutorial engine that makes you do the work, agent skills and design systems that scrub the AI look off your UI, a refactoring layer for agent diffs, an Emacs tutor that refuses to type for you, and, as the mirror, a parody component library of every AI-design trope sitting at the top of HN. We dropped the platform news (Apple's Gemini-powered Siri rebuild, MiMo's 1,000-tok/s launch) and Cognition's FrontierCode — a benchmark that "grades like a tech lead" but that you can't actually run.
Lathe
A Go CLI plus a set of agent skills that turn "teach me X" into a multi-part, source-backed tutorial you work through yourself. You type /lathe build a 3D slicer in Erlang inside Claude Code, Cursor, or Codex; the skill generates the curriculum and citations, and the CLI serves it in a local reader at port 4242 with verification steps. Brew tap, curl installer, or go install; v0.3.0 shipped two days ago; 388 points on Show HN.
The inversion is the point: the model does the curriculum design and source-gathering — where it's strong — and you write the code, because doing it is how you learn. Delete the "explain X like I'm a senior engineer who's new to it" threads you keep re-typing into a chat window. Tradeoff: the author cheerfully calls the tool itself vibecoded, and a generated tutorial inherits whatever its sources got wrong — source-backing makes it auditable, not correct.
link