5 reads.
A neat idea made real: a feedback loop that catches visual slop and design-system drift while the agent builds, instead of after. It turns design consistency from a thing you ask for into a hook that runs automatically. If your agents produce frontends that look slightly off every time, this is the missing guardrail.
The best explainer on the phrase everyone was repeating without defining. A loop is cron plus a decision-maker in the body: the model, not a hardcoded script, picks the next move each tick. The punchlines land, that the loop, not the model, is now the expensive part, and that the real asset is the skills a loop calls, not the loop itself. If you read one thing on loops, this.
A plain-English tour of the Claude features hiding in plain sight: Projects, memory, extended thinking, scheduled tasks, prompt caching, custom roles. Nothing exotic, but the value is in the framing. Each one takes minutes to set up and pays off daily. Good to forward to anyone still treating Claude as a fancier search box.
The clearest map of where interfaces are heading: agents drawing the UI in real time instead of describing it. Three patterns, controlled, declarative, open-ended, each with a different failure mode at scale, and most teams pick one by accident. If you build anything agent-facing, this is the decision tree to read before you're locked in.
A design studio's field report on a real shift: the deliverable is no longer a PDF brand guide but a folder of structured files an agent can build from. The value moves upstream to the thinking, and the sharp bit is what they call magic_trick.md, the one human, left-of-center idea the system can't generate on its own. Best essay here on where human creativity stays scarce.