ClaudeTemplate, 3 blanks to fill

You are a study coach who writes flashcards for spaced repetition apps such as Anki. <context> Subject and level: [SUBJECT] Exam or goal: [GOAL] My notes, slides or textbook section: [NOTES] </context> <instructions> 1. Pick out the facts, terms, processes and cause-and-effect links in the notes that an exam on this material would test. 2. Write one card per idea. Each front asks one question with one correct answer; split anything that needs a list into several cards. 3. Mix card types: definitions, "why" questions, steps in a process (one step per card), and cloze deletions for key sentences, written as {{c1::hidden text}}. 4. Phrase fronts so they cannot be answered by recognising the wording alone; ask from a different angle than the notes use. 5. Keep backs short: the answer first, then at most one line of explanation or an example. 6. If the notes are unclear or look wrong on a point, add it to a list called Check with teacher instead of making a card. </instructions> <constraints> - Use only what is in my notes. Do not add facts from outside them. - No card front longer than 20 words. - No yes or no questions. </constraints> <output_format> First, the basic cards as tab-separated lines (front, a tab, back), one card per line, no header, ready to import. Then the cloze cards in a separate block, one per line. Then the Check with teacher list. </output_format>

The words in brackets are the parts you replace with your own details.

What each part of the prompt does

One idea per card
A card that asks for five things gets marked wrong for one missing item, and you never learn which part you forgot. Splitting lists makes each review precise, which is what spaced repetition relies on.
Rephrased fronts
When a card repeats your notes word for word, you learn to recognise the sentence, not the idea. Rule 4 asks for a fresh angle, so recall still works when the exam phrases it differently.
Cloze syntax
{{c1::hidden text}} is the format Anki uses for fill-in-the-blank cards. Keeping cloze cards in their own block lets you import them with the Cloze note type and the rest as Basic.
Check with teacher
Notes taken at speed contain mistakes. Collecting doubtful points in a list, instead of turning them into cards, keeps an error from being drilled into memory for weeks.

Variations to try

Same idea, one thing changed.

  • Language vocabulary

    You are a study coach who writes flashcards for spaced repetition apps such as Anki. <context> Subject and level: [SUBJECT] Exam or goal: [GOAL] My notes, slides or textbook section: [NOTES] </context> <instructions> 1. Pick out the facts, terms, processes and cause-and-effect links in the notes that an exam on this material would test. 2. Write one card per idea. Each front asks one question with one correct answer; split anything that needs a list into several cards. 3. For each word or phrase, write a card from my language to the target language and a reverse card, with one short example sentence on the back. Make cloze cards from the example sentences, written as {{c1::hidden text}}. 4. Phrase fronts so they cannot be answered by recognising the wording alone; ask from a different angle than the notes use. 5. Keep backs short: the answer first, then at most one line of explanation or an example. 6. If the notes are unclear or look wrong on a point, add it to a list called Check with teacher instead of making a card. </instructions> <constraints> - Use only what is in my notes. Do not add facts from outside them. - No card front longer than 20 words. - No yes or no questions. </constraints> <output_format> First, the basic cards as tab-separated lines (front, a tab, back), one card per line, no header, ready to import. Then the cloze cards in a separate block, one per line. Then the Check with teacher list. </output_format>

  • Paper self-test

    You are a study coach who writes flashcards for spaced repetition apps such as Anki. <context> Subject and level: [SUBJECT] Exam or goal: [GOAL] My notes, slides or textbook section: [NOTES] </context> <instructions> 1. Pick out the facts, terms, processes and cause-and-effect links in the notes that an exam on this material would test. 2. Write one card per idea. Each front asks one question with one correct answer; split anything that needs a list into several cards. 3. Mix card types: definitions, "why" questions, steps in a process (one step per card), and cloze deletions for key sentences, written as {{c1::hidden text}}. 4. Phrase fronts so they cannot be answered by recognising the wording alone; ask from a different angle than the notes use. 5. Keep backs short: the answer first, then at most one line of explanation or an example. 6. If the notes are unclear or look wrong on a point, add it to a list called Check with teacher instead of making a card. </instructions> <constraints> - Use only what is in my notes. Do not add facts from outside them. - No card front longer than 20 words. - No yes or no questions. </constraints> <output_format> First, a numbered list of questions only. Then an answer list with the same numbers, so I can cover the answers and test myself on paper. Then the Check with teacher list. </output_format>

If the result isn't right

  • Run one lecture or chapter at a time; decks of 20 to 40 cards per run are small enough to read through for quality before importing.
  • In Anki, choose File, then Import, set the field separator to Tab and the note type to Basic; repeat for the cloze block with the Cloze type.
  • Delete any card you answer without effort on the first review; easy cards eat the daily review time that hard ones need.