Skip to content

Build it with ClaudeI wrote the manual so you wouldn't have to call me.

You'll probably call anyway. That's fine.

Pick your track โ€‹

You can switch at any time from the top of the sidebar.

How I build an app โ€‹

  1. Talk it through. I start in Claude Chat and discuss the idea for as long as it takes. Who it's for, what it does, what it won't do.
  2. Get mockups. Claude Design draws the screens. I keep going until I can say "if this existed, I'd be happy".
  3. Then pick the stack and write the tasks. Only now do we talk about code, a database and hosting. Claude writes the docs and a list of small tasks.
  4. Build a V1 on my own machine. One task per session. Claude builds, tests and shows me. I click around and report what's wrong.
  5. Fix, fix, fix. Lots of short bug-fix rounds. This is normal.
  6. Put it live. Only when it works locally does it go on a real server with a real domain.

Who this is for โ€‹

  • Founders who want a working version before they spend real money.
  • Non-coders who are curious and patient. The simple track was written for you.
  • Developers and team leads who want Claude to speed them up without making a mess.

A real example โ€‹

The VH Conference Toolkit was built this way. It's a set of open-source tools for event organisers. Have a look at the repo: the architecture docs, the rules, the task files and the decision records are all there.


...or do you?

You've got the whole method. What the guide can't do is look at your project. I can, and a short call is often enough to get you moving again.

Written by Richard Osborne ยท Visual Hive