for devs who want to be 10x faster in the terminal

Finally learn practical (neo)vim.

Not party tricks — the real terminal work you hit every day and still reach for VS Code to finish. A real vim buffer in your browser, drilled as missions with keystroke targets until your hands just know it.

Start training free → See the full curriculum →
5 free missions, ~5 minutes — ends with you editing a real file, mouse-free · nothing to install
▸ YOUR MISSION — Line 2 has a typo: “commannd” has an extra n. Use j to reach line 2, then h j k l to move onto that extra n, and x to delete it.
1  Vim rewards precise, tiny edits.
2  Every keystroke is a commannd.
3  Trust the home row.
NORMAL lesson 1 of the real arena ⌨ 0 / target 29

From the arena floor

Fun and educational! Leaned new things about VIM!
Andrew Lim @DanteShamest

The terminal came back. And it doesn't do mouse.

$ssh you@prod-box # 2:14am, one .env line to fix
VS Code can't follow you in here. No extensions, no cursor, no undo button — just you and the box. And the box speaks vim.
$git rebase -i HEAD~4
It doesn't ask permission — it drops you straight into an editor. Know the eight keys that matter, or spend the next five minutes googling ":q!". Again.
$claude # your pair programmer lives here now
The agent writes at 10x, then hands the file back to you — in the terminal. Fix the prompt, tweak the config, edit CLAUDE.md. Your hands are the bottleneck now.

How it works

01
A real vim engine, in your browser
The genuine article — the same vim engine Replit ships — in a browser tab. Nothing to install, nothing to configure. Every mission checks the real buffer, so any correct solution passes, and the reflexes carry straight over to vim, neovim, and any IDE's vim mode.
02
Real use cases you'll actually hit
“Copy line 5.” “Replace every hello with goodbye.” “Comment out four lines at once.” The edits you make two hundred times a day — not abstract puzzles about steering a cursor through a maze.
03
Become more than 10x faster
Every mission counts your keystrokes against a target — the fewest that solve it. Beat the target and watch your count fall, mission after mission. Your AI already moves at 10x; this is how your hands keep up.

Your path to black belt.

StageWhat sticks
Basics freex · dw · dd · u — delete anything, fearlessly
Insert mode tastei · A · o — in, edit, out
Moving fast10G · gg · G — stop scrolling forever
Search/pattern · n · . — find and fix at teleport speed
Substitution:%s//g and ranges — the terminal's find-and-replace
Yank & putyy · yiw · registers — copy exactly what you mean
Text objectsciw · ci" · di( — edit by meaning, not position
Visual modeV · Ctrl-v block edits — vim's multiple cursors
Power movesf · J · r · counts — the flourishes that compound
Registers II"ayy · "Ayy · named registers — juggle many clipboards
Marks & jumpsma · `a · Ctrl-o — teleport between edit sites
Macrosqa · @a · @@ — record once, replay a hundred times
Precision editingct( · di] · f;d — surgical, single-line strikes
Lines & indent>> · == · :m — reshape and reorder whole blocks
In the labReal-world packs: JSON surgery, git rebase -i, config files
Fifty missions, 30–90 seconds each — white belt to black in a weekend. The first stages cover everything the classic 30-minute tour does; the rest is what it never teaches — registers, marks, macros, visual block — verified, not just read.
Start the free missions →
The first stage is free — no card, nothing to install.

Why I built this

Every serious developer I admired had vim in their fingers. I learned the basics — enough to get by, never enough to be fully IDE-free. The moment anything got fiddly, I crawled back to the mouse.

Then AI changed where the work happens. Terminal agents, TUIs, a quick ssh edit on a box no IDE can reach — being able to edit a file without an IDE stopped being optional.

What finally stuck wasn't mastery. It was practical vim: the twenty percent you use two hundred times a day, drilled as tiny missions until my hands knew them cold. VimJutsu is that path — a real vim engine, keystroke targets, and a clear ladder so you can feel yourself getting faster.

— Chong-U · founder, VimJutsu

Take your seat in the arena

one payment · yours forever
$79$49
50 seats at the $49 opening price — then $79
  • All fifty missions — white belt to black
  • Challenge mode — hit the keystroke target on every mission
  • Cloud sync across all your devices
  • Every future update, free
  • 30-day black-belt guarantee — measurably faster or full refund
Take your seat — $49 →

One payment. No subscriptions.

The black-belt guarantee: finish the first three stages and if you don't feel measurably faster in a real terminal, email within 30 days — full refund, keep the reflexes.

FAQ

Is this real vim?

Real vim behavior, in the browser — the same engine Replit uses: modes, registers, text objects, counts, macros, ex commands. Missions validate against the actual buffer and registers — so the reflexes transfer 1:1 to vim, neovim, or any IDE's vim mode.

I've bounced off vim three times. Why is this different?

Because you don't read here — you do. Each mission is one skill, 30–90 seconds, validated by outcome. Any correct keystroke sequence passes. Watching your keystroke count fall toward the target shows you getting faster — the feedback loop tutorials never close.

I already did the built-in 30-minute tutorial. What's left?

The classic tour is a good map — but it's read-and-follow: you type what it says, once, and nothing checks whether it stuck. Here every mission is verified against the live buffer and scored against a keystroke target until it's reflex. And half the curriculum starts where that tour ends — text objects, named registers, marks, macros, visual block edits. That's the gap between “I did the tutorial” and “vim is in my fingers.”

I've never touched vim. Is this too advanced?

No — mission one is moving the cursor and deleting one character. No prior vim, no setup, no config file. The first stage is free, so you'll know within five minutes whether it clicks.

Do I have to give up VS Code or Cursor?

Keep them. The reflexes carry into any IDE's vim mode — and into the places your IDE can't follow: an ssh session, a git rebase, the file your terminal agent just handed back.

What if it doesn't work for me?

30-day full refund, no questionnaire. See the black-belt guarantee above.

Team licenses?

In the works — onboarding dashboards for teams standardizing on terminal workflows. DM @chongdashu for early access.

Your AI writes at 10x. Catch up.

Five free missions, about five minutes. By the last one you'll have edited a real file, mouse-free.

Start training free → Take your seat — $49 →

Stop googling vim.

The questions every developer searches at 2am — each answered in a one-page guide with a free practice mission.

How do I exit vim? Save a file Find & replace Delete a line Copy & paste a line Undo & redo Select all Comment multiple lines Copy to system clipboard Delete multiple lines Best way to learn vim Is vim worth learning?

All 63 guides →