“Add rate limiting
to search, like login.”
Clear to you. The agent still has to find the files, guess the pattern and work out how to check its own work.
THE INTENT IS THEREV8 ADVANCED PROMPT / 0.5.0
It knows
your project.
Type a rough request in Claude Code or Codex and press one key. v8 rewrites it in place as a short, outcome-first brief grounded in your repository: real file paths, your actual test command, and questions only when they matter.
Start with v8MADE FOR YOUR FLOW
Claude Code/Codex
PROMPT WORKSPACE
YOUR STARTING POINTCtrl ⇧ .
make the checkout page remember the cart after a reload, same way we keep the login session
01Read repo02Ground03Review
checkout-cart-persist.mdCLAUDE CODE BRIEF
## Goal Make the checkout page keep the cart after a reload, the same way we already keep the login session. ## Context - The session is the pattern to follow: inspect @src/lib/session.ts first. - The cart lives in @src/features/cart/store.ts. ## Done when - [ ] Items added to the cart are still there after a reload. - [ ] `pnpm test` passes
Ready to reviewCurated example
Curated illustrations, not captured model outputs. Paths and commands come from your repository; review before Enter.
ONE COMMAND. YOUR OWN TERMINAL.Start free. No account needed. Node.js 20+. Install guide ↗
npm install -g https://v8labs.app/downloads/v8-advanced-prompt-0.5.0.tgz01 / GROUNDED IN YOUR REPOSITORYSCROLL TO EXPLORE
02 / THE DIFFERENCE
Your repo, not a template.
Before the first line.
A generic prompt leaves the agent to search, guess and invent a test command. v8 reads a few facts about the repository you are in (names and commands, never file contents) and writes them into the brief.
“Add rate limiting
WITH V8 ADVANCED PROMPT
01
Your files, by path.
The route, the limiter to copy and its tests, named from your repository so the agent starts in the right place.
02
Done when your checks pass.
Observable outcomes, ending with the test command your project actually uses: pnpm test, pytest, cargo test.
03
Questions only when they matter.
At most three, and only for unknowns that change the result. Simple requests stay two to four lines.
Example prompt structure. Actual output depends on your request and repository, and requires your review.
03 / YOUR WORKFLOW, WITH CONTEXT
One shortcut.
Still your workspace.
No extra editor. No new conversation to manage.
Write it your way.
Type what you want in Claude Code or Codex. A rough thought is enough. Follow-ups like “now do the same for settings” work too when Claude Code shows its last reply in the editor.
It reads your repo, not your code.
Press Ctrl ⇧ . and v8 collects a few facts: stack, test command, matching file paths, recent commits. The prompt service writes the brief back into the same input box.
Answer, or skip.
In Claude Code, if an unknown would change the result, you get up to three numbered questions in the terminal; 0 skips. Answers are remembered for that repository, and the follow-up is free.
You make the call.
Review before Enter. Press the shortcut again to restore your original words.
04 / ROOM TO BUILD
A small tool.
A place in your flow.
Start free. Go Pro when it becomes
part of your everyday work.
Free
NO ACCOUNT NEEDED$0 / free plan
- 10 advanced prompts a week · 3 a day
- Claude Code and Codex
- Answering its questions is free
- Undo with the same shortcut
Pro
FOR YOUR DAILY FLOW$39 / year · or $4.99 / month
- Up to 350 advanced prompts a week
- No daily limit
- Every terminal you connect
A few things to know.
How does it know my project?
When you press the key, the CLI collects a small context pack from the repository you are in: its name, branch and whether there are uncommitted changes; the stack from your manifests; the test, build, lint, typecheck and run commands; which instruction files exist and which of them govern the files involved (CLAUDE.md, AGENTS.md, .cursor/rules); up to 8 file paths most relevant to your request, their test files and one existing file to follow as a pattern; up to 4 commands your CI runs (redacted); the last 5 commit subjects; and answers you confirmed earlier for that repository. To rank files, v8 searches file contents on your machine and sends only the names of the functions and classes that match; the contents are never sent. It is capped at 4 KB.
What leaves my computer?
The text in your input box and that context pack, only when you press the key, sent to our service and its AI provider. No file contents: not your code, not your .env. The one exception: when your manifests list no commands, up to 4 backticked command lines quoted from CLAUDE.md or AGENTS.md. Nothing is stored on our servers. Run v8-prompt context show to see exactly what would be sent, or v8-prompt context off to send the prompt alone.
When does it ask questions?
In Claude Code, only when an unknown would change the deliverable, stack, scope or data model: at most 3, with numbered options, and 0 skips. Answers are remembered on your computer for that repository (v8-prompt forget clears them). The follow-up with your answers does not count as a second prompt.
Is it different in Codex?
Codex is tuned to act rather than ask, so no questions are asked there. Unknowns become explicit assumption lines in the brief, which you can correct before pressing Enter.
Is there a Claude Code plugin?
Yes. The package includes a plugin with one command, /v8:prompt <request>, which hands Claude the advanced prompt as the task. It needs the CLI installed. See the install guide.
Can I use it without an account?
Yes. The free plan includes 10 advanced prompts per week, with a daily limit of 3.
What if I prefer my original prompt?
Press the shortcut again to restore it. Your coding agent receives the prompt only after you press Enter.
YOUR NEXT IDEA IS ENOUGH TO START.
Give it direction.