WITHOUT ROTE
Explain everything
again. Every time.
01 Rebuild the context02 Correct the same mistakes03 Hope it remembers tomorrow
Built during Rote Playoffs · 81 public Plays
Teach your AI how you work.
Reuse it forever.
Rote turns a successful AI workflow into a reusable Play. Teach it once, then run the same method whenever the problem comes back.
Built for real stuck momentsInspectable before you run
THE ROTE LOOP
01
You have a task“Why did my CI fail?”
02
You do it once with AIGuide the investigation
03
Rote learns the methodEvidence → reliable steps
04
A Play is createdReady to run again
05
Anyone can reuse itSame problem, less effort
01 / THE SIMPLE VERSION
Think of Rote as
an intern for your methods.
The first time, you show an intern every step. After that, they know the process. Rote does something similar for AI workflows — it helps turn a good conversation into something repeatable.
Explain everything
vs
WITH ROTE
Teach once.
Reuse the workflow.
01 Guide the task once02 Capture what worked03 Run a Play next time
02 / HOW IT WORKS
A Play is a task
your AI already knows.
Before it runs, you can see what a Play needs and what it is allowed to do. That makes the workflow useful, inspectable, and easy to trust.
01
Install Rote
One command gets you started.
curl -fsSL https://getrote.dev/playoffs/install.sh | sh02
Talk normally
Use Codex, Claude, Cursor, OpenCode, or another supported harness.
“Find why this build failed.”
03
Guide the work
Correct assumptions. Those corrections teach Rote what reliable looks like.
“Check the diff before guessing.”
04
Reuse the Play
When it works, the method can be run again — by you or your team.
READ ONLYREAD + WRITE
03 / COMMAND CHEAT SHEET
Small commands.
Big head start.
You do not need to design a workflow before using one. Start with a task, then let Rote help you make the method reusable.
$ play what's newSee interesting public Plays$ play run helloRun a simple example Play$ play [your task]Start teaching Rote a useful workflow$ play journey view --activeSee how the current Play was created04 / THE PLAYGROUND
Problems people
actually get stuck on.
81 Plays for debugging, studying, shipping, and finding your way back into a project.
81public Plays
and counting
and counting
No Play matches that search. Try a different phrase.
05 / START HERE
Six good reasons
to open a terminal.
These are the Plays I keep coming back to when a familiar problem shows up again.
DEBUGGING
CI Failure
Investigator
CI failed and the log looks like it was written by an angry robot. This Play finds the signal, ignores the noise, and gives you the next check.
Explore Play ↗GIT & REVIEW
Claim Vs
Reality Auditor
“No breaking changes” — is that actually true? Check the claim against the diff.
Explore Play ↗REPOSITORY HEALTH
Works On My
Machine Investigator
Find the assumptions your laptop has been quietly hiding.
Explore Play ↗TESTING
Test Gap
Mapper
See where a changed behavior may have no nearby test evidence.
Explore Play ↗STUDENT SURVIVAL
Assignment To
Checklist
Turn four pages of instructions into a checklist you can actually use.
Explore Play ↗GETTING UNSTUCK
Where Did
I Stop?
Open a project after two weeks and get a sensible next step.
Explore Play ↗06 / UNDER THE HOOD
One question.
Several evidence trails.
Complex Plays can inspect several pieces of information at once, then compare the evidence before giving you an answer.
YOU ASK“Why did
CI fail?”
CI fail?”
→
CI LOGGIT DIFFCONFIGDEPENDENCIESWORKFLOW
→
PLAY OUTPUT“Root cause
likely here.”+ what to check next
likely here.”+ what to check next
07 / WHY I BUILT THESE
Every repeated
stuck moment deserves
a better shortcut.
Most developer tools are built around what experienced engineers need. During the Playoffs, I kept thinking about the moments where beginners and students actually get stuck.
A giant CI log. A repository you haven't touched in weeks. A LeetCode solution that passes every sample but still gets Wrong Answer. An assignment with twelve hidden requirements.
I started turning those moments into Plays. The idea became simple: if I get stuck on the same problem more than once, that problem probably deserves a Play.
Saksham — builder of this playground
YOUR TURNWhat annoying task
What annoying task
do you repeat every week?
That might be your next Play.