Bracket-hunting in a notes app is not a workflow. If you’ve got a stash of go-to prompts sitting in a text file, you already know the drill. Open the file. Scroll past ten prompts you don’t need. Find the one you do. Then figure out which curly braces are placeholders and which ones you’re supposed to keep as-is. One commenter on the original thread put it perfectly. They’d been using a messy notes file for months. Every single time they grabbed a prompt, they burned five minutes just reformatting it. A Redditor posting as BathOk4147 over on r/PromptEngineering got tired of that exact loop and built something to kill it.
The fix is a small Android app called Mamout. It’s not a prompt generator, and it’s not another wrapper bolted onto an API. It’s a local library. Save your everyday prompts once, mark the parts that change each time, then run the prompt by filling in only the blanks. No more opening a raw text block and manually swapping out five different values before you can even hit send. The problem it solves is small on paper but expensive in practice. Multiply that five-minute reformatting tax by every prompt you run in a week. It adds up to real hours lost to busywork that has nothing to do with the actual thinking.
Here’s the twist: check the platform before you get too excited. The project is Android-only, built in Kotlin with Jetpack Compose, and shipped under an AGPL-3.0 license. A commenter flagged that the original post didn’t mention any of this upfront. That matters if you were picturing something for your desktop or iPhone. This is a solo build for one platform, released as open source. That’s the trade. Less polish and no cross-platform version yet. But you get the full source code and the freedom to bend it into whatever you actually need. The AGPL-3.0 part is worth sitting with for a second too. It’s a stronger copyleft license than the MIT or Apache licenses you see on most side projects. If you fork this and ship a modified version to other people, you’re on the hook to release your changes too. That’s true even if you just host it as a service.
Worth stacking this against what people already use for the same job. A lot of prompt hoarders lean on browser bookmarklets, Notion databases, or the saved-prompt features baked into ChatGPT and Claude’s own interfaces. Those all work, but they need a browser tab open and a login every time. A native app that lives on your phone and works offline is a different kind of convenient. That’s especially true if you’re firing off prompts between meetings rather than sitting at a desk.
If you want to try it, here’s the quick version:
- 📱 Grab the source from the project’s GitHub page and build the APK yourself, since it runs on Kotlin plus Jetpack Compose under the hood.
- 📝 Load in the prompts you actually reuse, and mark the swappable bits the same way every time, like {{topic}} or {{tone}}.
- 🔧 When you need one, open the app and pick the saved prompt. Fill in only the blanks instead of retyping the whole thing from scratch.
- ✅ Since it’s AGPL-3.0, fork it if you want extra features. Just know that anything you distribute has to stay open too.
Pro tip: pick one placeholder format and stick to it across every saved prompt. That’s the exact pain the top comment described. They spent five minutes reformatting a prompt because nobody could remember which brackets meant “replace me” and which ones were part of the actual instructions. Consistency here saves you the reformatting tax every single time you open the app.
Second pro tip: if you’re not on Android, don’t wait around for a port. The idea itself is simple: a template plus a fill-in-the-blank step. You can rebuild that in ten minutes using Notion, Apple Notes with text replacement, or a plain spreadsheet. The app is the polish. The trick underneath it is the actual leverage, and that part is free no matter what phone you carry.
This is a small release with barely any traction so far, just a couple of upvotes and a handful of comments. But the pattern underneath is worth stealing even if you never install it. Stop storing prompts as raw text. Start storing them as templates with clearly marked blanks. Go check out the GitHub repo, see how the developer structured the placeholder logic, and decide if it’s worth building your own version this weekend. 🚀
Frequently Asked Questions
Q: How does Mamout help with managing prompt templates and variables?
You know that feeling when you accidentally leave “INSERT_NAME_HERE” in a prompt and don’t catch it until the AI’s already responded three times? Mamout fixes this by letting you define prompts with placeholders that the app fills in each time you run them. No more reformatting, no more surprise test data slipping through.
Q: Is Mamout a web app or browser extension?
Nope, it’s Android-only, built with Kotlin and Jetpack Compose. If you’re looking for something desktop-based or browser-based, this won’t work for you. But if you want to manage prompts on your phone, it’s perfect.
Q: What’s the actual benefit over just using a notes file?
With notes, you’re reformatting brackets and swapping inputs manually every single time. With Mamout, you define your prompt template once, and the app handles the variable filling. Way less friction, way fewer mistakes.
Q: Can I see the code and maybe contribute?
Absolutely. It’s open source on GitHub under AGPL-3.0 and built with Kotlin and Jetpack Compose. If you’re into Android dev, you can explore it, learn from it, or jump in with improvements.
Built a quick tool to save and run your everyday prompts without the hassle
by u/BathOk4147 in PromptEngineering