General AI Skills
0 of 15 lessons done

Reference skills you can dip into anytime, in any order. They pay off across everything you build, not just one project. Each lesson has a short explanation, the steps, and a prompt you can paste straight into Claude.

General AI skills

Reference skills you can dip into anytime, in any order. They pay off across everything you build, not just this website.

Working with AI

0/5

These habits work with any AI tool, not just Claude. Get these down and everything else gets easier.

SkillTalk to AI like you're briefing a sharp new assistant
What's happening: AI is brilliant but it can't read your mind. The single biggest jump in your results comes from being specific. Imagine you hired a smart assistant on day one. They're capable, but they don't know you, your taste, or what "good" looks like to you yet. So you tell them.
The three things to always include
  1. Context. Who it's for, what you're trying to do, anything it should know.
  2. An example of what you mean, when you can. "Make it sound like this" beats "make it sound good."
  3. What "done" looks like. Tell it the finish line so it knows when it's there.
Weak ask vs. strong askWeak: "Write me a welcome message."
Strong: "Write a 2-sentence welcome for the top of my site. It's for new moms who feel overwhelmed. Warm and calm, like a friend who's been there. Here's a line I like the tone of: [paste]."
You've got it when: you stop getting generic answers and start getting ones that already sound like you, on the first try.
Watch out for: dumping everything in one giant message. Give the key context, then go back and forth. A conversation beats a monologue.
SkillTalk, don't type: use your voice
What's happening: Most people type short, careful prompts and leave out the context AI needs. When you talk instead, you naturally say more, and AI loves more. You can ramble, change your mind mid-sentence, and still get a great result. This is the unlock for anyone who thinks faster than they type.
How to do it
  1. On your phone: tap the microphone on your keyboard and just talk. It types for you.
  2. On your Mac: press the dictation key (or set one up in System Settings > Keyboard > Dictation), then talk into any text box.
  3. Don't worry about being tidy. Say it the way you'd explain it to a friend. AI cleans it up.
You've got it when: a two-minute ramble out loud gets you further than ten minutes of typing and deleting.
Watch out for: waiting until your thought is perfect before you speak. The point of voice is to think out loud, so start talking before you've figured it all out.
SkillAsk for a plan before the work
What's happening: When something feels big or you're not sure how to ask, don't make AI guess and run. Ask it to lay out a plan first. You read it, fix anything that's off, then say go. This catches wrong turns before they cost you time, and it teaches you what's actually involved.
Paste this when you're not sure how to start
I'm about to ask you to do something, but I want a plan first. Ask me one question at a time about what I'm trying to do, using each answer to get clearer. Then give me a short plan: list the steps, flag anything you're unsure about, and don't start until I say go.
You've got it when: you catch yourself saying "actually, change step 2" before any work happens, instead of redoing it after.
SkillGet unstuck when AI goes in circles
What's happening: Sometimes AI gets confused, repeats itself, or keeps "fixing" something the wrong way. This is normal and it's not you. You have three reliable moves to break the loop.
Your three moves
  1. Paste the error back. If you see a red error message, copy the whole thing and paste it in with "I got this, what do I do?" AI reads errors better than people do.
  2. Narrow the ask. If it's juggling too much, ask for one small piece at a time instead of the whole thing.
  3. Start fresh. If a conversation is hopelessly tangled, open a new chat and re-explain in two clean sentences. A fresh start often beats untangling.
You've got it when: getting stuck stops feeling like failure and starts feeling like a signal to switch moves: paste the error, narrow the ask, or start fresh.
Watch out for: repeating the exact same request louder. If it didn't land twice, change how you're asking, don't just ask again.
SkillLook before you approve (and how to undo)
What's happening: AI will often ask permission before it changes or deletes something. That pause is for you. You don't need to understand every line, but a quick glance at what it's about to do keeps you in control and builds your instinct over time.
Two safety habits
  1. Skim before you say yes. Read the one-line summary of what it's about to do. If it's about to delete a lot, slow down and ask "why?"
  2. Know your undo. Changed something you didn't want? Just say "undo that, go back to how it was." When you reach the launch lessons, you'll also learn how to save versions so you can always roll back.
You've got it when: approving a change feels like a quick check, not a leap of faith.

Getting the most out of Claude

