A lesson needs fewer pictures than most of us first imagine. One diagram that shows the cycle, one image of the thing being discussed, one short clip where movement explains the idea, and a quiet track for the intro. That is a kit. Everything else is decoration, and decoration is where lessons get slow.
Here is a calm way to build that kit for a course page, a worksheet, or a slide you will show in class.
Decide what each visual must explain
Write the lesson aim in a single line at the top of a notes file. Under it, list the moments that need help: the part students always ask about, the part that is hard to picture, the part that takes too long to describe.
For each moment, write one sentence saying what the visual should make clear. If you cannot write that sentence, the picture will not help. A useful test: could a colleague look at the image and say what it teaches? If not, the idea is still too vague.
Describe the picture in one plain sentence
Good prompts for teaching images are short. Name the subject, the setting, the style, and ask for a plain background. For example: "A glass of water on a windowsill, soft daylight, simple flat illustration, pale background, no text."
That last part matters. Do not ask an image tool to write labels, arrows, or headings. Text inside generated images is often wrong, half-spelled, or placed badly. Add all words later in your slide tool or document, where you can fix them and make them readable at the back of the room.
Keep the set looking related
Students notice when one picture is a photo, the next is a cartoon, and the third looks like a poster. Pick a style before you start and stay with it. If a tool offers custom LoRA styling, a saved style can help keep a whole set consistent without repeating the same long description each time. In NewYouGo this sits beside the image tools, so the same look can carry from one picture to the next.
Small choices go a long way: same light direction, same level of detail, same background tone. The set should feel like it came from one book.
Name files before you generate more
Save each image with a name you will still understand next term. A pattern such as lesson-topic-01-subject.png is enough. Lesson, topic, number, subject. Avoid names like final2 or image. When you have a folder of twenty, clear names are the only thing that saves you.
Keep a small prompt log beside the images. One line per picture: the sentence you used, the model or style, and anything you changed. When a colleague asks how the water glass was made, or when you need a matching image next month, the log answers in seconds.
Match sizes before you print or project
Decide where each image will live. A picture for a printed worksheet needs more pixels than one shown on a screen. Use the upscaler before you print or project, not after, so you are judging the real quality. If a picture will sit on a slide at full width, check it at that size on your own screen first.
Keep a consistent shape across the set where possible. Mixed shapes are fine in a document, but a row of images in a slide looks calmer when they share proportions.
Make the clip from a still
Pick the one image where motion adds understanding: water moving, a door opening, a plant turning toward light. Animate that still into a short, gentle clip. Keep it brief, keep the camera steady, and avoid effects that pull attention away from the idea.
One clip per lesson is usually enough. If two clips fight for attention, the class reads neither.
Add a quiet track last
If you need music for a slide or a short video intro, generate a soft instrumental and keep it low under your voice. Music should signal that the lesson is starting and then step back. If you have to raise your voice over it, it is too loud.
Review, then upload
Before anything goes to the course page or the projector, open every file once. Check that the details are correct. AI images can place a wrong number of parts, a strange hand, or a label-like smudge that looks like writing. You are the last check, not the tool.
Look for the obvious slips too: a missing file, a wrong size, a clip that starts mid-motion, a track that is louder than the speech. Fix them now, while the lesson is still in your head.
Then upload, and keep the folder and the prompt log together. Next time you teach this lesson, the kit is already half built.
Top comments (0)