Give it Plan mode first
The live Cline demo reveals the habit that prevents most vibe-coding disasters: make the agent restate the task before it touches code, because the plan shows you how badly you explained.
// trace: where this idea came from
- ↳ video diary @ 6:51 (el hábito, explicado en vivo)
- ↳ Entry 2-2: The AI does what you say, not what you mean (la ley antigua que este hábito implementa)
A live “how I actually use Cline” demo, putting Divo’s favicon in place, documented the workflow that months of vibe coding have settled into, and its cornerstone is one habit: never start in Act mode. Give it Plan mode first.
The reasoning, said while doing it: “in Plan it doesn’t start executing actions, so I get to read its understanding of the task I asked for. It’s very good, because often you believe you explained well, and then you realize you explained terribly” ▸ 6:51. That’s entry 2-2’s founding law, the AI does what you say, not what you mean, upgraded from diagnosis to procedure: the plan is a cheap mirror held up to your prompt before the mistake gets built.
The rest of the routine, equally deliberate: auto-approval of edits stays off, so every change arrives as a reviewable diff, old line, new line, approve or reject ▸ 9:14. Cheap mechanical asks (write me the one-line git add-commit-push) get switched to Flash to save the Pro tokens for thinking work ▸ 19:46. And deploys are two commands, npm run build “cooks the program” and firebase deploy publishes it ▸ 10:33.
el plan es el espejo barato del prompt →
Also in this episode, quietly, a full-circle moment: Divo’s logo got remade properly, vector-native in Figma with the Dot Grid plugin, thirty minutes, three colors ▸ 2:24, replacing a 2.24MB artifact-riddled export. Seed 22-1 (Canva can’t make logos) and entry 33-1 (the vector debt) taught this lesson expensively; watching it get done right the first time, casually, is what a lesson looks like after it’s been paid for…