<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>phbeks — Blog</title>
    <link>https://phbeks.com/blog</link>
    <description>Notes on home-lab infrastructure, AI automation, and full-stack projects — from the phbeks home lab.</description>
    <language>en-us</language>
    <atom:link href="https://phbeks.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <!-- FEED_ITEMS_START -->
    <item>
      <title>Prompt Composer: a sneak walk-through</title>
      <link>https://phbeks.com/blog/prompt-composer-walkthrough.html</link>
      <guid>https://phbeks.com/blog/prompt-composer-walkthrough.html</guid>
      <pubDate>Sat, 20 Jun 2026 15:00:00 GMT</pubDate>
      <description>An early two-minute screen recording of the Prompt Composer — building a structured prompt from blank frame to finished, copyable output.</description>
    </item>
    <item>
      <title>Why prompt composing is the skill that actually moves the needle</title>
      <link>https://phbeks.com/blog/why-prompt-composing-matters.html</link>
      <guid>https://phbeks.com/blog/why-prompt-composing-matters.html</guid>
      <pubDate>Sat, 20 Jun 2026 13:00:00 GMT</pubDate>
      <description>The model is rarely your bottleneck — your prompt is. Why composing prompts as reproducible artifacts, not throwaway chats, is the skill that scales your work.</description>
    </item>
    <item>
      <title>AI is an engine. You drive the car.</title>
      <link>https://phbeks.com/blog/prompt-composer-launch.html</link>
      <guid>https://phbeks.com/blog/prompt-composer-launch.html</guid>
      <pubDate>Wed, 20 May 2026 12:00:00 GMT</pubDate>
      <description>A year of sloppy prompts taught me the model is rarely the problem — the framing is. What changed, and the composer it turned into.</description>
    </item>
    <!-- FEED_ITEMS_END -->
  </channel>
</rss>
