Claude 101(15) — Build Tiny Tools and Personal Apps With Claude Code (No Programming Background Needed)

Learn how to build personal automation tools and tiny apps using Claude Code — no programming knowledge needed. Create photo organizers, price watchers, auto-backup scripts, and more.

Overview

Most non-technical people hear "Claude Code" and assume it's not for them. It is. The difference between Cowork (Article 11) and Claude Code is that Code can actually write programs that run on their own — not just one-off tasks Claude does for you. Want a script that organizes your photos every Sunday? Want a tiny price-watcher that emails you when a product drops below $50? Want a tool that converts every PDF in a folder to Word? Code builds these in an afternoon, and you keep them forever. In this guide, we'll install Claude Code (one command), build three real tools, and cover the gotchas that trip up non-developers.

Who This Is Useful For

People who hit a wall with Cowork — wanting tools that run on a schedule, not just on-demand chats

Anyone who's said "there should be a script for this" but didn't know how to make one

Curious learners who want a gentle, project-driven first taste of programming, with Claude doing the heavy lifting

What You Will Build

Three real, working programs that live on your computer:

Photo Organizer — sorts your photos folder into year/month subfolders based on each photo's actual date

Price Watcher — checks one product page once a day; emails you when the price drops below your target

Auto-Backup — copies a folder to a backup location every night, keeping the last 7 versions

Each tool is 30 to 80 lines of code that Claude writes for you. You'll never have to read most of it — the goal is "does it work" not "do I understand every line".

What You Need

A Mac, Windows (with WSL), or Linux computer

A Claude account with Claude Code access (Pro is enough for these tools)

The Terminal app (built into your computer)

1 hour for the first tool, faster after that

Willingness to copy-paste a few commands without panicking

Step 1: Install Claude Code (One Command)

Open Terminal (Mac: Cmd+Space → "Terminal" → Enter; Windows: open Ubuntu/WSL).

Paste this and press Enter:


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

Wait 30 seconds. The installer does its thing. When it finishes, type:


claude

The first time you run it, Claude Code asks you to log in. A browser opens — sign in with your Claude account. The terminal shows a success message and a prompt waiting for instructions.

That's it. You now have a working Claude Code installation.

Step 2: Understand the Mindset Shift

In Claude.ai chat, you describe a task, Claude does it once. In Claude Code, you describe a tool, and Claude:

1. Writes the program for you
2. Saves it to your computer as a real file
3. Tests it on a small example
4. Lets you run it yourself any time after that

The shift is from "Claude as assistant" to "Claude as tool builder". You're getting actual software you own.

Step 3: Build Tool #1 — Photo Organizer

With Claude Code running in your terminal (you should see a prompt with a blinking cursor), paste this:

Build me a small program that organizes a folder of photos.What it should do: Take a folder path as input (the user will type it in) Read every image file in that folder For each photo, find the date it was taken (from the photo's metadata; if there's no metadata, fall back to the file's modification date) Move each photo into a subfolder structure: YYYY/MM/ (e.g. 2024/03/photo.jpg for a March 2024 photo) Show me a summary at the end (how many photos, how many moved, how many couldn't be processed) Before moving anything, show me the plan and wait for "go".

Save the script somewhere I can run it again later. Tell me exactly what command I should type to run it.

Claude Code will:

1. Pick a programming language (probably Python — most "scripts" use it)
2. Write the script and save it (e.g. ~/scripts/photo-organizer.py)
3. Install any dependencies it needs
4. Run a test on a small example folder
5. Tell you the exact command to run it on your real photos

You'll see something like:

Done! Saved to /Users/you/scripts/photo-organizer.py

To run it on your photos: python3 /Users/you/scripts/photo-organizer.py /path/to/photos

Try it. Make a copy of a small folder of photos first (always test on copies, not originals). Run the command. Watch your photos get organized.

Step 4: Build Tool #2 — Price Watcher

This is the one that turns Code from "interesting" to "I can't believe I built this". Paste:

