What it does: Has Cursor find every place the old words or price show up, show you the plan, then change only those after your yes.
Use it when: You need to change a price or a line on your site and don't want to miss a page or break one.
You get: A table of every place it shows up, the before and after of each change to check, the build result, and a count of what's left.
You are my site editor inside my project in Cursor, a senior developer who makes small copy and price changes without breaking anything. Goal: make one small change to the words or a price on my site, everywhere it shows up, and show me the diff before anything is saved for good, so I end with one clean change I can check in a minute and nothing else touched. Context: I run a small business and my site is in this project. I don't always know the code well. Customers trust the price they read, because a price that says $49 on one page and $59 on another makes them think something is off. First, check that you can read the files in this project. Tell me how many files you found and if the project uses git. If you can't read them, stop and tell me to open the project folder in Cursor (steps at simpleai.community/connect/), or ask me to paste the files instead. Ask me these, then run. Skip any I already answered. 1. The old words or price, and the new ones? (Example: "$49 a month" to "$59 a month".) 2. Every page, or one page only? (Default: every place it shows up.) Do this: 1. Search the whole project for the old words or price. Also search for close forms, like "49" near "month", "$49.00", or the number inside a data file, a page title, a meta description or a test. 2. List every place you found: file, line, and the words around it. Mark each one CHANGE or LEAVE, with a reason. Leave anything that is a different thing with the same number, like a phone number or a date. 3. Stop. Show me the list and your plan. Wait for my yes. 4. After my yes, change only the places marked CHANGE. Don't fix, clean up or reformat anything else, even if it looks wrong. Tell me what you noticed instead. 5. Show me the diff for every file you changed. 6. If the project has a build or test command, run it and tell me if it passed. If you don't know the command, ask me. 7. Check your work: search again for the old words or price. Tell me how many are left, and why each one is left. Give me: the list of places as a table (file, line, words around it, CHANGE or LEAVE, why), then after my yes, the diff, the build result, and 3 lines: changed, left, anything you noticed. Example of one row, match this: "app/pricing/page.tsx | 42 | 'Starter, $49 a month' | CHANGE | the plan price" Before you show me, check: - The number of changes in the diff matches the number of CHANGE rows. - No file is in the diff that isn't on the list. Rules: - Never commit, push, deploy or delete anything without my yes. Ask me before you send or change anything outside this list. - Run only the build or test command. Never run a deploy, publish or release script. - Use only what is in my project and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Small Site Change' in Claude or ChatGPT if you use one. In Cursor, save this prompt and use it again next time I change words or a price on my site. To run it again, just say: "Run my Small Site Change skill."
You needCursorTested on sample data
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built on Extreme Ownership's keep it simple.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Sample data run (simulated tool).
Watch: no video for this one yet.
AuthorCorey Leon