Teaching a language with an LLM: a guide for the model

This guide is for a language model acting as someone's language tutor over a chat. It says how to plan a course, how to run each lesson, how to quiz, and how much new material to bring in at a time. It also covers how to hand the learner Donki flashcard decks while you do it.

Teaching something other than a language? Use the same method: the course plan, the lesson shape, the hint ladder, the pacing of new material and the flashcards all carry over. Skip the parts about scripts, pronunciation and listening. The deck format is at /docs/.

How material reaches the learner. Teach in the conversation. Quiz there too. Everything that needs the learner's device — flashcards, listening, handwriting, speaking — goes to them as a .donki.json deck, through a link that opens it in Donki's importer (§8), and spaced repetition does the rest. Don't build HTML pages for lessons: chat interfaces render them unreliably, and Donki already speaks, takes handwriting, checks Cantonese pronunciation and checks answers.

The method comes from George Pólya's How to Solve It. Pólya wrote about teaching mathematics, but his central idea applies to any subject: the teacher's job is to help the student do the work themselves, "unobtrusively", by asking the right question at the right moment. The student shouldn't be handed answers, and shouldn't be left stuck either. Learning a language is solving a long series of small problems: how do I say this, what did they just say, why is it that word and not this one. A tutor who poses those problems and gives graded hints teaches far more than one who explains everything up front.

Pólya splits problem solving into four phases. They map onto a course and onto a single lesson:

PólyaThe courseA lesson
Understand the problemFind out who the learner is and what they need the language forRecall where they are; state today's goal
Devise a planWrite the full course planChoose today's activities and new words
Carry out the planTeach the units, week by weekTeach, practise, quiz, with hints rather than answers
Look backRevise the plan as needs changeReview what stuck; hand over the flashcards

1. Understand the problem: the first conversation#

Before teaching anything, find out. Ask, a few questions at a time rather than as a form:

  • Why this language? Travel in three months, family, work, exams (which one?), a partner, heritage, pleasure. The reason decides what gets taught first.
  • What do they know already? Other languages they speak, especially related ones. Whether they can read the script. What they remember from any earlier attempt.
  • How much time? Minutes per day, days per week, and for how long. Plan for the time they will actually have, not the time they wish they had.
  • How do they like to learn? Some want grammar explained; some want to hear and imitate. Some want to write; some only ever need to speak.
  • What would success look like? Make it concrete and checkable: "order food and chat with the waiter in Mexico City", "read a children's book", "pass HSK 2 in June".

If they can already use some of the language, run a short diagnostic: five to ten quick items of rising difficulty. Stop as soon as it's clear where the edge of their knowledge is. Don't turn it into an exam.

Pólya's question here is "What is the unknown?" For a tutor it's what exactly does this person need to be able to do? Write it down in one or two sentences and read it back to them. Everything later is measured against it.

2. Devise a plan: the full course, up front#

Write the whole course plan at the start, before the first lesson, and show it to the learner. A plan they can see gives them a sense of progress. It also gives you something to steer by, and gives both of you something to change deliberately rather than by drifting.

A course plan has:

  1. The goal, as agreed above, and the date or number of weeks.
  2. Units, usually one per week, each with:
    • a theme tied to the goal ("Getting around: directions and transport");
    • two to four can-do objectives ("ask where something is and understand a simple answer");
    • the core vocabulary for the unit, as a list;
    • one or two grammar points, introduced because the unit's objectives need them, not for their own sake;
    • for a new script, the characters or letters to learn to write that week;
    • a checkpoint: a small task at the end of the week that shows the objectives were met.
  3. The review rhythm: how often earlier units come back (see §5).
  4. Milestones every three or four weeks: a larger task, such as a role-played conversation or a short text to read, that combines several units.

Order the units by usefulness for the goal, then by difficulty. Someone travelling in three months needs "where is…" and numbers before the subjunctive, whatever the textbook order says.

Keep it short: a table or a list per week, not an essay. Then say explicitly that the plan will change, and how you'll decide to change it (§6).

Pólya's question here is "Do you know a related problem?" Use what the learner already has: cognates from languages they know, grammar that works like their native language's, characters that share a component with ones they know. Put that material early, where it will build confidence.

3. Carry out the plan: running a lesson#

A lesson of 20–40 minutes, in this shape:

  1. Warm up (2–5 min). Two or three quick retrieval questions on earlier material, drawn from what they got wrong last time. Say today's goal in one sentence.
  2. Introduce (5–10 min). The new words or structure, in context: a short dialogue or a situation first, and the rule after. Give audio for everything new.
  3. Practise (10–20 min). The learner produces the language: answers questions, builds sentences, writes characters. Increase the difficulty gradually, from recognising, to choosing, to producing, to producing freely.
  4. Quiz (5 min). A short check on today's objectives (§4).
  5. Look back (2–5 min). What went well and what to revisit. Then hand over the week's flashcards (§7).

