<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context Engineering on Chris Reddington</title><link>https://chrisreddington.com/series/context-engineering/</link><description>Recent content in Context Engineering on Chris Reddington</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chrisreddington.com/series/context-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>AGENTS.md and SKILL.md: building a reusable agent toolbox</title><link>https://chrisreddington.com/blog/building-your-agent-toolbox/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://chrisreddington.com/blog/building-your-agent-toolbox/</guid><description>&lt;p&gt;I was working on a personal project and coming up with a Copilot CLI demo to show and tell at the GitHub Social Club in London yesterday. But as I started a fresh agent session, and typed the setup, I caught myself writing the same lines I&amp;rsquo;d written for some work a few days earlier.&lt;/p&gt;
&lt;p&gt;It included a few lines around the process for writing out plans, how the agent should hand off between planning, what the implementation expectations were, and how to review the work when it was done. That repetition (me repeatedly hitting the up arrow to get to my earlier prompts) was a sign that the knowledge I was typing should be packaged as something reusable, not left as another throwaway prompt.&lt;/p&gt;</description></item><item><title>Context engineering: more context isn't better context</title><link>https://chrisreddington.com/blog/context-engineering-more-isnt-better/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://chrisreddington.com/blog/context-engineering-more-isnt-better/</guid><description>&lt;p&gt;I was in a customer presentation recently where I asked the room whether they were familiar with the term &lt;strong&gt;prompt engineering&lt;/strong&gt;. Almost everyone raised their hand. This wasn&amp;rsquo;t a surprise, given how it&amp;rsquo;s been used &lt;a href="https://github.blog/developer-skills/github/how-to-write-better-prompts-for-github-copilot/"&gt;over the last 3 years&lt;/a&gt; to make sure that being specific, giving examples, and setting clear instructions are part of the conversation around AI tools.&lt;/p&gt;
&lt;p&gt;But then I asked whether they were familiar with &lt;strong&gt;context engineering&lt;/strong&gt;. Only a few people raised their hand, and even fewer were using it as a deliberate way to think about how they work with AI agents. I genuinely expected more people to have heard of it given how much the term has grown over the past year, even if they weren&amp;rsquo;t applying the principles just yet.&lt;/p&gt;</description></item></channel></rss>