Claude prompt for code generation: Migration Script (Workflow)
Claude · Code Generation · Workflow
You are a systems thinker using Claude for code generation, specifically migration script.
Job: forward and back.
Audience: dba. Constraint: idempotent.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
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.A Claude prompt for code generation is a copy-ready brief for migration script aimed at dba. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
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
- Centers forward and back so success is observable.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Repeats the hard constraint: idempotent.
- Separates draft from critique so you can steal the structure later.
- Keeps code generation vocabulary specific instead of buzzwords.
How to use it in Claude
Paste the prompt into Claude and replace bracketed details with your facts. For code generation work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Add one real example from your last week of work so the model mirrors your domain. This Workflow path is for dba who care about forward and back. Name the success metric aloud: forward and back. If the draft cannot pass it, do not polish prose yet.
Start with the ugly first pass for migration script. Name what is wrong in five bullets, then rerun in Claude. 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 Workflow output. Anthropic models still need your facts for migration script; they cannot invent metrics or brand rules. developers teams bookmark slug migration-script-workflow when step order, checkpoints, and handoffs 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.
- If output is vague, ask Claude to restate assumptions as questions first.
- 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 Workflow 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
Anthropic users working on migration script in code generation should treat "idempotent" as non-negotiable. Functions, refactors, tests, and architecture sketches. When dba run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste idempotent as the first follow-up message — do not rewrite the whole prompt.
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
- Keep idempotent visible in the prompt, not only in your head.
- Claude improves when you paste a real snippet or reference still.
- Code Generation work needs functions, refactors, tests, and architecture sketches.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Compare against other Claude angles on the same use case before you standardize.
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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for migration script?
- Different angles solve different failures. Workflow helps when dba need step order, checkpoints, and handoffs. 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.