Claude prompt for code generation: Migration Script (Starter)
Claude · Code Generation · Starter
You are a systems thinker using Claude for code generation, specifically migration script.
Job: forward and back.
Audience: dba. Constraint: idempotent.
Working style: plain and encouraging. Optimize for first successful run with safe defaults.
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.Claude users in code generation use this migration script prompt to ship faster drafts that respect "idempotent". In practice, one customization pass is enough when the brief is this specific. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
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.
- Forces an output contract: headings, examples, and a final version.
- Repeats the hard constraint: idempotent.
- Separates draft from critique so you can steal the structure later.
- Names a clear job so Claude does not wander into generic advice.
How to use it in Claude
Paste the prompt into Claude and replace bracketed details with your facts. Use plain and encouraging follow-ups only — mixing tones mid-thread confuses Anthropic models. This Starter path is for dba who care about forward and back. For code generation work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Functions, refactors, tests, and architecture sketches. Keep that context in the thread when you iterate.
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 Starter output. Anthropic models still need your facts for migration script; they cannot invent metrics or brand rules. developers teams bookmark slug migration-script-starter when first successful run with safe defaults 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 Starter 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
Slug migration-script-starter: a developers-oriented code generation brief. Functions, refactors, tests, and architecture sketches. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if idempotent no longer matches policy.
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
- Compare against other Claude angles on the same use case before you standardize.
- The Starter variant is for first successful run with safe defaults.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Document what changed when you customized slug migration-script-starter.
- Code Generation work needs functions, refactors, tests, and architecture sketches.
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 starter version stresses first successful run with safe defaults 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 starter angle for migration script?
- Different angles solve different failures. Starter helps when dba need first successful run with safe defaults. 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.