Yesterday a dev shipped something that should have existed three years ago.
It’s called prompt-mini. A Claude Code plugin that intercepts every vague prompt before the model touches it. The author’s previous tool hit 4000+ GitHub stars. This one is the missing piece: not a template library, but a pre-flight system that runs before Claude does.
What it does
Vague prompts are expensive. No scope, no stop conditions, no file paths. Claude guesses the framework, hallucinates a feature, burns credits on retries. prompt-mini catches 35 specific patterns that kill prompts before they start.
Clear prompts pass straight through untouched. Only the vague ones get intercepted and rebuilt.
The twist
It doesn’t ask you what stack you’re using. It reads your project files and figures it out. 40+ frameworks with their own routing rules: Next.js, Expo, Supabase, FastAPI, LangChain, Cloudflare Workers. Each one produces a different structured output. Nothing generic comes out the other side.
The output is a 6-block structured prompt, with hard stop conditions and MUST NOT rules locked into the first 30% of the prompt. That’s where Claude’s attention weighting is highest. That design choice is not accidental.
How to use it
- Install prompt-mini as a Claude Code plugin
- 💬 Type your idea, as vague as you normally would
- Answer the targeted questions: stack, UI style, auth approach, which pages to build
- 📋 Review the 6-block structured prompt: file paths, hard stops, and MUST NOT rules locked in
- 🚀 Execute. Claude runs it with full context in place from the start
Pro tip
Pair this with a CLAUDE.md file. The CLAUDE.md handles permanent project context: your architecture, global conventions, what to avoid everywhere. prompt-mini handles per-task clarification. One sets the baseline. The other closes the gaps.
Try it here: github.com/nidhinjs/prompt-mini ⭐
Frequently Asked Questions
Q: What happens if the plugin rewrites your prompt wrong?
You see the rewritten prompt before Claude executes it, so you catch mistakes immediately. Worst case: the plugin makes a vague prompt look confidently wrong, and you abort and re-prompt with better context. It’s a safety check, not a guarantee.
Q: Should you use CLAUDE.md or prompt-mini?
CLAUDE.md is permanent , write your project spec once and Claude reads it automatically for every task. prompt-mini is interactive , it asks clarifying questions on demand. Use CLAUDE.md for ongoing projects; use prompt-mini for one-off tasks or exploration.
Q: Does this work mid-conversation or with other Claude tools?
It intercepts new prompts, not past messages. If you’re deep in a chat with Opus and ask something new, prompt-mini refines just that input , it doesn’t reach back into history. For multi-turn context, include key scope in your prompt or use CLAUDE.md.
Q: When does prompt-mini actually help , big refactors or small fixes?
Best for vague, open-ended work where Claude would guess: building features, refactoring sections, choosing approaches. For surgical fixes, you already have context, so the interception adds friction. Real value is catching ambiguous requests before they burn credits on re-runs.
I built a Claude Code plugin that intercepts vague prompts and executes a improved version. Tired of wasting credits on bad prompts.
by u/CompetitionTrick2836 in PromptEngineering