If you've never written code, Claude Code can look like a tool for developers. It isn't only that. You describe what you want in plain words, it writes the code, and you decide what goes live. Here's how to start without installing anything or opening a terminal.
What Claude Code is
Claude Code is the part of Claude that works on a real project. A normal chat gives you code to copy and paste. Claude Code opens your project, makes the change itself, and saves it as a proposal you can accept or throw away.
You can use it in your browser at claude.ai/code or in the Claude desktop app. It's included in Claude Pro ($20 a month, or $17 a month paid yearly).
What you need
- A Claude Pro account. That's the only paid part to start.
- A free GitHub account. GitHub keeps every version of your code, so nothing gets lost and any mistake can be undone.
- Later, a free Vercel account to put your app on the internet.
Your first 20 minutes
- On GitHub, create a new repository (GitHub's word for a project folder). Make it private and tick "Add a README file".
- Open claude.ai/code, connect GitHub when it asks, and give it access to that one project only.
- Ask it to create a file called CLAUDE.md (more on that below).
- Ask for something small, like a simple landing page with your app's name.
When it's done, Claude Code saves its work as a pull request: a proposed change waiting for your OK. You read what it did, then press Merge. That's the whole loop.
The one file that makes it work
CLAUDE.md is a short note about your project. Claude Code reads it at the start of every session, so you never explain your app twice. Mine has three parts:
- One sentence about the app: "For [who], who struggle with [problem], [app] lets them [one action], so they [result]."
- What version one includes: a short list, nothing more.
- How to work with me: "I don't code. Explain things in plain words. Plan first and wait for my yes. One change at a time. Never put passwords or secret keys in the code."
That last part matters most. It turns the AI from something that guesses into something that checks with you first.
Four habits that save you hours
- Ask for a plan first. End every request with "Plan first and wait for my yes." Read the plan. If it lists five things and you asked for one, say no.
- One change at a time. "Add sign-in" is one request. "Add sign-in, a dashboard and payments" is three, and when something breaks you won't know which one did it.
- Check before you merge. If your project is connected to Vercel, every pull request gets its own preview link. Open it on your phone and click through it before you press Merge.
- Report bugs in four parts. What I did. What I expected. What happened. The exact error or a screenshot. "It doesn't work" gets you a guess. Those four lines get you a fix.
Mistakes almost every beginner makes
- Asking for the whole app in one message. You get a big pile of code that half works. Small steps are faster.
- Merging without reading. You don't need to understand the code. You do need to read the plain-words summary of what changed.
- Letting it add extras. AI likes to be helpful. "Keep it simple, no features I didn't ask for" belongs in CLAUDE.md.
- Pasting secret keys into the chat or the code. Keys go into your hosting settings (Vercel calls them environment variables). Ask Claude Code to show you where.
What it costs
While it's a personal project: Claude Pro, plus about $10 to $15 a year if you want your own domain. GitHub is free, and Vercel's Hobby plan is free for personal, non-commercial projects. Once your app takes money, Vercel needs its Pro plan ($20 a month).
Where to go from here
Pick an idea small enough to finish in a weekend, write the one sentence, and ask for the first page. The first merged pull request is the moment it stops feeling like a developer tool.
Live by Sunday is my 42-page guide for people who don't code: build your first app with Claude Code in one weekend and put it live on your own domain by Sunday night, with 30 copy-paste prompts. More at livebysunday.app.
Top comments (0)