Setup kits you paste straight into Claude.

The Short Version

Cloudflare isn't just your security layer anymore. It's becoming your one control center. Part Three set up the foundation: the account, the tunnel to your server, the locked doors. Now we add the next layer in the same place. Where your files live. Your CDN.

It's called R2. Think of it as a hard drive in the cloud that both your websites and your AI can reach. You give Claude one key, set once, that doesn't expire, and it manages your files for you.

This isn't about ditching Google Drive. Keep it. This is a second kind of storage, built for a code-first way of working, for the stuff you want Claude to operate on directly.

It's perfect for hosting your images. Drop them in, serve them from cdn.yoursite.com, and they load fast anywhere.

And yes, this costs money. Building does. But you're already paying to work this way, and what this piece buys you is worth far more than the price.

Full breakdown below. Copy-paste prompt at the bottom.

---

Part Four. One place for everything, now including your files.

I want to zoom out for a second, because this is where the picture comes together.

The whole point of what we're building is one control center. Instead of your stuff scattered across ten different accounts and dashboards, it all lives in one place, Cloudflare, and your AI has the keys to it.

In Part Three we set up the foundation there. The security layer. Your Cloudflare account as the control panel, the tunnel that lets you reach your server with nothing exposed, and the locked doors on your private dashboards. That's the "keep it safe and reachable" layer.

This part adds the next one, in the same account. Where your files actually live. Your CDN.

Let me explain it simply, because you don't need to be technical for this. That's the whole idea. You hand the technical part to Claude.

It's called R2. Forget the jargon and think of it as a hard drive in the cloud. A place to keep your files: your images, your downloads, your backups. Two things make it special. First, it lives in the same Cloudflare account as everything else, so it's one more thing in your one control center instead of another separate silo to manage. Second, it's built to be reached by code, which means it's built to be reached by Claude.

One honest note so you don't overspend, because this part confused me at first. The technical name for this kind of storage is object storage. Amazon built the first big one, called S3, and it became the standard everyone else copied. R2 is Cloudflare's version of that same idea, and it speaks the same S3 language, so all the same tools work with it. I use R2 because it sits in the same Cloudflare account as everything else, and it doesn't charge you to pull your files back out. But here's the part that matters for your wallet: if you already have an S3 bucket, or storage from someone else that speaks S3, you do not need to go get R2 on top of it. Point Claude at what you already have. R2 is just the one I would pick if you're starting fresh.

Now let me be clear about something, because I don't want you to hear this wrong. This is not "quit Google Drive." Keep your Drive. It's genuinely great at what it's for: your everyday documents, organizing things visually, sharing with people, and its own tools like NotebookLM and Google's AI, which are excellent. None of that is going anywhere, and I'm not here to talk down any of it.

R2 is a different tool for a different job. Google Drive is built for a person clicking around in a browser. That's perfect for you as a human, and a little fiddly when you want an always-on AI to reach in and work. R2 is built for code, so Claude connects once with a permanent key and just works, quietly, in the background. Drive is for you. R2 is for your agent. You'll use both, and that's exactly right.

Here's how you actually use R2. You give Claude one key, and from then on it handles your files. "Put these images in my storage." "Back up this folder." "Pull that file down." It just does it. No login screen in the way, no connection to keep re-fixing.

The clearest example is images. Say you're building a site and you've got a bunch of photos. If you pile them onto your web server, your site gets slow and clunky. Instead, you drop them into R2 and serve them from something like cdn.yoursite.com. Now they load fast from anywhere in the world, and they don't slow your site down. That's what a CDN is, and you just got one by turning on this layer.

One honest aside, because I use it myself. There's a tool called Cloudinary that does a different, narrower job. It automatically resizes and optimizes your images on the fly so your pages stay fast. It's good, and I use it. But it isn't the same thing as R2. Cloudinary transforms images, R2 stores and serves your files. You don't need it to start. R2 gets your images hosted and fast today, and I'll do a whole part later on image optimization. One layer at a time.

Not everything is public, though, and that matters. Your images, sure. Those are meant for the world, so they go on your public cdn address. But your backups and private files stay locked. When you need to hand one to a specific person, you send a link that expires on its own. Claude sets all of that up. You just tell it what's public and what's private.

Now step back and look at what you've got. Your security, and now your files, both in one Cloudflare account, both controllable by your AI with keys that don't expire. One place. One brain running it.

