Field Manual / Hannah
For Hannah, from Keegan

Build real websites by describing them.

This is the whole setup, in order, with the exact things to click and the exact things to paste. Work down the page. Tick each step off as you go.

Time to work through
About 90 minutes
What you need
A Mac and a card
You end up with
A live site

The money part, up front

Nobody likes finding the paywall on step five. There is one real subscription here. Everything else is free until you want a domain name.

$20/mo
Claude Pro

Required. The free Claude plan cannot use Claude Code, which is the part that writes and saves files on your Mac. $17/mo if you pay for a year up front.

$0
Cloudflare

The free plan hosts your sites, gives you an https address, and does not ask for a card. This is genuinely free, not free-trial free.

~$12/yr
A .dev domain

Optional, and only at the very end. Skip it until you have something you want to show people. Price is an estimate, so check at checkout.

Sources: claude.com/pricing and the Claude Code docs, checked 24 Aug 2026. Domain price is an estimate, confirm before paying.

What you are actually building

Five moving parts. Once you can see how they connect, the steps stop feeling random.

Seven steps, in order

Do not skip ahead. Step four does not work until step three is done. Your ticks are saved in this browser, so you can close the tab and come back.

01

Get a Claude Pro subscription

Claude has a free tier, but it cannot touch files on your computer. The thing you actually want, the one that builds a whole website into a folder, is called Claude Code, and it only comes with a paid plan.

  1. Go to claude.ai and make an account if you do not have one.
  2. Go to claude.com/pricing and pick Pro. Not Max. Max is for people running Claude all day.
  3. Monthly is fine to start. You can switch to annual later once you know you like it.
WHY

Pro gives you the desktop app, the chat, and Claude Code. That is everything on this page. If you find yourself hitting usage limits constantly after a month or two, that is when Max becomes a real question, not before.

02

Install the Claude desktop app

This is a normal Mac app. It already contains Claude Code inside it, so you do not need to install anything else, and you do not need to know what Node.js is.

  1. Download it: claude.ai/download
  2. Open the .dmg file that lands in your Downloads folder.
  3. Drag the Claude icon onto the Applications folder in that window.
  4. Open Claude from Applications. Sign in with the account you just paid for.

Along the top you will see three tabs: Chat, Cowork, and Code. Chat is the one you already know. Code is where websites get built. Ignore Cowork for now.

HEADS UP

If clicking the Code tab tells you to upgrade, your subscription has not attached to that account yet. Sign out, sign back in, and restart the app before you go looking for a bug.

03

Make a folder, then open it in the Code tab

Claude Code works on one folder at a time. That folder is your project. Everything it writes goes in there, and nothing outside it gets touched.

  1. Open Finder. Press Shift + Command + N in your home folder to make a new folder. Call it Sites.
  2. Inside Sites, make another folder called first-site.
  3. In Claude, click the Code tab, choose Local, click Select folder, and pick first-site.
  4. In the permission dropdown next to the send button, pick Manual for now.

Manual means Claude shows you every change and waits for you to approve it. It is slower and it is the right way to start. Once you trust it, switch to Accept edits and it stops asking.

Now type something in and watch what happens:

type this into the Code tab
Build me a one page site for a florist called Field & Fern.
Warm, a bit old fashioned, not corporate. Just index.html
and styles.css, no frameworks. Show me a plan before you
write anything.
TIP

Once it has built something, ask Claude to open it: "open this in the browser pane so I can see it". The app has a built-in browser. You do not have to go hunting for the file.

04

Install the design skills

A skill is a folder of instructions that Claude reads when it is relevant. Out of the box, Claude designs like a competent engineer with no taste. Skills are how you fix that. This is the single biggest quality jump available to you, and it takes about four minutes.

First, the Anthropic pack. Type these two lines into the Code tab, one at a time, pressing Enter after each. They start with a slash because they are commands, not questions.

in the Claude Code tab
> /plugin marketplace add anthropics/skills
then this one
> /plugin install example-skills@anthropic-agent-skills

That one install gets you eight skills at once, including the two that matter most for you: frontend-design and canvas-design. The full list is in the catalog below.

Then the two best outside ones. These go in the terminal rather than the chat box. In the Claude desktop app, press Control + backtick to open a terminal pane, make sure you are in your project folder, and paste:

