An Empathetech community project
Teach yourself a thing. Cite your sources. Help the next person.
A growing collection of personal learning curricula, built by members of our community using Claude Code — designed around things they actually wanted to be able to do.
Empathetech is built on the idea that good software engineers are good humans. This little corner of the community is for what good humans do when they want to learn something new: they study it, build something around it, and share what they figured out. The /teach-me Claude Code skill helps members shape their curiosity into a full curriculum — with full source attribution, honest credit for the AI collaboration, and an emphasis on doing all of this in as ethical a way as we know how.
What folks are teaching themselves
Each course is the work of an individual community member. Each has its own shape, its own voice, its own design — some are interactive SPAs, others might be long-form essays, galleries, or formats we haven't thought of yet. We don't enforce a template. We enforce care.
Three values, in order.
1. Personal curiosity is a worthy reason to build. Every course on this hub started with a community member wanting to learn something specific — not for a grade, not for resale, not for clout. Because it mattered to them. Designing your own curriculum is one of the better ways to learn something, and the artifact you produce can help someone else who shows up curious about the same thing.
2. Be honest about working with AI. Each course is designed by a human, with Claude Code as a collaborative writing and engineering partner. The human does the framing, scope, voice, and design decisions; Claude drafts prose and writes interactive components under direction. We name both — every page, every time. "Designed by [Name] with Claude Code." That phrasing isn't decoration; it's the truth about how these were made, and we think honesty about the collaboration is part of using AI responsibly.
3. Cite your sources. All of them. Every factual claim in any lesson is traceable to a real, linkable source — see the 📚 Sources section at the bottom of any lesson page, and each course's Credits page for the full bibliography. Libraries, fonts, content references, cooking-history attributions — they're all listed, with licenses. When you teach people things, you owe them the ability to verify. We treat sourcing as a first-class requirement, not a bonus.
Contributors
Community members who've designed and contributed a course. The work is theirs; the hub just gives it a home.
Want to build one?
If you're an Empathetech community member with something you want to learn, you can add a course to this hub. Here's the rough shape of it:
- Pick something specific you want to be able to do. Not a topic — an outcome. "Deploy a Lambda that checks this site every day" beats "learn AWS."
- Install Claude Code and the
/teach-meskill, fork this repo, run/teach-mefrom the repo root. The skill will recognize it's inside this hub and help you scaffold a new course as a subdirectory. - Build the course in whatever format fits your topic — a Learn/Pick/Cook SPA (like Brunch Made Real), a long-form book-style site, a notebook-driven walkthrough, a gallery, a worksheet collection. Design follows topic; topic follows curiosity.
- Cite every fact. Credit every source. Name yourself as designer and Claude Code as the collaboration partner.
- Open a pull request. The hub picks up your course card from
portfolio.jsonautomatically.
We're still figuring out exactly how the contribution flow should work in practice — what gets reviewed, what we ask for in a PR, how we keep the bar on attribution high without making the bar feel hostile. Come talk to us in the Empathetech community if you have an idea you want to start building.