AI owns
- Lesson interpretation
- Vocabulary selection
- Contextual translation
- Visual concept planning
- One illustration per concept
How I moved from an initial AI prototype to a more credible classroom product—through quality failure, model iteration, cost judgement and a deterministic worksheet workflow.
Standalone concept designed to fit a workflow like CoTeach. Not integrated with or endorsed by CoTeach.

I wanted to showcase a focused feature that could fit naturally after lesson creation. A teacher should be able to take the lesson they already have and create a multilingual visual vocabulary resource without re-entering every word.
That led to a deliberate separation: AI interprets the lesson and creates structured educational content; the application protects the worksheet structure.
Place the feature after lesson creation, as a downstream adaptation layer.
Selection, translation, independent images and structured exports worked end to end.
The pictures looked acceptable but did not reliably communicate the vocabulary meaning.
I rejected the route despite its low request cost. Technical completion was not pupil value.
“Would this image help a multilingual Grade 1 pupil understand the word in this lesson?”
I used the smallest model route that met the relevant quality threshold in live testing. Both choices remain replaceable environment variables rather than fixed product assumptions.
The first route was cheap and technically valid, but relevance was unreliable. Gemini produced a lesson-relevant “add” visual showing two groups joining.
The task was constrained structured extraction and translation. The smaller route met the live benchmark at a much lower token cost.

Reads the complete lesson and selects up to eight learner-critical terms.
Up to four image requests run at once and cards populate progressively.
One failed illustration can be retried without discarding seven successful cards.
PDF is print-ready; PowerPoint keeps text, shapes and images editable.
Optional vocabulary review and age-appropriate image constraints.
Replaceable models, request limits and a generation kill switch.