Hashing
Why a hash map lookup is one jump, when it stops being one, separate chaining, open addressing with tombstones, resizing, and the inputs that break it. Every code block runs.
Plan and write courses, chapters, notes and cheat sheets on anything, from binary search to how a rocket engine works. Every diagram is an interactive isometric machine whose working is the idea, and every page is built and checked before you see it.
$ npx skills add akshaypjoshi/course-studio -g -a claude-code
/plugin marketplace add akshaypjoshi/course-studio /plugin install course-studio@course-studio
This is the figure from the demo chapter on hashing, running live. A dial computes k mod 8 and a shuttle drops each key into its tray. Hover or use the arrow keys to step through inserts, and watch one bad set of keys pile into a single chain.
build.mjsSee it in the chapterFor a physical subject the figure is the thing itself. This is the figure from the second demo chapter, Inside the engine: Raptor 2, SpaceX's full-flow staged-combustion engine, on a test stand. Hover or use the arrow keys to take it apart part by part, then press Ignite and watch the preburners light before the chamber reaches 300 bar.
The skill picks the scope from your request, says it in one line, and gets to work in ./courses/.
"Plan a System Design course"
Outcomes, prerequisites and chapters in dependency order, each with one planned figure. Built into a syllabus page and a catalog.
"Write the binary search chapter"
A fixed teaching arc from hook to recap, code that has been run, its signature figure, and a built page.
"Notes on consistent hashing"
A compressed arc: idea, mechanism, code, pitfalls, two checks. Reuses a chapter figure where one fits.
"Cheat sheet for graphs"
Tables, patterns, complexity grids and one-liners on one or two screens. No new figures, links for depth.
"A course on how rockets work"
Machines, the body, physics, markets. Real things drawn as themselves, numbers taken from published sources.
"Lesson on how the heart pumps"
From school students to professionals. The writing adapts; the checks stay the same.
The figure is driven by the same model as the chapter's worked example, so the numbers on the card are the numbers in the text.
One outcome sentence per section, then the single insight that most needs to be seen moving.
The idea, the truth model with the chapter's exact numbers, a physical object from an atlas of about 90 concepts, and the tour beats.
The Anatomy engine draws a detailed isometric machine with a live readout, then audits it for painter's order and clipping.
The chapter is written around the figure, every code block is run, and the page is checked on desktop, phone and dark mode.
::figure directive for your own platform.Both bundled examples, written and checked with the skill, and rebuilt by its own scripts on every deploy. One is an algorithms course, the other a course on rockets for curious adults.
Why a hash map lookup is one jump, when it stops being one, separate chaining, open addressing with tombstones, resizing, and the inputs that break it. Every code block runs.
Why a rocket engine is a pump problem, and how SpaceX's Raptor drives its pumps with the propellants they pump. Real numbers with dates and sources, checked with back-of-envelope arithmetic.
The Anatomy figure engine is bundled, so the skill is all you add. Building pages and figures uses tools you likely have.
| Tool | Needed for |
|---|---|
Python 3.9+ with markdown, pyyaml, pygments | Building pages (pip install -r requirements.txt in the skill folder) |
playwright and Chromium | The headless page check |
| Node.js 20.10+ | Building figures. Without it the skill still writes; figures wait as briefs. |