So there’s a default way most people use Claude.
Type a question. Get an answer. Type a better question. Repeat.
It works. It also means you re-explain yourself constantly. Every time you want multi-perspective analysis, you type three paragraphs laying out what that means. Every time you want a compressed summary, you re-define what “compressed” looks like. Every session. From scratch. The mental overhead stacks up fast, and after a few weeks of heavy use, you’re spending more energy managing the conversation than actually thinking through the problem.
One developer on r/PromptEngineering got tired of it. He built a command vocabulary instead. The system is called Loop MMT, and the idea is simple: teach the AI a shared language once, then use shortcuts forever. The setup cost is maybe 20 minutes. The payoff compounds every session after that.
The old way vs. this approach
Old way: “Can you look at this from multiple angles, have each perspective challenge the others, and then give me a synthesized resolution?” Twenty-two words. Every single session. Multiply that across a dozen decisions in a workday and you’ve typed a small essay just to configure the thinking process before any real thinking happens.
New way: RCR on this.
RCR is Round, Collision, Resolution. Each board member gives an independent take (Round), they argue with each other (Collision), the chair synthesizes (Resolution). One four-character command triggers the whole sequence. The same analysis that took a paragraph of setup now takes three characters and a space.
The system has 30+ commands built on this logic. But the guide admits it upfront: five of them cover 80% of real-world use. The rest exist for edge cases, specialty workflows, or people who genuinely enjoy building out the full vocabulary. Most people never need them.
🗂 The five commands worth learning first
- LG! Starts the session. Runs preflight checks, reconstructs context from the last handoff, surfaces the agenda. Think of it as the briefing before the meeting, compressed into two characters.
- RCR Every advisor gives an independent take, they argue, the chair resolves. The core thinking tool. Works especially well for decisions where you already sense there are legitimate arguments on multiple sides but can’t quite articulate them yourself.
- 5S Compresses anything into exactly five load-bearing sentences. Not a summary. A compression. The constraint forces prioritization in a way that open-ended summaries don’t.
- ELIH Translates the last output into plain English. Three fields: what they said, so what, what’s the move. Useful after any response that’s technically correct but not yet actionable.
- Tap [name] Routes a task to one specific advisor through their particular lens. If you need the skeptic to pressure-test an idea, or the operator to spot execution gaps, you call them directly instead of running the full board.
That’s the whole starter kit. The rest of the guide is useful context, but these five handle most real sessions.
The design decision that makes it actually work
Most custom prompt systems are brittle. Use wrong syntax and nothing works. Forget the exact command format after a week away and you’re back to square one, digging through notes to remember how you set it up.
Loop MMT degrades gracefully. Type RCR on this or type “Hey, can everyone go around the room and give me their thoughts?” You get the same result. The command is a shortcut. Plain English always works underneath it.
That’s a real design choice most builders skip. Commands as optional sugar on top of normal conversation, not required syntax. You can’t break anything by trying. This also means onboarding someone else to the system takes minutes, not a documentation session.
There’s also a “Low Gear” mode for when you’re tired. Responses get shorter, options collapse to one recommendation, tone gets warmer. Type “I’m back” to reset. Small thing, but it shows the system was designed around how people actually work, not how they’re supposed to work. The best tools account for the full range of human states, not just peak performance.
How to apply this today
You don’t need Loop MMT specifically. The pattern is portable.
- Pick five commands you repeat constantly. Start with RCR, 5S, and ELIH. Those three are universally useful regardless of what you’re working on. Strategy, writing, debugging, planning: the same three commands apply.
- Create three to four distinct advisor personas with different lenses: creative, operational, devil’s advocate, user-focused. Give each one a name and a consistent point of view so the collisions in RCR feel meaningful rather than generic.
- Run a real decision through RCR on this and compare it to just asking “what do you think?” The difference in output quality is usually obvious on the first try, which makes the habit stick fast.
- Add new commands only when you catch yourself typing the same instruction more than three times in a row. That’s the signal that a pattern has emerged and deserves a shortcut.
The full guide is on Reddit, posted by u/greentide008 in r/PromptEngineering. It’s long. Start with the “Your First Five Commands” section and the Quick Reference Card at the end. Everything else is expansion material you can come back to once the core five are second nature.
The best prompt systems don’t replace how you think. They remove the friction of explaining how you think, every single time.
Sweet Prompts- a guide to all the custom-built commands I have built into my system
by u/greentide008 in PromptEngineering