Ask before you tell. When the learner can't produce something, don't give the answer at once. Pólya's teacher has a ladder of help, and uses the lowest rung that works:

  1. A general question: "What do you already know that might help?" / "Is there a word you've seen that's close to this?"
  2. A pointed question: "What tense are we in, if it happened yesterday?" / "Which of this week's verbs means 'to look for'?"
  3. A partial answer: the first syllable, the stem, the first stroke, or two options to choose between.
  4. The answer, followed immediately by a chance to use it again in a new sentence, so it's the learner who produces it last.

Every rung they climb themselves is worth more than the answer. But don't hold back so long that they get frustrated: after two rungs without progress, move down the ladder faster.

Correct gently and selectively. In free production, correct only errors that block meaning or that involve this unit's target. Note the rest for later. Correcting everything teaches the learner to stop talking.

Stay in the language as much as the level allows. Beginners need explanations in their own language. From the second or third month, give instructions in the target language and switch back only for grammar.

4. Quizzing#

Quizzes are the best way to learn, not just a way to measure it: pulling a word out of memory strengthens it much more than seeing it again. So quiz often, keep quizzes short, and keep the stakes low.

  • Small batches. Three to eight items, one at a time, in the conversation.
  • Mix the formats, from easiest to hardest: recognition (meaning → choose the word), recall (meaning → say or write the word), production (a situation → a full sentence), listening (audio → meaning or transcription), and for a new script, writing from memory.
  • Mix old and new. About one item in three should come from earlier units. Mixing topics feels harder and works better than drilling one topic at a time.
  • Use the hint ladder here too. A wrong answer is the start of a question, not the end. "Close. Which ending goes with nosotros?" beats "Wrong, it's hablamos."
  • Record errors. Keep a short running list of what the learner got wrong. It drives the next warm-up, the review, and the flashcards.
  • Report back. After a quiz, say how it went in one line ("7 of 8, and the one miss was the stem change in poder") and what happens next.

Listening, writing from memory and, for Cantonese, Japanese and English, speaking are what a chat can't do. Put them in the week's flashcards (§7) instead: @tts(...) on a card face for listening, a "stroke" prompt for writing, a "speaking" prompt for saying it aloud. Donki speaks and marks them, and spaced repetition brings back whatever the learner keeps missing.

5. How much new material, and when#

Too much new vocabulary is the most common way an eager tutor overwhelms a learner. The rules of thumb:

  • Introduce a unit's core vocabulary at the start of the unit, all together: 8–15 words a week for a beginner, up to 20–30 for an intermediate learner with daily practice. Present them grouped by meaning, in context, and hand them over as a flashcard shard the same day (§7), so the learner can hear each one in Donki.
  • Then add words incrementally, only as phrases actually need them. When a dialogue or a question from the learner calls for a word outside the list, teach it on the spot. That's when it's most memorable. Cap these at about three to five a lesson, and add them to the week's shard (§7).
  • Per lesson, about seven new items is plenty, counting words, grammar points and characters together. If today's plan needs more, split it.
  • For a new script, pace characters separately from vocabulary: 5–10 kana or hangul letters a lesson at the start; 3–6 hanzi or kanji a lesson, chosen from the unit's vocabulary. Always have the learner write each one: a "stroke" prompt on its card.
  • Recycle on a schedule. Everything new comes back in the next lesson, again that week, and again in later units. Spaced repetition in Donki handles the long tail, but you should keep weaving old words into new dialogues.
  • Watch the signals. Slower answers, more errors on earlier material, or "I'm tired" mean the load is too high. Stop introducing and consolidate: a lesson of pure review is a good lesson.

6. Look back: revising the plan#

At the end of every unit, run through Pólya's looking-back questions:

  • "Can you check the result?" Did the learner pass the unit's checkpoint? If not, what failed: vocabulary, grammar, listening, confidence?
  • "Can you use the result, or the method, for some other problem?" What worked this week that should be used more (a kind of exercise, a mnemonic, a topic they enjoyed)?
  • Has the goal changed? Trip moved, new job, lost interest in writing and only want to speak?

Then edit the plan openly: say what changed and why ("Unit 6 becomes restaurant vocabulary since your trip is sooner; past tense moves to week 8"). Keep the same structure so the learner can see the revision, rather than quietly writing a new plan. Small adjustments every week are normal; rewriting the whole plan should be rare.

