<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Plugins on Tim Schaeps</title>
    <link>https://www.timschaeps.be/tags/plugins/</link>
    <description>Recent content in Plugins on Tim Schaeps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2010–2026, all rights reserved.</copyright>
    <lastBuildDate>Wed, 11 Nov 2026 20:43:00 +0100</lastBuildDate><atom:link href="https://www.timschaeps.be/tags/plugins/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your Architecture Has a Story. Show More Than the Boxes.</title>
      <link>https://www.timschaeps.be/post/architecture-presenter-copilot-cli-plugin/</link>
      <pubDate>Wed, 11 Nov 2026 20:43:00 +0100</pubDate>
      
      <guid>https://www.timschaeps.be/post/architecture-presenter-copilot-cli-plugin/</guid>
      <description>
        
          
            &lt;p&gt;&lt;strong&gt;You&#39;ve built something interesting. Now you need to explain it.&lt;/strong&gt; So you open the architecture diagram, point at a few boxes, and start talking. Five minutes later, you&#39;re explaining the third arrow while half the room is still trying to understand the first one. Sound familiar?&lt;/p&gt;
&lt;p&gt;I wanted a better way to do this. Not because architecture diagrams are bad (I quite like a good diagram), but because showing the end result doesn&#39;t necessarily help someone understand how it works, or why you built it that way. So I built &lt;a href=&#34;https://github.com/timschps/architecture-presenter?utm_source=timschaeps.be&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Architecture Presenter&lt;/a&gt;


, a GitHub Copilot CLI plugin that helps turn project evidence into an interactive, step-by-step architecture walkthrough.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>