Yesterday a free prompt tool landed on r/PromptEngineering. It’s called Prompt Master, and it runs as a skill in Claude, Claude Code, ChatGPT, and Codex. The twist is that it doesn’t just polish your prompt. It refuses to invent facts you never gave it.
What’s new
You type pm: in front of a rough prompt. Before answering, it rewrites your prompt into a cleaner structure: goal up front, then context, constraints, output format, and what “done” looks like. Then it shows you the rewrite and answers it. You see exactly what the model is working from, which means you can spot a bad assumption before it costs you a bad answer.
Think about how most of us write prompts. We fire off a half-formed sentence, get a vague reply, then spend three more messages patching the gaps. Prompt Master moves that patching step to the front. One pass, and the structure is already there. If you have ever typed “fix my email” and gotten a generic template back, you know the pain this removes.
It’s free and MIT licensed, so you can use it at work, fork it, or tweak it for your own team without worrying about terms. The creator, u/Nikio10, built it with Claude. They decided what each command should do, and Claude helped write the skill and test it on sample prompts. That’s a nice small example of how a solo builder can ship something useful in a weekend with the right split: human decides the behavior, model drafts and stress-tests.
The twist
Here’s the part I like. When you leave something optional out, it doesn’t guess. It drops in a [placeholder] instead. It only asks you questions when answering would mean making up a fact, like a missing number, or “the file” with nothing attached. Even then it asks at most three, and each comes with a suggested default, so you can just say “yes, use the defaults” and keep moving.
Most prompt helpers fill gaps with confident fiction. They invent a deadline, an audience, a tech stack, and then build on top of it. You only notice three paragraphs later, when the answer is polished and wrong. This one marks the gap and moves on. A visible [placeholder] is honest. You can fill it in, or leave it and see how the model handles the blank.
Mini-workflow 🛠️
- 🧭 Type pm: before your rough prompt. It rewrites it and answers. Start here for anything you would normally just fire off in a hurry.
- 📋 Want just the polished prompt to use elsewhere? Use pm only: and copy the result into whatever tool you like. Great for prompts you plan to reuse in a project or a custom GPT.
- 🔍 Not sure your draft is any good? pm critique: scores it out of 10 and names the one fix to make first. One fix, not a list of twelve, so you actually do it.
- 🎯 Pick a preset for the task type: pm code:, email:, study:, or research:. Each makes sure the rewrite covers what that kind of task needs. For example, a code prompt should include the error and the expected behavior, while an email prompt needs the audience and the tone.
- 💡 Curious what it changed? pm why: explains the edits. This is the fastest way to learn what a strong prompt looks like, because you see the before, the after, and the reasoning.
Example from the post: “pm only code: my python script crashes on startup with KeyError: ‘config'”. You get back a prompt that asks for your code, the full error, what you expected to happen, and how you’ll know it’s fixed. Anything you didn’t say becomes a [placeholder]. Notice what it did not do: it did not guess which library you use or invent a config file structure. It left room for you to paste the real thing.
Pro tips
- pm again gives you a fresh rewrite. pm undo gives you an answer to your original prompt exactly as you typed it. That’s handy for comparing the two. Run both on the same prompt once and judge for yourself whether the rewrite earns its keep.
- ep: recommends which model and effort level to use for a task. That’s a small thing that saves real time, especially when you are tempted to throw the biggest model at a job a lighter one handles fine.
- pm help prints the full command list with examples.
- Run pm why: on your three most-used prompts this week. The patterns it points out, like missing context or a fuzzy definition of done, usually repeat. Fix those habits once and your raw prompts get better even without the tool.
Call to action ⚓
Grab it here: https://github.com/nishkarsh-shah/prompt-master
Try it on the messiest prompt you wrote this week, then compare pm critique’s score with what you expected. If you find a command it’s missing, the creator says feedback is welcome. Tell me what you find, because I’m curious which preset ends up as your daily driver!
I made a set of commands that rewrites a rough prompt before answering it (free, Claude + ChatGPT)
by u/Nikio10 in PromptEngineering