Now the real-talk part, because it matters. This costs money. If you're serious about building, that's not a surprise, it's the deal. You're already paying to work this way, and every real piece you add has a price. This one happens to be small and predictable, but the price was never the point. The point is what it gives you. Your data under your control. Your images served fast. Your AI running all of it without you in the loop. You can stand up things today, by yourself, that used to take a team or a budget you didn't have. That kind of leverage is the best money I spend, and I spend it gladly.

If you want to do it, I made the whole thing a copy-paste prompt. Go to connectwithcliff.com/kit, copy the storage-setup prompt, paste it into Claude, and it sets up your storage, your key, and the connection so your AI runs your files. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part: connecting your own domain, so everything you've built gets a real address. Then the small server your site runs on, and we put something online.

The Short Version

A domain is the one piece of your whole setup you actually own. You rent the server. You subscribe to the software. The domain is yours, and it's about ten dollars a year.

I buy mine at Porkbun. Cheap, WHOIS privacy included free, and a clean API. That API is the point: hand Claude the registrar key and "check if this domain is free, buy it, and point it at my server" becomes one sentence.

Then point the domain at your Kit 3 Cloudflare account, and your domain, DNS, tunnel, and CDN all run from one control panel.

Full breakdown below. Copy-paste prompt at the bottom.

---

Part Five. Your domain, the one piece you actually own.

The last few parts built your foundation: Cloudflare as your control panel (Part Three), and your storage and CDN living inside it (Part Four). This part gives all of it a real address.

Here's the thing about a domain. It's the one piece of your stack that's genuinely yours. Servers you rent. Software you subscribe to. The domain you own outright, and it's the cheapest business asset you'll ever buy. Everything else points at it.

Where I buy them: Porkbun. Not a sponsor, just what I use. About ten dollars a year for a .com, with the two things I actually care about baked in.

One, WHOIS privacy, free. When you register a domain, your name, address, and phone number go into a public database called WHOIS unless privacy is on. A lot of registrars charge to hide it. Porkbun includes it. Your home address shouldn't be one search away because you bought a domain.

Two, a clean API. That's the part that matters for how we work. The throughline of this whole series: you hand your AI a scoped key, and the boring stuff becomes a sentence. Same move as the Cloudflare key in Part Three and the storage key in Part Four. Give Claude your registrar key and "check if this domain is available, buy it, and point it at my server" is one instruction, not twenty minutes clicking through a checkout dodging upsells.

(Namecheap and GoDaddy work too. Namecheap is a solid, popular pick; GoDaddy reopened its API to single domains in 2026. I just land on Porkbun for the price and the free privacy. Different tool, same job. Use what you like.)

And since you're already in there from Part Three: Cloudflare sells domains too, at cost, right inside the same account. Honestly that's the easiest path of all. Buy it there and it's already wired to everything, nothing to point. Totally fine to do it that way. I keep mine at a separate registrar on purpose, for one reason: your domain is the one thing you truly own, and I don't want it living inside the same account that runs my infrastructure. If anything ever happens to that account (a lock, a billing dispute, a mistake), a domain held somewhere separate can be re-pointed elsewhere in minutes. It's your escape hatch, and I don't keep the escape hatch inside the building. That's a small trade of convenience for independence, and it's worth it to me. If you'd rather have it all in one place, buy it on Cloudflare and you're done.

One thing worth getting right: which domain to buy first, because this first one is your hub. If you already have a business or a brand idea, easy, buy that. If you don't, buy your own name. Either way the goal is the same: one primary hub with a real presence on it. A simple page, plus the basics like a privacy policy and terms.

Here's why that matters more than it sounds. The moment you start signing up for the tools we've been using, some of them ask for your website and your terms before they'll hand you a key. A hub page, connected to either your business or your name, is what clears that. You want it to already exist. And if you do have a company, point this at the company. It becomes the home base your other sites hang off, and it's the thing platforms want to see when you apply for API keys and ask "what's your brand." One domain, one presence, and the rest gets easier.

You don't need to be incorporated for any of this. A business name you run under your own name works fine. I run both a personal site and a business across a dozen-plus domains, but that's a different scale. This is just the one fundamental you build everything else on. Personal name or business, either one is golden. I'm not telling you how to structure it, and none of this is legal advice, it's just what's worked for me.

