Build It by Sunday

What Claude Code is, what you'll have by Sunday night, and how to pace the weekend.

You don't need to know how to code to build software any more. You need to know how to describe what you want, how to check what you get, and how to ask for changes until it's right. That's what this guide teaches.

Claude Code is an AI assistant made by Anthropic that can read, write and run code on your computer. You tell it what you want in plain English: "build me a habit tracker with a calendar view and a streak counter". It plans the work, creates the files, runs them, notices its own errors and fixes them. You stay in charge of every decision.

By the end of this weekend you will have:

You need to know how to describe what you want, how to check what you get, and how to ask for changes until it's right.

• Claude Code installed and working on your computer
• A real, working app that you described and Claude built
• The habits that separate people who ship from people who get stuck
• A shortlist of small apps you could build next, for yourself or for paying clients

How to use this guide

Read Chapters 1 to 3 on Saturday morning, build your first app on Saturday afternoon (Chapter 4), and use Sunday for Chapters 5 to 8, where you polish your app, put it online and plan the next one. Every chapter ends with a short checklist. Don't move on until you can tick every box.

How Claude Code differs from a chat window, where you can use it, and the key words explained.

The difference between chatting and building

Most people meet AI through a chat window. You ask a question, you get an answer, and you copy and paste what you need. That works for writing an email. It falls apart when you try to build software, because software is dozens of files that have to work together, and copying code between a chat and your computer quickly turns into a mess.

Claude Code removes the copy and paste. It works directly inside a folder on your computer. It can:

• create, read and edit files in that folder
• run commands, such as starting your app or installing a tool it needs
• read error messages and fix the cause
• explain what it did and why, in plain language
• remember project rules you give it in a special file called CLAUDE.md

Think of it as a patient developer sitting next to you. You're the product owner. You decide what gets built, and Claude does the typing.

Think of it as a patient developer sitting next to you. You're the product owner.

Where you can use it

Claude Code comes in several forms. They all use the same brain, so pick whichever feels most comfortable:

This guide uses the desktop app for screenshots-in-words and explanations, and shows the terminal command wherever it helps. Everything works the same in each version.

What you need

Words you'll hear (and what they mean)

Chapter 1 checklist

Install Claude Code, understand permission requests, and build a tiny web page in your first five minutes.

Option A: the desktop app (recommended for beginners)

Option B: the terminal

