1. Home
  2. Guides
  3. Claude Code for Non-Developers

Build things · Guide

Claude Code for Non-Developers.

I'm a project manager, not a programmer, and I built every site in my portfolio and a dozen work tools by describing what I wanted to Claude Code and reacting to what came back. This guide is that method, written down: setup, the brief that gets a usable first version, the look-react-redirect loop, three real projects, free publishing, and the honest line where a non-developer should stop.

Who it's for

Curious professionals who have an idea for a tool, a page or a chore they'd love to automate, and who have been told that needs a developer. You'll need a computer you're allowed to install software on, a Claude account, and an afternoon. You will not need to learn a programming language, though you'll stop being afraid of the terminal.

What's inside

  1. What Claude Code is, and isn'tA tireless builder that works from plain English, inside a folder on your computer. What it's great at and where it needs you.
  2. Set up in an afternoonThe terminal without fear, your first folder, your first "make me a page that..." and what good output looks like.
  3. The briefHow to describe what you want so the first version is usable: who it's for, what it must do, what it must not do, what done looks like.
  4. Look, react, redirectScreenshots and plain-language feedback are the whole skill. The phrases that fix things and the ones that make it worse.
  5. Project one: a one-page websiteFor a real business or yourself. Exactly how this site and my portfolio were made.
  6. Project two: a tool that saves an hour a weekA report formatter, a checklist app, a quote calculator. Pick yours and build it in a session.
  7. Project three: automating a choreRenaming files, turning a folder of photos into a gallery, generating a PDF from a spreadsheet.
  8. Publishing for freeGitHub Pages and Cloudflare Pages, your own domain, and a one-click publish you'll reuse forever.
  9. Staying safeWhat never goes into the folder, how to read what changed, and backups with git in two commands.
  10. When to stopPayments, logins, customer data and other places a non-developer should hire help, and how to brief that help.

You walk away with

  • 30 build briefs you can paste and adapt
  • The "fix it" phrasebook for steering a build
  • A publish checklist and a safety checklist
  • Three finished projects of your own, if you do the chapters