Prompts worth copying, filed by what they are for: coding agents, Grok Bots, design and writing. Copy one into your tool, or post it to X.
Before you write any code, read README.md and the three files most related to this task. Give me a numbered plan: the files you will touch and the tests you will add. Stop and wait for my OK.
Prompts for Claude Code, Cursor, Aider and the other agents that touch your repo.
Before you write any code, read README.md and the three files most related to this task. Give me a numbered plan: the files you will touch and the tests you will add. Stop and wait for my OK.
Review this diff as a senior engineer who has never seen the codebase. Bugs first, then risks, then nits. For each one, quote the line and show the fix.
Make the failing test pass with the smallest change you can. Do not touch files outside the source folder (src/ or your equivalent). Show me the diff and explain it in two sentences.
Write a commit message for the staged changes: a title under 50 characters, a blank line, then what changed and why in plain words. No bullet points.
Routines and rules to paste into a Grok Bot so it does one job well.
About 10 minutes before each meeting, send me a five-line brief: who's attending, why we're meeting, the last thread with them, anything open, and one question worth asking.
Read the mail from my kids’ schools. Send a digest on Sunday evening. Interrupt me the same day only for: a closure, a form due within 48 hours, or anything marked urgent.
Once a day, check my inbox for new order confirmations. For each one, note the return deadline and the warranty. Message me three days before any deadline, with the order and the amount.
Critiques and build specs, from a screenshot or a Figma frame.
Look at this screenshot as someone who has never seen the product. Rank the five biggest problems by how much they would hurt a first visit. For each, say what to change, in one line.
From this Figma frame, write a build spec: components, their states, spacing and type tokens, and every interaction. Flag anything the design leaves undecided.
Edits, rewrites and alt text that keep your voice.
Write alt text for this image in one line. Lead with the part that matters most to the point of the page. No “image of”.
Pairs with
BotImogenRewrite this so a busy person gets it in one read. Keep my voice and every fact. Cut filler. No bullet points unless the original had them.
Found a prompt that earns its place? Send it with the tool or Bot it is for, and where you found it. Prompts from X are filed with a link to the post and the handle that wrote them.
Every prompt on this page has its own link, such as https://vibecodershq.com/prompts/coding#plan-first.