Member-only story
Loop Engineering in Practice: Build Three Loops, Then Design Your Own
The primitives all ship inside Claude Code now. Build three real loops in your own repo over two weeks, and walk away able to design your own.
There are now more articles explaining loop engineering than there are people who have built a loop. Time to fix that ratio. Open a repository, because the next two weeks are hands on.
A quick note before we start: AI tools helped me structure and edit this piece. The three loops, the design decisions behind them, and every judgment call about what to trust come from my own work building with Claude Code and my team.
Here is the promise, and it is the only one that matters. By the end of this article you will not be copying my loops. You will have built three of your own, and more important, you will know the method well enough to design a loop for any job in your stack. The loops are the practice. The method is the point.
This is Part 3. If you skipped the first two, that is fine, but the short version helps.
Part 1 was the decision: a four-condition filter for whether a job deserves a loop at all, because most do not.
