Turning the Mistakes Claude Corrects into Anki Cards: My HTML Card Template for English Corrections

This post contains a referral link.

Using AI like Gemini and ChatGPT for English study has become normal. It’s really convenient, but AI is advancing much faster than it feels, and I find there’s more and more to learn.

When you chat with AI, the things you asked long ago just scroll away, right? Don’t you ever think, “I wish it remembered our earlier conversation,” or, when you ask the same thing again, “Haven’t I asked this before?”

Talking with AI is really convenient, but for English study, reviewing old mistakes and corrections means scrolling way back through past conversations or copying and pasting them somewhere to keep. It’s unbeatable for asking on the spot, but I felt it wasn’t very efficient for review.

I’d always thought it would be the best if the information Claude (Claude Code) gave me in these conversations, like the points I often get wrong and serious errors in my English, could slide straight into Anki cards, so I could flip through cards of nothing but my weak points.

So I decided that every time Claude corrected my English in VS Code, I’d have it organize what to fix, example sentences, other expressions and related words, and turn them into cards.

And yes, it can do it. Once you set the rules, it just keeps making them on its own.

But when I started making cards, honestly, Anki’s default cards are a bit bland. With the default settings, it’s just plain text, so the information isn’t organized. When I’m reviewing, it’s hard to tell at a glance, “Wait, why did I get this wrong?” or “What situation was I in when I made this mistake?”

I’m sure some people are happy with the default, but I’m the type who cares about this. I think contrast in color, font weight and size makes things easier for the brain to take in, and more efficient.

So I made a card deck just for English corrections, where Claude’s correction results go straight in, and designed it thoroughly in HTML. Oh, and of course, I had Claude do that too.

Sponsored links

Two systems that turn mistakes straight into cards

Having Claude correct my English when I send messages to friends overseas or write something in English has become a daily habit. The English I use with friends is exactly the everyday conversation I’m aiming for, so I want to fix serious errors in it before they become habits that are hard to break. I want to understand them.

Copying and pasting each mistake from these conversations by hand would be a hassle. There’s no fixed rule for when, but the moment I think, “Oh, let me get this corrected,” I save everything instead of letting it slip away.

But if I saved every single mistake, there would be a huge number of them ( ゚д゚)

So that my confidence doesn’t get torn to shreds, I split the rules for saving errors into two, depending on the type of mistake.

① Mistakes that change the meaning or don’t get across become cards on the spot

Keep it simple. You don’t need complicated rules. For example, something like “under such-and-such rule, when this be-verb becomes so-and-so…”

…rules like that just aren’t for me. Let’s keep it simple! So:

“Mistakes a native speaker would have to stop and think, ‘Huh?’ to understand”

“Words and expressions that change the meaning and don’t get across”

For these mistakes, instead of waiting until I repeat them a few times, Claude suggests making a card on the spot, even the first time, and the card is made once I say OK.

Here are a few that were actually turned into cards recently:

Original (mistake)Corrected
My daughters were kimono there.My daughters wore kimono there.
We had a lot of fun with there friends.We had a lot of fun with their friends.
I’m going to explore town by my foot.I’m going to explore town on foot.
How have you been up to?What have you been up to? / How have you been?

I also keep the reason for each mistake in the Point field, like “the past tense of wear (to put on clothes) is wore; were is a be-verb” or “there (a place) and their (possessive) sound the same, so I mix them up when writing.” That way, when I look back later, I remember right away: “Oh, that’s why I got it wrong.”

② Spelling mistakes and minor expressions become cards once they add up

On the other hand, making a card the first time for every minor mistake, like a typo, would never end. So I record grammar and expression mistakes in an Obsidian note called “Weak patterns,” and spelling mistakes in a separate note called “Minor mistakes box,” each with a count.

The spelling rule is simple: when the same spelling mistake happens three times, an Anki card is created automatically. In fact, looking back at my records, “corster” (correctly, coaster) became an Anki card right when I made that mistake for the third time.

MistakeCorrectTimesAnki card
corstercoaster3✅ Card made
espesiallyespecially1–
untilluntil1–
vegitablevegetable1–
reletivesrelatives1–

