<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI on Dejan Bosanac</title>
    <link>/categories/ai/</link>
    <description>Recent content in AI on Dejan Bosanac</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/categories/ai/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Master your skills</title>
      <link>/posts/2026-07-29-master-your-skills/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/2026-07-29-master-your-skills/</guid>
      <description>&lt;p&gt;We put a lot of effort into building context for our coding agents, but we rarely treat that context with the same engineering rigor as the rest of the project. I wanted to explore what it looks like when we do. Starting with the basics: what AGENTS.md and Agent Skills are and why they matter.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://developers.redhat.com/articles/2026/07/27/standardize-project-context-agentsmd-and-agent-skills&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;https://developers.redhat.com/articles/2026/07/27/standardize-project-context-agentsmd-and-agent-skills&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Next up, I&amp;rsquo;ll dive into topics like authoring, testing, evals, CI integration, etc.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
