<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>schristoph.online</title><link>https://schristoph.online/tags/softwarearchitecture/</link><description>Personal homepage and blog of Stefan Christoph</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Stefan Christoph. All rights reserved.</copyright><lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://schristoph.online/tags/softwarearchitecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Agent's Skills Are Bounded Contexts (Design Them Like It)</title><link>https://schristoph.online/blog/agent-skills-are-bounded-contexts/?utm=rss-feed</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://schristoph.online/blog/agent-skills-are-bounded-contexts/</guid><description>&lt;blockquote>
&lt;p>&lt;strong>TL;DR:&lt;/strong> My AWS colleague Dennis Traub made the case that Domain-Driven Design&amp;rsquo;s Ubiquitous Language is now critical infrastructure for AI agents. I want to take that one layer up, into architecture. After building a stack of agent skills to run my own work, I keep landing on the same rule: a skill that works is a bounded context. One consistent vocabulary inside one boundary. The skills that break are the ones that try to know everything and end up speaking three domains&amp;rsquo; languages at once.&lt;/p></description></item></channel></rss>