I needed a resume page. What I actually wanted to test was whether a session can keep raising its own bar without me in the chair. It ran twenty-nine rounds on its own, looked at its own screenshots after every one, and sent a Telegram message when it stopped finding things worth changing.
I already had a site with a finished visual language — tellingtechnology.skogstrom.se, ninety episode pages, a locked palette, a headshot, a render for every build. A resume page that invented its own look would have been a second design system to maintain, and a worse one. So the first instruction was not build, it was look: take scroll screenshots of the reference site, pull the design tokens out of what is already shipping, and treat every number on the new page as something that has to trace back to a file in my AIOS rather than something you write because it sounds good.
The first draft took about twenty minutes. Then I typed a self-paced /loop and left. A round is deliberately small and deliberately closed: read CHANGELOG.md so no idea gets tried twice, pick three to five concrete improvements — broken interaction first, then mobile layout, then motion, then typography, then copy — implement them, re-run Playwright at all sixteen scroll positions, read the resulting images, write a short report, then schedule its own next wakeup. No fixed interval. No human between rounds. The loop decides when it runs again, and it keeps going until the reports stop finding anything worth doing.
I was on the couch for roughly fifteen minutes of that. When I looked at my phone there was a message saying it was done and where to look. I opened it, asked for two changes — two, after twenty-nine rounds — and it went live. The version that shipped was number twenty-four, not twenty-nine: the last rounds were the loop confirming it had run out of real improvements, which is exactly the signal I wanted those reports to produce. Thirty-five minutes end to end, fifteen of them unattended.
I wrote the loop-setup skill for client work — “keep tuning X until it is good” pointed at a dashboard, a prompt, a test suite. The first thing it got pointed at seriously was my own career page. The tool built to iterate on someone else’s product spent a TV episode iterating on how I present myself, and it did a better job of it than I would have at 22:00 on a Tuesday.
Every round wrote something down — that is what makes it auditable instead of magic. Tap any image to enlarge it and read the exact prompt that drew it.




Dark theme locked, tokens borrowed from the episode site, every number on it traceable to a file. It is a resume that documents the way it was built as one of its own sections — which, for the kind of work I am looking for, carries more of the argument than the bullet points do.
The loop prompt going in, one round running end to end on screen, the changelog filling up, and the Telegram ping that ended it.
The valuable half is not the resume page — it is a round small enough to be safe and a stop condition honest enough to actually fire. Everything in this episode is free and open — clone it, run it, make it yours.
gh repo clone tellingtechnology/loop-setup # repo not published yet
No GitHub? Comment LOOP on the post and the bot DMs you the link.
Twenty-nine rounds went well. That is the easy case. The interesting question is what an unattended loop does when its own verify step passes something that is actually broken — and what has to be true before I would let one of these run against a client repo overnight.