Tools: How to "Program" Your AI Agent: Introducing Gemini CLI Conductor 🎻

Enter Gemini CLI Conductor ## The "Brain" of the Repo 🧠 ## 1. product.md ## 2. tech-stack.md ## 3. workflow.md ## The Example: Focus Flow Timer ⚡️ ## How to Adopt This Methodology Stop prompting. Start Conducting. We are entering a new era of AI-assisted coding. We moved from "Autocomplete" (tab-tab) to "Chat" (copy-paste), and now we are arriving at Agentic Coding - where the AI acts as a developer in your terminal, creating files, running tests, and executing commands. But Agentic Coding has a flaw: Context Amnesia. You ask an agent to "build a login form," and it forgets you use Tailwind. You remind it to use Tailwind, and it forgets you prefer TypeScript strict mode. You end up spending more time "prompt engineering" than engineering. Gemini CLI Conductor is not a new tool you install; it's a methodology. It’s a way of structuring your projects so that any AI Agent (like Gemini Code Assist) becomes an expert on your codebase instantly. This repository, focus-flow-timer, is a proof-of-concept demonstrating this pattern. The core of this methodology is a directory called /conductor that lives in the root of your project. Think of it as the "Sheet Music" for the AI. Instead of putting these details in a 500-word prompt every time you want a feature, you commit them to the repo. This file captures the soul of the product. "A distraction-free, keyboard-first Pomodoro timer. Interactions should feel instant (<50ms)." Result: The AI prioritizes performance and adds hotkeys automatically, without being asked. This is where you enforce your architectural decisions. "State Management: Zustand ONLY. No Context API. Styling: Tailwind CSS v4." Result: When I asked for a Theme Switcher, the AI didn't use useState or Redux. It read this file and built a Zustand store with persistence, matching the project's strict standards. This file defines your development lifecycle. "Workflow: 1. Plan. 2. Write failing test (TDD). 3. Implement." Result: The AI refused to write the UI component until it had written a passing test for the logic. It adhered to TDD because the Conductor told it to. To prove this works, I used Gemini Code Assist to build a functional Pomodoro timer. "Implement a Theme Switcher." I didn't have to explain any of this. I just gave the command, and the "Conductor" ensured the output was perfect. You don't need a special plugin. You just need structure. By treating your context as code, you turn your AI agent from a junior developer who needs constant supervision into a senior engineer who knows your stack inside and out. Check out the repo here: https://github.com/harishkotra/focus-flow-timer Checkout a video of how this works: https://youtu.be/VfznSzMV3Oc Checkout what Gemini CLI Conductor is: https://developers.googleblog.com/conductor-introducing-context-driven-development-for-gemini-cli/ Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse COMMAND_BLOCK: conductor/ ├── product.md # The Vision (WHY we are building this) ├── tech-stack.md # The Constraints (HOW we build this) └── workflow.md # The Process (The RULES we follow) Enter fullscreen mode Exit fullscreen mode COMMAND_BLOCK: conductor/ ├── product.md # The Vision (WHY we are building this) ├── tech-stack.md # The Constraints (HOW we build this) └── workflow.md # The Process (The RULES we follow) COMMAND_BLOCK: conductor/ ├── product.md # The Vision (WHY we are building this) ├── tech-stack.md # The Constraints (HOW we build this) └── workflow.md # The Process (The RULES we follow) - Analysis: The agent read /conductor/tech-stack.md and saw Tailwind CSS v4. - Configuration: It realized v4 handles dark mode differently and searched the web for the correct CSS-variable configuration. - Implementation: It created a useThemeStore.ts (Zustand) because tech-stack.md forbade other state libraries. - Verification: It wrote tests first, adhering to workflow.md. - Create a /conductor folder in your project root. - Define your constraints. Be strict. If you hate CSS modules, say "NO CSS MODULES" in tech-stack.md. - Point the Agent. When you start a task, tell the agent: "Read the /conductor directory first."