tutorial-creator: turn Claude Code sessions and your own project files into interactive lessons. Learn from the code you and Claude are actually building. Not Hello World.
TL;DR. A skill that takes code that you wrote (or worked with an AI to generate) and produces an annotated tutorial version of it: vocabulary table, pre-test, line by
line walkthrough, common mistakes, post-test. Tracks what you've learned
across tutorials, fills in learning gaps, and helps you learn as you code.
Repo: https://github.com/Terryc21/tutorial-creator (open source, Apache 2.0)
The problem it solves
AI is generating code faster than most of us can read it. You develop
features, the codebase grows, and you can read the words but you don't really know what's happening when it runs.
Traditional tutorials don't help. They teach syntax with Hello World
and let x = 5. Toy examples build toy fluency. Real projects have async workflows, state management, edge cases, conditional rendering, and accumulated design decisions nobody walked you through.
Early on I realized that if Claude Code was not accessible, I would be lost in my own coding. I wanted to be able to stop, look at a file from my own project, and have someone walk me through it line by line, including the parts where I'd say "I have no idea why that's there." Without leaving my project to study unrelated tutorials. That's the genesis of tutorial-creator skill.
What you get when you run it
After a session, if you want to learn from the coding that you and Claude Code just generated, launch tutorial-creator. It produces:
- A vocabulary table of new terms from that file
- A pre-test (what do you already know?)
- The file, annotated line by line
- A "common mistakes" section with real failure modes
- A post-test
- A check for prerequisites. If the lesson assumes things you haven't covered, it suggests bridge tutorials first
It also remembers. Vocabulary carries across sessions. Terms you keep
getting wrong show up in a gap view. Terms you've nailed three times in a row get marked mastered. You can run review sessions any time.
Example of a Lesson generated by tutorial-creator.
Three ways to use it
- Write a tutorial for yourself. Six different starting points, from "give me the next concept in my learning sequence" to "I'm confused about this, where do I start?"
- Write a tutorial for an audience. Same engine, six venue templates (Reddit post, blog, Medium article, book chapter, Apple Developer style article, repo doc), each with a different voice.
- Just manage your vocabulary. Add terms outside a lesson, review, see your gaps.
Languages
Swift and SwiftUI are the deepest; that's what I built it on (for my app Stuffolio). Also works with TypeScript / React, Python / Django, and Rust. Custom languages via a simple yaml config.
Who it's for
- People learning coding while using Claude Code to write an app
- Developers who want to actually understand the code they (or their AI) is shipping
- People learning a new framework in an existing codebase
- Anyone whose fluency is falling behind their output
Who it's not for
- People hoping AI will replace reading code. This is the opposite. It makes reading more deliberate.
- Pure beginners with no project yet. You need real source files to point it at. Start developing an app, then come back when you have a small codebase to learn FROM.
Other Coffee & Code skills
If tutorial-creator is useful, five sibling skills linked from the README:
- prompter : rewrites your Claude Code prompts for clarity and missing context before they run. Catches the ambiguity you didn't see. Sharpens your prompting by seeing how Claude Code would rewrite your prompts for better understanding.
- bug-echo: after you fix a bug, finds other places in your codebase with the same pattern. Stops the "fixed it once, missed three others" cycle.
- unforget Gathers, organizes and prioritizes deferred actions that are scattered across your codebase in differed lists, memories, TODOs, markdown files and in dusty corners that you thought you would remember... but forgot.
- workflow-audit: traces SwiftUI user journeys end to end, detects dead ends, broken back navigation, missing empty states, and dismiss traps.
- radar-suite: multi-domain code audit that grades your codebase A through F across UI paths, data models, release readiness, and more. Tells you what to fix before shipping.
Looking for
Honest feedback. I've used this on one project in one language. Genuinely curious whether the loop works for other people or whether I've built something only useful for me. Specific questions I'd love thoughts on are in the GitHub Discussion linked from the release.