Guides and resources for AI engineers: an agents course, five handbooks, a hands-on second-brain project and a vetted reading list.
JavaScript agent-skillsai-agentsai-engineeringclaudeclaude-codeclaude-skillsknowledge-graphknowledge-managementllmmcpobsidianpersonal-knowledge-basepkmsecond-brain
Resources
A health warning first: "loop engineering" was coined in June 2026 and is three months old as this page is written. The practices underneath are sturdier than the label — Steinberger himself was already asking whether the conversation had moved from loops to graphs by mid-July. Read for the mechanisms, hold the vocabulary loosely.
The naming
- Peter Steinberger's post — the line that caught, June 2026: "You shouldn't be prompting coding agents anymore. You should be designing loops that prompt your agents."
- Loop Engineering — Addy Osmani's essay, syndicated on O'Reilly Radar. The anatomy: automations, worktrees, skills, connectors, subagents, external state — and the honest closing warnings about verification burden and comprehension debt.
- Code review in the age of AI — Osmani's companion piece; "your job is to ship code you confirmed works" is this handbook in nine words.
- What is loop engineering? — IBM's topic page; useful as the sober institutional definition, strong on the risks (comprehension debt, intent debt, cognitive surrender).
Papers
- Stop Hand-Holding Your Coding Agent — Sandeco Macedo. The academic treatment: termination conditions, verification and critic components as first-class loop infrastructure.
- Less Context, Better Agents — efficient context engineering for long-horizon tool-using agents; the measured case for the pruning argued in context hygiene.
Anthropic material
- Managing context on the Claude Developer Platform — context editing and the memory tool, with the numbers this handbook quotes: an 84% token cut on a 100-turn evaluation, 29% from editing alone, 39% combined.
- The harness handbook's resources page holds the rest of the Anthropic canon — building effective agents, effective context engineering — which this handbook assumes rather than repeats.
Practice
- Ralph Wiggum as a "software engineer" — Geoffrey Huntley. The bash loop that started it, with unusually honest failure notes.
- Designing agentic loops — Simon Willison, September 2025. Which tasks loop well, and the security posture for letting one run.
Repos worth reading
- humanlayer/12-factor-agents — principles for agents that survive production; several factors are loop discipline by another name.
- anthropics/claude-code — the
ralph-wiggumplugin: the run-in-a-loop pattern as maintained, inspectable code. - vercel-labs/ralph-loop-agent — the same pattern rebuilt on the AI SDK, with verification and iteration made explicit.
Start here
- Write one goal test. Pick a task you keep hand-prompting and express done as a script that exits 0. If you cannot, per what loop engineering is, it is not a loop candidate yet.
- Build the retry loop. Work through Build: the goal test on a small repo with failing tests. One evening.
- Add the judge, then the rails. Critic pass, then ratchet and report — and only once the loop stops legibly every single time do you let it run while you sleep.