<?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</title><link>https://felixruecker.de/tags/claude-code/</link><description>Recent content in Claude-Code on</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://felixruecker.de/tags/claude-code/index.xml" rel="self" type="application/rss+xml"/><item><title>My Portfolio Management Routine: pp-cli, Obsidian, and Claude Code Agents</title><link>https://felixruecker.de/blog/portfolio-routine-obsidian-claude/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>https://felixruecker.de/blog/portfolio-routine-obsidian-claude/</guid><description>&lt;h2 id="why-a-routine-beats-a-dashboard" class="anchor-link"&gt;&lt;a href="#why-a-routine-beats-a-dashboard"&gt;Why a Routine Beats a Dashboard&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;For years my &amp;ldquo;portfolio management&amp;rdquo; was opening Portfolio Performance once in a while, staring at green and red numbers, feeling something, and closing it again. That isn&amp;rsquo;t a process — it&amp;rsquo;s a mood. What I actually wanted was a &lt;em&gt;routine&lt;/em&gt;: a repeatable check-in where I screen for new ideas, review what I already hold, and write down why I did what I did.&lt;/p&gt;
&lt;p&gt;Three pieces make that routine work for me today: a small CLI that liberates my portfolio data, Obsidian as the place where every decision lives, and Claude Code agents that do the heavy lifting on a schedule. Here&amp;rsquo;s how they fit together.&lt;/p&gt;</description></item></channel></rss>