How to Write Course Lesson Scripts Using Claude

Before you open Claude, gather three things. First, your lesson outline — not just a title, but the key points you want to cover, the order you want to cover them, and the outcome for this specific lesson. Second, a voice sample: two or three paragraphs of your own writing or a transcript of you teaching. This gives Claude a concrete target for tone and vocabulary. Third, a brief description of your students — who they are, what they already know, and what they're trying to accomplish.

The voice sample is the piece most people skip, and it's the piece that matters most. Without it, Claude produces competent instructional prose that sounds like everyone and no one. With it, the output will at least lean toward your patterns — your sentence length, your level of formality, your tendency to use questions or analogies or direct statements.

Start a new Claude conversation with your full context. Paste in the voice sample first, then the course outline, then the specific lesson brief. Frame it clearly:

Here is a sample of my writing voice:
[paste 2-3 paragraphs]

Here is my course outline:
[paste full outline]

I'm writing the script for Lesson 3: [lesson title].
Students are [audience description].

By the end of this lesson, students should be able to
[specific outcome].

Write a lesson script of approximately 1,500 words.
Match my writing voice. Use "you" to address students
directly. Include one concrete example and one practice
prompt. Don't use bullet points or numbered lists —
write in flowing prose as if I'm speaking to the student.

Notice the specificity: word count, voice matching, a named structural element (example, practice prompt), and a formatting constraint. Each of these steers the output away from generic AI writing and toward something you'd actually record.

Read the draft out loud. This is not optional. A lesson script is meant to be spoken, and sentences that look fine on screen often feel awkward in your mouth. Listen for places where the vocabulary shifts — where Claude's word choices don't match yours — and for sentences that are too long or too formal for spoken delivery.

Mark the sections where the voice drifts. Then tell Claude what to fix: "The opening paragraph sounds like me, but starting from the third paragraph you shift into a more formal academic tone. Bring it back to the conversational style of the opening. Also, I'd never say 'utilize' — use 'use' instead." Specific corrections teach Claude your preferences within the conversation, and subsequent drafts improve.

Claude can invent plausible examples, but they'll be generic. The examples that make a lesson memorable are yours — the student who struggled with a concept and then had a breakthrough, the mistake you made early in your career, the real situation your students will recognize from their own work. After Claude produces the structural draft, go through it and replace the placeholder examples with real ones.

You can also tell Claude about a specific example and ask it to weave it in: "I want to include a story about a client who tried [approach] and found that [result]. Work this into the section on [topic] as a teaching moment." Claude is good at integrating a story you provide into the flow of the lesson. It's less good at inventing stories worth telling.

Lesson scripts have a rhythm that written articles don't. Students need breathing room after a dense concept. They need a shift in energy every few minutes — from explanation to example, from example to reflection, from reflection to the next idea. Read through the script and notice where the density is too high for too long. Ask Claude to add a transitional moment, a quick recap, or a rhetorical question that gives the student a beat to absorb what they just heard.

Every lesson should end with something the student does — not just something they heard. Ask Claude to draft a practice activity that connects directly to the lesson content:

Write a practice prompt for the end of this lesson.
The activity should take 10-15 minutes, use materials
the student already has, and produce a concrete
artifact they can share or build on in the next lesson.
Keep the instructions clear and specific — no vague
"reflect on what you learned" prompts.

The constraint about producing a "concrete artifact" is important. It pushes Claude past generic reflection prompts toward activities with a visible output — a draft, a plan, a completed exercise — which research on active learning consistently shows produces better retention than passive review.

Once you've refined one lesson script and are happy with the voice and structure, use that as a template for the rest. Paste your approved script back into the conversation and say: "Here's the final version of Lesson 3. Use the same voice, structure, and pacing for Lesson 4. Here's the lesson brief: [details]." Working sequentially in one conversation means Claude carries forward your preferences, your corrections, and the overall course context. Each subsequent script should need fewer revisions than the first.

A lesson script is the closest thing in your course to a conversation with your students. It carries your personality, your judgment, and your experience in a way that an outline or a slide deck does not. Claude can produce the bones of that conversation — the logical flow, the transitions, the structural scaffolding — but it cannot produce the moments that make students feel taught rather than informed.

Those moments are specific. They're the aside where you say "I struggled with this too, and here's what helped me." They're the place where you slow down because you know from experience that this is where people get confused. They're the sentence where you say something slightly unexpected — a perspective that's yours alone — and the student thinks, "I hadn't considered that." No AI produces those moments. You add them after the draft exists.

Some course creators find it easier to record themselves talking through a lesson extemporaneously, transcribe it, and then ask Claude to turn the rough transcript into a polished script. This approach captures your natural voice perfectly — because it is your natural voice — and uses Claude for editing rather than generation. The result often sounds more authentic than a script Claude wrote from scratch.

If you're writing scripts for an entire course, compile your voice preferences into a single document: sentence length, vocabulary to use and avoid, how you address students, whether you use humor, your stance on jargon. Paste this at the start of each new conversation. It's more reliable than trying to convey your style through a single writing sample, and it makes your preferences explicit rather than implicit.

The first thirty seconds of a lesson set the tone. Even if Claude drafts the rest of the script, consider writing the opening yourself. A personal opening — something that happened that week, a question a student asked, a connection to the previous lesson — grounds the script in your voice before Claude takes over for the structural middle. Students notice openings more than any other part of a lesson.

Claude's lesson scripts tend to be too even-tempered. Real teaching has dynamics — moments of intensity, pauses, shifts in energy. Claude writes at a steady medium register throughout, which can produce scripts that feel flat when recorded. After generating a draft, look for places to add emphasis, urgency, or quiet. A script that reads well is not necessarily a script that sounds alive.

It also over-scaffolds. Claude will introduce a concept, explain why it matters, define it, give an example, recap the definition, and transition to the next point — all for a concept your students may grasp in two sentences. If your audience is experienced, you'll often need to cut Claude's explanations in half. Trust your knowledge of what your students already know.

Finally, Claude tends to end lessons with tidy summaries that feel formulaic after the third or fourth time. "In this lesson, we covered X, Y, and Z. In the next lesson, we'll explore W." That pattern is fine occasionally, but your course will feel more natural if some lessons end with a question, some with a challenge, and some with a moment of anticipation for what comes next. Vary the endings yourself.