<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent-Instructions on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/agent-instructions/</link><description>Recent content in Agent-Instructions on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 21 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/agent-instructions/index.xml" rel="self" type="application/rss+xml"/><item><title>Delete a Section and Watch the Agent</title><link>https://drlongnecker.com/blog/2026/10/delete-a-section-watch-the-agent/</link><pubDate>Wed, 21 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/delete-a-section-watch-the-agent/</guid><description>&lt;p&gt;Most agent instruction files grow the way a legacy README grows with each line or section going in after something goes wrong (a &amp;ldquo;lesson&amp;rdquo;). However, almost nobody goes back to ask whether it&amp;rsquo;s still valid. My own agent setup had the same problem and I&amp;rsquo;d guess yours does too.&lt;/p&gt;
&lt;p&gt;The usual advice is to give an agent more context, including architecture notes and conventions. Thoughtworks put the other side of that on its &lt;a href="https://www.thoughtworks.com/en-us/radar"&gt;Technology Radar&lt;/a&gt; this spring. The April 2026 edition lists Context engineering under Adopt and Agent instruction bloat under Caution. The bloat entry describes how files grow by accretion, with each addition sensible on its own while the total gets long, contradictory and easy to skim past.&lt;/p&gt;</description></item></channel></rss>