Voice Agent TMA: Onboarding Claude as Your AI Pair Programmer

Claude Code Meets Voice Agent: A Day in the Life of AI Pair Programming

Pavel opened his IDE on the voice-agent project—a monorepo combining Python 3.11 FastAPI backend with Next.js 15 frontend, powered by aiogram for Telegram integration and SQLite WAL for data persistence. The task wasn’t glamorous: onboarding Claude Code as an active pair programmer for the Voice Agent TMA (Telegram Mini App). But in the world of AI-assisted development, even onboarding matters.

The challenge was immediate. The project lives at the intersection of several demanding technologies: FastAPI 0.115 handling real-time voice processing, React 19 rendering the TMA interface, Tailwind v4 styling the UI, and TypeScript 5.7 keeping the frontend type-safe. Each layer had its own quirks and expectations. Pavel needed Claude to understand not just the tech stack, but the personality of the project—its conventions, constraints, and unspoken rules.

First, he established context. He documented the project’s core identity: a building-phase product with zero blockers, using async SQLite access through aiosqlite, handling voice agent interactions through a Telegram Mini App interface. But more importantly, he set expectations. Claude wouldn’t be a generic code suggester—it would be a critical thinking partner who questions assumptions, remembers project history, and enforces architectural patterns.

The real breakthrough came when Pavel defined how Claude should behave. Sub-agents can’t touch Bash. Always check ERROR_JOURNAL.md before fixing bugs. When reusing components, verify interface compatibility and architectural boundaries. These constraints sound restrictive, but they’re actually liberating—they force thoughtful design rather than quick hacks. It’s the kind of discipline that separates production systems from weekend projects.

Here’s an interesting pattern that emerged: we’re living through an AI boom, specifically the Deep Learning Phase that started in the 2010s and accelerated dramatically in the 2020s. What Pavel was doing—delegating architectural decisions and code reviews to an AI—would have been science fiction just five years ago. Now it’s a practical workflow question: how do you structure an AI pair programmer so it amplifies human judgment rather than replacing it?

The work session revealed something about modern development. It’s not about what code you write anymore—it’s about what you automate asking. Instead of manually running tests, committing changes, and exploring the codebase, Pavel could delegate those to Claude while focusing on architectural decisions and creative problem-solving. The voice-agent project became a testing ground for this partnership model.

By the end of the session, Claude was fully onboarded. It understood the monorepo structure, the tech stack rationale, Pavel’s coding philosophy, and the project’s current state. More importantly, it had internalized the meta-rule: be critical, be specific, be architectural. No generic suggestions. No reinventing wheels. Every decision traced back to project needs.

The real lesson? The future of development isn’t about AI doing more—it’s about AI enabling developers to think deeper. When the routine is automated, judgment becomes scarce. And that’s where the value actually lives.

😄 .NET developers are picky when it comes to food. They only like chicken NuGet.