AI Fluent·Chapter 04

AI as Your Engineering Team

One AI conversation is not a workflow. Give each conversation a job and it does that job well. Mix them and everything gets worse.

8 min readStandard Layout
Three AI chat windows — strategy, execution, builder
Plain English

Running everything through one AI chat is like one meeting where the chef, accountant, and marketer all talk simultaneously. The chef forgets tonight's specials because someone brought up tax filing. Give each department its own meeting.

The Multi-Chat Architecture

Three conversation types. Each with a specific job.

Strategy Chat

Architecture, trade-offs, priorities. The AI pushes back on your assumptions. No code here. The brain.

Claude Web

Execution Chat

CLI reads files, writes code, runs commands. Precise instructions in, working code out. The hands.

Claude Code

Builder Session

Single-purpose. "Build this page with these specs." Full context, one task. The specialists.

Claude Web (dedicated)

Mixing roles produces worse results for all of them. Separation isn't overhead — it's how you get quality from each conversation.

The Multi-Chat ArchitectureEach conversation type has one job. Mixing them degrades all of them. YOUThe Director Strategy ChatArchitecture · Trade-offs · DecisionsTHE BRAIN → Claude Web Execution ChatCode · Files · Commands · DeploysTHE HANDS → Claude Code Builder SessionSingle artifact · Full context · One taskTHE SPECIALIST → Dedicated Outputs: Brief / Plan Outputs: Working Code Outputs: Artifact PRODUCTION

Teaching AI to Disagree

By default, AI is agreeable. You suggest an approach and it says "great idea!" — then costs you days when the approach was flawed.

Tell the AI: "Challenge my ideas. If you see a better approach, say so." This turns a yes-machine into a thinking partner.

The worst conversations are ones where it does exactly what you ask without question.

Strategy Chat
S
I want to add real-time messaging between users.
AI
Push back: You have 12 active users. Real-time messaging adds WebSocket infrastructure, presence tracking, and moderation. That's 3 weeks of work for a feature nobody has asked for. What problem are you actually trying to solve?
S
...good point. Users just want to share progress.

How to Brief Your AI

Five components. Include all five and output lands first try.

01

Role

"You are the CTO of a language startup" produces different output than "You are a copywriter."

02

Context

What's built, what constraints exist, what decisions are made. Load your documentation.

03

Task

"Write the Stripe webhook handler" beats "help with payments."

04

Format

Code? A list? A document? Tell it what the output looks like.

05

Constraints

"Don't change existing functions. Don't add libraries." Boundaries prevent over-engineering.

When to Push Back

Unnecessary Complexity

50 users don't need microservices. Push back on complexity you don't need yet.

Conflicting Decisions

AI doesn't know your full context. Remind it of constraints when suggestions conflict.

Missing Error Handling

AI handles the happy path. Always ask: "What happens when this fails?"

The Golden Rule

Never let AI build something significant without confirming the plan first. The alignment check takes sixty seconds and prevents hours of rework.

Chapter Appendix
Strategy chat templateCLI prompt templateAlignment check templatePush-back setupProject knowledge loading