FREE COURSE · 5 MODULES

ClaudeHQ Foundations

Learn Claude well enough to use it for real work — today, not someday.

Five short modules. About an hour. Free forever, no signup to start. Each one ends with a prompt you paste straight into Claude and watch work. Finish all five and grab your certificate.

Who it's for: Anyone staring at a blank Claude chat wondering what to do next. New to AI, switching from ChatGPT or Gemini, or already using Claude for emails and sensing there's more — you're in the right place.

1 · Meet Claude 2 · First Prompt 3 · Make It Useful 4 · Don't Get Burned 5 · Your Workflow Certificate
Module 1 of 5

Meet Claude

By the end: you'll know what Claude is, how it's different, and which gear to reach for.

What this is

Claude is an AI assistant made by Anthropic. You tell it what you need in plain English, and it writes, explains, analyzes, summarizes, brainstorms, or builds things alongside you.

Why it matters

Most people treat AI like a search box — type a few words, hope for the best. Claude works better when you treat it like a sharp assistant you're handing a task to. Small shift, big difference. The whole course is built on it.

The idea — three gears, not one

Claude comes in a few versions, and you don't need to memorize their names. Think of them as three gears:

  • The fast model — quick drafts, summaries, simple rewrites. Speed over depth.
  • The balanced model — your everyday default. Most writing, analysis, and work lives here.
  • The strong model — the heavy lifter. Reach for it when the task is complex, high-stakes, or has a lot of moving parts.

Start with the balanced one. Move up when an answer feels thin, move down when you just want speed. (Want exact names and specs? The models table on ClaudeHQ has them — but you can use Claude for months without ever thinking about it.)

Coming from ChatGPT or Gemini?

You'll feel at home in about five minutes. Two habits are worth dropping at the door:

  1. Skip the search-engine shorthand. Claude rewards full sentences. "Marketing ideas" gets you a generic list. "Give me five newsletter angles for beginners trying Claude, under 12 words each, no hype" gets you something you can actually use.
  2. It's not just a chat box. The real value shows up when you bring it your own files and keep your work in one place — more on that in Module 5.
🎯 Your challenge — Say hello

Open Claude and paste this:

Hi Claude. I'm new here. Explain what you can help me with in plain English. Then give me five practical things a beginner should try first — one writing task, one research task, one task that uses a file, one brainstorm, and one that could save me time at work.
Done when: You've got a short list of things to try, and Claude feels less like a mystery box and more like an assistant waiting on instructions.
Module 2 of 5

Your First Real Prompt

By the end: you'll turn a vague request into one that actually works — every time.

What this is

A prompt is just the instruction you give Claude. This module teaches the one formula that fixes most weak results.

Why it matters

When Claude hands you something generic, it's usually not being dumb — it's guessing, because you didn't give it enough to work with. Better instructions, better output. That's almost the whole game early on.

The idea — What + How + Constraints

Every strong prompt has three parts:

  • What — the job. ("Write a LinkedIn post announcing our training.")
  • How — the style or role. ("Make it practical and beginner-friendly, no hype.")
  • Constraints — the limits. ("Under 180 words, strong first line, soft call to action at the end.")

Think of it like ordering at a deli. "Sandwich" gets you whatever they feel like making. "Turkey on rye, toasted, no mayo, extra pickles" gets you lunch. Claude's the same — tell it what, how, and what to leave off.

See it

Weak: "Write a LinkedIn post."
Better: "Write a LinkedIn post announcing our free Claude training. Practical and beginner-friendly, no hype. Under 180 words. Open with a hook, close with a soft call to action."

Same tool. Completely different result.

🎯 Your challenge — Fix a weak prompt

Paste this:

I'm going to give you a weak prompt. First tell me why it's weak. Then rewrite it using this structure: what + how + constraints. Then answer both versions so I can see the difference side by side. Weak prompt: "Make me something about AI."
Done when: You can feel the gap between hoping Claude guesses right and giving it enough to get it right.
Module 3 of 5

Make It Actually Useful

By the end: you'll know the four dials that turn a decent answer into one you'd actually send.

What this is

Module 2 got you a good answer. This one gets you the right answer — shaped to sound like you, land with your audience, and arrive in the format you need.

Why it matters

