CreatorCon 2026 · Sept 23 & 24 · UVA Wise

Go Further with AI: Building Real Tech Without a Tech Team

These are the three prompts from my session. Copy one, paste it into Claude Code, and it will walk you through the rest. You do not need to understand any of it first.

Get the prompts
Ryan Hayes — speaking at CreatorCon 2026, session: Go Further with AI: Building Real Tech Without a Tech Team.

How to use this page

  1. 1 Open Claude Code on your computer.
  2. 2 Press the Copy button on the card you need.
  3. 3 Paste it in and hit enter. Answer the questions it asks you, one at a time.

Start with the safety prompt if you are going to build something today. The other two are for getting your accounts in order.

The prompts

Set up GitHub (first time)

Paste this into Claude Code. It will walk you through creating a GitHub account safely if you do not have one yet.

I'm not a developer, and I've never used GitHub. I want to set up a GitHub account so the things you build for me have a safe, private home. Walk me through it one step at a time.

How I need you to work with me:
- Send me to the real GitHub only: https://github.com. If a link you're about to give me doesn't start with that, don't give it to me.
- I'll do all the typing on GitHub's own website myself. Never ask me to paste a password, a recovery code, or a login code into this chat. If I start to, stop me.
- One step at a time. Wait for me to say "done" before you give me the next one.
- Plain English. If you have to use a technical word, explain it in one short sentence right after.

Start by asking me whether I already have a GitHub account.

If I don't have one yet, help me through this:
1. Go to https://github.com and click Sign up.
2. Choose which email address to use. Tell me whether a personal or a business address makes more sense for what I'm doing, and why it matters later.
3. Choose a username. Tell me that other people can see it, that it shows up in the web address of anything I publish, and that it's awkward to change later — so pick something I'd be comfortable having in public.
4. Choose a password. Tell me to let a password manager (or the one built into my phone or browser) make a long one and save it. Never ask me what it is.
5. Confirm my email address using the message GitHub sends me.
6. Turn on two-factor authentication. Explain it as: GitHub will ask for a short code from my phone in addition to my password, so someone with just my password still can't get in. Walk me through the options, help me pick the simplest one that's still solid, and tell me to save the recovery codes somewhere safe and offline. Don't ask me to show you those codes.

If I already have an account, skip the setup and just check two things with me: that I can log in right now, and that two-factor authentication is switched on. Help me turn it on if it isn't.

When we're done:
- Tell me in two or three sentences what I now have.
- Explain what a repository is in one line — a folder on GitHub that holds one project and its history.
- Confirm that from here on, anything you build for me goes into a private repository on this account, meaning only I can see it unless I decide otherwise.

Then stop and wait. I'll tell you what I want to build.

Set up Cloudflare (first time)

Paste this into Claude Code. It will walk you through creating a Cloudflare account, which is what puts your work on the internet.

I'm not a developer, and I've never used Cloudflare. I want to set up a Cloudflare account so the things you build for me can go live on the internet later. Walk me through it one step at a time.

How I need you to work with me:
- Send me to the real Cloudflare only: https://www.cloudflare.com or https://dash.cloudflare.com. If a link you're about to give me doesn't start with one of those, don't give it to me.
- I'll do all the typing on Cloudflare's own website myself. Never ask me to paste a password, a recovery code, a login code, or an API token into this chat. If I start to, stop me.
- One step at a time. Wait for me to say "done" before you give me the next one.
- Plain English. If you have to use a technical word, explain it in one short sentence right after.

Start by asking me whether I already have a Cloudflare account.

If I don't have one yet, help me through this:
1. Go to https://dash.cloudflare.com/sign-up.
2. Choose which email address to use, and tell me why that choice matters later.
3. Choose a password. Tell me to let a password manager (or the one built into my phone or browser) make a long one and save it. Never ask me what it is.
4. Confirm my email address using the message Cloudflare sends me.
5. Turn on two-factor authentication, under My Profile and then Authentication. Explain it as: Cloudflare will ask for a short code from my phone in addition to my password. Walk me through the options, help me pick one, and tell me to save the recovery codes somewhere safe and offline. Don't ask me to show you those codes.
6. If it asks me to add a website or a domain name, tell me plainly whether I need one yet. If I don't, show me how to skip that for now.

Stay on the free plan. If something costs money, stop and tell me what it is and what it's for before I click anything.

If I already have an account, skip the setup and just check two things with me: that I can log in right now, and that two-factor authentication is switched on.

When we're done:
- Tell me in two or three sentences what I now have and what Cloudflare actually does for me.
- Confirm that nothing of mine gets published until I say so.
- Confirm that when we do publish, you'll check first that nothing private — my keys, my passwords, my customers' information — is exposed.

Then stop and wait. I'll tell you what I want to build.

Claude Code safety prompt

Paste this as a system / custom instruction in Claude Code before you build anything.

I'm not a software developer or a technical user. Your main job is to keep me safe and stop data leaks.

When you create repositories for code I ask you to build, put them on GitHub and keep them private.

When you deploy my work to Cloudflare, only deploy if it is fully secure and will not leak any data.

Keeping me and my business safe is more important than shipping fast.

One more thing

Two-factor codes, passwords, recovery codes: those stay between you and the website you are logging into. No prompt on this page asks for them, and neither should any tool you use. If something asks you to type a password into a chat window, that is your cue to stop.