You’re not asking for code.
You’re asking for code that fits.
Fits the architecture, the conventions, the product intent, your team’s taste.
And this is the problem with chat-centric AI workflows. they make the most important information temporary. The constraints live in a scroll.
Each new session quietly resets the context, and you end up restating rules that already should exist somewhere. Not because the tools can’t follow direction—but because the direction itself has no permanent home.
And that's what Conductor is here to solve.
Conductor’s bet is simple: pin the context and plan as standalone artifacts in the codebase, so the implementation keeps snapping back to the same center.
Instead of keeping your project’s “truth” trapped inside a chat thread, Conductor puts it where it naturally belongs: inside your repo, as living Markdown files—the kind you can read, edit, commit, and share with your team.
And once that’s in place, the workflow changes in a powerful way.
The idea: context-driven development
Conductor is a preview extension for Gemini CLI that introduces what Google calls context-driven development. The principle is simple:
If you want consistent output, stop treating context like a one-time prompt… and start treating it like a maintained asset.
So Conductor scaffolds a small “brain” inside your repository—documents that define things like:
what you’re building (product intent)
how you build here (workflow + conventions)
what tools and frameworks matter (tech stack)
what “good code” looks like in this project (style guides)
Think about the last time you joined a new codebase. The hardest part wasn’t typing code. It was absorbing the unwritten rules. Conductor’s goal is to make those rules written—and keep them close to where the work happens.
The workflow: three moves, no drama
Conductor is built around a short loop and you'll feel it fast.
1) /conductor:setup — plant the roots
This command creates the baseline context docs in your repo. It’s Conductor saying: “Cool. Let’s make the project’s standards explicit.”
This is where you capture the stuff you normally repeat:
architecture expectations
repo conventions
testing preferences
coding style decisions
product boundaries
Once it’s there, it’s there.
Find out why 100K+ engineers read The Code twice a week.
That engineer who always knows what's next? This is their secret.
Here's how you can get ahead too:
Sign up for The Code - tech newsletter read by 100K+ engineers
Get latest tech news, top research papers & resources
Become 10X more valuable
Why AI Isn’t Replacing Affiliate Marketing After All
“AI will make affiliate marketing irrelevant.”
Our research shows the opposite.
Shoppers use AI to explore options, but they trust creators, communities, and reviews before buying. With less than 10 percent clicking AI links, affiliate content now shapes both conversions and AI recommendations.