<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Claude-Code on SQP Dev</title>
    <link>/tags/claude-code/</link>
    <description>Recent content in Claude-Code on SQP Dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 28 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/claude-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pushing the Vault to TickTick — Closing the Loop Between Obsidian and Task Management</title>
      <link>/posts/2026-05-28-obsidian-ticktick-sync/</link>
      <pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-28-obsidian-ticktick-sync/</guid>
      <description>&lt;p&gt;The vault knows everything. It has the lesson schedule, the practice sessions, the quiz material. TickTick is where the day actually runs — it sits in the calendar, it sends reminders, it blocks time. For a while those two lived separately, and any reschedule meant updating both by hand.&lt;/p&gt;&#xA;&lt;p&gt;Today that gap is closed.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The Problem&lt;/h2&gt;&#xA;&lt;p&gt;Obsidian is the source of truth for the learning plan. But TickTick is what I actually look at during the day. When a lesson moved, I&amp;rsquo;d update the calendar note in Obsidian and then forget to touch TickTick. Or update TickTick and leave the vault behind. Either way, something was always out of sync.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reclaim, Google Calendar, and the Morning Briefing Skill</title>
      <link>/posts/2026-05-26-reclaim-morning-briefing/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-26-reclaim-morning-briefing/</guid>
      <description>&lt;p&gt;The moment that changed the whole system was realising that Claude Code is a terrible calendar manager.&lt;/p&gt;&#xA;&lt;p&gt;Not because it can&amp;rsquo;t do it — it can. The Google Calendar MCP integration works, skills can create and update events, everything is technically possible. The problem is cost. Every calendar operation burns tokens. Reschedule five tasks and you&amp;rsquo;ve spent more on API calls than the Reclaim monthly subscription.&lt;/p&gt;&#xA;&lt;p&gt;So I made a clean decision: Claude Code never touches the calendar for scheduling. That&amp;rsquo;s Reclaim&amp;rsquo;s job.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Claude Code as a Vault Brain — First Steps</title>
      <link>/posts/2026-05-23-claude-code-vault-brain/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-05-23-claude-code-vault-brain/</guid>
      <description>&lt;p&gt;The DevOps Learning Command Center dashboard existed. The problem was keeping it alive.&lt;/p&gt;&#xA;&lt;p&gt;A learning system that requires manual maintenance eventually stops being maintained. I wanted Claude Code — the terminal-based AI agent from Anthropic — to handle the vault upkeep so I could focus on the actual learning.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-claude-code-does&#34;&gt;What Claude Code Does&lt;/h2&gt;&#xA;&lt;p&gt;Claude Code runs in your terminal and has direct access to your filesystem. It reads files, writes files, runs commands. Combined with a &lt;code&gt;CLAUDE.md&lt;/code&gt; context file that explains who you are and what the vault is for, it becomes something like a personal assistant that actually knows your project.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
