<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Thomas Jamet</title>
    <description>The latest articles on Forem by Thomas Jamet (@thomasjamet).</description>
    <link>https://forem.com/thomasjamet</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3743639%2Fba3631cd-8709-4d64-802b-23e80fe2061c.png</url>
      <title>Forem: Thomas Jamet</title>
      <link>https://forem.com/thomasjamet</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/thomasjamet"/>
    <language>en</language>
    <item>
      <title>Why I Built a Multi-LLM Development Framework (And Why You Might Need One Too)</title>
      <dc:creator>Thomas Jamet</dc:creator>
      <pubDate>Sat, 31 Jan 2026 10:28:38 +0000</pubDate>
      <link>https://forem.com/thomasjamet/why-i-built-a-multi-llm-development-framework-and-why-you-might-need-one-too-1na8</link>
      <guid>https://forem.com/thomasjamet/why-i-built-a-multi-llm-development-framework-and-why-you-might-need-one-too-1na8</guid>
      <description>&lt;h2&gt;
  
  
  The Problem Nobody Talks About
&lt;/h2&gt;

&lt;p&gt;There's a lot of content about building apps with AI coding assistants. "Build a full-stack app in 10 minutes!" "AI writes your entire codebase!"&lt;/p&gt;

&lt;p&gt;But here's what nobody discusses: maintaining that code for 6 months.&lt;/p&gt;

&lt;p&gt;After working with AI assistants across dozens of projects, I noticed a pattern. Every project turned into chaos. Inconsistent file layouts, AI agents constantly asking "where is this file?", and technical debt that was invisible until it wasn't.&lt;/p&gt;

&lt;p&gt;This is what I call "vibe coding" — ad-hoc development without organizational structure. It works for demos. It fails for production.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Core Insight
&lt;/h2&gt;

&lt;p&gt;AI assistants are great at generating code but provide no organizational structure. They respond to prompts, but they don't enforce patterns. Each interaction starts from minimal context.&lt;/p&gt;

&lt;p&gt;This means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every project has a unique (chaotic) structure&lt;/li&gt;
&lt;li&gt;AI agents waste cycles re-orienting themselves&lt;/li&gt;
&lt;li&gt;Knowledge doesn't transfer between projects&lt;/li&gt;
&lt;li&gt;Cognitive overhead compounds with scale&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Solution: Consistent Patterns
&lt;/h2&gt;

&lt;p&gt;I built the Multi-LLM Development Framework — an open-source Python tool that creates consistent workspace structures across Gemini, Claude, and Codex.&lt;/p&gt;

&lt;p&gt;The idea is simple: if all your projects follow the same patterns, you spend less time explaining structure to AI (and yourself) and more time actually building.&lt;/p&gt;

&lt;h3&gt;
  
  
  What It Does
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Tiered Workspaces&lt;/strong&gt;: Lite/Standard/Enterprise matched to project complexity&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Provider-Agnostic&lt;/strong&gt;: Works with Gemini, Claude, or Codex&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Standardized Structure&lt;/strong&gt;: Predictable directory layouts&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Skills + Workflows&lt;/strong&gt;: Reusable capabilities and orchestrated sequences&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Session Management&lt;/strong&gt;: Makefile-based workflow control&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Usage
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Create a Standard tier workspace with Claude&lt;/span&gt;
python bootstrap.py &lt;span class="nt"&gt;-t&lt;/span&gt; 2 &lt;span class="nt"&gt;-n&lt;/span&gt; myproject &lt;span class="nt"&gt;--provider&lt;/span&gt; claude

&lt;span class="c"&gt;# Or with Gemini (default)&lt;/span&gt;
python bootstrap.py &lt;span class="nt"&gt;-t&lt;/span&gt; 2 &lt;span class="nt"&gt;-n&lt;/span&gt; myproject
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Why This Matters
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;For you:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Same structure across all projects = lower cognitive overhead&lt;/li&gt;
&lt;li&gt;Faster onboarding when returning to old projects&lt;/li&gt;
&lt;li&gt;Patterns that scale from 1 project to 10&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;For AI agents:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Predictable file locations = fewer clarifying questions&lt;/li&gt;
&lt;li&gt;Consistent patterns = faster execution&lt;/li&gt;
&lt;li&gt;Structured context = better suggestions&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Modular Architecture
&lt;/h2&gt;

&lt;p&gt;The framework itself follows these principles. The source is broken into maintainable building blocks that compile into a single distributable file (~5K lines).&lt;/p&gt;

&lt;p&gt;You get:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Modular development&lt;/strong&gt; — edit individual components&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-file distribution&lt;/strong&gt; — easy deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try It
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub&lt;/strong&gt;: &lt;a href="https://github.com/thomas-jamet/Multi-LLM-Development-Framework" rel="noopener noreferrer"&gt;https://github.com/thomas-jamet/Multi-LLM-Development-Framework&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;MIT licensed. Feedback welcome.&lt;/p&gt;

</description>
      <category>python</category>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
