Claude Prompt Library

30 Claude Code Prompts for Migrations

30 copy-paste prompts

Name the schema change and the files. Claude Code writes or fixes migrations in that scope, plans expand-contract if you ask, and does not invent a destructive down. Not a rewrite of prod.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.

By Louis Corneloup · Founder, Techpresso

Last updated September 8, 2026·Drafted with AI assistance (how we make prompts)

Add

5 prompts

Add Column

1/30

✨ What it does

Claude Code adds the column in [COLUMN] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a migration writer working in Claude Code. <context> I need you to add this column in a migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COLUMN] - Table: [TABLE] - Files: [FILES] - Null: [NULL OR VERIFY] </inputs> <task> 1. Migration in [FILES] 2. Null or ask 3. No invented default that lies </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent NOT NULL without a default I gave.

Add Table

2/30

✨ What it does

Claude Code adds the table in [TABLE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a table writer working in Claude Code. <context> I need you to add this table in a migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [TABLE] - Columns I have: [COLS] - Files: [FILES] </inputs> <task> 1. Only [COLS] 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent created_at unless I asked.

Index

3/30

✨ What it does

Claude Code adds the index in [INDEX] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an index writer working in Claude Code. <context> I need you to add this index in a migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [INDEX] - Table: [TABLE] - Files: [FILES] </inputs> <task> 1. Index I named 2. Stay in [FILES] 3. Concurrent [VERIFY] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent CONCURRENTLY if I did not ask.

FK

4/30

✨ What it does

Claude Code adds the foreign key in [FK] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an fk writer working in Claude Code. <context> I need you to add this foreign key in a migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FK] - Files: [FILES] </inputs> <task> 1. FK I named 2. Stay in [FILES] 3. On delete [VERIFY] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent CASCADE.

Enum

5/30

✨ What it does

Claude Code adds the enum value in [VALUE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an enum writer working in Claude Code. <context> I need you to add this enum value in a migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [VALUE] - Files: [FILES] </inputs> <task> 1. Value I named 2. Stay in [FILES] 3. Plan old rows [VERIFY] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a backfill.

Safe

5 prompts

Expand

6/30

✨ What it does

Claude Code does expand-contract in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an expand writer working in Claude Code. <context> I need you to expand-contract this change. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Expand first 2. Stay in [FILES] 3. Contract later only if I asked </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not drop the old column yet.

Backfill

7/30

✨ What it does

Claude Code writes the backfill in [RULE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a backfill writer working in Claude Code. <context> I need you to backfill I described. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [RULE] - Files: [FILES] - Batch: [BATCH OR VERIFY] </inputs> <task> 1. Backfill from [RULE] 2. Batch or ask 3. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent 1000 rows.

Nullable First

8/30

✨ What it does

Claude Code makes the column nullable first in [COLUMN] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a null writer working in Claude Code. <context> I need you to make it nullable first. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COLUMN] - Files: [FILES] </inputs> <task> 1. Nullable now 2. Stay in [FILES] 3. NOT NULL later only if I asked </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not lock the table if I forbade it.

Dual Write

9/30

✨ What it does

Claude Code plans dual write in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a dual-write writer working in Claude Code. <context> I need you to plan dual write I asked. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Plan or code in [FILES] 2. No invented queue </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent Kafka.

Check First

10/30

✨ What it does

Claude Code adds the check in [CHECK] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a check writer working in Claude Code. <context> I need you to add a check I named. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHECK] - Files: [FILES] </inputs> <task> 1. Check from [CHECK] 2. Stay in [FILES] 3. NOT VALID [VERIFY] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent VALIDATE.

Fix

5 prompts

Broken

11/30

✨ What it does

Claude Code fixes the broken migration in [ERROR] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a migration fixer working in Claude Code. <context> I need you to fix this broken migration. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [ERROR] - Files: [FILES] </inputs> <task> 1. Fix in [FILES] 2. What you ran 3. No rewrite of later migrations unless I asked </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a SHA.

Down Honest

12/30

✨ What it does

Claude Code writes a safe down in [MIGRATION] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a down writer working in Claude Code. <context> I need you to write a down that is safe. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [MIGRATION] - Files: [FILES] </inputs> <task> 1. Down in [FILES] 2. If data would die, say so and ask </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not drop prod data quietly.

Rename

13/30

✨ What it does

Claude Code renames without breaking reads in [OLD] [NEW] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a rename writer working in Claude Code. <context> I need you to rename without breaking reads. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [OLD] [NEW] - Files: [FILES] </inputs> <task> 1. Expand rename in [FILES] 2. No drop yet if I said so </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a view unless I asked.

Type Change

14/30

✨ What it does

Claude Code changes the type safely in [COLUMN] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a type writer working in Claude Code. <context> I need you to change this type safely. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COLUMN] - To: [TO] - Files: [FILES] </inputs> <task> 1. Safe path in [FILES] 2. Ask if you need a rewrite </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent USING.

Drop Later

15/30

✨ What it does

Claude Code plans the drop for later in [COLUMN] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a drop writer working in Claude Code. <context> I need you to do not drop yet, plan the drop. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [COLUMN] - Files: [FILES] </inputs> <task> 1. Plan only or a no-op note 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Drop is a later GO.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. The library keeps growing.

Try AI Academy Free

Run

5 prompts

Command

16/30

✨ What it does

