Type any of these into a session as written. The note under each one says what to expect and which words do the work.
Add a dark mode toggle to the settings page and remember the choice.A good first job. Small, visible, and easy to check. The agent will read your settings page, add the control and the stylesheet, and ask before it writes.
Run the tests. Fix whatever fails, one at a time, and tell me what you changed.Say "one at a time" and you get a readable trail instead of one big diff. Expect a few OK cards, one per file it touches.
Read every CSV in data/ and tell me which customers cancelled in August.Analysis with no code change. The agent writes a small script, runs it, and answers. If the columns are unclear it will ask what they mean.
Write a README for this folder. Keep it under 200 words and do not invent features.The word limit and the "do not invent" line matter. Without them you get a page of adjectives.
Find every place we call the old payments API and list them with line numbers. Do not change anything yet."Do not change anything yet" turns an agent into a very fast reader. Review the list, then send the change as a second request.
Rename the User model to Account everywhere, including tests and migrations.A wide change. Run it in its own pane and let it work while you do something else. Check the migration by hand before you run it.
Draft release notes from the git log since the last tag. Group by feature, plain English, no commit hashes.Good for a second agent while the first is coding. Point it at the same folder and it reads the same history.
Set up a GitHub Actions workflow that runs the tests on every push.The agent knows the YAML. You will be asked once to create the .github folder, once to write the file.
Explain what src/auth/passkey.ts does, like I am new to the codebase.No files change. Use this on any file you are about to edit yourself.
Make the checkout page work on a 375 pixel wide phone. Show me the CSS before you apply it."Show me before you apply it" is the safest way to hand over a stylesheet you care about.
Turn this CSV of contacts into a SQL insert script for the customers table. Skip rows with no email.The kind of ten-minute chore that used to take an afternoon. Look at the first few rows of the output before running it against a real database.
Build an MCP connector for the weather API at this URL, register it for this project, and tell me what tools it exposes.MoveMyCode copies the connection to every agent that reads the standard config, so the connector works in the next session too.
Say what "done" looks like. "Fix the bug" is a wish; "the test in tests/cart.test.js passes" is a job. Say what not to touch, when it matters. And ask for the plan first on anything wide: "tell me how you would do this before you start" costs one message and saves ten.