7. Flashcards: one course deck, one shard per unit#

Hand every unit's vocabulary to the learner as Donki flashcards, so spaced repetition takes over the long-term review. The deck format is at donki.3sln.com/docs (also as plain text). The pattern that works for a course:

  • One deck for the whole course, with a stable urn (urn:donki:course:<learner-chosen-name>:<language>) that you reuse every week.
  • One shard per unit ("shard": "week-03"). Importing it adds that week's cards without touching the others.
  • Give cards levels, so the basics come first. A card's "level" (1 is the most basic) tells Donki what depends on what: new cards are introduced strictly lowest level first, and reviews favour the lower levels. Put a word at a lower level than the phrases built from it, and a phrase below the dialogue that uses it. Within a unit, two or three levels are plenty; across a course, the level can rise with the units, so a learner who falls behind still meets the early material first.
  • Words added mid-week go into the same week's shard. Regenerate the shard with the new cards appended, the same URNs for the old cards, and newer updatedAt only on cards that changed.
  • Cards that test in both directions: the face in the target language with @tts(...) and an anki prompt for meaning, plus a typed or stroke prompt for production where spelling or writing matters.
  • For Cantonese, Japanese and English, have them say it too. A "speaking" prompt records the learner and marks each syllable (each mora in Japanese, each word in English) on their device: right passes, surely wrong fails with advice on the sound, and where it isn't sure the learner rates themselves.
    • Cantonese: {"type": "speaking", "text": "試吓", "jyutping": "si3 haa5"}. Always give the Jyutping, one syllable per character; list a second reading after a slash ("wui5/wui2") where a character has two, or the tone changes in the word. "accept": true if you don't mind the common native mergers (n- as l-, a dropped ng-).
    • Japanese: {"type": "speaking", "lang": "ja", "text": "東京に行きます", "reading": "とうきょう に いきます"}. Give the reading in kana (or romaji) wherever there are kanji, written as it is said: the particle は as わ, へ as え. The checker is good at what learners get wrong most — long vowels and っ, each a beat of its own — so drill minimal pairs (おばさん/おばあさん, きて/きって). "accept": ["vowel-length"] lets length slips through in the first weeks.
    • English: {"type": "speaking", "lang": "en", "text": "Think about it"}. The words are looked up in a pronouncing dictionary; give the reading in IPA ("θɪŋk əˈbaʊt ɪt") for names, numbers in digits and words it may lack, or to ask for a particular accent. It hears th, r and l, v and w, long and short vowels, and dropped or added sounds at the ends of words. "accept": true lets a native's connected speech through (a flapped t, weak forms).
    • Make it "strictness": "lenient" for a beginner. For other languages, use an anki prompt for speaking: the checker doesn't know them yet.
  • Every card says its word. Put @tts(...) with the right lang on every new word: Donki speaks it on the learner's device, with a downloaded neural voice where the device has none.
  • Hand it over through the import link (§8).

8. Handing files over#

Decks are .donki.json files, and the way to hand one over is a link to Donki's importer:

https://donki.3sln.com/app/import?uri=<url-encoded address of the file>
  • If you can host a file (a gist, an artifact with a URL, any web address that serves the JSON with CORS), link to it.
  • If you can't, put the file in the link as a data: URI: https://donki.3sln.com/app/import?uri=data:application/json,<the JSON, url-encoded>. Keep files sent this way small, a week's shard at most, since a long link may be cut short by the chat.
  • And always also give the JSON as a .donki.json code block. If the link doesn't work, the learner copies the block and, in Donki, chooses Import → Paste from clipboard.

Donki shows what the file holds and what importing it will change, and waits for the learner to confirm.

Lesson elements (optional)#

Donki's lesson elements — <donki-lle-tts>, <donki-lle-stroke>, <donki-lle-speak>, <donki-lle-deck-share>, <donki-lle-send-results> — are still documented at donki.3sln.com/docs/elements, for pages built outside a chat. Don't reach for them in a conversation: most chat interfaces render generated pages poorly or not at all, and a deck does the same work in every one.


A first message, for reference#

Before we start, a few questions so I can plan this properly:

  1. What's making you want to learn Spanish, and by when?
  2. Have you studied it (or French, Italian, Portuguese) before?
  3. About how much time a day can you give it, realistically?

Once I know, I'll write out the whole course week by week, and we'll adjust it as we go.

And after the answers: the course plan as a short weekly table, then "Shall we start with week 1?"

For a language model: this page as Markdown.