It’s a quiet moment of realizing, “Oh, so this is where I’m weak.” By the way, on top of the normal Anki card, these are set up to automatically add a typing practice card as Card 2.

Anki can even make typing cards. That surprised me.

Minor grammar and expression mistakes follow the same idea: the number of repeats decides the priority. So far, my most frequent mistakes are articles (7 times), missing prepositions (5 times) and tenses (4 times).

Serious mistakes become cards right away, and minor ones become cards once they repeat enough, so it feels like only my real weak points stay in Anki.

Just by sending my English, my weak points get organized into notes automatically. It’s amazing.

How I write it for Obsidian_to_Anki (final version)

In Obsidian, I write the notes in this format:

START
English correction card
Front: Original sentence
Back: Corrected sentence (color only the fixed part with <span style="color:#1D9E75;font-weight:500;">fixed part</span>)
Point: Explanation (number multiple mistakes ①②③)
Example: Example sentence 1<br>Example sentence 2
Alternatives: Alternative 1<br>Alternative 2
Words: <b>word</b><br>① meaning 1<br>② meaning 2
Spelling: <span style="color:#E24B4A;text-decoration:line-through;">misspelling</span> → <span style="color:#1D9E75;font-weight:500;">correct spelling</span> <span style="font-size:11px;background:#FCEBEB;color:#A32D2D;padding:1px 6px;border-radius:99px;">2nd time</span>
Level: High
END

This is the format I use when I want to create an Anki card. Anything written this way becomes an Anki card.

With the Obsidian_to_Anki plugin (I wrote about the sync setup in a separate post), I just press the sync button in Obsidian and the cards are created in Anki.

Until now, I had been making all of these by copying and typing by hand. I enjoyed it, so it wasn’t painful, but now that AI has taken over, I can’t help wondering what all that time was for…

Field design for the card deck (final version)

FieldContents
FrontThe original sentence
BackThe corrected sentence (only the fixed parts in green)
PointAn explanation when the meaning came out different. Multiple mistakes are numbered ①②③
ExampleExample sentences
AlternativesOther expressions at B2/C1 level
WordsWords, their multiple meanings and collocations (such as prepositions often used with them)
SpellingSpelling mistakes (with a count badge)
LevelImportance (high, medium, low)

With eight fields, you might think at first, “Isn’t that too many?” But I didn’t make all eight from the start. I added one at a time whenever something bugged me during review, and this is where it ended up.

By the way, after copying words into these fields by hand for eight years, it finally got too much, so now I have a setup where Claude Code does it for me.

I Copied and Pasted Anki Cards by Hand for 8 Years, So I Let Claude Code Do It

Oh, and if you want audio, just add a field and ask AI, and it will add the audio too.

From here on, it’s about how I actually turned this system into cards: the HTML design.

How I define importance

  • High: the meaning doesn’t get across, or it sounds unnatural to native speakers
  • Medium: it gets across but sounds unnatural
  • Low: minor mistakes

Splitting importance into three levels made my review priorities clear at a glance. When everything was treated the same, I used to wonder every time which ones to review first.

Design points

