Five habits and a few phrases. Do these and the output goes from good to great, and it compounds, the more you steer it well, the more you trust it, the more you use it. Keep this open while you work.
The whole game, in five moves.
It reads your whole business before it lifts a finger, your context, your files, where things stand. Skip it and Claude is working blind. One word, every time you sit down.
Don't just say "do this thing", it'll build too soon and guess the rest. Say "let's plan this out properly, and ask me clarifying questions." The questions are where it catches what you left out.
Never send it off unread, that's where it bites you. If something's wrong, tell it exactly what's wrong and say "make it better." Two or three passes to a great result is normal, not a failure.
Once you've got a result you love, tell it to save the whole process as a skill. It remembers how you like it and the mistakes to avoid, so you never explain that task again. This is how it gets better at your work.
Run /commit at the end of each session to save and back up your work. Don't stack three or four sessions before committing, do them one at a time and it stays clean.
If Claude keeps getting facts about your business wrong, the problem is usually its context files, the ones it reads every session. Spend 30 minutes one time: open your files, run /prime, and say "read your context files and I'll tell you what's out of date." Correct it at the source and every session after gets sharper.
Tap to copy. These are the phrases that do the heavy lifting.
Bookends for every working session.
/prime
/commit
Quick fixes for the usual frustrations.
Small habits, outsized payoff.
Hold to dictate and just talk. You'll give far more useful context in 30 seconds of talking than 30 seconds of typing, and better context means better output.
Keep each session focused on a single task. It stays sharper, and your commits stay clean and easy to follow.