Yesterday somebody dropped a neat little browser tool that kills one of the most annoying parts of AI chat: rewriting your instructions every single time. It’s called JigBench, and the second part of how it works is the actual twist. The original poster, a Redditor who goes by moonshotconsulting, built the whole thing with GPT-6 Astra inside Codex. The Redditor tested and steered every piece by hand, then opened it up for feedback from the community.
What’s New
JigBench is a free browser tool for building AI prompts out of reusable pieces. No login, no API key, nothing to install. You pick from ten built-in commands. You arrange the ones that fit together. You drop in your own material, then preview the finished prompt before copying it anywhere. Then paste it into ChatGPT, Claude, or Gemini. Use whatever tool you already have open. The tool itself never touches an AI model. It just assembles the text you’d otherwise be typing from scratch.
That last part matters more than it sounds. A lot of prompt tools quietly route your text through their own backend, which means your material passes through a server you didn’t choose. JigBench skips that step entirely. The assembly happens in your browser, and the finished prompt only leaves your machine when you paste it somewhere yourself.
The Twist
Here’s the part that makes this different from a folder of saved prompts. Most people store static text blocks and edit them by hand every time the task shifts slightly. JigBench treats commands like building blocks instead. You choose which ones go in and the order they run in, and only compatible steps snap together. Your saved workflows keep the command choices and order, but never your actual working material. That means the structure sticks around while the sensitive or one-off content stays out of storage. It’s a small design choice, but it changes what “reusable” actually means. You’re not reusing text, you’re reusing a sequence.
How It Works 🧩
- Pick from the ten available commands based on what you’re trying to do.
- Arrange the compatible steps in the order you want them to run.
- Add your own material, whatever the task needs.
- Preview the full assembled prompt before you touch copy.
- Paste it into your AI tool of choice and run it.
One example from the post shows the appeal. Run “/human” first to rewrite a rough draft. Then hit the result with “/VERIFY” so the AI checks its own claims against evidence you supply. Two commands, one clean prompt, zero rebuilding from scratch. Swap in different commands and you get a completely different mini-workflow without touching a single saved document.
Pro Tips
- Order matters more than you’d think. One commenter pointed out that most saved-prompt setups are just static blocks you edit by hand. Chaining compatible steps in sequence is what actually saves time.
- Keep notes on which combo worked for which task. A second commenter admitted the hard part was never finding old snippets. It was remembering which stack of commands solved a specific problem last time, which is a different problem than storage entirely.
- Think in modules, not monoliths. A third reply flagged that this kind of modularity could eventually let an AI assemble its own prompt chains with less hand-holding from you.
A few caveats worth knowing before you get attached. JigBench doesn’t run any AI model itself. It only builds the prompt. You still need ChatGPT, Claude, or Gemini open in another tab to actually run it. Your working material never gets saved, which is great for privacy, but it means you’re re-pasting your source content every session. One commenter raised a real point too: OpenAI’s own release notes have custom GPTs slated for retirement, with reusable instructions migrating toward plugins instead. Any tool built on prompt reuse is competing with a moving target, and JigBench is no exception to that.
Compared to a folder of saved prompts or a pinned doc of instructions, JigBench’s pitch is that structure and order do the heavy lifting. Storage alone isn’t the point. A static snippet library still asks you to remember what worked and edit it by hand every time. JigBench asks you to remember a sequence instead, and the sequence adapts to whatever material you feed it that day. Whether that beats a well-organized snippet library is still an open question. The creator is asking for exactly that kind of honest pushback in the comments. That’s the right question to ask before building anything more elaborate on top.
Worth five minutes if you’re tired of rebuilding the same instructions from scratch every time you open a new chat. Go poke around the full discussion on r/PromptEngineering and tell the original poster what’s missing 🚀.
Frequently Asked Questions
Q: What’s the advantage over just saving prompts in a folder?
You’re arranging reusable commands instead of editing static templates. The tradeoff: JigBench doesn’t track which combinations worked best for past projects, so you’ll want notes elsewhere if versioning and experiment history matter.
Q: Can I export the prompt as plain text?
Right now you can copy from the page, but one user wants plain text export for tools with finicky copy-paste. Worth checking the latest version or requesting the feature from the creator, since it’s clearly something people need.
Q: Does JigBench remember which command chains worked for my past projects?
It saves your workflow choices and command order in your browser, but doesn’t track which combos worked best for different tasks. Each new project starts fresh, so you’ll rely on your own documentation for tracking what worked when.
Q: Will this be affected by OpenAI retiring Custom GPTs?
No. JigBench runs in your browser with no dependency on OpenAI’s infrastructure. The Custom GPT retirement changes in-app saved instructions, but your browser-based prompt assembly continues working regardless.
I built a free browser tool for assembling reusable AI prompts. Would you use this instead of saved prompts?
by u/moonshotconsulting in PromptEngineering