Yesterday a builder dropped 52 of the strangest prompts you’ve ever seen, and every single one of them works. Greentide008 posted them on r/PromptEngineering under the title “My Sweet Prompts,” and the internet immediately noticed something was off. One commenter joked that the prompt reads like a management consultant on mushrooms, redesigning the concept of work itself.
Here’s what’s new. Over five months, this Redditor built a system called “Loop MMT.” It uses AI and determinism as its processing engine, with git as its state and memory. To document how it works, the creator published a whole page called “Sweet Prompts.” It holds the actual instructions that built the system and the software it produces. Fifty-two of them, sitting right there for anyone to study.
The twist is that these prompts don’t read like prompts at all. They read like a fever dream. One example, meant to design an email app’s UI, name-drops “Five Lenses,” “Kaleidoscope,” and “Ignition Block.” It also brings up Barcelona’s city grid, grocery stores, and yes, a line about hitting molly and LSD. Another commenter asked “who in the seventh f*** is Ed,” which is a fair question if you’re reading it cold. Strip away the surreal language, though, and a real structure sits underneath. Role assignment, named team members, a research step, a plan step, and a formal handoff at the end. The weirdness is decoration. The scaffolding is what actually does the work.
Here’s the prompt, reproduced exactly as posted, so you can study the pattern yourself:
“Here is what I want to do for design- I want to be SMART about how we do it. Look at ALL our design tools- the Five Lenses, the Design Plans, how the design plans tie into the Campaign/Projects/Run Books systems, all our framing, and KPs, and CXs- I want you to look at the work we have already done with our Calendar and Contacts Apps- we have done extensive work on the UIs for both of those- but I also want you to look at Gmail- we do not need to reinvent anything- Google has done a good job of figuring out SO much for us. Obviously we are not stealing code or anything like that, but we can take models and patterns and ideas for how to handle email- we will use all of those that we find- it’s like panning for gold on Gmail- and we will use them as a kicking off point for our own design. We will climb up on the shoulders of Google and start from there. They won’t even know we are standing there.
Please RCR on that. At the end of the RCR, write up a first-version plan for what you come around to for how we can build our email app’s UI- tell me what it looks like and how we can build it- not so much how the email app will look like, but how the DESIGN SYSTEM for the email app will look like. That is how I want to make this thing- like the system it is. Blocks, blocks of blocks, blocks of blocks of blocks, Block^N. 4C, FWW(C). Grocery Stores. Barcelona’s city grid design. No black boxing, and have everyone get involved- all 16 members plus Crux. No compression either- I want everyone to fully contribute. I want Margaux and Renata on lead. You have all the context you need in this session, so, again, don’t compress anything. Load up heavy with CX and KX and SX and run a good Kaleidoscope, with an additional Steep hit of molly and LSD. Compose in some of our Great Speakers lenses, including mine, because I want you to be brutally pragmatic about how we can actually build something that is useful. Make sure you look up all the things here so you are fully in compliance. Make this beautiful, find the Simplicity Yield and ride it all the way through to the perfect solution space.
Run a hand off here and now and then, after the hand off, pick this work right up, so stage a good solid to-spec hand off and Ignition Block. Again, make sure both are fully to-spec.”
Read past the jargon and the moves get clear fast. Pull inspiration from known products without copying their code. Assign named roles to specific parts of the task. Forbid “compression” so nothing gets quietly summarized away. Close with a formal handoff so the next session can pick up exactly where this one stopped.
Here’s a small workflow you can steal from it for your own prompts:
- 🧩 Name your components. Give recurring parts of your system a label, like “Five Lenses” or “Design Plans.” Then you can reference them in one word instead of re-explaining every time.
- 🔍 Point at real reference points. Tell the model to study something concrete, an app, a UI, a dataset, and pull patterns from it, not copy it.
- 👥 Assign roles explicitly. Naming who leads what keeps a long prompt from turning into mush.
- Ban compression outright. If you don’t want a summary, say so directly. Models default to condensing unless told otherwise.
- 🤝 End with a handoff. Close every long session with clear instructions for how the next one should pick up the thread.
Pro tip: the strangeness in these prompts isn’t an accident. A wall of vivid, specific, almost absurd language forces the model to hold more context active at once instead of quietly trimming it down. If your own prompts keep getting flattened into generic output, try making them weirder and more specific, not shorter. Vivid beats vague, even when vivid looks unhinged.
One more trick worth borrowing showed up in the replies. A commenter named bupkizz said they launch their own orchestration suite by typing “let’s get this agent-party bumpppiinnnnnn.” Silly on the surface, but it’s the exact same move. A distinctive, weird phrase becomes a reliable trigger the model recognizes every time.
Curious how deep this rabbit hole goes? The full collection covers all 52 prompts and the system they built together. Go dig through Loop MMT’s “Sweet Prompts” page. Or feed the whole site to your own AI and ask it to report back what it learned. 🏴☠
Frequently Asked Questions
Q: What is “meta-prompting” and why does adding layers of frameworks actually help?
Meta-prompting involves building multiple overlapping frameworks and references into a single prompt, forcing the AI to juggle competing models simultaneously. According to comments, this creates a state of “hyper-focus”, the AI makes more deliberate decisions when constrained by competing systems rather than given simple instructions. It sounds chaotic, but the structure paradoxically produces more coherent outputs.
Q: Do I need to use these exact prompts, or is this teaching me a technique?
These 52 prompts are examples of a meta-prompting technique, not templates to copy-paste. The approach emphasizes layering frameworks (design systems, reference architectures, competing models) to guide AI outputs. You’d adapt this by identifying the frameworks relevant to your own work and building them into your prompts the same way.
Q: How does git fit into this as a “state store”?
Loop MMT treats git as both memory and deterministic processor, prompts are versioned, outputs are tracked, and iterations are reproducible. This combines the flexibility of AI prompting with the rigor of version control, making the entire system auditable and iteratable rather than a black box.
Q: Can I use custom trigger phrases to automate my AI workflows?
Yes, community members reported success with consistent linguistic triggers (e.g., specific phrases) to reliably invoke orchestration tools and AI behaviors. The key is pairing trigger consistency with clear internal frameworks in your prompts, so the AI knows exactly which mode or system to activate.
My Sweet Prompts- 52 crazy looking prompts that work
by u/greentide008 in PromptEngineering