30 Claude Code Prompts for CLAUDE.md
Paste the stack, the test command, and off-limits files. Claude Code writes or tightens CLAUDE.md in that scope and does not invent a second style guide. Not a novel and not a secret dump.
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. Hand-curated and tested by the AI Academy team.
Write
5 promptsNew File
1/30✨ What it does
Claude Code writes a short CLAUDE.md in [STACK] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a claude.md writer working in Claude Code. <context> I need you to write a short CLAUDE.md. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [STACK] - Test: [TEST] - Off: [OFF] - Files: [FILES] </inputs> <task> 1. Short file in [FILES] 2. Stack from [STACK] 3. Test from [TEST] 4. Off from [OFF] </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 npm test.
Stack Only
2/30✨ What it does
Claude Code adds the stack section in [STACK] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a stack writer working in Claude Code. <context> I need you to add the stack section. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [STACK] - Files: [FILES] </inputs> <task> 1. Stack from [STACK] 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 Redis.
Test Command
3/30✨ What it does
Claude Code adds the test command in [TEST] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a test writer working in Claude Code. <context> I need you to add the test command I use. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [TEST] - Files: [FILES] </inputs> <task> 1. [TEST] 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 a coverage gate.
Off Limits
4/30✨ What it does
Claude Code adds off-limits files in [OFF] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are an off-limits writer working in Claude Code. <context> I need you to add off-limits files. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [OFF] - Files: [FILES] </inputs> <task> 1. [OFF] 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 .env if I did not say.
How To Run
5/30✨ What it does
Claude Code adds how to run locally in [RUN] 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 add how to run locally. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [RUN] - Files: [FILES] </inputs> <task> 1. [RUN] 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 docker compose.
Tighten
5 promptsCut Novel
6/30✨ What it does
Claude Code cuts CLAUDE.md down in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a cutter working in Claude Code. <context> I need you to cut CLAUDE.md down. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Cap: [CAP] - Keep: [KEEP] </inputs> <task> 1. Under [CAP] 2. Keep [KEEP] 3. Stay in that file </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: A short file gets read.
Dedup
7/30✨ What it does
Claude Code dedupes CLAUDE.md in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a deduper working in Claude Code. <context> I need you to dedupe CLAUDE.md rules. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Keep: [KEEP] </inputs> <task> 1. Merge repeats 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: Do not add a new rule.
Voice
8/30✨ What it does
Claude Code matches our voice in CLAUDE.md in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a voice editor working in Claude Code. <context> I need you to make CLAUDE.md sound like us. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Sample: [SAMPLE] </inputs> <task> 1. Match [SAMPLE] 2. Keep 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: If no sample, stay plain.
No Secrets
9/30✨ What it does
Claude Code strips secrets from CLAUDE.md in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a secrets cutter working in Claude Code. <context> I need you to strip secrets from CLAUDE.md. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Files: [FILES] </inputs> <task> 1. Strip keys 2. Stay in [FILES] 3. Point to env names I gave only </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 AWS_KEY.
Commands Honest
10/30✨ What it does
Claude Code keeps real commands in CLAUDE.md in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a commands editor working in Claude Code. <context> I need you to keep only commands I run. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Commands: [COMMANDS] </inputs> <task> 1. Only [COMMANDS] 2. Drop the rest </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 make test.
Sections
5 promptsPR Rule
11/30✨ What it does
Claude Code adds the PR rule 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 pr writer working in Claude Code. <context> I need you to add the PR rule I have. 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] </inputs> <task> 1. [RULE] 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 conventional commits.
Branch Rule
12/30✨ What it does
Claude Code adds the branch rule 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 branch writer working in Claude Code. <context> I need you to add the branch rule I have. 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] </inputs> <task> 1. [RULE] 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 main vs master.
DB Rule
13/30✨ What it does
Claude Code adds the DB rule 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 db writer working in Claude Code. <context> I need you to add the DB rule I have. 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] </inputs> <task> 1. [RULE] 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 prisma db push.
Product Rule
14/30✨ What it does
Claude Code adds the product rule 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 product writer working in Claude Code. <context> I need you to add the product rule I have. 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] </inputs> <task> 1. [RULE] 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 we never use dashes.
Links
15/30✨ What it does
Claude Code adds CLAUDE.md links in [LINKS] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a links writer working in Claude Code. <context> I need you to add links I have. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [LINKS] - Files: [FILES] </inputs> <task> 1. Only [LINKS] 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 wiki.
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. 300+ tutorials and growing.
Nest
5 promptsNested
16/30✨ What it does
Claude Code adds a nested CLAUDE.md in [DIR] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a nested writer working in Claude Code. <context> I need you to add a nested CLAUDE.md. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [DIR] - Extra rules: [RULES] - Files: [FILES] </inputs> <task> 1. Nested file for [DIR] 2. Only [RULES] 3. Do not repeat the root </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 second stack.
Import Honest
17/30✨ What it does
Claude Code adds a CLAUDE.md import in [IMPORT] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are an import writer working in Claude Code. <context> I need you to add an import I have. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [IMPORT] - Files: [FILES] </inputs> <task> 1. [IMPORT] 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 @parent.
Monorepo
18/30✨ What it does
Claude Code maps monorepo packages in [PACKAGES] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a monorepo writer working in Claude Code. <context> I need you to map packages I named. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [PACKAGES] - Files: [FILES] </inputs> <task> 1. Map [PACKAGES] 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 package.
Personal Vs Shared
19/30✨ What it does
Claude Code splits shared and personal rules in [SHARED] [PERSONAL] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a split writer working in Claude Code. <context> I need you to split shared vs personal rules. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [SHARED] [PERSONAL] - Files: [FILES] </inputs> <task> 1. Shared in repo file 2. Personal noted as local only if I said </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 commit personal secrets.
Stale Hunt
20/30✨ What it does
Claude Code cuts stale CLAUDE.md lines in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a stale hunter working in Claude Code. <context> I need you to cut stale CLAUDE.md lines. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Still true: [TRUE] </inputs> <task> 1. Keep [TRUE] 2. Cut the rest or UNVERIFIED </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 we still use X.
Stop
5 promptsAsk First
21/30✨ What it does
Claude Code plans CLAUDE.md then waits in [GOAL] 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 CLAUDE.md then wait. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [GOAL] - 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 until I say go.
One File
22/30✨ What it does
Claude Code edits one CLAUDE.md in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a one-file writer working in Claude Code. <context> I need you to edit one CLAUDE.md only. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Goal: [GOAL] </inputs> <task> 1. Only [FILE] 2. [GOAL] </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 spawn nested files.
No Style Guide
23/30✨ What it does
Claude Code avoids a new style guide in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a style cutter working in Claude Code. <context> I need you to do not invent a style guide. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - Keep: [KEEP] </inputs> <task> 1. Keep [KEEP] 2. No new lint religion </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: A style guide is out of scope.
Match Existing
24/30✨ What it does
Claude Code matches existing CLAUDE.md tone in [GOAL] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a match writer working in Claude Code. <context> I need you to match existing CLAUDE.md tone. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [GOAL] - Files: [FILES] </inputs> <task> 1. Match 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 headers we do not use.
Fence Off Limits
25/30✨ What it does
Claude Code honors CLAUDE.md off limits in [GOAL] 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 while editing CLAUDE.md. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [GOAL] - 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: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Fixes
5 promptsUndo Wander
26/30✨ What it does
Claude Code reverts extra markdown 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 markdown. 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 rules </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.
File Plus Test
27/30✨ What it does
Claude Code writes CLAUDE.md plus the test command in [STACK] 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 CLAUDE.md plus test command. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [STACK] - Test: [TEST] - Files: [FILES] </inputs> <task> 1. Short file 2. [TEST] </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: Test stays one line.
File Plus Off
28/30✨ What it does
Claude Code writes CLAUDE.md plus off limits in [STACK] 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 CLAUDE.md plus off limits. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [STACK] - Off: [OFF] - Files: [FILES] </inputs> <task> 1. Short file 2. [OFF] </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 a list.
Humanize
29/30✨ What it does
Claude Code humanizes CLAUDE.md in [FILE] 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 CLAUDE.md. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - 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 a note to a teammate.
Verify Commands
30/30✨ What it does
Claude Code marks unverified commands in [FILE] without wandering outside the files you named. Plan if more than two files change, then tell me what you ran.
You are a verifier working in Claude Code. <context> I need you to mark unverified commands. Stay inside the scope I name. Do not refactor neighbors. Do not add packages I did not ask for. </context> <inputs> - Primary: [FILE] - I have run: [RAN] </inputs> <task> 1. Keep [RAN] 2. Tag the rest UNVERIFIED </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 that make works.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.