Nobody enjoys staring at a blank prompt box, hoping the right words just show up. Most people type something rough, get a mediocre answer, then rewrite the whole thing from scratch three or four times before giving up entirely. u/ZioGino71 over on r/PromptEngineering just shared a fix for that exact problem, and it’s built entirely inside Gemini.
The tool is a custom Gemini Gem, essentially an interactive prompt builder. Instead of handing you an empty box and wishing you luck, it interviews you. It asks what you’re trying to do, generates options tailored to your context, and walks you step by step until you land on a structured, safe, ready-to-use prompt. No AI background needed, and no framework to memorize first.
Here’s the twist: the “dynamic options” part isn’t a fixed script running quietly in the background. The Gem reads your context and generates new choices each round, so two people asking about the same topic can end up with genuinely different follow-up questions. It feels less like filling out a form and more like a quick interview with someone who actually listens to your last answer before deciding what to ask next.
One commenter, u/Apart_Oven_5735, put it well. They said it’s nice to find “a good prompt builder that actually walks you through it instead of just dumping a blank box on you,” and that the dynamic options feel like the tool is “reading the room” instead of firing off the same five questions every time. That’s the part that stood out to me too. Most prompt templates are static, one path for everyone. This one adapts mid-conversation based on what you actually say.
Here’s the mini-workflow if you want to try it yourself:
- 🔗 Open the shared Gem link and save it into your own Gemini gems.
- 💬 Answer the first question honestly. Don’t overthink it, the tool adjusts either way.
- 🎯 Pick from the dynamic options it generates. These narrow down tone, format, and constraints round by round.
- ✅ Keep answering until it hands you the finished prompt, ready to paste elsewhere.
Pro tip: run the same starting idea through the Gem twice, but change your first answer slightly the second time around. Because the options are dynamic, you’ll see exactly how much the follow-up questions shift, and that’s a fast way to learn which details actually move the needle when you write your own prompts from scratch later.
Second pro tip: treat the output as a strong first draft, not gospel. It’s designed to be safe and immediately usable, which is great for getting unstuck fast when you’re staring down a deadline. But you should still skim the result for anything that doesn’t quite match your actual use case before you paste it into a client project or a production system.
A couple of things worth knowing before you jump in. This lives inside Gemini as a Gem, so you’ll need a Google account with Gem access to use it directly. It isn’t a standalone app or an API you can drop into your own stack, so if you’re building an internal tool, you’ll need to adapt the workflow rather than the code itself. And because it’s shared as a public link rather than open-sourced code, you get the flow itself but not the underlying logic, so you can’t peek under the hood or fork it the way you could with a self-hosted prompt tool.
Compared to the usual prompt engineering advice out there (memorize a framework, fill in a template, hope you didn’t skip a step), this flips the process around entirely. You don’t need to know what “role assignment” or “chain-of-thought” even means going in. The Gem quietly asks the questions that map to those techniques for you, then assembles the structure in the background while you’re just answering simple, plain-language questions about what you want.
That’s honestly the most useful part for anyone new to this. Prompt engineering guides tend to assume you already know the vocabulary before you can use the framework properly. This Gem inverts that assumption completely. You bring the goal, it brings the structure, and the terminology becomes something you pick up naturally by seeing it in action rather than something you have to study upfront.
It’s also worth noting the “safe” part of the pitch isn’t just marketing language. A guided builder that asks clarifying questions before generating anything tends to produce prompts with fewer ambiguous instructions and fewer accidental gaps, the kind of gaps that let a model wander off in a direction you didn’t intend. That matters more the moment you start using prompts for real work instead of just experimenting.
If you’ve ever abandoned a prompt halfway through because you didn’t know what to ask for next, this is worth five minutes of your afternoon. Check out the original thread on r/PromptEngineering, try the Gem on something you’re actually stuck on right now, and see how close it gets on the first pass 🚀.
The Art of Prompt Optimization, Made Simple and Safe.
by u/ZioGino71 in PromptEngineering