terminal, inside your project folder
$ npx impeccable install
terminal, same place
$ npx skills use vercel-labs/agent-skills \
    --skill web-design-guidelines --agent claude-code

Say yes when it asks to download the package. Then restart Claude and type /skills in the Code tab. Everything you installed should be listed.

WHERE THEY LIVE

Skills sit in one of two places. ~/.claude/skills/ is your personal shelf and works in every project. A .claude/skills/ folder inside a project only works in that project. When you are not sure why a skill is missing, that is usually the reason.

SAFETY

A skill is code from a stranger on the internet, and it runs on your machine. Before installing one that is not on this page, open its SKILL.md on GitHub and read it. The four above are from Anthropic, Vercel, and a well known designer, and I use them myself.

05

Make a Cloudflare account

Cloudflare is where your sites will live. The free plan is the real product, not a trial, and it does not ask for a card unless you buy a domain.

  1. Go to dash.cloudflare.com/sign-up.
  2. Use an email you will still have in three years. This account ends up owning your domain names.
  3. Click the link in the verification email.
  4. Turn on two factor authentication while you are in there. My Profile, then Authentication.

You do not need to add a website or a domain yet. Stop once you can see the dashboard.

06

Put your site on the internet

Do this the easy way the first time, so you get the feeling of it working. Drag and drop, no commands.

  1. In the Cloudflare dashboard, go to Workers & Pages.
  2. Click Create, then the Pages tab, then Upload assets.
  3. Give it a name, like first-site.
  4. Drag your first-site folder into the box. Click Deploy.

Thirty seconds later you get a real address ending in .pages.dev. That link works for anyone, on any phone, anywhere. Send it to someone.

Once that has clicked, here is the version you will actually use day to day. Two lines in the terminal, from inside your project folder:

terminal, once ever
$ npx wrangler login
terminal, every time you want to publish
$ npx wrangler pages deploy ./ --project-name=first-site

Better still, once you have done it once: just tell Claude "deploy this to Cloudflare Pages" and let it run the command.

LEARN FROM MY MISTAKE

That deploy command publishes every single file in the folder, not just the web pages. I once published a client's private pricing notes and a live payment key this way, and they sat on the public internet for two days.

So: one folder per site, and nothing in it that you would not put on a billboard. No notes, no invoices, no passwords, no screenshots you would not show a stranger.

07

Point a real domain at it

Only worth doing when you have something you are proud of. A .dev domain is a nice pick for this: it is what people who build things use, and it is forced to be secure, so you can never accidentally ship an insecure version.

  1. In Cloudflare, go to Domain Registration, then Register Domains. Search for the name you want.
  2. Buy it. Cloudflare sells at cost and does not do the renewal price trick that other registrars pull.
  3. Go back to your Pages project, then Custom domains, then Set up a domain, and enter it.
  4. Go to the domain's DNS tab and add a record: type CNAME, name @, target your-project.pages.dev, proxy on (the orange cloud).
THE ONE THAT GETS EVERYONE

Step four there is not optional, and Cloudflare will not remind you. Adding the custom domain to your Pages project does not create the DNS record for you. Miss it and the domain sits on "pending" forever while you refresh and wonder what broke.

ABOUT .DEV

Every .dev domain is on a browser list that refuses to load it over an insecure connection. There is no http version, only https. Cloudflare handles the certificate for you automatically, so this costs you nothing and means one whole category of problem cannot happen to you.

The skills worth having

Everything below is free and installs with one of the commands in step four. Ignore anything not on this list until you have a reason. Ten good skills beat forty you have never triggered.

Web design

the ones that change how it looks
frontend-designAnthropic
Start here

Makes Claude commit to an actual aesthetic before it writes any code, instead of defaulting to the same gray-and-purple layout every AI produces. It bans overused fonts and the tired centered-hero look outright.

Comes with the Anthropic pack. Say: "use frontend-design, make it feel like a 1970s field guide."

impeccablePaul Bakaus, open source
Start here

The one I lean on hardest. It gives you 23 named commands so you can direct the work with words instead of vibes: /audit, /critique, /polish, /bolder, /quieter, /typeset, /animate. It also carries a long list of things Claude is not allowed to do, which is where most of the improvement comes from.

Installed with npx impeccable install. Say: "/critique the homepage" or "/bolder, it is too safe."

