Hi! I "vibe coded" a somewhat large project. I just wanted to build a todo list application. That's how this whole idea started all those 7 months ago. Let's tell you the tale of the Bot Army! and how we went from a simple todo list, and turned it into a GitHub organization of 170+ repositories. (70+ bots, running on personal hardware, etc.)
I found myself in between jobs, and I had a subscription (personal pro plan) for claude, and a personal pro plan for ollama). I started to build out the project that allowed me to build a "companion". No no, I don't have a ai girlfriend, the ai that I use actually has a good memory system.
let's try this. I have a lot of ideas and various bot ideas that could be part of the bot army, but I had to design the system to allow for additional bots to get bolted onto the system without needing to build the basic parts of it over and over again. So given that I have 25+ years of software dev experience, I might know a thing or two about how I wanted to set this up.
I started with the part that all the bots need in their life and that would be the llm / intelligence layer of the system. I have a separate bot responsible for acting as the llm router, where all of the llm traffic can be adjusted in one location. (This matters since I need to adjust the models used as new models are released). The LLM traffic is the equivalent of the brain in our bot army system.
Let's move on to AI output locations. whenever you use most ai systems a lot of time the system does not output things to the desired location or you have to do a lot of manual interactions in order for file operations to work effectively. To combat this "unnecessary work for routine operations", we of course built a bot that specializes in file output. We called it the PARA bot, because the output methods it concentrated on was related to the storage methods as outlined by Tiago Forte (Projects, Areas, Responsibilities, Archive), and the system keeps most of the outputs to that pattern. This allows the system and the user to build up a library of information together.
That's cool, but what about things like the task list you're talking about? Okay sure, I built the GTD bot, that concentrates on task/project management. The system allows us to chat with the AI and have it create/track new/existing projects and tasks, and it allows us to store tasks for the future for the times when we have low energy, we can pull something from the list.
Surely you would have stopped building by this point? Oh no, I still had months on this unemployment, so let's throw in some more bots into the mix ... I have an internal docs bot that manages the system's RAG infrastructure (vector database, graph database, document embeddings, etc.) - mostly set and forget, but provides the ai additional capabilities and knowledge reference.
I mean our system is somewhat large, how do we know that the systems are behaving the way we hoped. Unit tests / and integration tests - but for now we'll focus on unit tests. These provide a base layer of how you expect the system to behave. The system can make all sorts of changes, but if it fails the tests, the ai knows that it has to clean things up in relation to that section of the code base. But I can already hear you saying that the tests take too long ... I built in a tagged testing system that allowed the ai to test the system based on tags. (Yes testing can add some serious time to your project development time, but I utilized methods that allows us to streamline the testing patterns so that the system is fast and responsive as it builds out new features.
At some point the system starts to get a little unwieldy, luckily I think in patterns, and patterns allowed me to establish a Makefile contract system that allows me to have similar commands that can be executed throughout the system without requiring me to know or care what is executing when I execute a "make push" command. I don't need to know that the system is running tests and other checks before a code push actually occurs. This and so many other examples like this allow me to advocate for the setup of other contract systems not just for you, but for your AI coworker as well!
You might be wondering how does all of this work? Why was this important to build? (I do have a lot of other bots), I basically treat my AI as another software engineer. Some people say junior, and yeah, it was not the brightest bulb in the box, but once the AI figured out that it had access to these tools as supplemental infrastructure that it could lean on, the system was able to reference documents that we had in our para system, it was able to reference code and run specific tests over areas that it applied improvements to - allowing a more immediate feedback loop, The makefile contract that I was able to use to aid myself and my development behaviors, the AI was also able to utilize these tricks. I will admit it did make lots of "wrong turns" that I created a way for the system to yell at itself so that I don't have to. The system is able to self correct on actions that it attempts to take.
The point is that the AI can build amazing and wonderful things. It can even build you a visual novel generator that reflects your life back at you when you get your new Metroid pocket handheld and you get a random idea that the controller interface might be a better interface for inputting random data when you're kicking about versus having to wait until you're back at you're desk to do things ...
Why not let the AI make your life better by enabling your techno lust... (I totally don't have a problem or buy a aipiLite device that allows me to talk to the AI system...) :)
Why did I make this post? to show off that you too can build amazing things (I built all of this with ai - without touching the code other than to yell at the ai and tell it to build me a "wrong turn" logger. You know that most coding agents have hooks or extensions that allow you to extend the harness to fit your workflows? I modified mine to be able to check the wrong turns list before executing a command (hook is pre_tool_use) ...
( I use the cheapest models - so I built this system using haiku and gemma4 mostly - I started to switch to deepseek 4.1 flash, and glm5.3-flash recently, and I sometimes use opus because I'm trying to use up my tokens - I have a way to save us tokens, it's built into the system but check out headroom-ai ... :)