These are small details, but here are the points I cared about.

  • Keep it consistent with the labels BEFORE/AFTER/POINT/EXAMPLE/ALTERNATIVES/WORDS/SPELLING
  • Color only the fixed parts green (not the whole sentence. At first I tried making the whole sentence green, but it actually became harder to see what was fixed, so I went back to pinpointing (;´Д`A)
  • Mark mistakes with a red wavy underline
  • Use a compact layout that needs little scrolling, even on a phone
  • Show expressions and words on separate lines
  • List multiple meanings for each word (after checking they’re accurate)
  • Place the importance badge quietly in the bottom right

So the layout doesn’t break even with long sentences or several mistakes, I numbered each mistake ①②③. BEFORE/AFTER color only the mistakes, so even long sentences are clear at a glance. There are dividers between sections, so you won’t get lost while scrolling.

Why I put collocations in the Words field

I don’t just put single words in; I put them in together with their collocations (the prepositions and verbs they’re often used with).

Take the word daunted. Even if you know the meaning, it suddenly sounds unnatural with any preposition other than daunted by. Excited is fine with about, but sounds off with in or by. If I only memorized the word, I still got stuck on prepositions when actually using it, so I decided to learn whole collocations.

<b>daunted</b><br>
① intimidated, discouraged<br>
Collocation: be daunted <b>by</b> ~ (to be intimidated by ~)<br>
⚠️ Note: don’t use at or of instead of by

After realizing that memorizing words and collocations separately led me to make the same preposition mistakes when it mattered, I started always writing them together in the Words field.

The SPELLING field

Only the spelling mistakes have a yellowish background, to set them apart from the other sections. It shows the change from the wrong spelling (red, crossed out) to the right one (green), and second and third mistakes get a red badge.

The main aim of this field is to make me notice when I keep repeating the same spelling mistake. I keep the count of spelling mistakes in one place, in the Obsidian note that collects my weak patterns, and every time I get a correction, that note is checked for “which time is this?” before the badge is added. Just seeing the count works surprisingly well.

HTML templates for Anki (to copy)

Based on the field design above, here are the exact HTML templates I paste into Anki under “Manage Note Types” → Cards → Front Template / Back Template. Copy and paste them, change only the field names to match your setup, and you can make cards that look the same.

Front template

<div style="font-family: sans-serif; padding: 20px 22px;">
  <p style="font-size: 16px; color: #333; margin: 0 0 10px; line-height: 1.6;">{{Front}}</p>
  <div style="display: inline-flex; align-items: center; gap: 6px; background: #f5f5f5; border-radius: 99px; padding: 3px 10px;">
    <span style="display: inline-block; width: 6px; height: 6px; border-radius: 50%; background: #E24B4A;"></span>
    <span style="font-size: 12px; color: #888;">What sounds unnatural?</span>
  </div>
</div>

Back template

<div style="font-family: sans-serif;">

  <div style="padding: 20px 22px 16px;">
    <p style="font-size: 11px; color: #aaa; margin: 0 0 6px; letter-spacing: 0.06em;">BEFORE</p>
    <p style="font-size: 15px; color: #333; margin: 0; line-height: 1.6;">{{Front}}</p>
  </div>

  <div style="height: 0.5px; background: #eee; margin: 0 22px;"></div>

  <div style="padding: 16px 22px;">
    <p style="font-size: 11px; color: #1D9E75; margin: 0 0 6px; letter-spacing: 0.06em; font-weight: 500;">AFTER</p>
    <p style="font-size: 15px; color: #333; margin: 0; line-height: 1.6;">{{Back}}</p>
  </div>

  <div style="background: #f9f9f9; padding: 16px 22px;">
    <p style="font-size: 11px; color: #aaa; margin: 0 0 6px; letter-spacing: 0.06em;">POINT</p>
    <p style="font-size: 14px; color: #333; margin: 0 0 12px; line-height: 1.6;">{{Point}}</p>
    {{#Example}}
    <div style="border-left: 2px solid #1D9E75; padding-left: 12px; border-radius: 0;">
      <p style="font-size: 11px; color: #aaa; margin: 0 0 4px; letter-spacing: 0.06em;">EXAMPLE</p>
      <p style="font-size: 13px; color: #666; margin: 0; line-height: 1.7;">{{Example}}</p>
    </div>
    {{/Example}}
  </div>

  {{#Alternatives}}
  <div style="height: 0.5px; background: #eee;"></div>
  <div style="padding: 14px 22px;">
    <p style="font-size: 11px; color: #aaa; margin: 0 0 8px; letter-spacing: 0.06em;">ALTERNATIVES</p>
    <p style="font-size: 13px; color: #333; margin: 0; line-height: 1.9;">{{Alternatives}}</p>
  </div>
  {{/Alternatives}}

  {{#Words}}
  <div style="height: 0.5px; background: #eee;"></div>
  <div style="padding: 14px 22px;">
    <p style="font-size: 11px; color: #aaa; margin: 0 0 8px; letter-spacing: 0.06em;">WORDS</p>
    <p style="font-size: 13px; color: #333; margin: 0; line-height: 1.9;">{{Words}}</p>
  </div>
  {{/Words}}

  {{#Spelling}}
  <div style="height: 0.5px; background: #eee;"></div>
  <div style="padding: 14px 22px; background: #FFFBF0;">
    <p style="font-size: 11px; color: #B8860B; margin: 0 0 8px; letter-spacing: 0.06em; font-weight: 500;">SPELLING</p>
    <p style="font-size: 13px; color: #333; margin: 0; line-height: 1.9;">{{Spelling}}</p>
  </div>
  {{/Spelling}}

  <div style="height: 0.5px; background: #eee;"></div>
  <div style="padding: 12px 22px; display: flex; align-items: center; justify-content: space-between;">
    {{#Level}}
    <span style="font-size: 11px; background: #FCEBEB; color: #A32D2D; padding: 3px 10px; border-radius: 99px; font-weight: 500;">Importance: {{Level}}</span>
    {{/Level}}
  </div>

</div>

What the finished cards look like

The front is simple: just the original sentence with a red badge asking “What sounds unnatural?” The back is arranged in this order: BEFORE → AFTER → POINT/EXAMPLE → ALTERNATIVES → WORDS → SPELLING → importance.

This is in preview mode, but here’s the front of the card. (The screenshots are from my own Japanese setup, so the badge and explanations are in Japanese.)

Front of the English correction card in Anki preview, with the original sentence and a red badge

And here’s the back.

Back of the English correction card, with the BEFORE, AFTER, POINT and other sections

Since the design doesn’t break even with long sentences or several mistakes, the biggest change is that every time I review, I can see instantly why I got it wrong. Before, even when I looked at the back, I’d spend time thinking, “Wait, what was different here?” Losing that time quietly makes a big difference.

Thoughts

Honestly, at first I didn’t plan to go this far. Oh, and the first version only had about three fields. But as I tried to get rid of the frustration of not knowing why I got something wrong, I naturally ended up building it out this much.

Color coding, badges, dividers: they’re all small touches, but together they change the review experience. Fellow learners, if Anki’s default cards leave you feeling a little unsatisfied, try starting by adding one field. I’d be happy if this helps anyone making English correction cards like I do.

Once your fields grow like this, the next problem is that the contents of your deck gradually turn into chaos. I had Claude Code sort that out too, so if you’re curious, take a look at this post.

🃏 I’ve also put all my Anki posts together on one page, sorted by what you need: getting started, settings, keeping it up, automation, audio and troubleshooting.

NO IMAGE

Referral link: if you sign up through it, I may receive free lesson minutes.

✍️ Do the mistakes you fixed in writing show up when you speak?

You can fix writing mistakes through corrections, but the same mistakes tend to come out when you speak. Talking with a native tutor helps you notice the phrases that have become habits. With Cambly, you can start a lesson any time, 24 hours a day, without booking. Through my referral link, you get 10 extra minutes when you buy a trial. I’ve been taking lessons on Cambly since July 2021.

Try Cambly with my referral link →

The referral program isn’t available in every region.

English expressions I learned (B2–C1)

I’m aiming for Eiken Grade 1, so I had AI pick out some useful phrases from this topic.

① at a glance (immediately, with just a quick look)

The priority is clear at a glance thanks to the color coding.

This one sums up exactly what I was going for with the design.

② recurring (happening again and again)

The badge highlights recurring spelling mistakes.

It fits the SPELLING field perfectly.

③ clutter (a messy collection of things)

I wanted to avoid visual clutter on mobile.

A perfect word for why I aimed for a compact layout.

Reference: Anki Manual (Card Templates)

☕ Enjoyed this post?

I'm a Japanese blogger who spent 8 years relearning English from scratch.
If this post helped you, a coffee would mean a lot — thank you for reading!

Leave a Reply

Your email address will not be published. Required fields are marked *

ABOUT US
Suitman
An office worker in Japan who has worked in three fields: education, manufacturing and sales. I started learning English at 35 and, after 8 years of keeping at it, passed Eiken Grade Pre-1. VERSANT score: 59. I write about work tips, Excel, AI, English and cameras, all based on my own experience.