0/5

A few things that are specific to Claude. Small setup, big payoff every time you sit down to build.

FoundationFiles and folders: where your stuff lives
What's happening: Everything you build with Claude lives in a folder on your computer, just like a folder of photos. Claude works inside one folder at a time. Once you're comfortable with "this is my project folder, and my files live in it," a lot of the mystery disappears.
The basics
  1. A folder holds your project. You already made one in the setup lessons (my-website).
  2. A file is one document inside it, like index.html (your web page) or notes.md (a plain text note).
  3. The file extension (the bit after the dot) tells the computer what kind of file it is. .html is a web page, .md is markdown (plain text with simple formatting), .jpg is a photo.
Try it: ask Claude to make a markdown file
In this folder, create a markdown file called notes.md with a heading that says "My project notes." Ask me, one at a time, for a few things I want to remember, with a quick follow-up if I want to add detail. Add them as a list, then show me where the file is.
You've got it when: you can open your project folder, see the files inside, and know which one is which by its name.
FoundationMake a CLAUDE.md so it knows your project
What's happening: A file named CLAUDE.md in your project folder is like a sticky note Claude reads every single time it starts. Put the stuff you'd otherwise re-explain in there once, who you are, what the project is, how you like things, and you stop repeating yourself.
What to put in it
  1. One line on who you are and what you're building.
  2. Your preferences ("keep copy warm, no jargon," "ask before deleting").
  3. Anything you keep having to remind it of.
