after the Young Lady's Illustrated Primer · The Diamond Age

Primer

A learning system that knows where you are, and keeps getting sharper the more you use it.

Schooling ends. An education isn't supposed to.

PRIMER
why now

The floor moved.

For a long time, knowing things was the differentiator.

Anything lookup-shaped is now free. An assistant hands it over in seconds.

What's left is judgment: knowing which question to ask, noticing when an answer is wrong, and having the thing in your head when it counts.

The version of it that started this:

“Tens of thousands of strong engineers are on the market. If I were too — what makes me distinguishable?”

Staying distinguishable is the job now, whatever your field. That means choosing what you learn, instead of letting circumstance choose for you.

PRIMER
the problem

But how we keep up is broken.

Demand-driven

You only learn what work or circumstance puts in front of you. Everything else stays a blind spot until it matters.

Generic and stale

Tutorials are written for everyone, so they fit no one. Happy-path demos, and a good share of them teach what the field has already moved past.

It doesn't stick

Read the article, feel smart, retain almost nothing. Fluent prose feels like learning. It isn't.

A search engine, a chatbot, and a folder of bookmarks don't fix any of this. They make progress easy to feel and hard to accumulate.

PRIMER
the north star

The book you wish you'd had.

In The Diamond Age, the Primer is a book that notices who's reading it and reshapes itself to fit them. It teaches through story and back-and-forth, always one step past what the reader can already do.

“The magic was never the nanotech. It's that the Primer is a relationship, not a syllabus — patient, genuinely curious about its reader, and built around exactly one person.”


Stephenson had to invent the nanotech. The rest of it — a tutor that knows where you are, adjusts to how you think, and is still there next year — turns out to be buildable without it.

Prompted by one field that keeps moving. Driven by everything else: how mountains get made, what counterpoint is, why the cat does that.

PRIMER
what it is

A knowledgeable friend who remembers every conversation.

A Claude Code skill. You type /primer <topic>; it runs a calibrated lesson and writes down what it learned about you. The rules it never breaks:

01

Peer, not lecturer

Talks to you like a peer, at whatever directness you ask for. No cheerleading. Disagrees when you're wrong, and holds that position under pushback.

02

Struggle > fluent answers

Makes you predict or derive before it explains. You build the idea in your own head. That's the part that sticks.

03

Current and grounded

Every technical claim tagged verified via docs or from-training. Never teaches a take the field has moved past.

Calibrated to you, and sharper the more you use it.

PRIMER
how it works · 1 of 3 — the shape

Public engine, private you.

The engine (public)

  • The skill + the lesson protocols
  • Source canon and stale-list
  • Profile templates
  • Zero personal data. Clone it, improve it
⇄ git-synced
across
your machines

Your instance (private)

  • Your profile and goals
  • Depth markers + evidence
  • Every lesson you've done
  • As rich as you like, and it never leaves

The split is what lets your data be honest about what you know and what you care about without any of it touching a public repo. The engine never goes digging through your own files.

PRIMER
how it works · 2 of 3 — a lesson

Every session runs the same loop.

Elicitwhat's your model now?
▸
Probepredict before I explain
▸
Diagnosewhere's the real edge?
▸
Deepenworked → faded → free
▸
Recapyou summarize; prompts out

It opens by asking what you already believe, then probes with a real failure scenario and waits. No auto-complete. It teaches only at your edge: skip what you know, slow down where you're fuzzy.

It closes by handing you the pen. You put the takeaway in your own words, which is where the encoding happens, and the session emits retrieval prompts for spaced review later.

PRIMER
how it works · 3 of 3 — it learns you

It tracks what it has seen vs. what it assumed.

Every topic carries a depth marker with confidence and evidence, never a certain-looking guess:

async event loop confidence: low
↳ intake probe: reasoned well, but the
   blocking-freezes-the-loop invariant isn't locked


outbox pattern confidence: high
↳ derived it live, sketched the schema

Confidence moves both ways, and the loop doesn't get to grade itself:

  • ↑ You correct its mistake → the evidence it weights most heavily.
  • ↓ You blank on a cold-recall prompt → confidence drops, topic requeues.
  • ⏳ Untouched too long → it decays toward needs-review. You lose knowledge you don't retrieve.

So the picture of you gets truer with use. It is allowed to get worse.

PRIMER
why not just ask the chatbot

Because a fluent answer feels like progress.

Ask a chatbot to “explain X” and you get a clean paragraph. You nod. You feel sharper. You retain almost none of it, because nothing was built in your head.

Primer is built against that:

  • Makes you produce the idea before it confirms it.
  • Cold-recall and spaced review. Anki-importable prompts from every lesson.
  • Honest about its own confidence. It flags guesses instead of faking authority.
  • Currency as a rule. It searches for current sources every lesson, with a stale-list as the guardrail. event-source everything Alpine by default

The goal isn't a good answer in the moment. It's getting good at the thing, and better at learning in general.

PRIMER
what you walk away with

Lessons that outlast the session.

A durable artifact

Every session writes a lesson file: TL;DR invariants, worked examples, diagrams, an honest tradeoff table, and the exact questions you asked.

Retrieval prompts

Atomic Q/A pairs from every lesson, built to test understanding. Review them in Primer or in your own SRS.

A truer model of you

Markers, evidence, open threads, next-lesson suggestions. The map sharpens, so the next lesson starts where you are.

It's all yours: plain markdown in your own private repo. Nothing locked inside a product.

PRIMER
a 60-second glimpse · one domain of many

From a guess to a calibrated start.

primer › you self-rate async as “can build with it.”

probe ›
“50 requests hit an async def handler that makes one blocking call. What happens — and would sync Falcon do better or worse?”

you › “…they'd fan out across workers? Though — if it's blocking, maybe the loop can't switch…”

diagnose › right instinct, invariant not locked.
→ marker set low, lesson built at that edge.

No quiz, no generic curriculum. One real scenario shows it the gap between what you said and what you can do.

Then it builds the lesson on that edge, with sources already verified against current docs, ready when you are.

(A real exchange from setting this up. The subject happens to be Python; it works the same on plate tectonics.)

PRIMER
try it

A tutor built around one person.

Where you are, what you're reaching for, and the way you like to be talked to. The picture gets truer every time you show up.

$ git clone … && ./tools/install.sh
› /primer init # one-time intake, then go
› /primer <topic>

Open core, private data, any subject: geology, astronomy, a new language, game design, music theory, distributed systems.

PRIMER