Then you connect it to what you already built. Once you own the domain, point its nameservers at the Cloudflare account from Part Three. Cloudflare gives you two, and they look like aiden.ns.cloudflare.com and olivia.ns.cloudflare.com. Claude can set them through the registrar, and if your registrar makes you do that part by hand, it hands you the exact two to paste and tells you where they go. Either way you're not guessing. Now your domain, your DNS, your tunnel, and your CDN all live in one control panel, and your AI has the keys to all of it. The domain points at Cloudflare, Cloudflare's tunnel points at your server, your site goes live. That's the chain, and Claude wires the whole thing because you handed it both keys.

A quick word on money, because this is a turning point. The domain is the first thing you actually buy, and from here real building costs a little. Not much, but this is the line where you stop setting things up and start building something that's truly yours. That's not a catch, it's the whole point. And owning a ten-dollar domain beats renting your presence on someone else's platform every time.

If you want to do it, I made the whole thing a copy-paste prompt. Go to connectwithcliff.com/kit, copy the domain-setup prompt, paste it into Claude, and it walks you through buying the domain and pointing it at your foundation. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part: the small server your site actually lives on. Then we put something online.

The Short Version

Time for your first API key that actually does something: your projects can send email.

Every key so far managed your setup (Cloudflare, storage, your domain). This one reaches people. A welcome email, a receipt, an alert when something breaks. All of it on one key you create once and hand to Claude.

I use Mailgun. It sends from your own domain, uses the Cloudflare foundation you already built, and teaches the thing worth learning: what an API key is, and how to give one to your AI safely.

Full breakdown below. Copy-paste prompt at the bottom.

---

Part Six. Your first key that does something.

Quick honesty first: I told you the server was next. One useful stop before it, because this is the piece that turns your setup into something that talks to the world.

Here's where we are. You've handed Claude a few keys already. Cloudflare, your storage, your registrar. Those all manage your own stuff. This one is the first that does something for other people: it lets your projects send email. And learning it teaches you the pattern behind almost everything you'll add from here.

So let me actually explain what an API key is, because once it clicks, a lot of the internet opens up.

When you log into a website, you type a password. But your code, and your AI, talk to services with no human clicking anything. So they prove who they are a different way: an API key. It's a long secret string that says "this request is really me." You make it once in the service's dashboard, hand it to your tool, and from then on the tool acts as you. No login screen.