web-design-guidelinesVercel

Checks your finished page against 100+ rules on accessibility, speed, and interface behavior. It is the closest thing to having a senior developer look over your shoulder, and it catches the things that make a site quietly unusable for someone on a phone or a screen reader.

Run it before you show anyone anything. Say: "review my UI against the web design guidelines."

webapp-testingAnthropic

Lets Claude open your site in a real browser, click things, and take screenshots. This matters more than it sounds: it means Claude can see its own work and find the bit that is broken on mobile, rather than guessing from the code.

Comes with the Anthropic pack. Say: "open it at phone width and screenshot it."

theme-factoryAnthropic

Builds a proper color and type system, so every page of a site matches instead of drifting. Worth using the moment a project grows past one page.

Comes with the Anthropic pack. Say: "build a theme from this palette and apply it everywhere."

Graphic design

the ones that make images and documents
canvas-designAnthropic
Start here

Real graphic design output: posters, flyers, social graphics, one-pagers, covers. It thinks in layout, hierarchy and margin rather than in code, and it exports to PNG and PDF.

Comes with the Anthropic pack. Say: "design a 4x5 poster for the spring market, warm and hand-made feeling."

brand-guidelinesAnthropic

Give it a client's fonts, colors and logo rules once, and every single thing you make afterwards follows them without you having to re-explain. This is the one that turns "I made a graphic" into "I run a brand."

Comes with the Anthropic pack. Say: "here is their brand guide, apply it to everything in this folder."

algorithmic-artAnthropic
Optional

Generative patterns, textures and backgrounds made from code. Useful when you need something original behind a headline and you do not want another stock photo.

Comes with the Anthropic pack. Say: "make me a subtle repeating background in these two colors."

pptx · docx · pdf · xlsxAnthropic, separate pack
Optional

Makes real PowerPoint decks, Word documents, PDFs and spreadsheets, not exports that look almost right. Get these when a client asks for a proposal or a deck.

Install separately: /plugin install document-skills@anthropic-agent-skills

Two more, for later

when you are past the first few sites
skill-creatorAnthropic

Writes new skills for you. The moment you notice you are pasting the same instructions into Claude for the third time, that is a skill. Ask this one to build it and it becomes permanent.

Comes with the Anthropic pack. Say: "turn my usual client intake questions into a skill."

web-artifacts-builderAnthropic

Builds self-contained interactive pages you can share as a link without deploying anything. Good for quick concepts and mockups when a client wants to see an idea today.

Comes with the Anthropic pack. Say: "make this an artifact I can send them."

Prompts you can steal

The gap between a mediocre result and a good one is almost always the prompt. Copy these, change the nouns.

starting a new site

Use frontend-design. Build a one page site for [business], who does [thing] for [customer]. It should feel [three words that are physical objects, not adjectives: "a linen apron", "a hardware store receipt"]. Not corporate, not a startup. Plan it first and show me the plan before writing code.

when it looks like every other AI site

/critique this page. Be honest, no grade inflation. Then tell me the three specific things that make it read as AI-generated, and fix those three only. Do not restructure anything else.

fixing one thing without breaking five

Only change the header. The gap between the logo and the navigation is too tight, and the navigation text is too light to read. Do not touch any other section, and show me the diff before you apply it.

checking it on a phone

Open this in the browser at 375px wide, screenshot it, and tell me what is wrong. Then fix it. Then screenshot it again so I can see the difference.

making a client graphic

Use canvas-design. A 1080x1350 graphic announcing [thing]. Follow the brand guide in this folder. One short headline and the logo, nothing else. No stock photo people, no gradients.

setting your rules once

Write me a CLAUDE.md for this folder. It should say: I am a designer, not a developer. Explain things in plain English. Never use em-dashes or emojis. Always show me a plan before a big change. Always check the page at phone width before saying it is done.

Things that will confuse you

