// Writing style guide for prose content - program descriptions, technique pages, blog posts, and any user-facing text. Use when writing or editing descriptive content.
Fix a production exception from Rollbar in an interactive Claude Code session. Fetches the occurrence data, analyzes the error, and either implements a fix or adds the error to the ignore list. Use when given a Rollbar occurrence ID.
Guidelines for writing React Native code in Liftosaur. Use when migrating web components to RN primitives, fixing RN performance issues, or building new RN screens.
Write, debug, and integrate Lezer grammars for the Liftosaur project. Use when creating or modifying .grammar files, evaluators, syntax highlighting, or CodeMirror integration.
Write idiomatic Liftoscript code for weightlifting programs. Use when creating or editing program files in programs/builtin/.
Capture important architectural decisions, bug patterns, feature designs, or other critical findings into the project knowledge base. Use proactively when significant technical decisions are made, non-obvious bugs are resolved, new subsystems are designed, or important product features are discussed.
Add a new server-rendered page to the Liftosaur website. Use when creating new public-facing pages with routing, SSR, and client hydration.
| name | writing-style |
| description | Writing style guide for prose content - program descriptions, technique pages, blog posts, and any user-facing text. Use when writing or editing descriptive content. |
| disable-model-invocation | true |
Apply these rules when writing any prose content for Liftosaur - program descriptions, technique pages, FAQ answers, whatsnew entries, blog posts, or any user-facing text.
Write like a knowledgeable training partner explaining something over coffee - conversational, honest, and encouraging. Not like an academic paper, a marketing brochure, or a corporate changelog.
Key traits of the Liftosaur voice:
Use simple, common words. Prefer casual phrasing where it fits naturally.
Don't go overboard - this isn't ELI5. Technical gym terms (periodization, progressive overload, AMRAP, RPE) are fine because the audience knows them. The goal is to avoid unnecessarily fancy phrasing where a simpler one says the same thing.
Bad (overwritten):
This methodology leverages undulating periodization to facilitate optimal neuromuscular adaptations across multiple training variables.
Bad (too dumbed down):
This program changes things up so your muscles keep growing.
Good (plain but precise):
The program uses undulating periodization - rep ranges change each session. Heavy one day, moderate the next, light after that. This keeps progress going longer than repeating the same sets and reps every workout.
Vary sentence length deliberately. Same-length sentences are boring and hard to scan.
Mix short sentences (3-8 words) with longer ones that add detail. Use fragments where they feel natural. This makes text easier to skim - readers grab key points from short sentences and read longer ones when they want more.
Bad (monotonous):
This program uses linear progression for the main lifts. You will add weight to the bar each session. The rep scheme is based on 5 sets of 5 reps. You should rest 3-5 minutes between sets.
Good (varied rhythm):
Linear progression on the main lifts. Add 5lb to upper body and 10lb to lower body each session - simple and effective. Rest 3-5 minutes between heavy sets. The 5x5 scheme builds both strength and technique through volume at moderate intensity.
Use these naturally - don't force them, but don't avoid them either:
When describing features or changes, lead with the problem users had, then show the solution. This makes the reader immediately understand WHY something exists.
Bad:
Added a new Exercises screen with 1RM editing capabilities.
Good:
A lot of users found it weird you can only adjust 1RM during a workout. So now there's a separate Exercises screen where you can change it anytime.
Bad:
Implemented weight rounding visualization with strikethrough formatting.
Good:
It's confusing when the app rounds your weights to available plates - looks like a bug. So now it shows strikethrough on the original weight, making it clear what happened.
Bad:
Good:
When something sounds complicated, acknowledge it and then show it's manageable:
"It sounds pretty complicated, but should be way more clear when you look at the example below."
Concrete walkthrough examples beat abstract explanations. Show specific numbers:
"For instance, if you can do 5 reps (and no more) with 100 kg, then your 5 rep max is 100 kg. Let's say you guessed your 10RM for Bench Press is 185lb. So, you do: 5 reps with empty bar, 5 reps with 95lb, 3 reps with 135lb, 10 reps with 185lb."
When writing pros and cons, every item must be concrete and actionable.
Do NOT list "lack of exercise variety" as a con. Repeating the same exercises builds technique, enables progressive overload tracking, and is how every proven program works.
When explaining WHY something is done, keep it to 1-2 sentences. Don't lecture. The reader wants the reason, not a textbook chapter.
--) for dashes - use a single hyphen (-) instead. "Linear progression on the main lifts - simple and effective" not "Linear progression on the main lifts -- simple and effective".