A generic answer is easy. A useful one is shaped before Claude writes a word. Four dials do most of the shaping.

The idea — four dials
  • Persona — who Claude should act like. ("Act like an experienced operations manager.")
  • Tone — how it should sound. ("Calm, direct, no corporate fluff.")
  • Format — what shape the answer takes. ("Subject line, one short paragraph, three next steps.")
  • Examples — what "good" looks like. (Paste one in and say "match this style.")

If Module 2 was ordering at the deli, this is deciding whether a line cook, a chef, or a caterer makes it. Same ingredients, very different result.

See it

Instead of: "Rewrite this email."
Try: "Rewrite this email as an experienced operations manager. Keep it calm, clear, and professional. Format it as a subject line, one short paragraph, and three bullet next steps. Plain English, no fluff."

🎯 Your challenge — Rewrite a real email

Paste this, then drop in a rough email of your own:

Rewrite the email below using these settings: Persona: experienced operations manager Tone: calm, clear, professional Format: subject line + short email + 3 bullet next steps Goal: make it obvious what the reader needs to do next Email: [paste your rough email here]
Done when: You see that the best prompts don't just ask for an answer — they shape it first.
Module 4 of 5

Don't Get Burned

By the end: you'll know exactly where to trust Claude and where to check its work.

What this is

Claude is fast and capable. It's also not automatically right. This module is about knowing the difference.

Why it matters

Claude can be confident and wrong at the same time. It can sound polished while making something up. If you're using it for anything that matters, your job isn't just to prompt well — it's to verify smart.

The idea — the trust boundary

Treat Claude like a sharp junior teammate. Great for drafts, summaries, brainstorms, reshaping things, and analyzing what you give it. Not your final word on facts, law, money, or medicine.

Lean on Claude to: draft, summarize, brainstorm, reorganize, transform, and analyze material you hand it.

Don't blindly trust it to: invent citations, give final legal or medical advice, replace an expert, or be right just because it sounds sure.

A two-second habit that catches a lot

After Claude answers something that matters, ask:

  • "What are you least sure about here?"
  • "What did you assume?"
  • "How would I check this?"
🎯 Your challenge — Catch it slipping

Paste this:

Give me eight specific factual claims about a topic I know a little about. Then tell me which three you're least confident in, and how I'd verify each one.
Done when: You stop reading Claude's output as "true" and start reading it as "a strong draft I get to check." That habit is the line between people who get burned and people who don't.
Module 5 of 5

Your Workflow Starts Now

By the end: you'll have used the three features that turn Claude from a chat box into part of how you actually work.

What this is

Up to now you've been typing into a blank chat. This module shows you the features most people never find: Projects, file uploads, and artifacts.

Why it matters

A blank chat is fine for one-off questions. Real work is repeat work — same context, same files, same kind of output. These three features are how you stop starting from scratch every time.

The idea — three features
  • Projects — a home for one body of work. Keep your files and instructions in one place, so every chat inside it already knows the context. No more re-explaining yourself.
  • File uploads — give Claude the actual material. Drop in a PDF, a spreadsheet, a doc, your notes — and it works from your real stuff instead of guessing.
  • Artifacts — when Claude makes something you'll reuse (a document, a summary, a simple web page), it builds it in its own window you can edit, copy, and download.

The shift: beginners ask Claude to "help" in the abstract. Real users hand it the actual brief, the actual file, and ask for a specific thing back.

🎯 Your challenge — Build a one-page project

Gather a couple of real files (an outline, a source doc, maybe a sample whose style you like). Then paste this:

I'm building a small project from real materials, and I'll upload a few files for context. First, look at what I uploaded and tell me what each one is good for. Then create a clear, well-structured one-page summary that pulls the important parts together. If it makes sense, turn the final version into an artifact I can edit or download.
Done when: You've made something real from your own files — and you get why Claude gets more useful the more context you give it.

Go deeper on Projects in the full guide →

Get your certificate

Finished all five? Drop your name and email and your ClaudeHQ Foundations certificate appears right here — ready to save, screenshot, or share. It's the only thing here that asks for an email — everything else is free, no signup, forever.

Honor system. No tracking, no spam — and the rest of the course stays free forever.

Keep going

You've got the foundations. Here's the full path to Claude as a complete work stack.

ProjectsCoworkVisualsFull Stack