BuildWithOli

Claude Code

How I go from idea to working product every time

The 3-Step AI Build System

Every AI project I build starts the same way. Not with a prompt. Not with a tool. With a notepad and five minutes of thinking. This system has saved me more time than any model upgrade or workflow hack.

1

Pen & Paper MVP

Before opening any tool, grab a notepad and answer three questions:

  • -What is the core thing this needs to do? — Strip it down to the one job the product has to nail.
  • -What are the 3-4 features that make it useful? — Not everything it could do. Just what makes it worth using.
  • -What does "done" look like? — Define the finish line before you start running.

Why this matters

AI is fast. That is the problem. Without a clear target, it will build the wrong thing quickly. The notepad forces clarity. It is the cheapest and most effective filter in your entire workflow.

2

Plan Mode

Take everything from the notepad and feed it into Claude Code in plan mode. Hit Shift+Tab to switch into plan mode — it is the one with the blue outline. This is where AI becomes your co-architect.

  • -What to build first (dependency order)
  • -Where the risks are (what might break or need rethinking)
  • -The architecture (file structure, tech choices, data flow)

Why this matters

Most people skip straight to code generation and spend more time fixing bad output than they would have spent planning. Plan mode turns Claude from a code generator into a thinking partner.

3

Auto-Accept & Build

Once the plan is solid, hit Shift+Tab again to switch into auto-accept mode and let Claude build.

Because you did the thinking upfront — pen and paper, then the plan — you can trust the output. You are not micromanaging every line. You are reviewing the result, not babysitting the process.

This is where the magic happens. Claude writes code, creates files, runs commands — all following the plan you aligned on. Your job now is to review, test, and iterate.

Why this matters

Auto-accept without a plan is a recipe for chaos. Auto-accept with a plan is the fastest way to build. The system only works because steps 1 and 2 set it up for success.

The System at a Glance

1

Pen & Paper Map the MVP. Define done. 5 minutes.

2

Plan Mode Align with AI on architecture before any code is written.

3

Auto-Accept Let it build. Review the result, not the process.

One Last Thing

Commit after every milestone. Feature works? Commit. Bug fixed? Commit. Something stable? Stop and commit. Claude will break things eventually — give yourself a safe place to rewind to.

This system is how I build everything. It is not about the tools — it is about thinking before you build. The tools just make the building part fast.

Tips & Lessons

Everything I have learned about building real things with AI — organised from the messy notes I have been collecting for weeks.

These articles started as a pile of random notes, half-finished thoughts, and things I had jotted down while building with AI every day. I dumped all of it into Claude, asked it to find the natural groupings, and turned the chaos into something structured. AI wrote the first drafts. I made them sound like me. This is the result.

Workflow4 min readComing Soon

Plan Before You Prompt

Why five minutes with a notepad beats an hour of back-and-forth with AI. The case for thinking before you build.

Prompting5 min readComing Soon

Stop Typing Your Prompts

How switching from typing to dictation changed the quality of my AI outputs overnight. The communication gap is real.

Dev Workflow3 min readComing Soon

The Commit Habit

Claude Code will break things. When it does, you need somewhere safe to rewind to. This is the habit that saves everything.

Claude Code6 min readComing Soon

Claude Code Plan Mode — The Full Guide

How to use plan mode to turn Claude from a code generator into a thinking partner. Architecture before execution.

More articles coming every week