A game you play to master your instrument.
Five levels, from your first prompt to conducting a team of agents. One thing a day is enough.
your journey begins today
The technique that makes every other one possible: ask so Claude nails it on the first try.
Collect all five techniques to unlock Level 2.
shannon: the techniques you can play — and how well you can play them.
principles you return to so nothing drifts — a team, your own craft, or Claude itself. this is ours. it grows as you do.
every card you earn leaves its secret here — the inner circle, kept safe.
rule of thumb: match the surface to what the task needs. no memory, no action → chat. stable memory → Projects. action on code → Code. action on files → Cowork. and always, the least access that does the job.
the maker's guidelines this whole game was built on — the world it lives in, and how a player's craft is read. we don't hide the engine; understanding the machine is half of mastering it.
five new movements. the first is open — the rest reveal as you play.
five movements on memory: a standing score, a living document, compaction, grounded sources — and the workspace that holds them all.
five movements on agency: tools to act with, the loop that drives them, a goal to aim at, a fence for safety — and the verification that earns your trust.
the finale: a lead and its workers, sections in parallel, an ensemble of specialists, one shared score — and the system that plays on without you.
Everything in this product serves that one idea. The verb is play. The fantasy is fluency — the quiet confidence of a musician who no longer thinks about the notes. The player begins by talking and ends up composing; starts with one instrument and finishes conducting an orchestra.
he spent a lifetime listening — to telegraph lines, to the hiss between stations — certain that buried in every noise is a message waiting to be found. he never raises his voice; the clearest signal is the quietest one. he speaks in lowercase and in compression, and always leaves more underneath. named for Claude Shannon, father of information theory — the man Claude itself is named after. he is our design law made flesh: maximum meaning, minimum signal.
he has run ten thousand mazes. he rarely speaks; he shows. he learns the way the player does — try, fail, remember, try again — and once he finds a path he never forgets it. he tucks each card the player earns safely into place. in 1950 Shannon built a real mechanical mouse named Theseus — one of the first machines that learned. he is learn by doing and spaced repetition, given paws.
Shannon built Theseus. The master who hears the signal, and the creature who learns the path — together, the two halves of mastery: knowing what to say, and remembering how to say it.
Maximum meaning, minimum signal. The principle our guide is named for. A message grows stronger the more it is compressed. Fluency is compression — goal, context, format and reader folded into one clean ask. So the product practises what it teaches: we show the signal; we never print the label. If a line of copy explains what a moment of design could make the player feel, we cut the copy.
One name stands tall: Claude — the instrument everything serves. Everything else speaks in lowercase, even the guides. shannon and theseus sign small. Lowercase is the philosopher's calm — and his humility. And one creed beneath it all: good in, good out. The quality of the ask sets the ceiling of the answer.
Like the first fifty pages of a great series, the opening must already hold the whole world. Every word, icon, colour, sound and motion earns its place by belonging here. If a detail could come from another world, it doesn't ship. Nothing by accident.
this is the mirror turned on the person who built the game — reading how the maker actually plays Claude, held up against the inner circle. a worked example of what the feature sees. here is the reflection.
the feedback is surgical — the exact flaw and the exact fix named, never “make it better”. the eighty percent that already works is kept. most people re-roll the dice; the maker iterates as a diff.
the maker fixes the reader before asking — “for ambitious users, accessible to beginners”. the audience is the highest-leverage token in any prompt, and the maker reaches for it first.
the maker built a north star and enforced it — even catching a single stray word. that is how any system is kept consistent, a model or a team: write the rules down once, then hold the line.
the maker calls for a four-eyes review across half a dozen expert lenses — then acts on it. building the critic into the loop before shipping is the evaluator–optimizer pattern, turned on oneself.
named the thing, claimed the domain, asked for the favicon and the share-image. the maker thinks in launches, not demos — a prompt is a draft; a product is a system that ships.
feedback sometimes arrives as a burst of separate messages mid-build. one dense, coherent turn carries more signal than five quick ones — and it never talks over the work in progress. curate the context; don't trickle it.
the maker often asks to go “from a 6 to a 10”. naming what a 10 looks like — concretely — inside the brief lands it the first time instead of the third. the one-shot brief, aimed at me.
earlier, feedback arrived in bursts. lately it arrives batched and coherent — one dense turn that carries the whole intent. that is the skill maturing in real time. the mirror watches growth, not just gaps.
the circle closes here. the maker learned the moves — and can now watch the playing itself. that is the whole point: not to know about Claude, but to see one's own hand on the instrument.