If you prefer the terminal, open it (on a Mac it's called Terminal; on Windows use PowerShell) and run the installer command shown on Anthropic's Claude Code documentation page. On a Mac it looks like this:

curl -fsSL https://claude.ai/install.sh | bash

Then make a folder, move into it, and start Claude:

mkdir my-first-app
cd my-first-app
claude

The first time, Claude Code opens your browser so you can sign in. After that, typing claude in any folder starts a session in that folder.

Understanding permissions

Claude Code asks before it does anything that changes your computer. You'll see requests like:

• "Claude wants to create index.html" (Allow or Deny)
• "Claude wants to run npm install" (Allow once, Always allow or Deny)

As a beginner, read every request for the first hour. You'll quickly see that most are boring and safe: creating files in your project folder, starting a local preview. Once you're comfortable, you can let it make routine edits without asking every time.

It's tiny, but the loop you used (describe, build, look, adjust) is the whole method.

Two rules keep you safe:

1. 1
   Only work inside your project folder. Don't point Claude at your whole Documents folder or your desktop.
2. 2
   Never paste passwords, bank details or private keys into the chat. If an app needs a secret key later, Claude will show you where to put it yourself.

Your first five minutes

Type these one at a time and read the replies. They teach you how Claude talks.

What can you do in this folder? Answer in plain English, no jargon.

Create a simple web page called index.html that says "Hello, I built this with Claude Code" in big friendly letters on a soft blue background. Then tell me how to open it.

Open the file in your browser (Claude will tell you how). You just built something. It's tiny, but the loop you used (describe, build, look, adjust) is the whole method. Try one adjustment:

Make the background a sunset gradient and add today's date underneath in smaller text.

Chapter 2 checklist

Choose a small, finishable app using the Weekend App rules and capture it in a one-page brief.

The number one reason beginners never finish an app is that they start too big. "An app like Instagram but for dog owners" is a team-of-twenty project. "A page where I log my dog's walks and see a weekly chart" is a weekend project, and a genuinely useful one.

The Weekend App rules

A good first app:

• solves one problem for one kind of person (start with yourself)
• has one main screen and maybe one or two extra screens
• saves data on your own device (no logins, no servers, no payments yet)
• can be explained in one sentence

20 weekend-sized ideas

Pick one. If you can't decide, choose #1, the habit streak tracker. It's the example we'll build together in Chapter 4.

The "Out of scope" line is the most important line in the brief. It stops the app from growing out of control.

Write a one-page brief

Before you ask Claude to build anything, write a short brief. It takes ten minutes and saves hours. Copy this template into a note:

APP BRIEF Name: Streakly One sentence: A simple habit tracker that shows my daily streaks. Who it's for: Me, on my laptop and phone browser. Main screen: list of habits, each with a big tick button and a streak number. Other screens: "Add habit" form; a calendar view for each habit. Must have: add/delete habits, tick today, streak count, data saved on this device. Nice to have later: dark mode, export to CSV, reminders. Look and feel: clean, friendly, lots of white space, rounded buttons, soft green accent. Out of scope: logins, cloud sync, payments.

The "Out of scope" line is the most important line in the brief. It stops the app from growing out of control.

Chapter 3 checklist

Build the habit tracker step by step: plan, build, test, design, then save your rules in CLAUDE.md.

This is the heart of the guide. We'll build the habit tracker. If you chose a different app, follow the same steps with your own brief.

Step 1: Start in plan mode

Plan mode lets Claude think and propose a plan without touching any files. In the desktop app you'll find a mode selector near the chat box. In the terminal, press Shift+Tab until you see "plan mode". Then paste your brief with this message:

I'm a complete beginner. Here is the brief for my first app.

[paste your brief]

Please propose a plan before writing any code:
1. The simplest technology choice for a beginner (I'd like it to run in a web browser with no complicated setup).
2. The list of files you'll create and what each one does, in plain English.
3. The steps you'll take, in order.
4. Anything in my brief that is unclear or that you'd suggest changing. Keep it short and jargon-free.

Claude will usually suggest a simple web app: HTML, CSS and JavaScript that runs in any browser and saves data in the browser's own storage. That's perfect for a first app. Read the plan. If something sounds complicated, ask:

Can we make this simpler? I'd rather have fewer files and no build tools.

When you're happy, approve the plan (or switch out of plan mode) and say:

Great, go ahead and build it. When you're done, tell me exactly how to open it.

Step 2: Watch it build

Claude will create the files, one at a time, and ask permission for each. You'll see it write the page layout, the styles and the logic. It may run a small local server so you can open the app at an address like http://localhost:8000. That address only works on your computer.

Open the app. Add a habit. Tick it. Refresh the page. Is it still ticked? If so, your data is being saved. Congratulations: you've built a working app.

Step 3: Test it like a picky customer

Now try to break it. Make a list of everything that feels wrong:

Design changes are where Claude shines. Describe the feel you want, not the code.

• Can you add a habit with an empty name?
• What happens with a very long habit name?
• Does it look right on a narrow window (drag your browser narrower)?
• Does the streak reset correctly if you skip a day?

Then give Claude the whole list at once:

I tested the app. Please fix these, one at a time, and tell me what you changed:
1. I can add a habit with an empty name. It should show a friendly message instead.
2. Long names overflow the card on a narrow screen.
3. I'm not sure the streak resets if I skip a day. Can you explain how it works and add a quick way for me to test it?

Step 4: Make it beautiful

Design changes are where Claude shines. Describe the feel you want, not the code:

Make it feel like a premium app: softer shadows, a friendly rounded font, a subtle confetti burst when I tick a habit, and a big streak number with a small flame icon. Keep it clean.

Add a dark mode that follows my computer's setting automatically.

If you don't like a change, simply say so: "Undo the confetti, it's too much." Claude keeps track of what it changed.

Step 5: Save your rules in CLAUDE.md

Ask Claude to write a project notes file. It reads this file at the start of every future session, so you never have to repeat yourself:

Create a CLAUDE.md file for this project. Include: what the app does, the files and what each one is for, my design preferences, and these rules: keep things simple for a beginner, explain changes in plain English, never add logins or payments unless I ask.

In the terminal you can also type /init to have Claude draft this file for you.

Chapter 4 checklist

The five habits that separate beginners who ship polished apps from those who get stuck.

Two beginners use the same tool. One finishes a polished app in a weekend; the other gives up on Sunday morning in a tangle of errors. The difference is almost always these five habits.

Habit 1: One change at a time

Asking for ten changes in one message works sometimes, but when something breaks you won't know which change caused it. While you're learning, ask for one thing, check it, then ask for the next. Batch only small, unrelated tweaks.

Habit 2: Describe what you see, not what you guess

Bad: "The JavaScript is broken."

Good: "When I click the tick button on the second habit, the first habit gets ticked instead. This started after the last change."

Describe what you did, what you expected and what happened. If there's an error message, copy it in full. Claude is excellent at reading errors.

Habit 3: Save checkpoints

Before a big change, save a checkpoint so you can always go back. Claude Code can roll back its own recent edits, but the beginner-proof method is version control with Git, which Claude can set up for you:

Describe what you did, what you expected and what happened. If there's an error message, copy it in full.

Set up Git for this project and save a checkpoint called "first working version". Explain in one paragraph what Git does and how I go back to this checkpoint if something breaks.

After every working feature, say: "Save a checkpoint called [feature name]."

Habit 4: Ask "why" until you understand

You don't need to learn to code, but understanding the shape of your app makes you ten times better at directing Claude. Try:

Explain how my app works as if I'm a smart 12-year-old. Which file does what, and what happens step by step when I tick a habit?

Habit 5: Know when to start a fresh conversation

Long sessions slowly fill Claude's working memory. If Claude starts forgetting earlier decisions or going in circles, start a fresh session (in the terminal, /clear). Your CLAUDE.md file and your files are still there, so Claude picks up the project quickly.

When Claude gets stuck

Sometimes Claude tries the same fix three times. Break the loop:

Stop. Let's step back. Summarise what we've tried, what the error actually is, and three different possible causes. Don't change any code yet.

Add some temporary logging so we can see exactly what's happening when I click the button, then tell me what to click and what to read back to you.

Chapter 5 checklist

Deploy your app for free with a real web address, and check it before you share.

A local app is great for you. To share it, you need to deploy it: put it on the internet with a real address. For a simple browser app like ours, this is free and takes about fifteen minutes.

The easiest free options

The drag-and-drop route

The automatic-updates route

If you'd like every change to go live automatically, ask Claude to help you connect GitHub and Vercel or Netlify:

The phrase "wait for me to finish each step" is magic for beginners.

I want my app to update online automatically whenever I save a checkpoint. Walk me through connecting this project to GitHub and then to Vercel, one step at a time. Wait for me to finish each step before giving the next one.

The phrase "wait for me to finish each step" is magic for beginners. It stops Claude from dumping twenty steps on you at once.

Before you share

• Remove any test data and placeholder text.
• Add a simple footer with your name and the year.

Chapter 6 checklist

Five small upgrades, done in order, that each teach you a new building block.

Each upgrade below is small, but it teaches you a new building block. Do them in order.

Upgrade 1: Export your data

Add an "Export to CSV" button that downloads all my habits and the dates I ticked them. Explain what a CSV file is and how to open it in Excel or Google Sheets.

YOU LEARN files and downloads.

Upgrade 2: Make it installable on a phone

Turn this into a Progressive Web App so I can "Add to Home Screen" on my phone and it opens like a real app, even offline. Explain what changed.

YOU LEARN how web apps can feel like phone apps without an app store.

Upgrade 3: Add a chart

Add a simple weekly bar chart for each habit showing how many days I completed it in each of the last 8 weeks. Use a small, well-known charting library or plain code, whichever is simpler.

YOU LEARN displaying data visually.

Upgrade 4: Reminders

Add an optional daily reminder notification at a time I choose. Explain any limits (for example, if the browser must be open).

YOU LEARN browser permissions and honest limitations. (Asking Claude to explain the limits is a great habit. It stops you promising features that don't work.)

Upgrade 5: A landing page

Create a separate landing page that explains what Streakly is, with three benefits, a screenshot area, and a button that opens the app. Match the app's design.

YOU LEARN how apps are presented and sold.

Honest, realistic ways to turn your new skill into time saved, local projects or small products.

You now have a skill that many small businesses would pay for: turning a clear description into a working tool. Here are honest, realistic next steps.

Use it for yourself first

The fastest return is time saved in your own life or job. Look for repetitive tasks: a spreadsheet you update by hand, a calculation you redo every week, a checklist you keep rewriting. Each one is a small app waiting to be built.

Small tools for local businesses

Many small businesses still run on paper, messages and spreadsheets. Simple tools they understand and value include:

Start small, ship fast, and listen to the people who use what you make.

• a quote calculator for a cleaner, painter or landscaper
• a digital menu or price list page for a café, salon or barber
• a booking-request form that emails the owner
• a stock or order checklist for a small shop
• a simple loyalty-stamp page

Start by building one for a business you know, even for free, in exchange for honest feedback and a testimonial.

Sell your own small app

Some tiny apps sell well as templates or tools on marketplaces. Others become free tools that bring visitors to your website. Start small, ship fast, and listen to the people who use what you make.

Keep learning in the right order

An hour-by-hour Saturday and Sunday schedule, with a clear 'done when' for every step.

Five reusable prompts and the essential terminal commands, all in one place.

Prompts worth saving

PLAN FIRST Before changing anything, propose a short plan: files, steps, and anything unclear. Keep it jargon-free. Wait for my OK.

FIX WITH CARE Here's what I did, what I expected and what happened: [describe]. Error message: [paste]. Find the cause before changing code, then fix it and tell me what changed.

EXPLAIN IT Explain how this part of my app works as if I'm a smart 12-year-old. No jargon.

STEP BY STEP Walk me through this one step at a time. Wait for me to say "done" before giving the next step.

CHECK BEFORE PUBLISH Review the app for test data, broken links, console errors, accessibility problems and anything that collects personal data. List issues before fixing them.

Useful terminal commands