Build me a tiny price watcher.What it should do: Take a URL of a product page and a target price (e.g. USD 50) Visit that URL, find the current price, and compare to my target If the price is at or below the target, send me an email Save a log of every check (date, time, current price) to a CSV file so I can see price history later Setup it should ask for the first time: My email address (where to send alerts) My SMTP credentials (for sending email — I have a Gmail app password ready) Save the script and tell me how to run it manually.

Then build a second small script that I can use to schedule this to run once a day, automatically. Tell me how to set the schedule on a Mac (or Windows / Linux as appropriate).

Claude will write the price watcher, ask you for the URL/email/credentials when needed, run a test check, and walk you through setting up a daily schedule.

The first day you get an email saying "the price dropped to $47" while you're at lunch — that's when this clicks.

Step 5: Build Tool #3 — Auto-Backup

The third tool is the one you'll be most grateful for the day your laptop dies.

Build me an auto-backup tool.What it should do: Copy the contents of a folder I specify (the "source") to another folder (the "backup destination") every time it runs Keep the last 7 daily backups, each in its own subfolder named with the date (e.g. 2026-05-07) Delete backups older than 7 days automatically Print a clean summary at the end (X files copied, Y MB total, oldest backup deleted) Source folder: [I'll tell you when you ask] Backup destination: [I'll tell you when you ask]

Save the script. Tell me how to schedule it to run nightly at 11 PM.

After Claude finishes, you'll have a script that runs at 11 PM every night, backing up your most important folder to an external drive (or another folder, or a Dropbox folder, or wherever you point it).

For real safety, point the backup at an external drive or cloud-synced folder

Don't backup huge folders (your full Photos library) — pick the folders that would hurt to lose

If you change source/destination later, just edit the file Claude saved — or ask Claude to do it for you

Step 6: The Five Common Gotchas

Stuff that confuses non-developers on their first Claude Code projects:

Permissions errors ("permission denied"). Usually means the script tried to read or write somewhere it doesn't have access. Tell Claude — it'll fix the permissions or move the file.

"command not found". Means a tool isn't installed yet. Claude will install it for you when you say so. Type "y" or "yes" when asked.

Scripts that work once, then stop. Often this means a website changed (for the price watcher), or your folder moved. Tell Claude what changed; it'll update the script.

Schedule didn't run. Mac/Windows scheduling has quirks. Easiest fix: ask Claude to walk you through verifying the schedule, then run a test manually first.

Forgot the command to run it. Open Terminal, type claude, and ask: "How do I run my photo organizer again?" Claude reads the saved scripts and reminds you.

Step 7: Maintenance — Talking to Old Tools

The best thing about tools you build with Claude Code: you can change them later by talking, not editing.

Open Terminal, type claude, then paste:


I want to update my photo-organizer script. Open it, then
add: also rename each photo to "YYYY-MM-DD_<original-name>"
when moving it.

Claude reads your script, makes the change, tests it, saves the new version. The next time you run it, the new behavior is in effect.

This is the magic that makes Claude Code different from "learn to program". You're not maintaining code; you're maintaining a conversation about a tool.

Going Further

Build a small habit. Whenever you say "I wish there was a tool for this" — open terminal, type claude, and describe the tool. After 5 such sessions, you'll have your own personal toolkit.

Combine with Cowork. For one-off tasks (clean up Downloads), use Cowork (Article 11). For recurring/schedulable tasks (back up nightly), use Code. Each has its place.

Read along, gently. After your 3rd tool, glance at the script files Claude saved. Don't try to understand line-by-line — just notice the shape. Over weeks, you'll start picking up enough that you can spot small things to tweak yourself.

Key Takeaways

Here's what you learned in this guide:

Claude Code = Claude that builds you actual programs. Saved as files on your computer, runnable anytime.

- Install is one command. curl ...	sh, then claude. That's the whole "scary" part.

Describe the outcome, not the code. "Build me a tool that..." is the right opener every time.

Always test on copies first. Especially for tools that move, delete, or modify files.

Errors aren't scary; paste them back. Claude reads its own output and fixes itself.

Update by talking. "Open my photo-organizer and add X" — same conversation pattern, no manual editing.

The first tool feels miraculous. The third feels normal. By the tenth, you'll have a small library of personal automations that nobody else has — because nobody else has your specific itches.