Not bugs. Just the handful of places where the thing that happens is not the thing you expected.

  • A skill you installed is not showing up

    Restart Claude. New folders are only picked up at startup. If it still is not there, you probably installed it into one project's .claude/skills/ folder rather than your personal ~/.claude/skills/ one, so it only exists in that project.

  • Your domain says "pending" and nothing loads

    You added the custom domain to Pages but not the DNS record. They are two separate jobs. Go to the DNS tab and add the CNAME from step seven.

  • You deployed but the site looks like the old version

    Wait a minute and reload. A deploy takes up to a minute to reach everywhere, and it is not an instant flip. Refreshing angrily for thirty seconds is a rite of passage. Add ?x=1 to the end of the address to be certain you are not seeing a cached copy.

  • Claude keeps getting more stubborn as the chat goes on

    Long conversations drag old decisions along with them. Type /clear and start fresh. Your files are untouched, only the conversation resets. Do this between tasks, not in the middle of one.

  • It says it fixed something and it clearly did not

    It is describing what it intended, not what it verified. Ask it to prove it: open the page, screenshot it, and show you. If it cannot show you, it did not check.

  • You need to give Claude a password or an API key

    Never paste it into the chat. Make a file called .env in the project folder, put it in there yourself, and tell Claude the file exists. Anything you type in a chat box is in the conversation forever.

Claude 101

Twelve habits, one at a time. These are the difference between Claude as a novelty and Claude as the thing you work with all day. Arrow keys work too.

01 / 12

Say what it is, not how to build it

You are the client and the art director, not the engineer. Describe the outcome, the feeling, and who it is for. Claude already knows the code part. It cannot guess the taste part.

Instead of: make a div with three columns
Try: a booking page for a dog groomer, calm and a bit playful, aimed at nervous first-time owners
02 / 12

Ask for a plan before the build

Switch the dropdown to Plan mode, or just say "plan it first". Claude proposes an approach and touches nothing. You read it, you push back, then you let it go. Reading a plan takes a minute. Undoing a bad build takes an hour.

Say: Before you write anything, tell me your plan and what files you will create.
03 / 12

One thing at a time

A request with three jobs in it gets you three half-finished jobs. Ask for one change, look at it, then ask for the next. It feels slower and it is much faster.

Instead of: fix the header, add a contact form, and change all the colors
Try: fix the header spacing. Just that.
04 / 12

Show, do not describe

Drag a screenshot straight into the prompt box. A picture of the thing you mean is worth four paragraphs of trying to name it. This works for inspiration, for bugs, and for "it looks wrong and I cannot explain why".

Say: here is a screenshot of what I mean. Match this spacing and this weight of type, not the colors.
05 / 12

Say what you do not want

Claude has defaults, and its defaults are the average of the whole internet. Naming what to avoid moves the result further than naming what to aim at.

Say: No purple gradients. No three-column card grid. Do not center everything. No stock photos of people in an office.
06 / 12

Write a CLAUDE.md once

A plain text file in your project folder that Claude reads at the start of every session. Your rules, your fonts, your voice, how you like to be spoken to. Write it once and stop repeating yourself forever.

Say: Write me a CLAUDE.md with these rules, then follow it from now on.
07 / 12

Read the diff before you accept

After Claude edits something, a small counter appears like +12 -1. Click it. You get a side by side of exactly what changed. Ten seconds of looking now saves an hour of "when did that break".

You can comment on a specific line in that view and Claude will revise just that line.
08 / 12

Make it check its own work

Claude reading its own code is not the same as Claude looking at the page. Make it open the thing in a browser. Half the bugs you would have found yourself, it finds first.

Say: open it in the browser at phone width, screenshot it, and tell me what looks wrong.
09 / 12

When it is wrong, be specific about how

"That is not it" gets you another guess. Naming the element and the problem gets you a fix. You already do this with clients. Same skill.

Instead of: I do not like it
Try: the headline is too big and too tightly spaced, and the section under it needs about twice the breathing room
10 / 12

Fresh task, fresh chat

Type /clear when you move to something new. Old context makes Claude cling to decisions you already moved past. Your files are safe, it is only the conversation that resets.

Rule of thumb: new page, new client, or "why is it still doing that" all mean it is time to clear.
11 / 12

Treat downloaded skills like code from a stranger

Because that is what they are, and they run on your machine. Open the SKILL.md, read it, then install. Most are fine. Most is not all, and it takes two minutes.

Prefer skills from an organization you can name: Anthropic, Vercel, a designer with a real reputation.
12 / 12

Ship it before it is perfect

A live site you keep improving beats a perfect one on your laptop. Deploy on day one, then change it every day. You will learn more from one page other people can see than from five you polish alone.

Then text me the link. That is the actual last step.
Copied