Claude prompt for code generation: Migration Script (Advanced)
Claude · Code Generation · Advanced
You are a systems thinker using Claude for code generation, specifically migration script.
Job: forward and back.
Audience: dba. Constraint: idempotent.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Looking for a Claude prompt for migration script? Start here — the advanced angle focuses on constraints, evaluation, and edge cases. Teams report saving 15–30 minutes per task when prompts include constraints up front. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
When to use this prompt
For Anthropic models, code generation prompts fail when they mix strategy and execution. This migration script brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Asks for a self-check pass, which cuts hallucinated details.
- Keeps code generation vocabulary specific instead of buzzwords.
- Locks the audience (dba) before style so tone stays honest.
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Name the success metric aloud: forward and back. If the draft cannot pass it, do not polish prose yet. For code generation work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Use precise and demanding follow-ups only — mixing tones mid-thread confuses Anthropic models. Functions, refactors, tests, and architecture sketches. Keep that context in the thread when you iterate. Save the winning variant for migration script — teams with a short library ship faster.
Have Claude list assumptions about code generation before drafting. Delete any you cannot defend. For migration script in code generation, the failure mode is usually no example. This prompt blocks that by design — especially "idempotent". Expect two minutes customizing and two minutes editing for Advanced output. Anthropic models still need your facts for migration script; they cannot invent metrics or brand rules. developers teams bookmark slug migration-script-advanced when constraints, evaluation, and edge cases matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (dba, offer, timeline).
- Confirm the constraint is still visible: idempotent.
- For code generation work, paste a rubric and ask for a self-score.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Migration Script, 3 short sections, bullet list of recommendations, closing line that states idempotent. Facts you supply appear; nothing invented.
Common mistakes
- Using the Advanced prompt but editing it into a vague one-liner.
- Ignoring the output contract headings.
- Accepting the first draft without checking forward and back.
Expert notes
Practitioners choose Advanced when migration script needs constraints, evaluation, and edge cases. Claude from Anthropic still needs your facts — especially for idempotent.
For code generation, compare this Advanced prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on forward and back.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a migration script piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Document what changed when you customized slug migration-script-advanced.
- Keep idempotent visible in the prompt, not only in your head.
- Compare against other Claude angles on the same use case before you standardize.
- Ship a draft, then tighten. Do not chase a perfect first token.
- dba should recognize themselves in the first paragraph.
FAQ
- What is a Claude prompt for migration script?
- It is a structured brief that tells Claude how to produce code generation output for dba. This advanced version stresses constraints, evaluation, and edge cases and keeps "idempotent" in the instructions.
- How do I customize this Claude code generation prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "idempotent" should stay unless your brief truly changed.
- Why use the advanced angle for migration script?
- Different angles solve different failures. Advanced helps when dba need constraints, evaluation, and edge cases. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.