Do this first
Ten words. 6:58.
Not a signup, not a call. Learn the vocabulary. These are Walkthrough Rudiments — named for the drum rudiment, the small figure you drill until it is automatic and out of which everything longer is built. One runs show, name, stop.
Each clip carries two layers. The first is what the tool calls it. The second is the practice underneath — the craft that was true before any of this existed and stays true after. If you never buy anything, take the second layer and go.
10 recorded · 6:58 in total · 4 named and not yet filmed
-
01 Repository or project 44s
Galaxy
In the product
A repository held with its configuration, credentials, analysis state and history as one thing, so opening it means opening all of that.
The practice underneath
A working set. Everything needed to work on a codebase kept together, rather than scattered across a README, a password manager and somebody’s memory.
-
02 Layer of the architecture, drawn 42s
Ring
In the product
One of five concentric circles in the 3D view. A file sits on a ring by the job it does, not the folder it is in.
The practice underneath
Architectural layering. Core, services, APIs, UI, infrastructure. Drawing a system by responsibility is how you find the file that is in the wrong place.
-
03 Where an epic is built 42s
Big Bang
In the product
The screen that turns a document or a description into phases, work units, gaps and an architecture drawing per phase.
The practice underneath
Planning from a requirement instead of from a backlog. The decomposition happens before anyone writes code, and it is written down where it can be argued with.
-
04 A body of work, broken down 37s
Epic
In the product
A feature large enough that it has to be decomposed into phases and work units before anyone starts.
The practice underneath
Decomposition. Split the work until each piece is small enough to estimate honestly and small enough to review in one sitting.
-
05 One epic delivered across several repositories 43s
Constellation Epic
In the product
A single body of work planned and executed across several repositories at once, with the seams between them resolved deliberately rather than discovered late.
The practice underneath
Cross-repository release coordination. The hard part of multi-repo work is never the code in any one repo, it is the order and the contracts between them.
-
06 Generate a working project from a description 44s
Vibe
In the product
A description in, a project that runs out.
The practice underneath
The spike. Build the throwaway to learn the shape, then decide whether the real one is worth building. The mistake is keeping the spike.
-
07 A packaged capability for Claude Code 36s
Skill
In the product
A capability packaged with its instructions and its resources, so it runs the same way for the next person.
The practice underneath
The runbook. A procedure written down well enough that the person who did not invent it can run it correctly at three in the morning.
-
08 A recorded or live demonstration 43s
Walkthrough
In the product
A run of the real product, captured, so the demonstration is of the thing rather than of a slide about the thing.
The practice underneath
The review at the end of an increment. Show the work running. Describing it is not the same act and everyone in the room knows it.
-
09 The cloud instances you run 43s
Fleet
In the product
The instances you have running, and what each of them is for.
The practice underneath
Environment management. Knowing what is deployed where, who it belongs to, and which one you are about to break.
-
10 A teammate's cloud dev environment 44s
Ghost
In the product
A teammate’s own instance, running in the cloud rather than on their machine.
The practice underneath
The development environment that is not a laptop. It is the step everything in the demo economy skips, and it is the step that decides whether the work survives the person who did it.
-
11 A question the plan cannot answer on its own not filmed
Gap
No clip.Why it is here anyway
The strongest idea in the product has no clip. It was not in the glossary at all until 2026-08-28.
-
12 A single implementable task not filmed
Work Unit
No clip.Why it is here anyway
The unit the hours are added up from. Not recorded.
-
13 A reusable AI prompt template not filmed
Smart Prompt
No clip.Why it is here anyway
Instructions kept in files you can open and change. Not recorded.
-
14 An automated workflow not filmed
Mission
No clip.Why it is here anyway
A run with named phases and a record of what was asked and answered. Not recorded.
Four words in the vocabulary have no clip. They are listed in sequence rather than hidden, because a set with a visible hole in it is something being built, and a set with no holes is a brochure. Every definition is on the vocabulary page.
Then
The case, in order →