Generate Weekly Interactive Safety Courses for Kids with Claude

5 comments

Apps it uses

I built a weekly interactive training-course generator for my 10-year-old son and eventually landed on a much simpler final version than where I started.

I wanted a way to teach him practical safety and life skills, starting with how to swim confidently and what to do if he gets into trouble in the water. I needed something more engaging than simply talking at him, but writing a polished, interactive lesson from scratch every week was not sustainable.

First, Claude and I designed a single interactive HTML course as a proof of concept. It was a swim-safety course with a branded look, including a custom color palette, fonts, and a progress tracker styled like pool lanes. The course was divided into modules: a welcome screen, a comfort-and-basics lesson, a step-by-step skills walkthrough, a safety checklist, a “what to do if something goes wrong” module, a quiz, and a certificate at the end. The “what to do if something goes wrong” module was the most important part.

Once the course worked, I wanted to reuse the same format for a new topic every week. Claude first built a version that called the Claude API live from inside the page to generate new content on demand. However, it only worked while the page stayed open inside Claude.ai, and occasionally a section failed to generate cleanly.

We pivoted to a simpler approach. Instead of using a live tool, Claude documented the entire course format—including the visual identity, module structure, tone, and content rules—as a standing “brief” document. Each week, I open Claude Cowork, paste in the brief and that week’s topic—bike safety, fire safety, or whatever is next—and Cowork returns a finished, fully self-contained HTML file. There is no app to babysit and no live API call; I can simply open the file and hand it to my son.

The result is a repeatable, no-maintenance weekly workflow for turning any topic into a polished interactive lesson for my kid.

Step-by-step

  1. I identified a need for more engaging lessons on practical safety and life skills, starting with swimming and water safety.
  2. I worked with Claude to create a proof-of-concept interactive HTML swim-safety course.
  3. I structured the course into a welcome screen, comfort-and-basics lesson, skills walkthrough, safety checklist, emergency-response module, quiz, and certificate.
  4. I tested a live-generation version that called the Claude API from inside the page, then noted that it only worked while open inside Claude.ai and that sections sometimes failed to generate cleanly.
  5. I had Claude document the course’s visual identity, module structure, tone, and content rules in a reusable brief.
  6. Each week, I open Claude Cowork, provide the brief and a new topic, and receive a finished, self-contained HTML course file.
  7. I open the file and give the interactive lesson to my son without maintaining an app or making live API calls.

5 comments

Have a question about this workflow, or a way to improve it?

Log in to comment Create a free account
Guillermo Gómez

Running this weekly with the same shape every time is what will keep him turning up, and that's harder than it sounds. The one thing I'd move is the emergency module. You call it the part that matters and it sits fifth, behind the comfortable material, and I've lost good sequences by placing them after the point where the viewer had already decided what the thing was about. A quiz measures recognition anyway, and what you want to know is what he does in the water with his pulse at 160. A week later, what did he actually remember?

Tony Ojeda

This seems like a fun and engaging way for kids to learn important life skills. The great thing is that you can customize it not only for what you want the kid to learn but also for what their interests are (e.g. Pokemon teach self motivation, Power Rangers teach conflict resolution, etc.). I'm going to look into creating something similar for my daughter. Thanks so much for sharing!

Brooke Benson Pro The Rundown team

amazing - building this for your 10-year-old and making the "what to do if something goes wrong" module the centerpiece is wonderful. Which part of the brief took the most rewriting before a brand new topic came back looking like the same course?

Billy Howell The Rundown team

This is a pretty cool way to think about this.

Posting guidelines