Everyone designs loops. No one asks what the agent knows each tick.
Loop engineering's six building blocks are context primitives wearing new names. The scheduling is cron; what decides the outcome is the context on each tick.
#skills
6 posts tagged #skills.
Your agent re-litigates decisions because you delete the answer.
Session transcripts are an external memory most people delete after 30 days. A skill that greps and re-ranks them turns 'what did we decide' into an answer.
A Skill That Writes Your Skills
Your debugging ability isn't intelligence, it's a procedure - and procedures are exactly what you write down once and hand to an agent. Start with a meta-skill.
Commission the Skill, Don't Write It
You don't author a skill from a blank page. You send a subagent to research the problem once, and the research becomes the skill - a build artifact.
Design the Codebase Your Agent Can Read
The highest-leverage thing you can do for your agent isn't a better prompt - it's a better interface. Deep modules are context the agent reads at a glance.
The planning step's value isn't the document. It's the interrogation.
Your judgment lives in your head until something extracts it. A procedure that explores the repo, then grills you branch by branch, turns an idea into a spec.