Understand any dense paper
deeply enough to explain it
Drop in the paper. Instead of summarizing it, Ritsu does what a good advisor does — shows what it assumed, rebuilds the step it skipped, and asks where the claim breaks — until you can explain it yourself.
It was never written for you
You're not failing the paper. It was written for someone else.
A paper isn't trying to teach you. It's trying to survive peer review — and those produce very different documents.
The methods section is compressed because the reviewer already knows the method. The notation goes unexplained because the reviewer already knows the notation. The step between equation 4 and equation 5 is missing because, to the reviewer, it's obvious.
You are not the reviewer. You've read it three times and still couldn't say, out loud, what they actually did or why it works. That isn't a failure of your intelligence — it's the document working exactly as designed, on someone it was never written for. A paper is written to be defended, not to be understood.
There's only one way in: stop trying to read it. Start interrogating it.
The workflow
A good advisor doesn't summarize the paper. They interrogate it.
01 · Drop in the PDF
Drop in the PDF
arXiv PDF, a journal PDF, a scan. Not the link — the file. Ritsu keeps the equations as math and shows every figure alongside the text.
/prereq — what it assumed you'd read
Almost every “this paper is impenetrable” moment is an unstated dependency — it assumes you've read the one it's answering. Ritsu names it, in learning order, and the paper goes from impossible to merely hard.
/derive — the step between equation 4 and 5
The step is missing because the reviewer didn't need it. You do. Ritsu rebuilds it — then hands you the pivotal line to produce yourself, because that's the one you'll need in a viva.
/counter-example — where the claim breaks
You don't understand a result by restating it. You understand it by finding its edge — the case where it fails, the assumption carrying all the weight. Ritsu makes “what if n isn't large?” one word.
/askme — say the contribution back
The real test: explain what this paper contributes, in one paragraph, in your own words. Ritsu tells you where your explanation broke — the way your advisor would.
Keep it past the forgetting curve
One click puts each concept on a spaced-review schedule, so the paper you cracked today is still yours at your next lab meeting.
Pedagogy, packaged
Every command packs a proven learning method.
Take one idea from the paper. Six commands take it from “I followed the words” to “I could defend it” — each one asking more of you than the last.
Understand
The core idea first, then the layers — built from the paper you just dropped in.
Recall
Retrieval practice: the most proven way to make it stick. Pull it back out, cold.
Drill
The parts that have to be automatic, turned into cards you'll actually run.
Explain back
The Feynman test. Say it in your own words — that's where the gaps show.
Apply
A real problem on the real concept. Knowing it and using it aren't the same.
Create
Write it out in full. The highest bar there is: if you can write it, it's yours.
The two moves off the ladder — and no chat box offers “show me where this breaks” as a first-class move, because nobody thinks to type it. Ritsu makes it one word.
That's Bloom's taxonomy, climbed one command at a time. And the science isn't a slogan — it's a flag on the command:
/quiz --bloom="auto"
40+ commands, all built like this.
Knowledge Map
You always know exactly where you stand.
A paper gives you no way to check whether you got it — until a lab meeting does, in public. Ritsu scores every concept as you work, so you find your gaps at your desk instead of across a table.
Every concept, scored.
Not one vague sense of “I think I get it” — a mastery score per idea in the paper.
Dim = what will catch you out.
The concepts you haven't got yet, named — before someone else names them for you.
The whole paper, one screen.
Contribution, method, and the claims it rests on — mapped.
Spaced review
Understand it today. Still have it at your next lab meeting.
You forget most of what you read within days — Ebbinghaus measured it in 1885. Ritsu brings each concept back right before it fades, so the paper you cracked this week is still there when someone asks you about it.
Five minutes tonight. Three tomorrow. Two in three days.
Built from your paper — no cards to make.
When you're stuck
The moments you actually get stuck — and what to type.
Then the paper probably assumed something you haven't seen. /prereq names what it took for granted — in learning order — so you fix the missing prerequisite, not the symptom.
every piece of reasoning, restored
Stop re-reading. Start understanding.
Free forever · no card