Script your workouts

ReptoLang is a tiny language for writing strength programs as plain text. You describe your training the way a coach would write it on a whiteboard — exercises, sets, weights, rest, and progression rules — and Reptor compiles it into a fully configured, trackable program. No tapping through menus, no rebuilding week 7 by hand.

That compiles into a one-week program with two days' worth of prescribed sets, with weights calculated from your training maxes. Hit Open in Playground above to run it live in your browser.

Why text?

• It's faster. Typing 5 @%80 beats five taps. A 9-week block is a few screens of text.
• It's reusable. Define a progression rule once, apply it to a dozen lifts.
• It's yours. Programs are plain text you can copy, diff, share, and version.
• It's powerful. State variables, lifecycle hooks, deload weeks, and supersets are all first-class — things spreadsheets and tap-through builders struggle with.

Why not just use LiftOScript?

Liftosaur's LiftOScript gets the core idea right — programs as text — and has an established user base. ReptoLang isn't "LiftOScript with some additions"; it's a re-design around a few gaps that kept coming up:

• State everywhere, not just in special blocks. LiftOScript only allows state variables inside its progress:/update: scripts. In ReptoLang, state.load * 0.85 is valid in any weight expression.
• Comments survive. LiftOScript wipes comments after every workout. ReptoLang keeps them as part of the program source, so notes to yourself (or an athlete you coach) stick around.
• One hook system, not two. LiftOScript splits logic across progress: (post-workout) and update: (mid-workout) contexts with different variable access rules. ReptoLang has one: on_complete and on_set, same variables, same rules.
• Deload weeks and supersets are native, not something you hand-roll by re-typing scaled sets.
• @version 1 pins the grammar. A program written today parses identically in five years — LiftOScript's syntax has changed under existing scripts before.

Where to go next

• Getting started — the anatomy of a .repto file.
• Sets & syntax — every way to write a set.
• Progressions & hooks — auto-progression, state, deloads.
• Language reference — directives, variables, functions.
• Exercise library — the 434 exercises you can reference by name.

Everything runs locally in the Playground — paste a program, watch it compile, and see exactly what Reptor will build.