Teach: Your teach skill, but every lesson opens as a poster

[VictorMarri]

Hey Matt, I've been using your teach skill daily and forked it into ensinar ("to teach", in Portuguese). The short version: every lesson now opens as a poster, where a big drawn analogy teaches before the text does, written in the learner's native language. This is lesson 1 of a clusters track it produced, the analogy being a supermarket that grows taller vs wider:

Notice what's NOT there: no wall of text, at most three new terms, and the drawing answers the lesson's question on its own.

I didn't build this to drift away from teach. I built it hoping the best parts can flow back into it.

Your pedagogical skeleton is all still there, intact: the mission anchoring every decision, fluency vs retention, the glossary as official language, learning records. That foundation is excellent. What the fork adds came from pains that surfaced after weeks of daily use:

• Map before lesson 1. The original numbered lessons forever; you never knew how many were left or what "done" meant. Now every lesson says "Lesson 3 of 7", never "of ?".
• Isomorphic analogies only. An analogy is allowed at most one declared breaking point; two or more means it's stretched, and the learner pays three lessons later. The analogy that passes becomes the physical object the figure draws, not a labeled box. My first Docker lesson opens with a locked cake mold: delete the cake, the mold stays. That's why you have 1.7 GB of Postgres images and zero running databases.
• Jargon budget. 3 new terms per lesson, max. Each named in the learner's language first, English label second: the camada de base (base branch), never the reverse.
• The eraser test. Mentally delete every jargon term from the lesson. Does it still teach? If not, it was translation, not teaching.
• Teaching language as a per-track parameter. The track is written entirely in the learner's native language (mine are Portuguese), technical labels stay in English because docs and CLIs live there. For English learners the translation layer simply disappears and the jargon budget still applies.

Same skin, different world: lesson 1 of the Docker track, in Portuguese.

Everything derived from teach stays MIT with full attribution in NOTICE.md; the fork is MIT too.

If you can spare ten minutes, I'd love for you to test it yourself:

git clone https://github.com/VictorMarri/ensinar ~/.claude/skills/ensinar

Then type /ensinar I want to learn <anything> in Claude Code. The skill's internals are written in Portuguese today, but that doesn't matter in practice: Claude reads them fine, and the lessons come out in whatever language the learner speaks, so yours would be English end to end. What I want most from this post is your honest judgment: does this meet the bar you set with teach, and where does it fall short?

To be direct about what I want: I'd love for the language-agnostic parts of this to live in teach itself, and to help build and maintain them there. The map rule, the isomorphism test and the language parameter would drop in cleanly, and I'm ready to shape each one into a focused PR that follows your conventions, one at a time, starting wherever you see the most value. Say the word and the first one lands this week. And whatever you decide, thanks for the excellent foundation.

[VictorMarri]

@mattpocock