Two things to remember. Whoever holds the key can act as you, so you guard it like a password (it's usually shown only once, so you copy it and keep it safe, which is exactly what the last note was about). And good services let you make a scoped key that can do only one narrow thing. That last part is the trick I want you to steal.

For email I use Mailgun, and it shows the idea perfectly. It gives you two kinds of keys: a full account key that can do everything, and a sending key that can only send email for one domain. You give Claude the sending key. If it ever leaks, all it can do is send mail for that one domain. It can't touch the rest of your account. That's least privilege, and it's how you should hand every key to an AI: the smallest one that does the job.

Here's the nice part, and where the foundation pays off. To send from your own domain, email needs a couple of DNS records that prove you're allowed to (they're called SPF and DKIM). Your DNS already lives in Cloudflare from Part Three, on the domain you bought in Part Five. So Claude just adds those records for you, Mailgun verifies them, and you're sending from [email protected]. One honest warning I'll save you: don't let anything add "MX" records unless you actually want to receive mail there. MX is for incoming mail, and bolting it on can break email you already get. Sending only needs SPF and DKIM. Claude will ask before touching it.

Then it sends a test email to you, it lands, and you're done. From that moment, "email me when a sale comes in" or "send this person a welcome note" is a sentence Claude can act on.

On cost, straight: the free plan sends 100 emails a day and needs no card to start, which is plenty to build and test on. To send to real people from your own domain, plan on putting a card on file (the entry paid tier runs about fifteen dollars a month once you outgrow free). Same as the last few parts. The basics are cheap, and now your stuff can reach the world instead of just sitting there.

If you want to do it, I made it a copy-paste prompt. Go to connectwithcliff.com/kit, copy the email-setup prompt, paste it into Claude, and it walks you through the account, the records, the key, and a test send. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part, for real this time: the small server your site lives on. Then we put something online.

The short version

Get your own server. A small, always-on computer your projects actually live on.

Most people will point you to Hostinger, DigitalOcean, Vultr, or Linode. They're all good. I use Contabo. The price is hard to beat and it's been rock solid for me, zero issues.

Then hand Claude the access and let it do the setup: a locked-down login, a firewall, and a way to keep your projects running around the clock.

Bring the Cloudflare account from Kit 3. We use it to close every open port on the box, so there's nothing for bots to knock on.

---

Kit 6 was your first real API key. This one is the first time you rent an actual computer.

Of all the kits, this is the one that sounds scariest. A "server." It sounds like the thing real engineers set up, not something you have any business touching. It turned out to be the simplest.

A server is just a small computer that sits in a datacenter, stays on 24/7, and only you can log into. Your laptop sleeps and moves and closes. Your projects want to stay up. A site people can reach at 3am. A script that runs every hour. A place your email sends from. That is what this is: the always-on home everything you build from here lives in. And you barely touch it directly. You hand Claude a key, and Claude drives it.

The part I care about most is the security, because this is the first thing you own that faces the whole internet. So we do it right, before anything is even on the box. No passwords, only a key that lives on your laptop. No logging in as root. A firewall that blocks everything you are not using.

And the part I am proudest of in my own setup: using your Cloudflare account, we put the server behind a tunnel so it has zero open ports. Nothing exposed. Nothing to brute force. The box quietly dials out to Cloudflare, you reach it through Cloudflare, and the bots never find a door. It sounds advanced. It is a few instructions to Claude.

That is the whole theme of these kits. The stuff that used to require a specialist is now a conversation.

If you want to do it, I made it a copy-paste prompt. Go to connectwithcliff.com/kit, copy the VPS-setup prompt, paste it into Claude, and it walks you through creating the server, locking it down, and putting it behind Cloudflare. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part: the payoff. We finally put something online, on your own server, at your own domain.

The short version

Put your name online. One simple page: who you are, what you do, where to send people. Your portfolio, your free stuff, your business, your socials, all hanging off one page you own.

Claude interviews you first (your promise, your links, your colors), writes the copy with you, builds one clean file, and puts it live on the server from Kit 7, at the domain from Kit 5, behind the Cloudflare from Kit 3.

It also ships the two boring pages every real site has: privacy and terms. Nobody reads them until the day something needs them.

---

Seven kits of accounts, keys, and a server. This is the night it all pays off.

Here is the thing most people get backwards about personal sites. They treat them like a project: a builder subscription, a theme, weeks of tinkering, and it still ends up saying coming soon. Meanwhile some of the sharpest marketers alive run eight-figure campaigns through pages that are basically a headline, a photo, a few buttons, and good copy. Plain looking. Fast. Clear. And they get clicks, because clarity beats decoration every single time.

So Kit 8 is a hub page, not a masterpiece. A headline that makes a promise. A short paragraph that sounds like you at a table, not a resume. A card for each place you want to send people, each with one line about what is in it for them. One loud button for the single action you actually want. That is the whole page, and it is enough.

And one rule sits under all of it: the page is about what you offer, never about you as a person. Your skills are on the page as help, not as trophies. Claude even runs a test before it shows you a draft: if the copy says I and my more than it says you and your, it rewrites the page until it faces the reader. Mid-interview, when you reach for your titles and your journey (everyone does), it asks the only question that matters: what does the visitor get from that?

The part I like most is how it starts. You do not open a template. Claude asks you questions, one at a time: what do you do and for whom, where should people go, what is the one thing you want a visitor to do, dark or light, what color feels like you. Then it drafts the copy and pushes back when your answers are vague. The page comes out yours, not a template with your name pasted in.

And then the moment the whole series has been building to: you type your own domain into your phone, and your page loads. From your machine. At your address. Most people online are a bio field on someone else's platform. You are now a website. When a platform changes its rules, your front door does not move.

From then on, updates are a sentence. Change the accent to green. Add a card for the new project. Swap the photo. The page is one file your assistant knows by heart, so it stays current because updating it is easier than ignoring it.

If you want to do it, I made it a copy-paste prompt. Go to connectwithcliff.com/kit, copy the personal-page prompt, paste it into Claude, and it interviews you, builds the page, and puts it live. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part: now that you have a front door, we start putting things behind it.

The short version

Kit 8 gave you a front door. This is the doorbell. A form on your page, a small endpoint on your server, and a welcome email that goes out the second somebody signs up.

Your list lives in one file on your own machine. No monthly bill, no platform holding your audience, no embed script loading on your site.

Four forms are free to copy at connectwithcliff.com/forms, one for each kind of business. The kit wires whichever one you pick to your own Kit 6 Mailgun, on your Kit 5 domain, on your Kit 7 server.

---

Somebody lands on your page, reads it, likes it, and leaves. You never find out they were there. That is every personal site on the internet: a front door with nobody writing down who knocked.

Here is what a list actually is, because it is four things and not one. A form the person fills in. A place the address lands that you control. A reply that goes out immediately, while they still remember signing up. And a way out, in every message, that works. Skip the third and they forget you within a day. Skip the fourth and you are, practically and legally, a spammer. Most people build the first one and think they are finished.

What makes that failure so common is that it does not look like a failure. The box works. The address saves. The page says thanks. The person who just raised their hand simply never hears back, and you have no way of knowing.

The four forms are four different businesses, not four colors. The Booked Calendar for people who sell their time, where you are filtering for someone worth talking to rather than collecting addresses. The Blueprint for people who sell what they know, where the headline is boring and specific on purpose, because "a guide" is worth nothing and "42 pages" is a thing. The First Order for people who ship something in a box, because a discount is the only lead magnet that has ever really worked in retail. And The Walk-In for people who have an address, where the offer is handed over first with no email required, and the ask comes after.

On where your list should live: one SQLite file on your own server. It is a real database, but it is one file you can copy, back up, or mail to yourself. And every signup also lands in your normal inbox, which sounds redundant and is the cheapest backup you will ever build. If the server dies tonight, your whole list is still sitting in your email.

There are excellent email platforms out there and this is not about avoiding them. It is about not needing one on day one, when you have four subscribers and no reason to pay a monthly bill or hand your list to somebody else to hold. You already own a domain, a server, and a mail key. Start here, learn what the moving parts are, and move to a platform later from understanding instead of guessing. Exporting a list is a file, not a migration.

One rule the kit builds in for you: every form on your site runs through the same shared function. If adding a second form means copying the logic, then one day you copy nine tenths of it and ship the version that saves the address and never writes back. Build it once, call it from everywhere, and that failure stops being possible.

If you want to do it, I made it a copy-paste prompt. Go to connectwithcliff.com/kit, copy the form prompt, paste it into Claude, and it interviews you, builds it, and tests it in front of you as if it were a stranger. New here? Start with Kit 1 (terminal setup) first, so Claude can actually run.

Next part: something worth giving away, so the form has a reason to exist.

Part Ten. Your first phone number.

Kit 9 caught an email address. That's a fine thing to own. It's also one channel, and it's the slow one. Somebody signs up on a Tuesday night, your welcome lands, and it sits in a tab with forty other tabs until the weekend, if it gets opened at all.

A phone number is the other channel. A text gets read in about three minutes, by almost everyone who gets it, and nobody has a "promotions" folder for it. So this kit gives your projects a number of their own. Not your personal cell. A number your code can send from and, this is the part people skip, receive on.

Here's what it actually opens up, because "SMS" sounds like marketing and most of what you'll use it for isn't.

A code that proves the person signing up owns the number they typed. An order update that says shipped, with a link. A heads-up to your own pocket the second a form comes in, so you can answer while they're still on the page. And an alert when your server goes quiet at 3am, from a system that noticed before you did. One number does all of it.

I use Twilio. Not because it's the only one, but because it's the one every piece of code already knows how to talk to, it starts free, and it has the same scoped-key idea you learned in Kit 6. So there's only one genuinely new thing in this kit, and it's a rule, not a technique.

The carriers changed the rules a couple of years ago. If you're a business sending texts from a normal ten-digit number in the US, you have to be registered first. They call it A2P 10DLC, which is a terrible name for a simple idea: they want to know who you're and what you send before they carry it. Unregistered traffic from a local number is blocked outright, and there's nothing you can do about that from code. Registration also needs a paid account, so the card goes on before this step.

So before you buy a number, you pick a door.

Door one is a local number, registered. You register yourself as a brand, one person without a business entity counts, then you register one campaign, which is a paragraph describing what you send and how people opt in. Twilio's current numbers are about twenty dollars once and two dollars a month for a sole proprietor, and the review takes days. Their page says five to ten right now. That's the honest timeline and you should plan around it, not fight it. One thing to know about this door: a sole proprietor brand is deliberately small, one number, one campaign, one message a second, and it's only for people without an EIN. If you have one, you register as a low-volume standard brand instead.

Door two is a toll-free number, verified. No campaign, no monthly campaign fee, and verification runs about three to five business days. The catch is that since January 31, 2024 an unverified or still-pending toll-free number can't send at all, not even a test. And a toll-free number reads as a company. That's right for order updates and codes. It's wrong for a text that's supposed to feel like it came from you.

My take: one person building their own thing takes door one and starts the paperwork tonight. A business with an EIN sending transactional texts takes door two. Door two is less paperwork, not no paperwork: you still describe the use case, the opt-in flow, your site and sample messages, and most rejections come from vague opt-in wording. Either way, the free trial lets you verify your own mobile and send a test to it, trial prefix and all. A custom text from your own new number can still wait on the door clearing. So do the paperwork first and treat the test as the last step, not the first.

Now the pieces, because there are three and only one of them is new.

The key. Twilio hands you an Account SID and an Auth Token at signup, and the Auth Token can do everything, including spend your money. You don't give that to Claude. You make a separate API key, Twilio's restricted kind, ticked to send messages and nothing else, and that's what your code uses. If it leaks you revoke that one key and the account is untouched. Same lesson as Kit 6. Least privilege isn't paranoia, it's just where you keep the blast radius.

The send. One request with a from, a to, and a body. That's the whole API for outbound. When your phone buzzes with a text from your own number, sent by your own code, you're through the hard part. In trial it'll say "sent from a Twilio trial account" on the front. That's expected and it goes away when you add a card.

The inbound endpoint, which is the piece most people never build. When somebody replies to your number, Twilio doesn't keep it. It delivers the reply to a URL you name, and if you never named one, the reply goes nowhere. So Claude adds one small endpoint on your Kit 7 server, the same shape as the Kit 9 form endpoint: Twilio posts the sender and the text, the endpoint checks the request really came from Twilio, saves it, and emails it to you through your Kit 6 domain. Every reply lands in your inbox in seconds. You now have a phone number that answers to your code and reports to you.

Two things the kit puts in from the start, because bolting them on later is how people end up as spammers with a phone bill.

Opt-out, twice. Twilio handles the legal words on standard numbers: STOP blocks the person, START lets them back in, HELP gets an automatic answer. But Twilio only stops what Twilio sees. So the kit also keeps a do-not-text list in the same SQLite file from Kit 9, writes to it on every STOP that hits your endpoint, and every send checks it first. Belt and braces, and the braces are yours.

Quiet hours. One rule in the code, yours rather than Twilio's and a notch stricter than the usual legal window: no marketing texts before nine in the morning or after eight at night in the recipient's time zone, and never more than a couple a week unless they asked for more. Codes and order updates are exempt, because they're answering something the person just did.

What it costs: a local number is about a dollar a month, toll-free a little over two, and a text is under a cent plus a small carrier fee. Registration is the only real line item and it's about the price of lunch. What you feel isn't the money. It's the first time your phone buzzes because your own code decided it should.

The honest part. What you've built is one number, one key, and about a hundred lines you understand. If you grow into needing segments and campaigns and a dashboard, there are good products for that and you should use one. What this gives you is the thing underneath all of them: a channel you own, that your projects can use, with the consent and the opt-out done right on day one, so that whatever you build on top of it later starts from a clean list.

If you want to do it, it's a copy-paste prompt. Go to connectwithcliff.com/kit, copy the Kit 10 prompt, paste it into Claude, and it walks you through the account, asks you which door, buys the number, starts the paperwork, and sends the first text to your phone in front of you. New here? Start with Kit 1 so Claude can actually run.

One more thing, and it's new to the kits from this one on. Every kit now starts with a short legend Claude reads first: what the kit assumes, and which earlier kit provides it, with the address. So if you paste Kit 10 and you never did Kit 6, Claude fetches Kit 6, does it with you, and comes back. You don't have to know the order. Claude does. The whole list, in a form Claude can read, is at connectwithcliff.com/downloads/INDEX.md.

Next part: the Kit 9 form gets an optional phone field, with a one-time code, so you only ever store a number that really belongs to the person typing it.