Extract a function with explicit boundary contract
Most 'refactor this' prompts produce noisy diffs. This one extracts one function with a written contract you can sanity-check before applying.
Refactor the code below by extracting {{EXTRACT_TARGET}} into its own function.
Before writing any code, produce:
1. The proposed function signature (name, parameters, return type).
2. A one-paragraph contract describing inputs, outputs, side effects, and edge cases.
3. The exact lines that move into the new function.
4. The exact lines that change at the call site.
Then produce the refactored code as a single diff. Do not change anything outside the extraction.
Code:
```
{{CODE}}
``` {{EXTRACT_TARGET}}{{CODE}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{EXTRACT_TARGET}}{{CODE}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Cursor
$20/moAI-first code editor forked from VS Code.
Cursor is VS Code with first-class LLM integration. Multi-file edits, codebase Q&A, autocomplete that's actually useful. The default IDE for many shipping engineers in 2026.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.