Have Claude make it for you
Create a CLAUDE.md file in this folder so you remember my project every time. Ask me one question at a time about who I am, what this project is, and how I like things done, using each answer to get more specific. Let me say "I'm not sure, let's add that later" on anything I don't know yet. Then write it up, short and clear.
You've got it when: you open a fresh session, give a short instruction, and Claude already knows the context you'd normally have to repeat.
FoundationHow Claude's memory works
What's happening: Within one conversation, Claude remembers everything you've said. Start a brand-new conversation, and it begins fresh, it doesn't carry your last chat over by default. Knowing this saves a lot of confusion: if Claude "forgot" something, it's usually because you're in a new session.
What carries over, and what doesn't
  1. Same conversation: it remembers the whole thread. No need to repeat yourself.
  2. New conversation: a clean slate, except for anything written into your CLAUDE.md (that's why that file is so handy).
  3. The fix: put anything you want remembered long-term into CLAUDE.md or a notes file, not just in the chat.
You've got it when: a new session starting fresh doesn't surprise you, because the important stuff already lives in a file.
Watch out for: assuming Claude remembers a decision from last week's chat. If it mattered, write it down in your project.
Foundation"Remember this" and where it actually goes
What's happening: You can just tell Claude "remember this" and it will write it down for next time, usually into your CLAUDE.md. This is how you teach Claude your preferences over time without re-explaining them. The more you do it, the more it feels like working with someone who knows you.
Try it
I want to teach you something to remember for next time. Ask me one question at a time about the preference or fact I want you to keep, with a follow-up to make it specific. Then save it where you'll see it in future sessions.
You've got it when: you've taught Claude two or three of your preferences, and you notice it applying them without being asked.
FoundationEnd every session with a clean wrap-up
What's happening: Before you close the terminal, take thirty seconds to make sure nothing you did is left hanging. Work that only lives in a chat window, or in a file you never saved, can quietly disappear. A quick wrap-up question at the end of every session is the habit that keeps your project safe and your future self sane.
Why this matters
This is the question I ask at the end of every working session, and it has saved me more times than I can count: "Are we clear? Is everything saved, updated, and live where it needs to be?" Asking it out loud, every time, turns "I think I'm done" into "I know I'm done."
Paste this at the end of any session
Before I close this, let's do a wrap-up. Walk me through it one item at a time: Is there anything that still needs to be saved or finished? Anything I should put live or deploy? Anything worth writing into CLAUDE.md or a notes file so we don't lose it next time? Then tell me plainly what's done and what's still open.
You've got it when: closing your laptop stops feeling like a gamble, because you always ask "is everything saved and live?" before you walk away.
Watch out for: assuming a change is live just because you made it. Making it, saving it, and putting it live are three different steps, and the wrap-up question catches the ones you missed.

Learn anything with Claude

0/4

Claude isn't just for building. It's the most patient tutor you'll ever have. These skills let you teach yourself almost anything, at your own pace.

SkillShow Claude your screen with a screenshot
What's happening: Claude can see images. So instead of trying to describe a confusing screen in words, you take a screenshot of it, an error message, a menu you're lost in, a design you like, and drop it straight into the Claude desktop app. Then you just ask about it.
Why this matters
Describing what's on your screen in words is slow and easy to get wrong. Showing it is instant and exact. This one habit turns "I have no idea what I'm looking at" into a two-second question.
Do this
  1. On a Mac: press Cmd + Shift + 4, then drag a box around what you want. It saves to your Desktop. (Cmd + Shift + 3 grabs the whole screen.)
  2. On Windows: press Windows + Shift + S to grab part of the screen.
  3. Drag that image into the Claude desktop app, or paste it, and type your question.
Paste this into Claude (with your screenshot)
Here's a screenshot of what I'm seeing. Ask me what I'm trying to do if it's not obvious, then tell me in plain language what this is and exactly what to click or type next.
You've got it when: you can grab a screenshot and drop it into Claude, and it tells you what you're looking at and what to do next.
Watch out for: sharing sensitive info by accident. Crop or blur out passwords and personal details before you send a screenshot.
SkillAsk Claude to walk you through anything, step by step
What's happening: Claude is a tutor that never sighs and never rushes you. For anything you don't know how to do, you can ask it to walk you through it one step at a time, waiting for you to finish each step before it gives you the next.
Why this matters
Most tutorials move too fast and quietly assume you already know things. Claude goes at your pace, and you can ask "wait, what does that mean?" as many times as you need without ever feeling dumb.
Do this
  1. Pick one thing you've been meaning to figure out. It doesn't have to be about websites, it can be anything.
  2. Open Claude and use the prompt below.
  3. Do each step as it gives it to you, and tell Claude when you're ready for the next.
Paste this into Claude
I want to learn how to do something. Ask me what it is, then walk me through it one step at a time, in plain language. Assume I'm a total beginner, give me just one step, and wait for me to tell you I've done it before giving me the next. Check I'm with you before moving on.
You've got it when: you've had Claude walk you through something one step at a time and you finished it without getting lost or overwhelmed.
Watch out for: Claude dumping all the steps at once. If it does, just say "one step at a time, and wait for me" and it'll slow down.
SkillPull the lesson out of a YouTube video
What's happening: There's a great how-to video, but you don't want to sit through 40 minutes for the two minutes you need. Every YouTube video has a transcript (the full text of what's said). You can grab it and have Claude summarize it, pull out the steps, or answer your one specific question, in seconds.
Why this matters
This turns any long video into exactly the part you need, in text you can skim and act on. It's one of the fastest ways to learn something without losing an afternoon.
Do this
  1. Open the transcript. Under the video, click the "..." (more) or expand the description, then click Show transcript.
  2. Select all the transcript text and copy it.
  3. Paste it into Claude along with your question.
Paste this into Claude (with the transcript)
Here's the transcript of a YouTube video. Pull out the key steps as a simple numbered list I can actually follow, and tell me anything I should watch out for. If I ask a specific question about it, just answer that.
You've got it when: you've turned a long video into a short, skimmable set of steps without watching the whole thing.
Watch out for: very long transcripts. If it's huge, tell Claude what you're after ("just the part about setting up the account") so it stays focused.
SkillGet anything explained in plain language
What's happening: Any time you hit a word, a concept, or an error you don't understand, Claude can explain it like you're brand new, with a simple example, and zero judgment. This is how you stop feeling behind.
Why this matters
The fastest learners aren't smarter, they just ask "what does that mean?" more often. Claude makes asking that free and instant, so there's no reason to nod along when you're lost.
Paste this into Claude
Explain something to me like I'm brand new. Ask me what I want explained, then put it in plain language with a simple everyday example. Then ask me one question to check I actually got it, and explain it a different way if I didn't.
You've got it when: you can take anything that confused you and get an explanation that actually lands, in your own terms.
Watch out for: nodding along when you still don't get it. Just say "explain it a different way" until it clicks.

You did the whole thing.

Every lesson, done. You've got the skills to keep building, so go make the next one.