Claude Code uses my migrate command in [CMD] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a run writer working in Claude Code. <context> I need you to use my migrate command only. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CMD] - Files: [FILES] </inputs> <task> 1. Use [CMD] 2. Stay in [FILES] 3. Paste what happened </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent prisma migrate.

Dry Run

17/30

✨ What it does

Claude Code dry-runs the migration in [CMD] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a dry-run writer working in Claude Code. <context> I need you to dry-run the migration if I can. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CMD] - Files: [FILES] </inputs> <task> 1. Dry-run [CMD] if possible 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent --dry-run.

Prod Note

18/30

✨ What it does

Claude Code writes prod migrate notes in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a prod writer working in Claude Code. <context> I need you to write prod migrate notes. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - How we ship: [SHIP OR VERIFY] </inputs> <task> 1. Notes from [SHIP] or ask 2. Stay about [CHANGE] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent downtime 0.

Lock Note

19/30

✨ What it does

Claude Code notes migration locks in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a lock writer working in Claude Code. <context> I need you to note locks this may take. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Locks from what I know 2. UNVERIFIED otherwise </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent ACCESS EXCLUSIVE.

Order

20/30

✨ What it does

Claude Code orders the migrations in [LIST] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an order writer working in Claude Code. <context> I need you to order these migrations. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [LIST] - Files: [FILES] </inputs> <task> 1. Order [LIST] 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent a missing file.

Stop

5 prompts

Ask First

21/30

✨ What it does

Claude Code plans the migration then waits in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a plan writer working in Claude Code. <context> I need you to plan the migration then wait. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Plan only 2. Wait for GO </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not write SQL until I say.

No Prod

22/30

✨ What it does

Claude Code skips a prod migrate run in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a prod cutter working in Claude Code. <context> I need you to do not run against prod. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Files only 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Prod run is out of scope.

No Seed

23/30

✨ What it does

Claude Code skips invented seed data in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a seed cutter working in Claude Code. <context> I need you to do not invent seed data. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Schema only unless I gave rows 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent admin@.

Match Tool

24/30

✨ What it does

Claude Code uses our migrate tool in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a tool matcher working in Claude Code. <context> I need you to use our migrate tool only. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Tool: [TOOL] - Files: [FILES] </inputs> <task> 1. [TOOL] only 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Do not invent Flyway if we use Prisma.

Off Limits

25/30

✨ What it does

Claude Code honors migration off limits in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a fence writer working in Claude Code. <context> I need you to honor off limits on migrations. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Off: [OFF] - Files: [FILES] </inputs> <task> 1. Honor [OFF] 2. Stay in [FILES] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Off limits stays off.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: hands-on tutorials on Claude, ChatGPT, Midjourney, and many other AI tools. New tutorials are added regularly.

Start Your Free Trial

Fixes

5 prompts

Undo Wander

26/30

✨ What it does

Claude Code reverts extra migration files in [DIFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a scope writer working in Claude Code. <context> I need you to revert extra migration files. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIFF] - Allowed: [FILES] </inputs> <task> 1. Revert extras 2. Keep the change </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Neighbors stay.

Mig Plus Note

27/30

✨ What it does

Claude Code writes a migration plus apply note in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a combo writer working in Claude Code. <context> I need you to migration plus apply note. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Cmd: [CMD] - Files: [FILES] </inputs> <task> 1. Migration 2. How I apply with [CMD] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Note stays local.

Mig Plus Down

28/30

✨ What it does

Claude Code writes a migration plus safe down in [CHANGE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a combo writer working in Claude Code. <context> I need you to migration plus safe down. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [CHANGE] - Files: [FILES] </inputs> <task> 1. Up 2. Safe down or ask </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Down must not quietly drop data.

Humanize

29/30

✨ What it does

Claude Code humanizes the migrate note in [NOTE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are a humanizer working in Claude Code. <context> I need you to humanize the migrate note. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [NOTE] - Keep: [KEEP] </inputs> <task> 1. Cut delve 2. Keep [KEEP] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: It should sound like ops.

Unverified SQL

30/30

✨ What it does

Claude Code tags invented SQL in [SQL] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.

You are an honesty writer working in Claude Code. <context> I need you to tag invented SQL. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [SQL] - Facts: [FACTS] </inputs> <task> 1. Tag extras 2. Stay about [FACTS] </task> <constraints> - Plan before you edit if more than two files change. - Do not touch files I mark OFF LIMITS. - Run the test command I gave. If I gave none, ask before inventing one. - Do not invent APIs, env vars, or tickets. </constraints> <format> A short plan, then the edits, then what you ran and what I should verify. </format>

💡

Pro tip: Drop invented tables.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

They are written for Claude Code in the terminal: plan, edit, test, and stay inside migrations. You can paste a shorter version into claude.ai if you are not in a repo.

Each prompt sets scope and non-goals. Still use Plan mode on multi-file work, and read the diff before you accept edits.

It helps. A short CLAUDE.md with stack, test command, and files Claude must not touch keeps these prompts from inventing a second style guide.

The prompts are free to copy. Claude Code needs your Anthropic login and uses your plan's usage. Local files never leave your machine except through that session.

The hub is a 21-prompt overview. This page is only migrations: thirty copy-paste jobs with scope, verify, and non-goals already written.

Prompts are the starting line. Tutorials are the finish.

A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.

Start 7-Day Free Trial Explore AI for Entrepreneurs

7-day free trial. Cancel anytime.

Browse All Claude Prompt Collections Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts