<?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 SREKubeCraft | Nick Nikolakakis</title><link>https://srekubecraft.io/tags/claude-code/</link><description>Recent content in Claude-Code on SREKubeCraft | Nick Nikolakakis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://srekubecraft.io/tags/claude-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Pinax - Shipping a Production-Grade Obsidian Plugin with a Coding Agent</title><link>https://srekubecraft.io/posts/shipping-an-obsidian-plugin-with-a-coding-agent/</link><pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate><guid>https://srekubecraft.io/posts/shipping-an-obsidian-plugin-with-a-coding-agent/</guid><description>&lt;p&gt;I spend my days building platforms with strong contracts: schemas, admission policies, CI gates, provenance. Last week I applied the same discipline to something completely different, a plugin for my note-taking app, and let a coding agent do most of the typing. Two days later &lt;a href="https://github.com/sphragis-oss/pinax"&gt;Pinax&lt;/a&gt; passed Obsidian&amp;rsquo;s automated community review with a clean scorecard and went live in the plugin directory.&lt;/p&gt;
&lt;p&gt;This post is not &amp;ldquo;look, AI wrote my code&amp;rdquo;. It is about the engineering system around the agent: the machine-checkable success criteria, the verification harness, the trust model, and the three rounds of automated review rejections that only strict guardrails made cheap to fix. The lessons transfer directly to how we ship operators, controllers, and internal tooling at work.&lt;/p&gt;</description></item></channel></rss>