Verified 
Famous Singer 🐾 CatCodeLabs
Welcome to CatCodeLabs, an independent open-source software lab built by VoxyTheCat.
Our Projects
Links
AI Usage at CatCodeLabs
Good Software.
We believe good software comes from people who understand, wrote, and care about the code they ship. We write the absolute majority of our code ourselves, as we find that process more engaging, more reliable for long-term maintenance, and, ultimately, more fun (which, honestly, is what all this is about). We do use AI tools in limited, targeted ways as assistants, but never as the primary authors of our projects. We are not vibe coders, and we are determined to never be classified as such.
Where do we use AI?
Mostly Debugging and investigation on our projects. When we hit difficult issues, we sometimes consult AI models for explanations, hypotheses, or candidate fixes. We treat the output exclusively as input to our own analysis and fixes, never as the final statement.
AI and Scaffolding
When it comes to early exploration and initial UI/UX design sketches on certain pre-release projects, AI can help generate starting points or layout ideas that can give us a place to start, or act as placeholders until we finish the final UI design. A scaffolding, one could say. Note: "pre-release" refers to any version before 1.0
Where we do not rely on AI
We do not generate the bulk of production or client-facing code via AI and accept it with minimal review. We do not treat AI output as a substitute for understanding architecture, ownership rules (especially important in our current main language, Rust), edge cases, security, or long-term maintainability.
Humans.
Core design decisions, final implementations, testing strategy, and accountability remain with the human developers on the team.
Our Standards
Every suggestion we take from an AI tool is reviewed, understood, tested, and adapted (or dismissed) by a person who can explain what the resulting code does and why it belongs (or doesn't belong) in the project. If we cannot stand behind a change, it simply will not be shipped. We prefer slower, deliberate work that builds real skill and durable systems over maximum speed via heavy automation. At the core of everything we do sits the enjoyment of actually writing software. Tools will continue to evolve, and we will re-evaluate our practices as they do. What will not change is our commitment to shipping code that humans understand and are responsible for.