<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>claude on AgilePhD</title>
    <link>http://blog.agilephd.com/tags/claude/</link>
    <description>Recent content in claude on AgilePhD</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://blog.agilephd.com/tags/claude/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude Code Part3: Workflows and Integration</title>
      <link>http://blog.agilephd.com/posts/claude_code_part3/</link>
      <pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>http://blog.agilephd.com/posts/claude_code_part3/</guid>
      <description>Part 1 introduced Claude Code and got it installed. Part 2 walked through building a real feature on hexutil, backed by a CLAUDE.md file and a plan-then-act loop. Both of those posts assumed a single person, sitting at a keyboard, working on one task at a time. That&amp;rsquo;s a fine place to start, but it&amp;rsquo;s not where Claude Code stays useful. This post is about the other side of it: getting it to work with the tools you already use, and getting it to work when you&amp;rsquo;re not sitting there at all.</description>
    </item>
    
    <item>
      <title>Claude Code Part2: Building a Feature</title>
      <link>http://blog.agilephd.com/posts/claude_code_part2/</link>
      <pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>http://blog.agilephd.com/posts/claude_code_part2/</guid>
      <description>In Part 1, I introduced Claude Code and got it installed. That post was intentionally light on hands-on work. This one isn&amp;rsquo;t. We&amp;rsquo;re going to give Claude Code a real project, give it real context about that project, and have it build an actual feature from a plain-English request. By the end, you&amp;rsquo;ll understand the two things that make Claude Code useful for anything beyond toy demos: persistent project memory through CLAUDE.</description>
    </item>
    
    <item>
      <title>Claude Code Part1: An Introduction</title>
      <link>http://blog.agilephd.com/posts/claude_code_part1/</link>
      <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>http://blog.agilephd.com/posts/claude_code_part1/</guid>
      <description>When I was in the Army, we had a saying about good soldiers: you didn&amp;rsquo;t have to tell them how to do something, just what needed to get done and why it mattered. They would figure out the rest, come back with questions if something didn&amp;rsquo;t add up, and get the job done. That is roughly the mental model I want you to have walking into this series. Not a chatbot that answers questions in a side panel.</description>
    </item>
    
  </channel>
</rss>
