Free prompt library
1020 copy-and-paste prompts for ChatGPT, Claude, Gemini, Grok and leading image and video tools. Swap the [BRACKETED] parts for your details and go. New prompts are added regularly.
Built with love by Shushant Lakhyani. Building bestproductivityresources.com
Filter by what you want to do and the AI tool you use.
Category
Tool
Showing 1020 of 1020 prompts
I keep running into this problem: [DESCRIBE PROBLEM]. Use the 5 Whys method to dig past the symptoms. Ask me one question at a time, wait for my answer, and after five rounds state the most likely root cause, how confident you are, and the single smallest change that would test whether you're right.
I have to choose between [OPTION A] and [OPTION B] by [DEADLINE]. My priorities, in order, are: [PRIORITIES]. Build a weighted decision matrix, score each option 1-10 per priority with a one-line reason, show the totals, then tell me what new information would flip the result. End with a clear recommendation in one sentence.
Imagine it is six months from now and my plan has failed badly. The plan: [PLAN]. List the 7 most plausible reasons it failed, ranked by likelihood. For each, give an early warning sign I can watch for this month and one cheap action I can take now to prevent it.
I'm stuck on [PROBLEM] and don't know where to start. Break it into no more than 7 concrete sub-problems, order them so each unblocks the next, and mark which ones I can finish in under 30 minutes. Then tell me exactly what to do in the first 10 minutes.
Here is something stressing me out at work: [WORRY]. Separate it into (1) things I control, (2) things I can influence, and (3) things I can't change. For the first two groups give one specific next action each, with a time estimate. Keep the whole answer under 200 words.
I believe [POSITION/DECISION]. Write the strongest possible case against it, as a smart, informed skeptic would. Then list which of those objections are genuinely serious, which are weak, and what evidence would settle each one.
Our team keeps getting slowed down at this step: [BOTTLENECK]. Here is how the process works now: [PROCESS]. Suggest 5 fixes ranging from a 5-minute tweak to a bigger redesign. For each, estimate time saved per week, effort to implement, and the risk of making things worse.
Here is a list of tasks I spend my week on, with rough hours: [TASK LIST]. My main goal is [GOAL]. Apply the Pareto principle: identify the few tasks that likely produce most of the results, the ones I could cut, delegate or automate, and propose a new weekly time split.
Something stopped working: [WHAT BROKE]. It last worked [WHEN], and since then these things changed: [CHANGES]. Act as a methodical troubleshooter. List hypotheses from most to least likely, and for each give the quickest test that would confirm or rule it out. Start with tests that take under 2 minutes.
I need to raise a difficult topic with [PERSON/ROLE]: [ISSUE]. My goal is [OUTCOME] while keeping the relationship good. Give me an opening line, three key points phrased without blame, likely pushback with calm responses, and a clear ask to close the conversation.
Here is everything on my plate today: [TASKS]. I have [HOURS] hours of focused time, meetings at [TIMES], and my energy peaks around [TIME]. Pick my top 3 priorities, time-block the day in 30-60 minute chunks with buffers, put deep work at my peak, and list what to push to tomorrow without guilt.
Run me through a 15-minute weekly review. Ask one question at a time about: wins, what slipped and why, open loops, next week's top 3 outcomes, and one habit to adjust. After my answers, summarize my plan for next week in a short checklist I can paste into my notes.
My goal: [GOAL]. I can spend [TIME] per day on it, and my deadline is [DATE]. Create a 30-day plan split into weekly milestones and daily tasks no longer than [TIME]. Include a checkpoint each Friday where I decide whether to adjust, and flag the riskiest week.
Here is my to-do list: [LIST]. Sort every item into the Eisenhower matrix (do now, schedule, delegate, delete). Be ruthless: at least 20% should land in delete. Explain each delete in a few words, then give me the do-now list in order.
I need to finish [TASK] and keep getting distracted by [DISTRACTIONS]. Design a 90-minute focus session for me: setup checklist (2 minutes), Pomodoro-style intervals, what to do in each break, and a rule for handling sudden urges to check something. Keep it practical.
I'm running a [LENGTH]-minute meeting about [TOPIC] with [ATTENDEES]. The decision we need is [DECISION]. Write a tight agenda with timed items, the pre-read people should look at, the exact question to answer in each item, and a closing step that assigns owners and deadlines.
Every [FREQUENCY] I do this manually: [TASK STEPS]. I use these tools: [TOOLS]. Suggest ways to automate or template it, from no-code options to simple scripts. Rank them by setup time and time saved, and give step-by-step setup for the best one.
I want to hand off [TASK] to [PERSON/ROLE]. Write a delegation brief with: the goal and why it matters, what 'done' looks like, deadline, budget or limits, decisions they can make alone, when to check in, and links or context they need. Keep it skimmable.
Turn these rough notes about how I do [PROCESS] into a clear SOP: [NOTES]. Use numbered steps, note the tool used at each step, add common mistakes and how to avoid them, and finish with a quick quality checklist someone new could follow on day one.
I'm overwhelmed. Here is everything I'm carrying: [BRAIN DUMP]. Help me sort it into projects, single actions, waiting-on-others and someday items. Then pick the 3 actions that would reduce my stress the most if done by tomorrow, and draft a one-line message for anything I should renegotiate.
Edit the text below to be about 30% shorter. Keep every key idea and my voice, remove filler, hedging and repetition, and prefer short sentences and active verbs. After the edit, list the 3 biggest changes you made. [PASTE TEXT]
Turn these messy notes into a well-structured document for [AUDIENCE]: [NOTES]. Add a one-paragraph summary at the top, logical headings, and bullet points where they help. Flag anything that seems missing or contradictory instead of making it up.
Rewrite the text below so it sounds like a real person talking to a smart friend: plain words, varied sentence length, no buzzwords, no clichés like 'in today's fast-paced world'. Keep the facts exactly the same. [PASTE TEXT]
Proofread the text below for grammar, spelling, punctuation and clarity. Return the corrected version first, then a table of each change with the original, the fix, and a short reason. Don't change my tone or style unless something is unclear. [PASTE TEXT]
Write a 5-sentence executive summary of the document below for a busy [ROLE]. Sentence 1: the main point. Sentences 2-4: the evidence and impact. Sentence 5: the decision or action needed and by when. [PASTE DOCUMENT]
Rewrite this message three ways: for a senior executive (brief, outcome-focused), for a teammate (friendly, practical), and for a customer (warm, clear, no jargon). Keep the core information identical. [PASTE MESSAGE]
Act as a tough but fair editor. Review the draft below for [GOAL/AUDIENCE]. Point out the weakest argument, the most confusing paragraph, anything boring, and where a reader would stop reading. Give specific fixes, not general advice. [PASTE DRAFT]
Explain [COMPLEX TOPIC] so a smart 14-year-old would understand it. Use one everyday analogy, avoid jargon (or define it in brackets), and finish with three bullet points they could repeat to someone else.
Here is my article draft: [DRAFT]. Write 10 headline options in different styles (benefit, curiosity, number, how-to, contrarian) and 3 opening paragraphs that hook the reader in the first sentence. Mark your top pick and say why.
Analyze these samples of my writing: [SAMPLES]. Describe my voice in a short style guide: tone, sentence length, words I use, words I avoid, formatting habits. Make it something I can paste at the start of future prompts so AI writes like me.
Here's an email I received: [PASTE EMAIL]. Summarize what the sender actually wants in one line, then draft a reply that answers every question, keeps a [TONE] tone, and is under 120 words. Add a clear next step at the end.
Draft a short, kind email declining [REQUEST] from [PERSON/ROLE]. Give a brief honest reason without over-apologizing, offer [ALTERNATIVE, if any], and keep the door open for the future. Give me two versions: one warm, one more formal.
I emailed [PERSON] about [TOPIC] on [DATE] and got no reply. Write a follow-up under 80 words that adds something useful (a new detail, a deadline or an easy yes/no question), sounds friendly, and makes replying effortless.
Write a cold email to [ROLE] at [COMPANY TYPE] about [OFFER]. Keep it under 100 words, open with something specific about their situation, state one clear benefit, include proof in one line, and end with a low-effort ask. Give 3 subject lines under 6 words.
Here's a long email thread: [PASTE THREAD]. Give me: the decisions made, open questions, who owns what action and by when, and anything that sounds like a risk or disagreement. Use bullet points and keep it under 150 words.
Write an email to [PERSON] asking to move the deadline for [DELIVERABLE] from [DATE] to [NEW DATE]. Take responsibility briefly, explain the reason in one sentence, share what's already done, and propose a plan that protects quality. Professional and confident, not apologetic.
Turn these notes into a weekly project update email for stakeholders: [NOTES]. Use sections: Status (green/yellow/red with one-line reason), Done this week, Next week, Risks and help needed. Keep it scannable in under a minute.
A customer sent this: [PASTE EMAIL]. Draft a reply that acknowledges their frustration specifically, takes ownership where we're at fault, explains what we'll do and by when, and offers [REMEDY]. Calm and human, no corporate filler.
I keep answering these kinds of emails: [LIST TYPES]. Write a short, reusable template for each with [PLACEHOLDERS] for the parts that change. Keep each under 90 words and friendly but professional.
Write a thank-you email to [PERSON] for [WHAT THEY DID]. Mention the specific impact it had on [RESULT], keep it genuine and under 100 words, and avoid generic phrases like 'I really appreciate it'.
I need to understand [TOPIC] quickly for [PURPOSE]. Give me: a plain-English overview, the 5 key concepts with one-line definitions, the main debates or open questions, common misconceptions, and 3 high-quality sources to read next. Tell me what you're unsure about.
What are the most important developments about [TOPIC] in the last [TIMEFRAME]? Summarize each in two sentences, say why it matters for [MY ROLE/INDUSTRY], and link or name the sources. Separate confirmed facts from speculation.
Summarize the document below for someone who has 3 minutes. Give the main conclusion, 5 key findings with numbers where available, the methodology in one line, the limitations, and 3 questions I should ask the author. [PASTE DOCUMENT]
Compare [OPTION A], [OPTION B] and [OPTION C] for [USE CASE]. Make a table covering price, key features, ease of use, integrations, limits and best fit. Then recommend one for a [TEAM SIZE/BUDGET] team and explain the trade-off. Tell me which details I should double-check on their websites.
I want to support this claim: [CLAIM]. Find credible statistics or studies that support or contradict it, with source, year and sample size where possible. Flag anything outdated or weak, and suggest a more accurate way to phrase the claim if needed.
Research [COMPANY] as a competitor to [MY PRODUCT]. Summarize their positioning, target customers, pricing, recent launches, what users praise and complain about, and gaps I could exploit. Separate verified facts from your inferences.
I'm interviewing a [TYPE OF EXPERT] about [TOPIC] for [PURPOSE]. Write 12 open-ended questions that move from broad to specific, include 3 that challenge common assumptions, and add a follow-up for each to dig deeper.
Here are my raw research notes and quotes: [NOTES]. Group them into themes, name each theme, count how often it appears, pull the best supporting quote, and list the 3 most surprising or actionable insights.
I want to become competent in [SUBJECT] in [TIMEFRAME], spending [TIME] per week. Build a reading and learning plan with books, articles, courses and practice exercises in order, with one key takeaway to look for in each.
Fact-check the text below. List each factual claim, rate it as likely accurate, questionable or likely wrong, explain why, and say what source would confirm it. Don't rewrite the text; just audit it. [PASTE TEXT]
Here's a piece of content I made: [PASTE OR SUMMARIZE]. Turn it into: 3 LinkedIn posts, a 6-tweet thread, 2 short video scripts under 45 seconds, a newsletter intro, an Instagram carousel outline (8 slides) and a blog post outline. Keep the core message consistent.
Write an X thread about [TOPIC] for [AUDIENCE]. Start with a hook that makes a bold, specific claim, follow with 6-8 short posts each giving one useful insight or example, and end with a summary and a soft call to action. No hashtags, no emojis overload.
Create a detailed outline for a blog post targeting the keyword [KEYWORD] for [AUDIENCE]. Include a title, meta description under 155 characters, H2/H3 structure, key points under each, questions people also ask, and where to add examples or visuals.
I create content about [NICHE] on [PLATFORMS], posting [FREQUENCY]. Build a 4-week content calendar mixing educational, story, opinion and promotional posts. For each post give the hook, format and main takeaway. Keep it realistic for one person.
Write a [LENGTH]-minute YouTube script about [TOPIC]. Include a 10-second hook, a quick promise of what viewers will get, 3-5 main sections with b-roll suggestions, a mid-video retention line, and a strong ending with a call to action.
Turn this experience into a LinkedIn post: [STORY]. Open with a one-line hook, tell the story in short paragraphs, share the lesson clearly, and end with a question that invites comments. Under 220 words, honest, no humblebragging.
Write 20 hooks for short-form content about [TOPIC] aimed at [AUDIENCE]. Mix styles: surprising stat, mistake, contrarian take, question, before/after, and 'nobody tells you'. Each under 12 words.
Write a newsletter issue about [TOPIC] for [AUDIENCE]. Structure: a personal opener (2-3 sentences), one main idea explained with an example, 3 quick useful links or tips, and a sign-off with a question for readers to reply to. Friendly and under 500 words.
Write a product description for [PRODUCT] aimed at [CUSTOMER]. Lead with the main outcome, list 5 benefits (not just features), handle the top objection, and finish with a clear call to action. Give a short version (50 words) and a long one (150 words).
Plan a [LENGTH]-minute podcast episode on [TOPIC] with [GUEST/SOLO]. Include a cold open, intro, 4 segments with talking points and questions, a listener takeaway, and 3 clip-worthy moments to cut for social media.
Brainstorm 50 ideas for [GOAL/PROBLEM]. Go for quantity first, including some wild ones. Then score every idea on impact and effort (1-5), and show the top 5 quick wins and the top 3 bold bets with one sentence each on how to start.
Suggest 25 names for [PRODUCT/PROJECT], which is [DESCRIPTION] for [AUDIENCE]. Mix descriptive, invented, metaphor and two-word names. Keep them short, easy to spell and say. Mark the top 5 and note any that might have obvious trademark or domain issues to check.
Help me brainstorm solutions to [CHALLENGE] by thinking as 6 different people: a frugal startup founder, a customer, a designer, an engineer, a lawyer and a 10-year-old. Give 3 ideas from each, then combine the best into 3 strong concepts.
I have these skills: [SKILLS], about [HOURS] hours a week and a budget of [BUDGET]. Suggest 10 side project or small business ideas that fit. For each give the target customer, how it makes money, the first step to validate it this week, and a realistic difficulty rating.
Instead of asking how to fix [PROBLEM], list 15 ways we could make it much worse. Then flip each one into a positive action, and highlight the 5 flipped ideas that are most practical to try first.
Brainstorm 15 ideas for a [EVENT TYPE] for [AUDIENCE] with a budget of [BUDGET]. Include formats, a catchy title, a hook that makes people sign up, and one memorable moment for each. Mark which ones work online.
Use forced connections: take [MY PRODUCT/TOPIC] and combine it with each of these random concepts: a library, a video game, a subscription box, a farmers' market, a fitness tracker. Generate 2 practical ideas from each pairing and rate their originality.
My product is [PRODUCT] for [AUDIENCE]. List 15 different marketing angles (pain, aspiration, identity, fear of missing out, comparison, social proof, etc.). For each give a one-line headline and the channel where it would work best.
List 30 questions that [AUDIENCE] commonly ask about [TOPIC], including beginner, intermediate and expert questions. Mark the ones with the least good answers online so I can create content that stands out.
Apply the SCAMPER method (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse) to [IDEA/PRODUCT]. Give 2 concrete ideas per letter, then pick the 3 most promising and explain how to test each cheaply.
Explain what this code does, step by step, for someone who knows [LANGUAGE] basics. Then list any bugs, edge cases or security issues you notice, and suggest a cleaner version if one exists. [PASTE CODE]
I'm getting this error: [ERROR MESSAGE]. Here's the relevant code: [CODE]. My environment: [LANGUAGE/FRAMEWORK/VERSION]. Explain what the error means, list the likely causes in order, and give the fix for the most likely one. Ask me for more info if needed.
Write a [LANGUAGE] script that [TASK, e.g. renames files in a folder by date]. Include clear comments, handle errors gracefully, add a dry-run option, and explain how to run it on [OPERATING SYSTEM].
Review this code like a senior engineer doing a pull request review. Comment on correctness, readability, performance, security and test coverage. Prioritize issues as must-fix, should-fix and nice-to-have, with suggested changes. [PASTE CODE]
Write unit tests for the function below using [TEST FRAMEWORK]. Cover the normal cases, edge cases, invalid inputs and error handling. Use clear test names that describe the behavior. [PASTE FUNCTION]
In [EXCEL/GOOGLE SHEETS], my data looks like this: [DESCRIBE COLUMNS]. I want to [GOAL]. Give me the formula, explain how it works piece by piece, and show an alternative if my sheet has blank or messy cells.
My tables are: [TABLES AND COLUMNS]. Write a SQL query that [WHAT I WANT]. Explain each part, note any assumptions, and suggest an index if the query would be slow on a large table.
I want to build [APP IDEA] for [USERS]. Before any code, give me: core features for version 1 (max 5), the data model, the screens, a suggested simple tech stack, and a step-by-step build order I can finish in [TIMEFRAME].
Refactor the code below to be easier to read and maintain without changing its behavior. Use clear names, small functions and remove duplication. Show the new code, then a short list of what changed and why. [PASTE CODE]
Write a regular expression that matches [PATTERN DESCRIPTION] in [LANGUAGE]. Give 5 examples it should match and 5 it shouldn't, explain each part of the regex, and note any edge cases it misses.
Minimalist product photography of [PRODUCT] on a [COLOR] seamless background, soft diffused studio lighting, subtle shadow, centered composition, crisp detail, premium commercial look, shot on 85mm lens --ar 16:9 --style raw
Create a clean, flat-design infographic illustrating [CONCEPT] in [NUMBER] steps. Use a white background, a limited palette of [COLORS], simple icons for each step, short readable labels, and lots of white space. No tiny text.
Editorial illustration for a blog post about [TOPIC], modern flat vector style, bold shapes, limited palette of [COLORS], plenty of negative space on the left for a headline, friendly and professional --ar 21:9
Edit the uploaded photo: replace the background with [NEW BACKGROUND], keep the person's face, hair and clothing exactly the same, match the lighting direction and color temperature, and make the result look like a real photograph.
Square social media graphic with the text "[QUOTE]" in bold modern sans-serif typography, centered, high contrast on a [COLOR] gradient background, small subtle geometric shapes in corners, clean and readable
Cozy, organized home office desk at golden hour, laptop, notebook, coffee mug, small plant, warm natural window light, shallow depth of field, calm productive mood, realistic photography --ar 3:2
Create a realistic mockup of a [APP/WEBSITE TYPE] shown on a modern laptop and phone side by side on a clean desk. The interface should feel [STYLE: minimal/playful/corporate] with a [COLOR] accent color. Soft lighting, neutral background.
Create a friendly cartoon mascot for [BRAND/TOPIC]: a [ANIMAL/OBJECT] with [DISTINCTIVE FEATURES], simple rounded shapes, [COLORS]. Show it in 4 poses on a white background: waving, thinking, celebrating and pointing, keeping the design identical in each.
Abstract minimalist background for presentation slides, soft gradient from [COLOR 1] to [COLOR 2], subtle flowing shapes, lots of empty space for text, modern corporate style, no text --ar 16:9
Poster for "[EVENT NAME]" on [DATE], bold retro-modern design, large headline text, smaller subtitle "[SUBTITLE]", vibrant [COLORS], playful geometric shapes, clear hierarchy, print-ready
A slow, cinematic 360-degree orbit around [PRODUCT] on a reflective black surface, dramatic rim lighting, light particles drifting, ending on a close-up of the logo. Smooth camera motion, premium commercial feel, 8 seconds.
Bright modern office, a person types on a laptop as floating holographic charts and checkmarks appear above the keyboard, camera slowly pushes in, clean and optimistic mood, natural lighting, 6 seconds, no text on screen.
Animate the uploaded image: add gentle camera push-in, subtle movement in [ELEMENTS: hair, leaves, steam, clouds], keep the subject's face and the composition unchanged, calm and realistic motion, loopable 5-second clip.
A [CHARACTER] walks through [SETTING] at [TIME OF DAY], stops and notices [OBJECT/EVENT], reacts with [EMOTION]. Handheld camera following from behind, then a slow turn to the face. Cinematic color grading, natural sound of the environment.
Fast, energetic 5-second intro for a channel about [NICHE]: quick cuts of [3-4 RELATED VISUALS], bold colorful transitions, vertical 9:16 format, upbeat feel, ending on a clean empty frame for a logo.
Seamless looping background video of a softly blurred modern bookshelf and warm lamp, very slight camera drift, subtle bokeh lights, calm and professional, 10 seconds, suitable behind a speaker on a video call or recording.
Time-lapse of an empty, messy desk becoming a clean, organized workspace: items move into place, papers stack themselves, a plant grows slightly, light shifts from morning to afternoon. Top-down view, satisfying and smooth, 8 seconds.
Overhead close-up of hands [ACTION: writing a plan in a notebook / sketching on a tablet], steady camera, soft daylight, shallow depth of field, calm and focused mood, realistic detail, 7 seconds.
Write a 6-shot storyboard for a [LENGTH]-second video about [TOPIC] that I'll generate with an AI video tool. For each shot give: duration, camera movement, subject and action, lighting, and a ready-to-paste text-to-video prompt. Keep the visual style consistent.
Smooth aerial drone shot rising over [LOCATION/TYPE OF CITY OR LANDSCAPE] at sunrise, mist below, warm golden light, camera slowly tilts up to reveal the horizon, cinematic and peaceful, 8 seconds.
I'm considering this decision: [DECISION]. For each option, list the immediate consequences, then what happens because of those consequences in 6 months, and again in 2 years. Flag any outcome that looks good now but bad later, or the reverse. End with the option that holds up best over time and the one assumption I should test first.
Here are my tasks for the week: [LIST TASKS]. My energy is usually highest around [TIME] and lowest around [TIME]. Sort each task as deep work, shallow work, or admin, then build a Monday to Friday schedule that puts deep work in my high-energy hours and batches admin into low-energy slots. Leave a 30-minute buffer each day and tell me which task to drop if the week overflows.
Rewrite the text below so a smart 14-year-old could understand it on the first read. Replace jargon with everyday words, split long sentences, and keep every important fact. After the rewrite, list each term you replaced and what you replaced it with so I can check nothing lost its meaning. [PASTE TEXT]
Write a short email introducing [PERSON A, their role] to [PERSON B, their role]. Explain in one sentence each why they should talk, mention one specific thing they have in common, and suggest a clear next step. Keep it under 120 words, friendly but not gushing, and make it easy for either person to reply first.
I want to understand the debate around [TOPIC]. Build a table with the strongest arguments for and against, the best evidence behind each one, and how strong that evidence is (weak, moderate, strong). Note where experts genuinely disagree versus where the evidence is settled, and list three questions that are still open.
A customer asked: [QUESTION]. Turn it into a helpful FAQ-style blog post. Start with a direct two-sentence answer, then explain the why, give a short step-by-step if relevant, cover two related follow-up questions people usually ask, and end with a one-line call to action for [PRODUCT OR SERVICE]. Keep it skimmable with short paragraphs.
I need ideas for [GOAL]. Give me 5 ideas each under these constraints: zero budget, only one day to execute, must use something I already own, must involve another person, and must be the opposite of what competitors do. Then pick the three most promising across all lists and explain why in one line each.
Convert the following [SOURCE LANGUAGE] code into idiomatic [TARGET LANGUAGE]. Keep the same behavior, use the target language's standard libraries and conventions, and add brief comments where the approach differs from the original. After the code, list any behavior that might change (like number handling or error handling) and how to test it. [PASTE CODE]
Top-down flat-lay photo of productivity essentials on a light oak desk: an open notebook with a handwritten checklist, a ceramic coffee cup, a pen, a small plant, and a closed laptop. Soft natural window light from the left, gentle shadows, neutral warm tones, minimalist arrangement with plenty of empty space for text on the right. Photorealistic, high detail, 16:9.
A 10-second cinematic montage of a calm morning routine: sunlight slowly filling a bedroom, a hand opening curtains, steam rising from a cup of tea, a pen writing in a journal. Slow, smooth camera moves with shallow depth of field, warm golden light, soft color grade, no text, no faces visible. Gentle pacing that feels peaceful and focused.
Here is a problem I'm stuck on: [DESCRIBE PROBLEM]. Strip it down to first principles. List every assumption I'm probably making, mark which ones are actually true versus just habit or convention, then rebuild a solution from only the true facts. End with the single boldest option this reveals and the cheapest way to test it this week.
These are my fixed commitments this week: [LIST MEETINGS, CLASSES, ERRANDS]. These are the tasks I want to finish: [LIST TASKS WITH ROUGH TIME ESTIMATES]. Build a day-by-day plan that fits the tasks into the open gaps, adds a 25% buffer to every estimate, protects one deep-work block each day, and flags anything that will not fit so I can drop or delegate it now instead of on Friday.
Below is a messy transcript of me talking through an idea out loud: [PASTE TRANSCRIPT]. Turn it into a clean, well-structured piece of writing that keeps my voice, phrases, and opinions. Remove filler words and repetition, group related points under short subheadings, and keep it under [WORD COUNT] words. Then list any points I contradicted myself on so I can decide which one I mean.
Here are my rough notes from a meeting: [PASTE NOTES]. Write a short recap email to the attendees with three sections: decisions made, action items (each with one owner and a due date), and open questions. Keep it skimmable, under 150 words, with a friendly one-line opener and no fluff. If an action item has no clear owner in my notes, mark it [OWNER?] so I can fill it in.
I want to understand the debate around [TOPIC]. Identify the 3 to 5 biggest points where knowledgeable people genuinely disagree. For each one, explain both sides in their strongest form, the evidence each side leans on, and what new information would settle it. Finish with which questions are mostly settled and which are still truly open, and be clear about where your own knowledge may be out of date.
Turn this process into a 7-slide carousel for Instagram or LinkedIn: [DESCRIBE THE PROCESS OR PASTE THE GUIDE]. Slide 1 is a bold hook under 10 words. Slides 2 to 6 each cover one step with a short headline and one or two lines of supporting text. Slide 7 is a recap plus a call to save or share. Also suggest a simple visual idea for each slide and a caption under 100 words.
I need ideas for [GOAL OR PROBLEM]. First give me 15 deliberately terrible, ridiculous, or backwards ideas. Then go through each bad idea and flip it, find the hidden useful insight in it, or combine it with another to turn it into a workable idea. Finish with the top 3 workable ideas ranked by how easy they are to try and how surprising they are.
Here is my project: [DESCRIBE WHAT IT DOES, OR PASTE THE MAIN FILES AND PACKAGE CONFIG]. Write a README.md with a one-sentence summary, a short feature list, prerequisites, step-by-step install and run instructions, a usage example with code, configuration options in a table, and a troubleshooting section for the 3 most likely problems. Use plain language a beginner can follow and do not invent features that are not in the code.
Isometric 3D illustration of a tiny cozy home office floating on a single square tile: a desk with a laptop showing a kanban board, a wall calendar, a shelf of books, a plant, a warm desk lamp, and a cat asleep on a cushion. Soft pastel palette, clean edges, gentle ambient occlusion, soft studio lighting, plain light background, no text, high detail, 1:1.
An 8-second locked-off overhead shot of a messy desk covered in papers, sticky notes, cables, and empty cups. Over the clip, items smoothly glide off-frame and the remaining ones neatly arrange themselves into a tidy, minimal setup with a laptop, a notebook, and a plant. Bright natural daylight, crisp detail, satisfying smooth motion, no people, no text.
I'm stuck on this problem: [describe the problem]. List every assumption I seem to be making about it, including ones I haven't said out loud. For each assumption, rate how confident I should be that it's true (high, medium, low) and explain why. Then pick the two shakiest assumptions, show how the problem changes if each one is false, and suggest one quick, cheap test I can run this week to check each of them.
Help me plan tomorrow before I end my day. Here's what I finished today: [list]. Here's what's still open: [list]. Here are tomorrow's fixed commitments: [meetings and times]. Ask me no more than three quick questions, then give me: my single most important task for tomorrow, up to three supporting tasks, a time-blocked schedule that fits around my commitments with buffers, and one thing I should deliberately not do tomorrow. Keep it short enough to read in one minute.
Turn these bullet points into one or two well-written paragraphs: [paste bullets]. Keep every fact, but add natural transitions so the ideas flow logically from one to the next. Use plain, confident language, vary sentence length, and avoid filler phrases like 'in today's world' or 'it's important to note'. After the paragraphs, briefly list any spot where the bullets were unclear and you had to guess the connection.
Write a short, polite but firm email reminding a client that an invoice is overdue. Details: client name [name], invoice number [number], amount [amount], original due date [date], days overdue [number], payment link or method [details]. Keep the tone friendly and professional, assume it was an oversight, make the amount and how to pay impossible to miss, and end with a clear next step. Give me three versions: a gentle first reminder, a firmer second reminder, and a final notice that mentions next steps without sounding threatening.
I'm new to [field or topic] and keep running into terms I don't understand. Create a glossary of the 25 most important terms a beginner needs to know, ordered from most basic to more advanced. For each term, give a one-sentence plain-English definition, a simple real-world example, and note any term it's often confused with. Finish with the five terms I should learn first and why.
Turn this customer result into a short, engaging social post: [paste the customer's situation, what they did, and the results]. Structure it as: a one-line hook that leads with the result, the problem they faced, the one change that made the difference, the concrete outcome with numbers, and a soft call to action. Keep it under 150 words, make it sound like a real story rather than an ad, and give me two alternative hooks to test.
I want fresh ideas for this challenge: [describe the challenge]. Pick five industries that have nothing obvious to do with mine, such as hospitality, gaming, aviation, retail, and healthcare. For each one, explain how that industry solves a similar underlying problem, then translate it into two concrete ideas I could try. Finally, rank all ten ideas by how easy they'd be to test in the next two weeks.
Here is a code diff: [paste diff]. Write a commit message for it that follows common conventions: a summary line under 60 characters in the imperative mood, a blank line, then a short body explaining what changed and why, not how. If the diff mixes unrelated changes, say so and suggest how to split it into separate commits, with a message for each. Point out anything in the diff that looks like a leftover debug line or an accidental change.
A set of nine minimal line-art icons arranged in a clean 3x3 grid on a plain off-white background, representing productivity themes: calendar, checklist, timer, lightbulb, inbox, target, notebook, coffee cup, and laptop. Consistent 2px stroke weight, rounded line ends, single dark navy color, generous spacing, flat vector style, no shading, no text --ar 1:1 --style raw
A 6-second close-up of an open paper notebook on a wooden desk in soft morning light. Hand-drawn doodles on the page, a to-do list, a small rocket, and a lightbulb, gently animate: checkboxes tick themselves, the rocket lifts off the page leaving a pencil-line trail, and the lightbulb glows warmly. Slow push-in camera move, shallow depth of field, cozy and playful mood, no people, no readable text.
Here is a problem I am trying to solve: [PROBLEM]. Here is the solution I plan to use: [SOLUTION]. Act as a skeptical reviewer. List the five most likely ways this solution could fail or backfire, rate each by likelihood and impact from 1 to 5, and for the top three suggest a cheap test I can run this week to find out before committing. End with a one-line verdict: go, adjust, or rethink.
My recurring responsibilities are: [LIST YOUR RECURRING WORK, e.g. meetings, admin, deep work, sales, learning]. Group them into themes and assign one theme to each weekday so similar tasks happen together. Show the result as a simple Monday to Friday table with the theme, the main tasks, and one rule for protecting that day. Then flag any task that does not fit a theme and suggest where it should go.
Rewrite the text below so a busy reader can scan it in 15 seconds. Keep every important fact, but break it into a one-sentence summary followed by short bullet points with bolded lead words. Remove filler and repetition, keep my original meaning, and do not add new information. Text: [PASTE TEXT]
Write a short email to my manager [NAME] asking for feedback on [WORK OR PROJECT]. Make it easy for them to say yes: keep it under 120 words, name the two or three specific questions I want answered, offer a quick format (a 10-minute call or reply by email), and suggest a deadline of [DATE]. Tone: confident and respectful of their time. Give me a subject line too.
Create a clear timeline showing how [TOPIC, e.g. remote work, electric cars, AI assistants] has developed from its beginnings to today. For each key milestone give the year, what happened, and why it mattered in one sentence. Group milestones into three to five eras with a short label for each, then finish with the two biggest trends to watch next. Mark anything you are unsure about so I can verify it.
Below is a transcript of a webinar or talk. Turn it into a well-structured blog post of about 900 words for [AUDIENCE]. Write a fresh headline, a hook opening, three to five sections with subheadings based on the strongest ideas, and a short takeaway list at the end. Remove filler, small talk, and repetition, keep the speaker's best lines as quotes, and suggest a meta description under 155 characters. Transcript: [PASTE TRANSCRIPT]
Help me brainstorm fresh ideas for [PROJECT, PRODUCT, OR PROBLEM]. Generate 20 'What if...' questions that challenge a normal assumption about it, such as what if it were free, ten times faster, aimed at kids, or had no screen. For each question give one concrete idea it suggests. Then pick the three ideas that seem most practical and the one that seems most surprising, and explain why in a sentence each.
Here is some code that runs slower than I want: [PASTE CODE]. It is written in [LANGUAGE] and usually handles [DESCRIBE INPUT SIZE]. Identify the parts most likely causing the slowdown and explain why in plain language. Then give an optimized version, note the expected improvement in Big-O terms where relevant, and list any trade-offs, like extra memory use or reduced readability. Keep the behavior exactly the same.
A vertical motivational poster with large bold sans-serif text reading "DONE IS BETTER THAN PERFECT", stacked on three lines and centered. Deep charcoal background with a single bright coral accent stripe behind the word "DONE". Clean modern Swiss design, generous margins, subtle paper grain texture, high contrast, no other text or images, portrait 4:5 ratio.
An 8-second smooth animation of a laptop screen showing a cluttered email inbox. Unread messages slide away one by one into neat folders with a soft swoosh motion, the counter drops to zero, and a calm sunrise illustration fills the screen as the camera slowly pulls back to reveal a tidy desk with a cup of tea. Soft pastel colors, gentle easing, satisfying and relaxing mood, no readable text.
I keep running into this issue: [describe it]. List every symptom I've mentioned, then help me separate symptoms from the underlying problem. Ask me up to 5 clarifying questions, then give me your best guess at the one core problem and three small experiments to confirm it.
Here are my goals, projects, and commitments for the next 3 months: [paste]. Help me choose only three must-win priorities. For each, explain why it matters, what 'done' looks like, the first action this week, and what I should explicitly stop or postpone to make room.
Here is my topic and the main point I want readers to take away: [paste]. Write five different opening paragraphs, each using a different approach (a question, a surprising fact, a short story, a bold claim, a problem statement). Keep each under 60 words and tell me which one fits best and why.
Write a short, friendly email declining this meeting invite: [paste details]. Explain briefly that I can't attend, offer an async alternative (like a written update or a quick recorded video), and suggest one other time if a live chat is really needed. Keep it under 100 words and not apologetic.
I want to understand the [industry/niche] landscape. Group the main companies, tools, or organizations into clear categories, give one sentence on what each does, and point out the leaders, the fast-growing newcomers, and any gaps nobody is serving well. Flag anything you are unsure about so I can verify it.
Here is a list of questions my audience often asks: [paste]. Turn each into a 30-45 second short-form video script with a hook in the first line, a clear answer in three beats, and a one-line call to action. Add a suggested on-screen text caption for each.
List 10 unwritten rules most people follow in [field or activity]. For each one, imagine flipping it completely and describe one product, process, or content idea that comes from doing the opposite. Finish by picking the three most practical flipped ideas and explaining how to test each cheaply.
I want to add this feature to my project: [describe feature, stack, and relevant files]. Before writing any code, give me a step-by-step implementation plan: files to change, data changes, edge cases, and how I'll test it. Then ask me to confirm before generating code for step one.
A cozy reading nook by a large window, soft morning sunlight, a comfy armchair with a knitted blanket, a stack of books and a steaming mug on a small wooden side table, potted plants, warm neutral tones, shallow depth of field, photorealistic, calm and inviting mood --ar 4:5
Close-up shot of a hand writing a neat daily plan in a paper planner on a wooden desk, slow cinematic push-in, soft natural window light, a cup of coffee and a pen beside it, gentle focus shift from the pen tip to the written checklist, calm and productive mood, 8 seconds.
I'm stuck on this problem: [describe problem]. Start by describing what the ideal end state looks like in concrete detail. Then work backwards step by step: what must be true just before that, and before that, until you reach where I am today. Highlight the first step I can take this week and the riskiest step in the chain.
Here is my task list for the week: [paste tasks]. Group the tasks into batches that use the same tools, context, or energy level (for example calls, deep writing, admin, errands). Suggest a time block for each batch with a realistic duration, the best time of day to do it, and one rule to protect that block from interruptions.
Read this draft: [paste text]. Find every sentence that is abstract or vague and rewrite it with a specific example, number, or image a reader can picture. Show the original and the improved version side by side, and keep my voice and length roughly the same.
Write a short, friendly email to reconnect with [name], who I last spoke with [when and context]. Mention one specific thing we shared, a genuine update from my side, and a light reason to catch up, without sounding like I want a favor. Keep it under 100 words and give me two subject line options.
My position is: [state your claim]. Research and list the five strongest counterarguments made by credible people or sources, explain the evidence behind each, and rate how serious each one is. Finish with which counterargument I should address first and how I might respond honestly.
Here is something that happened to me: [describe the story]. Turn it into a short social post with a hook in the first line, the story told in three to five short beats, a clear lesson, and a question at the end that invites replies. Write two versions: one for LinkedIn and one for X under 280 characters.
I need fresh ideas for [project or problem]. Pick five random, unrelated everyday words. For each word, generate three ideas that connect it to my project in a surprising way. Then choose the two most practical ideas and explain how I could test each one in a day.
Here is my code: [paste code]. Identify every place it could fail (bad input, network errors, missing files, empty data). Add clear error handling with useful messages that tell the user what went wrong and how to fix it. Explain each change briefly and keep the code style consistent with mine.
A hand-painted watercolor illustration of a habit tracker page in an open notebook, small colorful checkmarks and doodles, a few drops of paint and a brush beside it, soft pastel palette, light paper texture, gentle shadows, cheerful and calm mood, top-down view --ar 3:2
A wall covered in messy, scattered colorful sticky notes. The notes lift off and glide smoothly into neat columns labeled To Do, Doing, and Done, settling into place one by one. Bright office lighting, steady camera, satisfying organized ending, 6 seconds.
I'm trying to fix this problem: [DESCRIBE PROBLEM]. List three to five realistic solutions. For each one, show what it costs in time, money, and effort, what it makes worse or riskier, and who it affects. Then recommend the option with the best balance for someone with [MY CONSTRAINTS], and tell me what would make you change that recommendation.
Help me design a 10-minute end-of-day shutdown ritual. My work involves [DESCRIBE WORK] and I usually struggle with [E.G. LEAVING TASKS HALF-DONE, CHECKING EMAIL AT NIGHT]. Give me a short checklist covering capturing loose ends, choosing tomorrow's first task, and a clear signal that work is over. Keep each step under one line so I can pin it next to my screen.
Here are some sentences from my draft that feel too long or tangled: [PASTE SENTENCES]. Rewrite each one as two or three shorter sentences that keep the exact meaning. Show the original and the rewrite side by side, and briefly note what made the original hard to read so I can avoid it next time.
Write an out-of-office email reply for me. I'm away from [START DATE] to [END DATE] for [REASON, OPTIONAL]. Include when I'll respond, who to contact for urgent matters ([NAME AND EMAIL]), and where to find answers to common questions ([LINK OR NOTE]). Keep it friendly, under 80 words, and give me one formal and one casual version.
Here is the transcript of a podcast episode: [PASTE TRANSCRIPT]. Pull out the seven most useful takeaways, each with a one-line explanation and a short supporting quote with its approximate position in the transcript. Then list any claims that sound surprising or worth verifying, and suggest one action I could take this week based on the episode.
I want to write a behind-the-scenes post about how I [DESCRIBE PROCESS, E.G. PLAN MY WEEK OR BUILD MY PRODUCT]. Interview me with five short questions, one at a time. After my answers, write a post for [PLATFORM] that opens with a specific moment, shows the real steps and tools I use, admits one thing that didn't work, and ends with a question for readers.
I've been working on [TOPIC OR PROJECT] for a long time and my ideas feel stale. Pretend you are a curious beginner who knows nothing about it. Ask 15 naive questions an outsider would ask, then turn the five most interesting questions into fresh ideas I could try, with one sentence on why each might work.
I need sample data to test my app. The data represents [DESCRIBE ENTITY, E.G. CUSTOMERS OR ORDERS] with these fields: [LIST FIELDS AND TYPES]. Generate [NUMBER] realistic rows as [JSON/CSV], including a few edge cases like empty optional fields, very long names, and unusual but valid values. Then give me a short script in [LANGUAGE] that can generate more rows like these.
A layered paper-cut illustration of a weekly calendar with colorful time blocks, small paper clocks, checkmarks, and a coffee cup, soft shadows between paper layers giving depth, pastel palette of mint, peach, and sky blue, clean composition centered on a light background, high detail, 16:9 aspect ratio
Close-up of a smartphone on a wooden desk buzzing with stacked notification banners. The camera slowly pulls back as the notifications fade away one by one and the screen dims to a simple focus timer. Warm afternoon light shifts softer, a plant sways slightly in the background. Calm, cinematic, shallow depth of field, 8 seconds, 16:9.
I'm going to describe a recent setback: [describe what went wrong]. Walk me through the Five Whys technique one question at a time. After each of my answers, ask the next 'why' based on what I said, and stop when we reach a cause I can actually control. Then summarize the chain of causes, name the root cause in one sentence, and suggest two small changes that would stop this from happening again.
Here is everything on my mind right now, unfiltered: [paste brain dump]. Sort it into tasks, ideas, worries, and things to delete. For the tasks, group them by project, estimate effort as small, medium, or large, and rank the top five by impact and urgency. Finish with a realistic plan for the next two days that fits around [fixed commitments], and list anything I should drop or postpone.
Rewrite the text below so that most sentences use active voice and start with who is doing what. Keep the meaning and facts exactly the same, keep my tone [casual / professional], and don't add new claims. After the rewrite, list the five changes that made the biggest difference and explain each in one line so I can learn the pattern. Text: [paste text]
Write a short email to [recipient and role] asking them to decide on [decision] by [date]. Lay out the options as two or three numbered choices with a one-line trade-off for each, state which one I recommend and why in one sentence, and make it easy to reply with just a number. Keep it under 120 words, friendly but direct, with a clear subject line.
Read the research paper below and write a one-page brief for a smart non-expert. Include the question the authors asked, how they studied it in plain words, the three most important findings with numbers where given, the main limitations, and what this means in practice for [my field or goal]. Flag any claim in the paper that seems weakly supported. Paper: [paste text or upload PDF]
Create a social post for [platform] busting five common myths about [topic] for [audience]. For each, write the myth in one short line, then the fact in one or two sentences with a simple example or reason. Open with a hook that challenges what most people believe and close with a question that invites comments. Keep the language plain and avoid hype.
I'm working on [problem or project]. Imagine it's ten years in the future and this problem has been completely solved. Describe three very different futures in which it was solved, each in a short paragraph. Then work backwards from each one and list the ideas, tools, or habits that made it possible. Finish by picking the five ideas I could start testing this month, with a first step for each.
Add clear documentation to the code below. Write a docstring for every function and class that explains what it does, its parameters, return value, and any errors it raises, in the standard style for [language]. Add inline comments only where the logic isn't obvious, and don't change any behavior. After the code, list anything confusing you noticed that might deserve a rename or refactor. Code: [paste code]
A cute claymation-style 3D illustration of a giant to-do list on a clipboard with chunky checkboxes, three items checked off with bright green ticks, a tiny clay pencil leaning against it, soft studio lighting, rounded shapes, matte clay texture, pastel yellow and lavender background, playful and tidy composition, high detail --ar 4:5
Macro shot of a glass hourglass on a clean white desk. As the sand falls, each grain that lands transforms into tiny glowing checkmarks that pile up neatly at the bottom. Soft morning light, gentle slow-motion movement, calm ambient mood, shallow depth of field, smooth camera orbit halfway around the hourglass, 6 seconds, 16:9.
I tried to solve this and it didn't work: [WHAT I TRIED AND WHAT HAPPENED]. Act as a calm, honest coach. First, help me separate what went wrong because of my approach from what went wrong because of bad luck or outside factors. Then list the three most useful lessons, and design a second attempt that changes only what actually needs changing. End with one small test I can run this week to check the new plan works before I commit fully.
I'm running on low energy today because [REASON], but I still have these tasks: [LIST TASKS]. Sort them into three groups: must do today, can do on autopilot, and can wait. Suggest an easy order that starts with a quick win, put short breaks between blocks, and rewrite each must-do task as the smallest possible first step. Keep the tone kind and realistic, not hustle-driven.
Here's a piece of writing that explains something but feels dry: [PASTE TEXT]. Rewrite it so it opens with a short, relatable story or moment (3-4 sentences) that shows the problem in real life, then flows naturally into the explanation. Keep every fact accurate, keep my voice, and don't make it longer than 20% of the original length. Show me the rewrite, then point out the one line where the story connects to the main point.
A client or colleague keeps adding new requests to a project we already agreed on. Here's the original scope: [SCOPE] and the new asks: [NEW REQUESTS]. Write a short, friendly email that thanks them, reminds them what we agreed, explains how the new requests affect time or cost, and offers two clear options (add it as a paid extra or move it to a later phase). No guilt-tripping, no corporate jargon, under 150 words.
I'm researching [PRODUCT, TOOL, OR TOPIC]. Search recent posts and discussions to find the most common complaints and frustrations real people share about it. Group them into themes, show how often each theme comes up, and quote 2-3 short examples for each (with where they came from). Finish with the biggest unmet need you see and one idea for how someone could solve it.
Here's a mistake I made recently and what it cost me: [DESCRIBE MISTAKE]. Turn it into a short social post that starts with the moment I realized I messed up, walks through what happened in plain language, and ends with the one lesson I'd give someone else. Make it honest and a little self-deprecating, not preachy. Give me a version for LinkedIn (under 200 words) and one for X (under 280 characters).
My challenge is: [DESCRIBE CHALLENGE]. Brainstorm solutions by imagining how this exact problem would be solved for five very different audiences: a busy parent, a retiree, a student, a small business owner, and a kid. Give three ideas for each audience. Then pick the four ideas that could work best for my real audience, [MY AUDIENCE], and explain how to adapt each one.
Before I modify this code, I want to fully understand it: [PASTE CODE]. Walk me through what it does step by step, as if you're pairing with me. Point out any hidden assumptions, edge cases it already handles, and anything that would break if I changed [THE PART I WANT TO CHANGE]. Finish with a short checklist of things I should test after my change.
A warm, inviting home office at golden hour, sunlight streaming through a large window onto a wooden desk with an open laptop, a ceramic mug of coffee, and a neatly stacked notebook. Lush green plants in terracotta pots on the windowsill, soft long shadows, dust particles glowing in the light, cozy and focused mood, photorealistic, shot on 35mm lens, shallow depth of field, editorial interior photography style
Close-up of a steaming cup of coffee on a minimalist kitchen counter in soft morning light. The rising steam slowly curls and forms simple floating words of a daily plan: 'Focus', 'Walk', 'Create', 'Rest', each fading gently as the next appears. Slow, steady camera push-in, calm ambient atmosphere, warm color palette, realistic textures, 8 seconds, 16:9.
Here's a problem I'm dealing with: [DESCRIBE PROBLEM]. Before we jump to fixes, help me list everyone it touches, from me and my team to customers, partners, and anyone downstream. For each group, describe how they feel it, what they'd count as solved, and what they might lose if we change things. Then point out which group I've probably been ignoring and suggest one fix that works for the most people at once.
I keep letting small admin tasks pile up: [LIST TASKS LIKE BILLS, FORMS, REPLIES, FILING]. Help me design one weekly 60-minute admin hour. Group the tasks into a sensible order, give each a time box, suggest the best day and time based on my schedule ([DESCRIBE WEEK]), and write a short checklist I can reuse every week. End with a rule for what to do with any task that won't fit.
Rewrite these instructions so someone doing it for the first time can follow them without asking me a single question: [PASTE INSTRUCTIONS]. Use numbered steps, one action per step, and say what they should see when each step worked. Flag any step where people usually get stuck and add a short tip there. Keep my wording where it's already clear.
I'm handing off [PROJECT] to [PERSON] because [REASON]. Write a friendly, clear handoff email that covers where things stand, what's done, what's next, open risks, key contacts, and where every file lives. Here are my notes: [PASTE NOTES]. Keep it skimmable with short sections, and end by offering a 15-minute call to answer questions.
People in my field often say: [COMMON BELIEF OR SAYING]. Dig into where this idea came from. Who first said or studied it, what the original evidence actually showed, and how it changed as it got repeated. Then tell me whether it still holds up today, what the current evidence says, and how I could explain the nuance in two sentences. Show sources for each claim.
My audience keeps asking me: [QUESTION]. Turn my answer into a short mini guide for [PLATFORM]. Start with a one-line direct answer, then three to five practical steps, one common mistake to avoid, and a quick real-life example. Here's my rough answer: [PASTE NOTES]. Keep the tone warm and conversational, like I'm explaining it to a friend.
I want fresh ideas for [GOAL, LIKE A PROJECT, PRODUCT, OR CONTENT SERIES]. Two things I genuinely love are [THING 1] and [THING 2]. Give me 20 ideas that mash these two together in surprising ways, from safe to wild. Mark the three that feel most doable this month and explain in one line why each could work.
Every week I do these steps by hand on my computer: [LIST STEPS]. My setup is [OS AND TOOLS]. Write a simple script that does as much of this as safely possible. Explain what each part does in plain English, add a dry-run mode that shows what would happen without changing anything, and list the steps that still need a human and why.
Overhead flat shot of an open weekly planner on a light oak desk, handwritten tasks in neat ink, a few colorful sticky tabs, a brass pen, a small succulent, and a cup of tea in the corner. Soft diffused daylight from the left, gentle shadows, calm and organized mood, muted pastel accents, crisp paper texture, high detail, editorial stationery photography --ar 4:5
A glowing laptop screen in a dim, cozy room shows a chaotic pile of floating email envelopes. One by one, the envelopes fold themselves into tidy, labeled paper folders that slide neatly onto a shelf beside the laptop. Smooth, satisfying motion, soft warm lighting, slow camera orbit, clean modern aesthetic, 6 seconds, 9:16.
I think this change might solve my problem: [DESCRIBE PROBLEM AND PROPOSED FIX]. Before I commit real time or money, help me design the smallest, cheapest experiment that would tell me if it works. Give me three options ranked by cost and speed, what result would count as success or failure for each, and which one you'd run first and why.
Help me build a 45-minute Sunday reset I can repeat every week. My life looks like this: [WORK, HOME, HABITS, COMMITMENTS]. Split the reset into short blocks (clear, review, plan, prep), list exactly what I do in each one, and keep it light enough that I'll still do it on a tired Sunday. End with a printable checklist.
Here are a few flat sentences from my draft: [PASTE SENTENCES]. For each one, give me three rewrites: one more specific, one with a concrete image or detail, and one shorter and punchier. Keep my original meaning and voice, and tell me in one line why the strongest version works.
I want to ask [PERSON AND ROLE] for advice about [TOPIC]. We've never met. Write a short email (under 120 words) that shows I've done my homework on them, asks one specific question they can answer in a couple of minutes, and makes it easy to say no. Give me two subject line options too.
I keep hearing that [TREND OR CLAIM] is growing fast. Find the most recent, credible numbers on it, with the source and date for each. Separate hard data from estimates and opinion, point out anything that looks inflated or outdated, and give me a two-sentence honest summary of what the numbers actually say.
Here's one tip I know works: [DESCRIBE TIP]. Turn it into seven short social posts for seven days, each from a different angle: the story of how I learned it, a common mistake, a quick how-to, a myth it busts, a before-and-after, a question to the audience, and a one-line takeaway. Keep them conversational and under 60 words each.
My problem is: [DESCRIBE PROBLEM]. Brainstorm 15 ideas as if a curious, fearless 10-year-old were solving it, simple, playful, and ignoring how things are usually done. Then pick the three that could actually work for an adult and explain how to make each one practical.
Here's a bug report from a user: [PASTE REPORT] and the relevant code: [PASTE CODE]. Work out the exact steps and inputs that reproduce the bug, write a minimal failing test that captures it, and explain what the test proves. Don't fix the bug yet, just make it impossible to ignore.
Minimalist poster design: a single large analog clock face showing one highlighted hour in warm amber, surrounded by generous off-white negative space. Small, clean sans-serif text at the bottom reads "One Hour. One Thing." Subtle paper grain texture, Swiss design influence, balanced composition, calm and confident mood, high resolution.
Close-up of a lit candle on a wooden desk at night beside an open notebook with a handwritten to-do list. As the candle slowly burns down, each item on the list gets a neat checkmark drawn by an unseen pen. Warm flickering light, shallow depth of field, cozy and quietly satisfying mood, gentle static camera, 8 seconds, 16:9.
I keep stressing about this situation: [describe it]. Help me split it into three honest buckets: what I fully control, what I can influence, and what I simply have to accept. For each thing I control, give me one small action I can take this week. Keep it warm and practical, like a friend who's been through it, not a therapist reading from a script.
Here's my week: [paste tasks, meetings, deadlines]. Build me a plan that leaves real breathing room for the stuff I can't predict. Mark which tasks are must-do, which can slide a day, and which I can drop if things go sideways. Then tell me the one task I should knock out first on Monday so the rest of the week feels lighter.
Here's a draft that wanders all over the place: [paste draft]. Rework it so it reads like a story with a clear beginning, a moment of tension, and a payoff at the end. Keep my voice and my examples, cut anything that doesn't move the story forward, and show me the three biggest changes you made and why.
I want to ask my manager for a raise. Here's what I've done over the past year: [list wins, numbers, extra responsibilities]. Write a short, confident email asking for a conversation about my pay. Lead with the value I've added, keep it calm and specific, and avoid anything that sounds like begging or an ultimatum. Give me one version that's direct and one that's a bit softer.
I've been out of the loop on [topic or industry] for about a year. Search what's happened since then and give me the five biggest shifts, why each one matters, and who's driving it. Tell it to me like a friend catching me up over coffee, then list the sources so I can dig deeper on anything that catches my eye.
Here's something I changed and how it turned out: [describe the before, what you did, and the after]. Write a short social post that tells it as a mini story: where I started, the moment I decided to change, what I actually did, and what's different now. Keep it real, skip the hype, and end with one takeaway someone could try today.
Here are a few things that worked really well for me before: [list past wins]. Look at what they have in common, then brainstorm 15 new ideas for [current goal] that reuse those same ingredients in fresh ways. For each idea, note which past win it borrows from. Finish by picking the three ideas you'd bet on and say why.
This function has grown too long and nobody wants to touch it: [paste code]. Walk me through what it does in plain words first. Then split it into smaller, well-named functions without changing its behavior, and show the new version. Point out anything risky you noticed along the way and suggest one test I should write before merging.
A cozy home desk beside a large window on a rainy evening, raindrops streaking the glass, a warm brass lamp glowing over an open notebook and a half-finished cup of tea, soft city lights blurred in the background, calm and focused mood, cinematic lighting, shallow depth of field, photorealistic --ar 16:9
A slow, dreamy shot of a tidy desk where folded paper airplanes glide in one by one and land softly on a to-do list, each landing checks off a task with a small ink tick, warm afternoon sunlight, gentle camera drift to the right, soft focus background, relaxing ambient mood, 8 seconds.
I keep running into the same kind of problem and fixing it from scratch every time. Here's what happened the last few times: [describe 2-3 situations]. Read them like a friend who's watching from the outside. Tell me the pattern I'm missing, why it keeps coming back, and one small system or habit that would stop me from solving it again next month. Keep it practical and honest.
I've got one big deadline this week: [deliverable, due date]. Everything else still needs to keep moving: [list other commitments]. Build me a day-by-day plan that protects deep work for the deadline, squeezes the small stuff into short blocks, and leaves a buffer day in case something slips. Flag anything I should push, delegate, or drop, and tell me why.
Here's a draft that feels stiff and written for a crowd: [paste draft]. Rewrite it so it sounds like I'm talking to one person over coffee. Use 'you', short sentences, a little personality, and one quick real-life moment that makes the point land. Keep my meaning and key facts exactly the same, then show me the three biggest changes you made.
A project with [person or team] went quiet about [time] ago. The last thing that happened was [context]. Write a short, friendly email that restarts it without guilt-tripping anyone. Remind them where we left off in one line, suggest one clear next step, and make it easy to say yes with a simple question at the end. Give me a warm version and a more direct version.
I'm researching [topic]. Most articles cover the same obvious points. Dig deeper and give me 10 questions that smart people in this space should be asking but rarely do. For each one, explain in a sentence why it matters and where I could start looking for an answer. Then pick the two that would make the most interesting piece of content.
I recently helped [client or person] with [problem] and got [result]. Turn it into a short social post told as a story: start with the moment things felt stuck, walk through what we tried (including one thing that didn't work), and end with the result and one lesson anyone can use. Keep it humble, specific, and under 200 words. Don't share anything private about the client.
I want to [goal], but I keep assuming it needs money. Pretend my budget is zero. Brainstorm 20 ways to make progress using only time, skills, free tools, and people I already know. Then group them into quick wins, slow builds, and long shots, and tell me which three to try this week.
Here's a code diff from a pull request: [paste diff]. Explain what it changes as if you're telling a teammate who hasn't seen the code. Cover what the change does, why someone probably made it, what could break, and what I should test before merging. Finish with a two-line summary I could paste into the PR description.
A clean wooden desk in early morning light, a laptop closed to the side, a steaming mug, and one bright yellow sticky note in the center that reads 'ONE THING' in bold handwritten marker, soft window light, calm minimal mood, crisp readable lettering, photorealistic, 3:2 aspect ratio
A smooth, satisfying animation of a messy weekly calendar where colorful time blocks float out of place, then slide and snap neatly into an organized schedule one by one, soft click on each snap, clean pastel colors on a white background, gentle camera push-in, calm productive mood, 8 seconds.
Here's a goal I keep missing: [DESCRIBE GOAL] and what usually gets in the way: [LIST OBSTACLES]. Use the theory of constraints to find the single bottleneck that, if fixed, would make most of the other obstacles shrink. Explain why you picked it, give me one small action to loosen it this week, and tell me what signal would show it's working.
My week looks like this: [PASTE MEETINGS AND COMMITMENTS]. My most important projects are [LIST PROJECTS]. Find three 90-minute blocks of deep work that I can actually protect, tell me which project goes in each, and suggest what I should move, shorten, or decline to make room. Keep it realistic, not idealistic.
Here's my draft: [PASTE DRAFT]. Find every sentence at the start that warms up instead of saying something real, the throat-clearing, the 'in today's world' openers, the repeated setup. Cut them, show me where the piece should actually begin, and rewrite the new first two sentences so they pull the reader straight in.
I just finished working with [CLIENT NAME] on [PROJECT]. The result was [RESULT]. Write a short, warm email asking them for a testimonial. Make it easy to say yes: remind them of the win in one line, suggest two or three questions they can answer, offer to draft it for them to edit, and keep it under 120 words with no pressure.
Search for the current debate around [TOPIC]. Give me the three strongest pieces of evidence for each side, with sources and dates, and flag which ones are studies, which are expert opinion, and which are anecdotes. End with what a fair-minded person would conclude today and what new evidence would change that.
I just read [BOOK TITLE] and the idea that stuck with me is [IDEA]. Write a short post (under 200 words) that opens with a moment from my own life where this idea would have helped: [MY MOMENT]. Then explain the idea simply, give one way readers can try it today, and end with a question that invites replies. Keep it conversational, no hype.
I'm working on [PRODUCT, SERVICE, OR IDEA]. Its most obvious feature is [FEATURE]. Imagine that feature had to be removed completely. Brainstorm 15 ways the idea could still work or even get better without it, then pick the three most surprising ones and explain what each would mean for real users.
Here's my function: [PASTE CODE]. List the edge cases it doesn't handle, empty inputs, nulls, huge values, weird characters, timezones, concurrency, whatever applies. For each, show an example input, what happens now, and what should happen. Then give me a revised version that handles the important ones without overcomplicating it.
A quiet home desk late at night, a warm desk lamp casting a soft circle of light over a paper checklist where every item is ticked off, a pen resting on top, a half-finished cup of tea, city lights blurred through the window behind, calm and satisfied mood, cinematic photography, shallow depth of field --ar 3:2
A slow, cinematic close-up of hands gently closing a laptop on a tidy desk at sunset, warm orange light sweeping across the keyboard, a notebook with a completed to-do list beside it, the person leans back and stretches, soft ambient sound, peaceful end-of-workday mood, 8 seconds.
I'm stuck on this problem: [describe it]. Don't solve it yet. First, help me describe in one or two sentences what 'solved' would look like a month from now. Then work backward from that picture, step by step, until we reach something I can do today in under 30 minutes. Point out any step where I'm assuming something I haven't checked.
Here's when I usually feel sharpest and when I crash during the day: [describe your energy pattern]. Here are my tasks for this week: [list]. Sort my tasks into deep-focus work, light admin and people stuff, then build me a simple Monday-to-Friday plan that puts the hardest work in my best hours and the easy stuff in my slumps. Keep at least one hour a day completely empty as a buffer.
Here's a draft I wrote: [paste draft]. A lot of people will skim it on their phone. Rewrite it so someone skimming gets the main point from the first line of each paragraph, break up any paragraph longer than four lines, and swap any word a 12-year-old wouldn't know for a plainer one. Don't cut any of my actual ideas or change my voice.
Someone invited me to a meeting I don't think I need to be in. Here's the invite and who it's from: [paste details]. Write a short, warm email that declines, suggests a faster alternative (like a quick written update or me reading the notes afterward), and makes it clear I still care about the project. Give me a version for a coworker and one for my boss.
I'm trying to understand [topic] properly. Map out the two or three biggest points where knowledgeable people genuinely disagree. For each one, explain each side in a sentence or two, what evidence or experience each side leans on, and what would have to be true for each side to be right. Finish by telling me which question I should look into first if I only have one hour.
Here's a mistake I made at work or in my business, and what it cost me: [describe it]. Turn it into a short social post that opens with the moment I realized I'd messed up, tells what happened in plain words, and ends with the one thing I do differently now. Keep it honest, no humblebragging, and under 150 words. Give me three different opening lines to choose from.
I need fresh ideas for [project or problem]. Pick five random things from completely unrelated areas, like cooking, sports, gardening, video games and airports. For each one, force a connection to my problem and give me one idea it sparks, even if it sounds a bit weird at first. Then tell me which two ideas are most worth trying this week and why.
Here's a piece of my code, or a description of what my app does: [paste code or describe]. List the main ways this can fail for a real user, like bad input, no internet or a timeout. For each one, write an error message that tells the user in plain words what went wrong and what they can do next, with no jargon or blame. Then show me where in the code each message should go.
Top-down overhead photo of a clean wooden desk on a Monday morning, an open notebook with a short handwritten list of three goals, a freshly sharpened pencil, a cup of black coffee with steam rising, a small green plant in the corner, soft natural morning light from the side, minimal and calm mood, crisp detail, editorial lifestyle photography
A short, satisfying animation of a laptop screen showing a cluttered email inbox with dozens of unread messages; one by one the emails fold into paper envelopes, fly off the screen and drop neatly into labeled folders on the desk, until the screen shows a clean empty inbox with a small checkmark. Warm office lighting, smooth camera push-in, calm and rewarding mood, 8 seconds.
Something I fixed a while back is broken again, and I'm annoyed because I thought it was done. Here's what the problem was, what I did to fix it, and what's happening now: [describe]. Walk me through it like a patient friend who's good at detective work. First list what might have changed since the fix (people, tools, volume, timing, habits). Then help me tell apart a fix that patched the symptom from one that removed the cause. End with one small test I can run this week to know which it was, and what a fix that actually sticks would look like.
I'm back from [number] days off and I can already feel the pile waiting for me. Here's what I know is on my plate: [list]. Help me plan my first week back so I don't spend Monday drowning. Give me a short catch-up block for day one, sort the rest into what truly can't wait, what can slide a few days, and what I can quietly let go. Keep the plan realistic for someone whose brain is still half on vacation, and tell me what to say to people who expect instant replies.
I've got a bunch of bullet points that make sense to me but read like a shopping list to anyone else: [paste bullets]. Turn them into one or two paragraphs that flow like someone telling a story over coffee. Keep every real point, keep my words where they already sound like me, and add only the small connecting bits that show why one thing leads to the next. Then show me which bullet you think is weakest and why.
I want to get back in touch with [name], who I worked with [when/how] but haven't talked to in [time]. I feel a little awkward because the only reason I'm reaching out now is [reason]. Write a short, honest email that opens with a real memory we share, admits it's been a while without overdoing the apology, mentions what I've been up to in one line, and makes my ask small and easy to say no to. Give me two versions: one warmer, one more to the point.
Help me understand how thinking about [topic] has shifted over the last ten years. Tell it like a story in three or four chapters: what people believed at the start, what event, study or product made them change their minds, and where things stand now. For each chapter, name the kind of sources I should check to confirm it, and flag anything you're unsure about rather than guessing. Finish with the one open question people are still arguing about today.
A customer asked me this the other day: [paste question]. I suspect plenty of other people wonder the same thing but never ask. Turn it into a short post that starts with the moment they asked, explains the answer the way I'd say it out loud, and ends with one practical tip people can use today. Keep it under 200 words, keep the customer anonymous, and give me three opening lines to choose from.
I've been stuck on [problem or project] for a while, and I think I know too much about it to see it fresh. Pretend you're five different total beginners: a kid, a retiree, someone from a totally different industry, a tourist, and a first-week intern. For each one, tell me the naive idea they'd suggest and why it might actually work. Then pick the two that sound silliest but are worth a quick test, and tell me how I'd try each one cheaply this week.
Here's a script I wrote in a hurry that works but scares me every time I run it: [paste code]. Help me make it safe to rerun. Point out anything that would break or cause damage if it ran twice, add clear checks before anything destructive, pull hard-coded values into settings at the top, and add short comments a future me would thank you for. Explain each change in plain words before showing the final version.
A cozy reading nook beside a tall window on a rainy afternoon, raindrops streaking down the glass, a soft armchair with a knitted blanket, a half-finished mug of tea on a small wooden side table, an open notebook with handwritten notes and a pencil resting on it, warm lamp light mixing with cool grey daylight, shallow depth of field, calm and focused mood, photographic style --ar 4:5
A wall covered in dozens of scattered, overlapping sticky notes in different colors. Slowly, the notes peel off and drift through the air, regrouping themselves into three neat columns labeled Now, Next and Later, settling with a gentle tap. The camera pulls back to reveal a person smiling and stepping toward the wall with a coffee. Soft natural office light, smooth motion, satisfying and calm mood, 8 seconds.
Use Claude Opus 5.5 for this one, since it is a hard judgement call. I am deciding whether to [DECISION] by [DEADLINE]. Context: [BACKGROUND, NUMBERS, CONSTRAINTS]. First list the assumptions my case depends on and mark each as verified, likely or a guess. Then argue against my preferred option as strongly as you honestly can, and tell me which single assumption, if wrong, would change the answer. Finish with a recommendation in three sentences and the cheapest check I can run this week to confirm it.
(Claude Cowork is rolling out gradually to Pro and Max plans, so it may not appear on every account yet.) I want you to take this on as a larger task: [TASK, e.g. organise the files in my project folder and draft a status summary]. Before you start, tell me your plan in 5 steps or fewer, list anything you need from me, and say what you will not touch. Work through it, check in if something is unclear, and finish with a short summary of what you did, what is left and what I should review myself.
Create an Artifact (Artifacts are available on every plan) that helps me compare [OPTIONS] against these criteria: [CRITERIA]. I want a clean one-page layout with a table, a weight for each criterion that I can change, and a total score for each option that updates. Use sample data first and mark clearly where I should replace it with my own numbers. Keep the design simple and readable on a phone.
Make a 6-slide deck for [AUDIENCE] about [TOPIC]. The goal is to [GOAL, e.g. get approval for a pilot]. Slide 1 is the key message, slides 2 to 5 cover the problem, the options, the recommendation and the costs, and slide 6 is the clear next step. Keep each slide to a headline and at most three short bullets, and add one line of speaker notes per slide. Use plain language and no jargon. (Claude Slides is available inside Artifacts on every plan, and in beta on Enterprise.)
Here are [NUMBER] emails and messages pasted below: [PASTE]. Work fast, this is a triage job. Sort them into four groups: reply today, reply this week, delegate, and ignore. For each item give a one-line reason. Then list the three replies I should send first, with a draft of two sentences each in a [TONE] tone. Return the result as four labelled lists, nothing else.
Below are my raw notes from a meeting about [PROJECT]: [PASTE NOTES]. Rewrite them as: (1) decisions made, (2) open questions, (3) action items with an owner and a due date, using [DATE] as today. If an owner or date is missing from my notes, write 'needs owner' or 'needs date' instead of guessing. Keep it under 250 words and end with a two-line message I can send to the group.
A client sent this message: [PASTE MESSAGE]. My situation: [WHAT REALLY HAPPENED]. My goal is to [GOAL, e.g. keep the relationship and agree a new deadline]. Write a reply under 150 words that acknowledges their concern in one sentence, takes responsibility only for what is actually mine, states the next step with a date, and does not sound defensive. Give me two versions, one warm and one more formal, and note what I could safely cut if I want it shorter.
I have attached [NUMBER] documents about [TOPIC]. Read them all, then give me a table with one row per key claim and columns for what each source says. Mark where the sources agree, where they disagree and where only one source speaks. Do not fill gaps from memory: if something is not in the documents, write 'not covered'. End with the three questions I should still answer before relying on this.
My core idea is: [IDEA]. My audience is [AUDIENCE] and I publish on [PLATFORM] about [FREQUENCY]. Plan a series of 8 pieces that build on each other, starting with the most beginner-friendly. For each give a working title, the one thing the reader should take away, a hook in one sentence and a simple call to action. Then suggest which two pieces would work best as a free starter pack, and why.
Use Claude Haiku 5.5 for speed, since I want lots of rough ideas fast. My process is: [DESCRIBE THE STEPS I FOLLOW]. Give me 15 ways to make it simpler, split into: remove a step, combine steps, automate a step and hand a step off. Keep each idea to one line. Then star the 3 ideas that would save the most time with the least setup, and tell me what to try first on Monday.
/plan I want to add [FEATURE] to this project. Do not edit any files yet. Explore the codebase and tell me: which files are involved, how similar features are already built here, what could break, and what tests exist near this area. Then give me a step-by-step plan with small, separately reviewable changes, say how you will test each step, and list any questions you need answered before starting.
The test [TEST NAME OR PATH] is failing. First run only that test and show me the exact failure. Find the root cause and explain it in two sentences before changing anything. Then make the smallest change that fixes it, without editing the test to make it pass, and rerun that test and the tests in the same folder. Show me the final diff and tell me if you think the bug could exist elsewhere, but do not fix other places without asking.
Run /code-review on the changes on my current branch compared with [BASE BRANCH]. Look for bugs, missing error handling, unclear names and missing tests. Report findings in order of severity, with the file and line for each, and mark which ones you are sure about and which are guesses. Do not change any files. After the report, propose the 3 fixes you would make first.
I have a larger or riskier change on [BRANCH OR PR NUMBER] that touches [AREA, e.g. billing or auth]. Run /ultrareview on it (it runs a multi-agent review in a cloud sandbox, so check it is available on your plan and that you trust this workspace first). When it finishes, summarise the findings by severity, tell me which are likely real problems and which look like noise, and list the follow-up tests I should add. Do not apply any fixes until I say so.
Our [PAGE OR ENDPOINT] feels slow. Start by measuring: find how to run it locally, record a baseline timing and tell me the number. Use /subtask to have a forked subagent read the related database or API code while you profile the front end, and have it report only the likely bottlenecks. Then propose up to 3 changes ranked by expected impact and risk, apply only the safest one, re-measure and show before and after numbers. Keep the diff small.
Look at the module [PATH] and find the functions with the weakest test coverage. List them and why they matter. Then write tests for the 3 most important ones, following the style and tools already used in this repo. Cover normal use, empty or missing input and one failure case each. Run the tests, fix problems in the tests only, and report what is now covered. Do not change the production code; if you find a bug, describe it instead.
Read this repository and write a CLAUDE.md file under 80 lines. Include: what the project does, how to install and run it, the exact commands for tests, linting and build, the folder layout in one line each, coding conventions you can actually see in the code, and things to avoid. Only include commands you have confirmed exist in the repo files. Show me the draft first and wait for my approval before saving it.
I have a CSV at [PATH] with problems such as inconsistent dates, duplicate rows and stray spaces. First read the first 30 rows and describe every problem you find. Then write a small Python script that reads the original, writes a cleaned copy to a new file named [OUTPUT NAME] and never overwrites the original. Print a summary of how many rows changed, were merged or were dropped, with a few examples of each. Run it on a copy and show me the results before I use it on real data.
Compare the documentation in [DOCS PATH OR README] with the actual code in [CODE PATH]. List every place where the docs are wrong, missing or out of date, such as commands, options, file names or examples. Then update only the docs, keeping the existing tone and formatting, and check each command or example you keep by reading the code or running it where it is safe. Give me a short list of what changed and anything you could not verify.
Read the git log for the last 7 days on this branch (read only, do not run anything that changes the repo). Group the commits into features, fixes and maintenance, and write a plain-English update of under 200 words for a non-technical reader, with a short list of what to expect next based on open TODO comments. Do not include commit hashes or names. Save it to [FILENAME].md and show me the text for review.
I need to choose between [OPTION A], [OPTION B] and [OPTION C] for [PURPOSE]. My top priorities are [PRIORITY 1], [PRIORITY 2] and [PRIORITY 3]. Ask me up to five questions first to learn what matters most. Then build a weighted scorecard (weights add up to 100), score each option from 1 to 5 with a one-line reason, and give a final recommendation. Return a table, then a short paragraph on the biggest risk of the winner.
My project is [PROJECT] and it must be finished by [DEADLINE]. Today is [TODAY'S DATE]. I can work [HOURS PER WEEK] hours a week. Work backwards from the deadline and give me milestones, the tasks under each one, and a buffer of at least 15 percent. Return a week-by-week table with columns: Week, Milestone, Tasks, Hours. Flag the two weeks most likely to slip and say why.
Here is my draft: [PASTE DRAFT]. My reader is [AUDIENCE] and they are skeptical because [REASON]. Rewrite it so it answers their likely objections early, uses plain words, and backs each claim with a specific example. Keep it under [WORD LIMIT] words. Return the rewrite, then a short list of the three biggest changes you made and why.
Write three versions of an email chasing invoice [INVOICE NUMBER] for [AMOUNT], now 30 days overdue, to [CLIENT NAME]. Version 1 is friendly, version 2 is firm and clear about next steps, version 3 is a final notice that mentions [LATE FEE OR POLICY]. Each should be under 120 words with a clear subject line and one specific payment deadline. Do not threaten anything I have not listed.
I have a call with [COMPANY] on [DATE]. I sell [PRODUCT]. Using only what I paste below and general knowledge, build a one-page briefing: what the company does, likely priorities this year, three questions to ask, two likely objections with answers, and one thing to avoid saying. Mark anything you are unsure of as 'check this'. My notes: [PASTE NOTES OR WEBSITE TEXT].
Turn this case study into five LinkedIn posts for one week: [PASTE CASE STUDY]. Use a different angle each day (the problem, the surprise, the numbers, the lesson, a question for readers). Each post is 80 to 140 words, written in first person for [MY ROLE], with no hashtags except one at the end. Return them labelled Monday to Friday.
My idea is [IDEA] for [CUSTOMER]. Suggest ten ways to test whether people want it in under two weeks and for less than [BUDGET]. For each give: what I do, what result would count as a yes, and what result would count as a no. Return a table sorted from cheapest to most expensive, then tell me which two to run first.
Here is an error and the code around it. Error: [PASTE STACK TRACE]. Code: [PASTE CODE]. Language and version: [LANGUAGE]. Explain in plain English what the error means, list the three most likely causes ranked by probability, and give the smallest fix for each. Tell me how to confirm which cause is real before I change anything.
I am unsure whether to fix, replace or stop [PROCESS OR TOOL]. Facts: it costs [COST] and [TIME] each month, it causes [PROBLEM], and the people affected are [WHO]. Walk me through each option with the cost, benefit and risk. Then give a recommendation, a rough first step for this week, and the one fact that would change your mind.
Create a weekly checklist for a team of [NUMBER] people who do [WORK]. Our recurring tasks are: [LIST TASKS]. Group them by day, give each an owner role (not a name), an estimated time, and a done condition. Keep it to one page and return it as a table, then suggest two tasks we could drop or automate.
Use Claude Sonnet 5.5 for this. I must decide [DECISION] by [DATE]. Options: [LIST OPTIONS]. What I care about: [VALUES]. Ask me three clarifying questions, wait for answers, then lay out the strongest case for each option, the main risk, and a reversible first step. End with your recommendation and how confident you are.
Create a document in Claude Docs (available inside Artifacts) titled '[POLICY NAME]' for [COMPANY OR TEAM]. Include: purpose, who it applies to, the rules in plain language, examples of what is and is not allowed, who to ask with questions, and a review date. Keep it under two pages and friendly in tone. Here are the facts to use: [PASTE DETAILS]. Do not invent legal requirements; mark anything I should check with a lawyer.
I want Claude to remember how I like to work. Memory is in Settings, and I can review it there. Ask me ten short questions about my role, how I like answers formatted, my usual tools and my pet peeves. Do not include sensitive topics such as health or finances. After my answers, summarize what you would remember in a list I can edit or delete.
A client keeps adding work. Here are their latest messages: [PASTE MESSAGES]. Our agreed scope: [SCOPE]. Write a reply under 150 words that thanks them, names what is in scope, offers two clear options (add to the project for [EXTRA COST OR TIME], or schedule for phase two), and asks them to choose by [DATE]. Return a subject line and the email only.
Compare these approaches to [PROBLEM]: [APPROACH A], [APPROACH B], [APPROACH C]. Use only the sources I paste below, and quote the line you rely on for each claim. Return a table with: strengths, weaknesses, best for, and cost. Then list what the sources do not tell us, so I know what to check next. Sources: [PASTE SOURCES].
Write a five email onboarding sequence for new customers of [PRODUCT]. The customer is [WHO] and their goal is [GOAL]. Each email has a subject line, a 90 to 130 word body, one action to take and a send timing (day 0, 1, 3, 7, 14). Keep the tone warm and clear, with no hype. Return them numbered, then a one line summary of the sequence's job.
Use Claude Haiku 5.5 for quick ideas. I am naming [PROJECT]. It is for [AUDIENCE] and should feel [TONE]. Give me 20 names in four groups: plain and descriptive, playful, short and invented, and metaphor based. Add a five word tagline for the five best. Flag any that might clash with well known brands so I can check.
Here is my draft: [PASTE DRAFT]. Rewrite it three ways: warm and personal, crisp and professional, and short and direct (under 60 words). Keep every fact the same. Under each version, add one line on when I should use it. Do not add claims that are not in my draft.
I am negotiating [WHAT] with [OTHER PARTY]. My ideal outcome is [IDEAL], my walk away point is [LIMIT], and what I know about them is [CONTEXT]. Give me: their likely goals, three things I can trade that cost me little, an opening position, responses to their three likeliest pushbacks, and a closing line. Keep it honest, with no pressure tricks.
I will be away from [DATE] to [DATE]. Interview me one question at a time to build a handover document for [COLLEAGUE'S ROLE]. Cover: ongoing tasks and deadlines, who to contact, where files live, decisions they can make alone and decisions to save for me. Do not ask for passwords. When we are done, return the final document in a clean format.
Summarize how different groups are discussing [TOPIC] right now: [GROUP 1], [GROUP 2] and [GROUP 3]. For each, list the main points, the tone, and one representative example described in your own words. Then say where they agree, where they truly disagree, and what claims are unsupported. Note how recent your information is, and label anything unverified.
Here is my plan: [PASTE PLAN]. Act as a sharp but fair critic. List the five weakest assumptions, the single most likely way it fails, and what a competitor would do in response. Be direct, but do not insult me. End with three specific changes that would make it stronger, ranked by effort.
Write five versions of a short X post announcing [PRODUCT OR UPDATE] to [AUDIENCE]. Each is under 260 characters, has a different hook (a question, a number, a problem, a result, a plain statement), and ends with a clear next step: [ACTION]. No hashtags and no emojis. Then pick the one you think performs best and say why in one sentence.
Here is the email I received: [PASTE EMAIL]. Write a reply under 80 words that answers the question directly, confirms the next step and date, and ends the thread politely. Give me two versions: one casual and one formal. Do not add promises I have not mentioned.
I create content about [TOPIC] for [AUDIENCE]. Give me 15 content angles that are different from what everyone else posts. For each: a working title, the unexpected angle in one sentence, and the format (post, video, thread, newsletter). Mark the three that would be easiest to make this week.
Write a [LANGUAGE] script that [TASK]. Input is [INPUT FORMAT] and output should be [OUTPUT FORMAT]. Keep it under 60 lines, handle empty and bad input, and avoid extra libraries. After the code, explain each section in plain English and give two example inputs with the expected output.
Build a 15 minute morning routine for someone who works as [ROLE] and gets [NUMBER] messages a day. Include: what to check first, what to ignore until later, how to pick one top priority, and a rule for when to say no. Return it as a numbered checklist with a time for each step.
Here is my piece: [PASTE TEXT]. Identify the three strongest points and rewrite the piece around only those, in under [WORD LIMIT] words. Remove filler, repeated ideas and weak examples. Afterward, list what you cut and why, so I can decide whether to put anything back.
Write a neutral one page briefing on [TOPIC] for someone who knows nothing about it. Include: the key terms, the main positions with their strongest arguments, the facts most people agree on, and the open questions. Avoid loaded words. Label which statements are facts and which are opinions, and note how current your information is.
My [METRIC] dropped from [OLD VALUE] to [NEW VALUE] over [PERIOD]. Things that changed: [LIST CHANGES]. Things that stayed the same: [LIST]. Give me a ranked list of the six most likely causes, a quick way to test each one, and what result would rule it out. Start with the cheapest test.
I will paste two versions of a document. Version A: [PASTE A]. Version B: [PASTE B]. List every meaningful difference, grouped as added, removed and changed, and quote the exact words. Then summarize in three sentences what the changes mean for [AUDIENCE], and flag anything that creates risk or confusion.
My goal is [GOAL] and I have [MINUTES] minutes on weekdays and [MINUTES] on weekends. My energy is highest at [TIME OF DAY]. Design a 4 week routine that starts small and builds. Return a weekly table with the daily action, how to know it is done, and one fallback for a bad day. Keep it believable.
Rewrite this paragraph so a smart reader with no background can understand it: [PASTE PARAGRAPH]. Keep the meaning accurate, replace jargon with plain words (or explain it once), and add one everyday comparison. Return the rewrite, then a list of any terms you simplified so I can check them.
Write an invitation email for [EVENT] on [DATE AND TIME] at [PLACE OR LINK]. The audience is [WHO] and the reason to come is [BENEFIT]. Include a subject line, a short body of under 120 words, the RSVP deadline [DATE] and one line about what to bring or prepare. Friendly tone, no pressure.
Create an outline for a [LENGTH] minute tutorial video that teaches [SKILL] to [AUDIENCE]. Return: a hook for the first 10 seconds, the sections with timings, what to show on screen in each, and a closing call to action. Add three common mistakes to mention. Keep the language simple.
I need ideas for [RECIPIENT TYPE, e.g. a team of 6 or a new client] with a budget of [AMOUNT] per person. Their interests: [INTERESTS]. Give me 15 ideas grouped as practical, experience and personal touch. For each, add a rough price and one sentence on why it fits. Avoid anything generic.
Two priorities clash: [PRIORITY A] and [PRIORITY B]. Deadlines are [DATES] and the people involved are [WHO]. Help me think it through: what happens if I pick each, what can be delegated or delayed, and what I should tell each stakeholder. Return a short plan and the exact wording for the hardest message.
I have a list in [SPREADSHEET OR CSV] with problems: [DESCRIBE, e.g. mixed capitals, extra spaces, duplicates, dates in different formats]. Show me the steps to clean it using [GOOGLE SHEETS OR PYTHON], with the exact formulas or code. Include a before and after example and a check I can run to confirm nothing was lost.
Turn these notes into a study guide: [PASTE NOTES]. Return: the 10 key ideas in plain words, a glossary of terms, 8 practice questions with answers hidden under each question as 'Answer:' lines, and a 3 day review schedule. Do not add facts that are not in the notes.
I am meeting [PERSON'S ROLE] for a one on one lasting [MINUTES] minutes. Topics on my mind: [TOPICS]. Create an agenda with time for each topic, the question I should ask for each, and what outcome I want. Add a closing question that surfaces anything I missed.
Do not edit any files yet. I want to [CHANGE] in this repository. Read the relevant code and tests, then tell me: which files you would change, why, what could break, and how you would verify it. Give a numbered plan of small steps, each ending in a passing test run. Wait for my approval before making changes.
The type checker reports errors related to [TYPE OR FUNCTION NAME]. Run the type check command for this project and show me the first output. Find the root cause, explain it in two sentences, then fix it with the smallest change, avoiding any casts to 'any' or ignore comments. Re-run the type check and the tests, and show me the final diff. Do not touch config, lock files or anything with secrets.
Add input validation to [ENDPOINT OR FUNCTION] in [FILE]. First read how validation is done elsewhere in this repo and match that style. Reject missing, wrongly typed and oversized values with clear error messages. Add tests for each case, run the test suite, and show the diff. Keep changes to this endpoint and its tests only.
Search this repository for code that looks unused: functions, exports, files and config flags in [DIRECTORY]. Do not delete or edit anything. For each candidate, show where it is defined, search results proving no references, and a confidence level. Return a markdown table I can review, and mark anything that could be used dynamically.
Review the uncommitted changes in this repo. Do not modify files. Look for bugs, missing tests, unclear names, security problems and anything that looks accidental. Return findings grouped as must fix, should fix and nit, each with the file and line and a suggested change. If the changes look good, say so plainly.
Look at [MODULE PATH] and its existing tests. Write a new test file covering the untested behaviour: normal cases, edge cases and error cases. Follow the repo's testing style and avoid network calls or real data. Run the new tests and the full suite, fix any problems in the tests, and show me a summary of what is now covered.
Read the README and follow its setup steps as written, using a safe local environment. Do not use real credentials. Note every step that fails or is out of date. Then update the README with corrected commands, required versions and a short troubleshooting section. Show me the diff and the list of problems you found.
Read the git history since [TAG OR DATE] (read only). Group the changes into new features, fixes and internal changes, and write release notes in plain English for non technical customers, under 250 words. Leave out commit hashes and author names. Save the result to [FILENAME].md and show me the text.
I have several export files in [FOLDER] (formats: [CSV OR JSON]). Write a [LANGUAGE] script that reads them without changing the originals, combines them, removes duplicate rows by [KEY COLUMN], and writes one summary file [OUTPUT FILE] with totals by [GROUP COLUMN]. Log how many rows were read and dropped. Add a small test with sample rows, run it, and show me the summary.
Read [FILE] and write clear docstrings for the public functions, covering what each does, parameters, return values, errors raised and one short example. Do not change any behaviour. Match the comment style already used in this repo, run the linter and tests, and show me the diff.
/goal All tests in [TEST DIRECTORY] pass and the linter reports no new warnings. Work in small steps: run the tests, find the first failure, fix it with the smallest change, and re-run. Do not edit test expectations unless you explain why they are wrong, do not touch .env files or lock files, and stop to ask me if a fix needs a change outside [DIRECTORY].
/simplify the changes on this branch. Look for duplicated logic, existing helpers I should have reused, needless complexity and wasteful loops. Apply only low risk cleanups, keep behaviour the same, run the tests after, and give me a short list of what changed and anything you left alone on purpose.
/btw In the code we are working on, what does [FUNCTION OR CONCEPT] do and where is it called from? Answer briefly in under 150 words with file paths, and do not change anything. After that, continue the main task we were doing.
/branch refactor-trial Try refactoring [MODULE] to [GOAL]. Plan first and show me the plan. Make the change in small steps, running the tests after each one. If the tests cannot pass without large side effects, stop and explain what you found so I can go back to the original conversation.
/verify the change I just made to [FEATURE]. Build and start the app in a local dev setup, exercise the feature the way a user would, and tell me what you observed. Include any errors in the console or logs. Do not use real accounts or production data, and tell me clearly if something could not be checked.
/loop 10m Run the test suite for [PACKAGE] and report only if something newly fails. If it fails, show the failing test name, the likely cause in one sentence and the smallest fix you would suggest, but do not apply it without asking me.
/deep-research Which should I use for [PURPOSE] in a [LANGUAGE] project: [OPTION A], [OPTION B] or [OPTION C]? Compare maintenance, license, bundle size, learning curve and fit with the stack in this repo. Give a cited report with a recommendation and the main risks. Do not install anything.
/security-review the code for [FEATURE]. Look for injection, missing authorization checks, unsafe file handling and secrets in code. Report findings by severity with file and line, and the smallest fix for each. Do not edit anything or read any secret values; just describe where they should come from instead.
Read this repository (read only) and write an onboarding guide for a new teammate, under 800 words. Cover: what the project does, how it is laid out, how to run it and the tests, the three files to read first, and common pitfalls. Save it as docs/onboarding.md and show me the outline before you write the full text.
/context Show me what is using the most space in this session. Then suggest what to drop, summarize or move into a CLAUDE.md file so future sessions start leaner. Propose any CLAUDE.md edits as a diff for me to approve, and do not include any secrets or personal data.
A clean, modern pricing comparison graphic with three columns titled 'Starter', 'Team' and 'Business', each with a short list of three features and a soft rounded card, white background, one accent color of deep teal, friendly sans serif font, plenty of white space, checkmark icons, centered layout, crisp text, 16:9 aspect ratio.
A friendly flat vector illustration of a support agent at a tidy desk helping a customer on a laptop screen, warm color palette of coral, cream and navy, simple shapes, soft shadows, no text, centered composition with space on the right for a headline, suitable for a help center header.
A realistic photo of a whiteboard in a bright meeting room with a hand drawn product roadmap in three columns labelled 'Now', 'Next' and 'Later', colored sticky notes, black marker handwriting, slightly angled view, soft natural window light, shallow depth of field, readable text.
Using the product photo I upload, place the same product on a light oak table beside a small green plant and a ceramic mug, morning window light from the left, soft shadows, neutral warm tones, shallow depth of field, keep the product shape, color and logo unchanged, square crop for a social post.
Create a friendly round robot mascot with a teal body, one antenna and large eyes, in the same style across three poses: waving, holding a clipboard and giving a thumbs up. Flat vector look, white background, equal sizing, consistent colors and proportions, no text.
Editorial style photograph of a bakery owner dusting flour from her hands behind a wooden counter, morning light through a large window, warm tones, candid expression, shallow depth of field, 35mm lens look, tidy shelves of bread in the background --ar 3:2 --style raw
Abstract minimal desktop wallpaper, soft flowing gradient of peach, lavender and pale blue with subtle grain, smooth curved shapes, calm mood, lots of empty space, no objects, no text --ar 16:9
A bold title card for a conference talk with the exact text 'Work Smarter, Not Louder' in large rounded sans serif letters, deep navy background, a single yellow underline stroke beneath the words, small geometric shapes in the corners, clean layout, high contrast, 16:9.
A book cover design with the exact title 'The Quiet Week' and the subtitle 'A calmer way to get things done', minimalist layout, cream background, a single hand drawn sun and horizon line in muted orange, elegant serif title text, author placeholder text 'Your Name' at the bottom, portrait 2:3.
A simple circular logo for a coffee shop named 'Morning Table' with the exact text in a friendly rounded font around the edge, a small steaming cup in the center, two colors only (dark brown and cream), flat vector style, balanced, easy to read at small sizes, plain white background.
A wide shot of an empty modern desk by a large window at sunrise, camera slowly dollies forward as warm light spreads across a laptop, a notebook and a plant, gentle dust particles in the air, calm and hopeful mood, soft natural color grade, 6 seconds, no people, no text.
Close up of two hands opening a small cardboard box on a wooden table and lifting out a [PRODUCT], camera slightly above and tilting down, soft diffused light, tidy and satisfying motion, shallow depth of field, neutral background, 6 seconds, no brand logos.
A time lapse style shot of a busy city crosswalk at golden hour, people crossing in streams, long shadows, camera fixed on a tripod at street level, warm orange light, slight motion blur on moving traffic, cinematic mood, 6 seconds, no readable signs.
Extreme close up of coffee being poured into a white ceramic mug in slow motion, steam curling upward, camera holds steady then drifts slightly to the right, warm kitchen light, rich dark tones, cozy mood, 5 seconds, no text.
A small green seedling on a desk grows into a leafy plant in a smooth time lapse, background shows window light moving from morning to evening, fixed camera at desk level, calm and satisfying, soft natural colors, 5 seconds, no people.
A smooth steady tracking shot moving forward down a quiet library aisle between tall wooden shelves, soft overhead lighting, dust floating in light beams, peaceful atmosphere, slightly desaturated colors, 5 seconds, no people, no readable text.
Take my uploaded product photo and add a slow push in with a subtle parallax effect, soft light shifting across the surface, background slightly blurring, keep the product exactly as it is, premium and clean mood, 5 seconds, no added objects or text.
A flat paper map on a table folds upward into a 3D paper cut skyline of buildings, top down camera slowly rotating, soft studio lighting, pastel colors, smooth satisfying motion, 5 seconds, no text.
Low angle shot of gentle ocean waves rolling toward the camera on a sandy beach at dawn, pink and blue sky, foam sliding across wet sand, slow motion, camera static, peaceful mood, 5 seconds, no people.
Close up of raindrops running down a window glass, soft out of focus city lights glowing behind in warm yellow and blue, camera slowly pulls focus from drops to lights, quiet moody atmosphere, 5 seconds, no people, no text.
Act as an operations coach. Here is how my process works today: [PASTE THE STEPS IN ORDER]. For each step, tell me what could go wrong, how likely it is, and how much damage it would do. Then name the single weakest link and suggest one low cost fix I can try this week. Return a table with columns Step, Risk, Likelihood (low/medium/high), Impact (low/medium/high), followed by your pick and the fix in three sentences.
I have 90 minutes of uninterrupted time on [DAY]. My goal is [GOAL] and my task list is [TASKS WITH ROUGH TIME ESTIMATES]. Build a 90-minute plan with a clear first step, two short breaks, and a buffer for things that run over. Tell me what to leave out if time runs short. Return a minute-by-minute schedule and one line on how I will know the block went well.
Here is the opening of my proposal for [CLIENT OR AUDIENCE]: [PASTE TEXT]. Rewrite it in three sentences: the problem they have, what I propose, and the result they can expect. Keep my tone [TONE] and remove filler words. Return the new version first, then a short list of what you cut and why.
A supplier has missed a delivery date. Details: order [ORDER], promised date [DATE], impact on me [IMPACT]. Write a firm but friendly email that asks for a new confirmed date, asks what caused the delay, and says what I need if it slips again. Keep it under 150 words. Return a subject line and the email body, then one softer alternative opening line.
I am choosing between [OPTION A] and [OPTION B] for [USE CASE]. Compare them on price, ease of use, support and long term risk. Mark every claim as Verified (you are confident it is widely documented) or Check this (I should confirm on the official site). Return a table plus a short recommendation and a list of the exact things I should verify before buying.
Here is a real customer review I have permission to share: [PASTE REVIEW]. Turn it into one social post for [PLATFORM] that quotes the strongest line, adds the context of what we do ([BUSINESS]), and ends with a soft invitation to [ACTION]. Return the post, a shorter caption version under 120 characters, and three hashtag options. Do not exaggerate beyond what the review says.
My newsletter is for [AUDIENCE] and covers [TOPIC]. Give me 20 issue ideas split into four groups: how-to, story, opinion and curated links. For each, give a working title and one sentence on why this audience would open it. Then pick the five easiest to write this month and say why. Return clean lists with headings.
Review this SQL query for [DATABASE]: [PASTE QUERY]. Table shapes: [PASTE SCHEMA]. Check for wrong joins, missing filters, accidental duplicates and slow patterns. Explain any problem in plain English, give a corrected query, and list which indexes might help. Do not invent columns that are not in the schema. Return Issues, Fixed query and Index ideas as three sections.
My team of [NUMBER] people makes decisions in [WHERE: chat, meetings, email] and we keep forgetting why we chose things. Design a simple decision log with fields we will actually fill in. Add two example entries for [TEAM TYPE], a 5-minute habit for keeping it up, and a rule for when a decision should be written down. Return the template as a table and the habit as a short list.
Here is my current job post for a [ROLE] at [COMPANY TYPE]: [PASTE]. Rewrite it so it is clear, honest and welcoming. Lead with the work and the outcomes, list must-haves separately from nice-to-haves, remove vague buzzwords, and include pay or range if I give it: [PAY OR LEAVE BLANK]. Return the new post and a short list of changes you made.
I will paste a project plan that has grown messy: [PASTE PLAN]. Use your strongest reasoning. Find hidden dependencies, tasks without an owner, steps in the wrong order and anything that does not support the goal [GOAL]. Return: 1) a cleaned up ordered plan, 2) a list of open questions for me, 3) the three biggest risks. Ask me before you assume anything important.
Use the fast model for this. Here are my tasks for the week with deadlines and rough effort: [PASTE]. Sort them into Do first, Schedule, Delegate and Drop. Give one line of reasoning for each and flag anything that has a hidden deadline. Return four short lists and a suggested order for Monday morning.
Here is my draft for [AUDIENCE]: [PASTE]. Pass one: only point out unclear sentences, repeated ideas and places where a reader might get lost, without rewriting. Pass two: after I reply 'go', rewrite the draft keeping my voice and my facts. Return pass one now as a numbered list and wait for my reply before pass two.
I have chased [VENDOR] about [ISSUE] on [DATES]. They have not answered. Write an email to a more senior contact that stays polite, states the facts in order, says what I need and by when ([DATE]), and mentions the next step I will take if I hear nothing ([NEXT STEP]). Keep it under 170 words. Return the email and a one-line subject.
I will upload documents about [TOPIC]. Write a one-page briefing for [AUDIENCE]. For every claim, quote the supporting line and name which document it came from. If documents disagree, show both versions. If something is not in the documents, say so instead of filling the gap. Return Summary, Key points with sources, Conflicts, and Gaps.
Create a single page mockup as an Artifact for [PRODUCT OR SERVICE] aimed at [AUDIENCE]. Include a headline, a short subhead, three benefits, a social proof area using clearly marked placeholder text, one call to action ([ACTION]) and a simple footer. Use calm colors that suit [BRAND MOOD]. After the Artifact, list three copy variations for the headline.
I run a [SERVICE BUSINESS] for [CUSTOMER TYPE]. My usual price is [PRICE] and my slow season is [MONTHS]. Brainstorm 12 offers that could fill the slow season, such as bundles, check-ups or memberships. For each, give a name, who it is for, a fair price range and the main effort for me. Mark the three I should test first and explain why.
Every [FREQUENCY] I do this by hand in a spreadsheet: [DESCRIBE STEPS]. The file has columns [COLUMNS]. Write a small Python script that does it, reads from a file path I pass in, never overwrites the original, and writes a new output file. Explain how to run it step by step for a beginner and list two things that could go wrong.
I am trying Claude Duet, which needs a Pro or Max plan and is a research preview. Act as a proactive helper for my weekly review. Ask me up to five short questions about [PROJECTS], then suggest what I should wrap up, what should wait and what I should start next week. Offer to remind me of anything that needs follow-up and keep every suggestion under two lines.
I want Cowork (Pro or Max) to help tidy the folder [FOLDER NAME]. First read the contents and propose a folder structure and a naming rule. Do not delete anything and do not move files until I approve your plan. Then list exactly which files you would move where, flag possible duplicates for me to decide on, and wait for my yes.
Here are recent customer complaints or reviews about [PRODUCT OR SERVICE]: [PASTE]. Group them into themes, count roughly how often each appears, and separate symptoms from root causes. Tell me which theme is cheapest to fix and which hurts retention the most. Return a ranked table and the single fix you would try first.
Tomorrow I must finish [TASK] by [TIME]. My fixed commitments are [MEETINGS] and my energy is best at [TIME OF DAY]. Plan the day so the key task gets my best hours, with a short buffer and a fallback if it takes longer. Keep it realistic. Return a simple hour-by-hour schedule and one rule for what I say no to.
Here is my announcement draft for [AUDIENCE]: [PASTE]. Cut it by a third without losing facts, dates or the call to action. Replace vague words with specific ones and keep a friendly, direct tone. Return the shorter version, then a list of the three phrases you removed that were doing the least work.
I need to move a deadline for [PROJECT] from [OLD DATE] to [NEW DATE] because [REASON]. The reader is [ROLE]. Write an email that owns the change, gives the reason in one sentence, offers what I can deliver by the old date, and asks for a yes or no by [DATE]. Under 140 words. Return subject and body.
Topic: [TOPIC]. Describe the main positions people hold, who typically holds them (types of people or groups, not named individuals), the best argument for each, and what each side tends to ignore. Use the latest information you can find and tell me which parts are fast moving. Return a table and a list of three questions to check before forming a view.
A topic in my field is getting attention: [TOPIC]. I work in [FIELD]. Draft a thread of 5 posts for X that adds something useful and honest: one real lesson from my work ([EXPERIENCE]), one practical tip, and one question for readers. No hype, no fake stats. Return the thread numbered and a short first post alternative.
I am naming [PRODUCT] for [AUDIENCE]. Give me 25 names that are short, easy to spell and easy to say out loud. Group them by style (plain, playful, invented, descriptive). Flag any that might be confused with a well-known brand so I can check them myself. Return the list, then your top three with one sentence each.
I need to rename files in [FOLDER STRUCTURE] from [OLD PATTERN] to [NEW PATTERN]. Write a bash script that first prints what it would do (dry run) and only renames when I pass a flag. It must skip existing names instead of overwriting. Explain each line briefly and show an example run with sample output.
My project [PROJECT] has been running for [TIME] and results are [RESULTS] against a goal of [GOAL]. Help me decide whether to continue, change course or stop. Ask me five sharp questions first, then give a recommendation with the evidence that would change your mind. Return questions first and wait for my answers.
I work as [ROLE] and my week usually ends messy. Build a 20 minute Friday routine that clears loose ends, records wins, prepares Monday and lets me switch off. Use my tools: [TOOLS]. Return a checklist with time per step and one question to ask myself at the end.
Someone is upset about [SITUATION]. Their message: [PASTE]. Split it into facts, feelings and requests. Tell me what I can fix now, what needs more information and what I cannot control. Draft a calm two-sentence reply opener I can use. Return the breakdown as three short lists and the opener.
I am planning [BIG CHANGE] in six weeks, on [DATE]. My constraints: [BUDGET, TIME, PEOPLE]. Build a week by week plan with the most important tasks, the ones that have lead time, and a short list of things to decide now. Add a checklist for the final 48 hours. Return a table by week.
Here is a long summary I wrote for [AUDIENCE]: [PASTE]. Reformat it with clear headings, short paragraphs and a top line that states the conclusion. Keep all facts. Highlight the three numbers or decisions a busy reader must see. Return the reformatted version and a one-sentence takeaway.
I just met with [PERSON, ROLE] about [TOPIC]. We agreed on: [AGREEMENTS]. Write a warm thank-you email that restates the agreements in a short list, names who does what and by when, and asks for confirmation. Under 160 words. Return a subject and body, plus a one-line text message version.
Compare [APPROACH A] and [APPROACH B] for [GOAL]. Use criteria that matter for someone in [SITUATION]: cost, effort, risk and time to results. Give both a fair hearing, say what each does best, and list where the evidence is weak. Return a table, a recommendation for my situation and three claims I should verify on official pages.
I want to write a how-to post about [TOPIC] for [AUDIENCE] based on my experience: [NOTES]. Create an outline with a hook, five steps, one mistake to avoid and a short closing. Then write the full post in about 400 words in a friendly voice. Return outline first, then the post.
I already have [CONTENT: guides, talks, emails, videos] about [TOPIC]. Brainstorm 15 ways to reuse it for [AUDIENCE] across formats such as checklists, short videos, emails and talks. For each, give the format, the first step and how long it should take. Mark the five that take under one hour.
Here is a Google Sheets formula: [PASTE]. The sheet has columns [COLUMNS]. Explain what it does in plain English, point out cases where it would break (blank cells, text instead of numbers), and give a more robust version. Return Explanation, Weak spots and Improved formula.
My errands this week: [LIST WITH LOCATIONS AND OPENING HOURS]. Group them by area, order them to save time, and put them into my free slots: [FREE SLOTS]. Point out which ones can be done online instead. Return a day by day plan and a short list of tasks to drop if I run out of time.
Here is my cold intro message to [PERSON TYPE]: [PASTE]. Rewrite it in under 90 words, lead with something relevant to them, make one clear ask and make it easy to say no. Return the new message and a version with an even softer ask.
Task: add pagination to the endpoint [ROUTE] in [PROJECT]. First read the relevant files and write a short plan (files to change, parameters, defaults, edge cases) and stop for my approval. After approval, make the smallest change that works, add tests for first page, last page and invalid input, run the test suite and show me the diff. Do not touch other endpoints, dependencies or secrets.
The module [FILE] uses a deprecated call [OLD CALL] and the replacement is [NEW CALL]. Plan first: list every use in this module. Then update only those uses, keep behavior identical, run the existing tests and linter, and show a summary diff. If tests fail, explain why instead of changing tests to pass. Do not edit other modules.
The test [TEST NAME] fails sometimes. First read the test and the code it covers, then list likely causes (timing, shared state, order dependence, randomness). Run it 20 times if safe and report the failure rate. Propose the smallest fix and wait for my approval before editing. Never skip or disable the test.
We plan to change [SCHEMA CHANGE] in [PROJECT]. Read the code that touches these tables and write a migration plan: affected files, steps in a safe order, how to roll back, how to test on a copy of the data and what could break. Do not edit files or run migrations. Return the plan as a numbered checklist with risks at the end.
The function [FUNCTION] in [FILE] is slow. Add timing logs around the main steps without changing behavior, keep log lines short and free of personal data or secrets, and make them easy to switch off. Run the tests, then show the diff and explain how I should read the output to find the slow step.
I repeatedly do this by hand: [DESCRIBE TASK]. Look at the repo conventions, then write a small script in [LANGUAGE] under [FOLDER] that does it, with a dry-run mode and clear error messages. Add a short usage section to the README. Do not run it against real data. Show how to test it with sample files.
The file [PATH] has inconsistent dates, extra spaces and duplicate rows. Write a script that cleans a copy of it, never the original, and prints a report of what would change (counts and 5 examples) before writing the output. Add a few tests with tiny sample data. Do not include real records in tests.
Read the repo and write a CONTRIBUTING.md that matches reality: how to set up, run tests, name branches, format code and open pull requests. Only include commands you can find in the repo's scripts or config, and mark anything uncertain with a TODO for me. Make no code changes and show the file for review.
Review the component [FILE] for accessibility issues: labels, keyboard use, focus order, color contrast hints and ARIA misuse. List the issues by severity with line references, then fix only the clear ones with small changes. Run the tests and linter, and show the diff. Do not redesign the component.
Search the repo for TODO and FIXME comments. Do not edit any file. Group them by area, estimate effort (small, medium, large), flag any that look like bugs or security concerns, and suggest the top five to tackle first. Return a table with file, line, comment, effort and your reason.
/plan Add rate limiting to [ENDPOINT OR ROUTE] in this project. Read the existing middleware and tests first. In the plan, list files to change, the limit and window I should choose, how it behaves for logged in versus anonymous users and how we will test it. Wait for my approval before editing. Afterwards, make small reviewable diffs, run the tests and show /diff.
/batch Rename the function [OLD NAME] to [NEW NAME] everywhere it is used, including tests and docs. Research the codebase first and show me the plan with the list of units of work. Only continue after I approve. Keep each unit small and independent, run the tests for each, and report anything that needs a human decision. Do not push or change unrelated files.
My branch [BRANCH] has an open pull request. Run /autofix-pr with this instruction: fix CI failures and clear review comments with the smallest possible changes, never skip or disable tests, never rewrite published history and never touch secrets or config outside the files involved. If a comment needs a design decision, stop and ask me instead of guessing.
Run /auto-mode-setup for this project. Read the repo and my recent sessions, then draft entries that describe our environment, such as trusted internal services, branch rules and what is safe to run. Show me the draft, explain each entry in one line, and let me edit before saving. Do not include secrets, tokens or personal data.
/schedule Create a weekly cloud scheduled task for [REPO] that checks which dependencies have newer versions, lists security notes from the changelog, and opens no pull requests. It should only produce a short report with risk level per package. Walk me through the setup, and tell me which connectors it will use before you create it.
Run /insights and summarize the report for me. Tell me which projects I use Claude Code on most, where things went wrong repeatedly, and three features or habits that would save me time. Then suggest a few lines to add to my CLAUDE.md based on what the report shows. Do not change any files without asking.
We are finishing today's session on [TASK]. Run /recap, then write handoff notes for a teammate: what was done, what is left, files touched, commands to run and open questions. Keep it under 300 words and leave out anything sensitive. Then use /export to save the conversation to [FILENAME] outside the repo.
The file [PATH] has dates in mixed formats. Write a script that converts them to YYYY-MM-DD in a copy of the file. First print a dry-run report with counts and 10 sample conversions, and list any values that cannot be parsed. Add tests with made up sample rows. Do not modify the original file and do not log real records.
Run /security-review on my current branch. List findings by severity. Then fix only the highest one with the smallest diff, add a test that would have caught it and run the full test suite. Show /diff and stop so I can review before you move to the next finding. Do not edit secrets, environment files or unrelated code.
I changed [FEATURE] in [FILES]. Run /verify to build and start the app, then check the change in practice: [STEPS TO TRY]. Report what you saw, what matched my expectation and what did not, with exact error messages. Fix only clear bugs in the files I changed, and rerun the check afterwards.
Create a clean horizontal infographic showing a three step process for [TOPIC]: step 1 '[STEP ONE]', step 2 '[STEP TWO]', step 3 '[STEP THREE]'. Flat vector style, white background, rounded cards connected by arrows, a simple icon per step, a calm palette of navy, teal and warm orange. Render the text exactly as written in a readable sans serif. 16:9 layout with generous spacing.
A realistic photo of a small glass jar of [PRODUCT] on a light wooden kitchen shelf, a white label on the jar reading '[PRODUCT NAME]' in clean dark lettering, a linen cloth and a small plant nearby. Soft window light from the left, shallow depth of field, natural colors, no extra text, no logos. Close, slightly angled shot.
Use the attached photo of my [ROOM] and keep the layout, windows and furniture position the same. Restyle it as a calm Scandinavian look: light oak, white walls, soft wool textures and warm evening light. Do not add people or text. Keep proportions realistic and the lighting consistent with the original.
A clear labeled diagram of [CONCEPT] for [AUDIENCE], drawn like a clean textbook illustration on a white background. Label the parts '[LABEL ONE]', '[LABEL TWO]' and '[LABEL THREE]' with thin leader lines. Muted colors, consistent line weight, readable text, nothing decorative around it.
Editorial photograph of a [CRAFT] artisan at a workbench in a small studio, hands in sharp focus, tools and materials around, warm window light from the right, subtle dust in the air, muted earthy palette, shot on a 50mm lens at f/2, candid, authentic, no text. --ar 4:5 --style raw
Isometric miniature city where each building is a day of the week, with small workers, calendars and coffee carts, soft pastel palette, clean lines, gentle shadows, white background, playful but tidy, high detail, no text. --ar 3:2
A bold typographic poster with the headline '[SHORT HEADLINE]' in large rounded letters centered, a small tagline '[TAGLINE]' beneath it, abstract soft shapes in [COLOR ONE] and [COLOR TWO] behind, lots of empty space, grain texture, flat modern design. Spell the text exactly. 4:5 ratio.
A square social card with the text 'Tip of the day' in small caps at the top and '[ONE LINE TIP]' as the main message in bold dark letters on a cream background. Add a simple hand drawn underline, a small icon of [SIMPLE ICON] in the corner and a thin [BRAND COLOR] border. Clean, readable, no extra words.
Product photograph of a [COLOR] hardcover notebook with a ribbon bookmark on a pale stone surface next to a pen and a ceramic cup, soft diffused daylight, gentle shadow, subtle paper texture, minimal composition with space at the top for text, realistic, sharp focus, no logo, no text.
A set of six matching vector icons for a settings page: profile, notifications, billing, security, language and help. Simple 2 pixel outline style, rounded corners, single color [HEX COLOR] on white, equal size on a clean grid, flat, no gradients, no text.
Slow dolly forward through a quiet sunlit cafe in the morning, steam rising from cups on wooden tables, soft golden light through large windows, shallow depth of field, calm warm mood, no people in focus, no text, 5 seconds, 16:9.
Close up of a hand writing a short checklist in a paper notebook with a fine pen, a ceramic cup and a plant softly blurred behind, gentle camera push in, natural window light, calm focused mood, legible handwriting not required, 5 seconds, 16:9.
A tidy wooden bookshelf assembles itself in a bright room, books sliding in one by one by color, smooth stop-motion feel, fixed wide shot, soft daylight, satisfying and calm, no people, no text, 5 seconds.
Reflection of a city skyline in a tram window at sunrise, passing buildings, soft blue to orange gradient, gentle camera sway, a commuter's hand holding a coffee cup in the foreground, quiet reflective mood, no readable text, 5 seconds, 16:9.
Macro time lapse of a seed sprouting in a small clay pot on a sunny windowsill, soil cracking, green shoot rising and unfolding two leaves, fixed camera slightly low angle, soft morning light, peaceful mood, no text, 5 seconds.
Tracking shot following a bike courier from behind on an empty city street at dawn, mist on the road, warm streetlights fading, smooth forward camera movement, cinematic color, realistic motion, no logos, no readable text, 5 seconds, 16:9.
Starting from the supplied flat lay photo of desk items, animate a slow orbit around the scene, a gentle shift of light across the objects, steam curling from the cup, everything else stays still and consistent, smooth natural motion, 5 seconds.
Wide static shot of a mountain lake at first light, mist drifting slowly across the water, faint ripples, pink and blue sky slowly brightening, peaceful, no people, no boats, no text, 5 seconds, 16:9.
Low angle shot of a small paper boat floating along a rain gutter after a shower, droplets splashing around it, camera tracks alongside at water level, cool soft light, playful mood, shallow depth of field, no people, no text, 5 seconds.
Medium shot of a chef's hands placing herbs on a plated dish in a clean professional kitchen, steady camera with a slow push in, warm overhead light, realistic motion and textures, quiet focused mood, no faces shown, no text, 5 seconds, 16:9.
I need a flyer concept for [EVENT NAME] on [DATE] at [VENUE]. Audience: [AUDIENCE]. Tone: [TONE, e.g. friendly and professional]. Use Claude Design (check it is available on your plan) to make a first layout. Include the headline, date and place, one line of detail, and a clear call to action: [CALL TO ACTION]. Use only these brand colors: [COLORS]. Then give me three short notes on what to tweak, and offer two alternative layouts I can compare.
Open this in Claude Docs. Draft a proposal for [CLIENT] about [PROJECT]. Use this structure: a short summary of their problem, our approach in 3 steps, deliverables, timeline, price, and next steps. Facts to use: [KEY FACTS, SCOPE, BUDGET]. Keep the language plain and under two pages. Mark anything you had to assume with [CHECK] so I can confirm it before sending.
I use Claude with Cowork (Pro or Max plan). Please work only inside the folder I shared: [FOLDER]. Read the files there and build a one page monthly report for [CLIENT]: what we did, results with numbers copied exactly from the files, what is slipping, and next month's plan. Do not rename, move or delete any file. Save the report as a new file and list which source file each number came from. Ask me before you do anything beyond that.
Act as a fair but sharp reviewer using Claude Opus 5.5. Here is my pitch: [PITCH]. The audience is [AUDIENCE] and the goal is [GOAL]. Find the 5 weakest points in the logic, such as missing evidence, jumps in reasoning or unstated assumptions. For each, show the exact sentence, why it is weak, and one fix. End with the single change that would improve the pitch most.
Using Claude Sonnet 5.5, write an email to [CLIENT NAME] about a delay on [PROJECT]. Facts: original date [DATE], new date [NEW DATE], reason [REASON], what we are doing to recover [ACTIONS]. Tone: honest, calm and accountable, no excuses and no jargon. Keep it under 150 words, lead with the new date, and end with one clear question or next step. Give me a subject line and one shorter variant for a text message.
Write my professional bio in three lengths: one sentence (under 25 words), a short paragraph (about 60 words) and a full version (about 150 words). Facts: [ROLE], [COMPANY OR PROJECT], [KEY ACHIEVEMENTS], [WHAT I CARE ABOUT]. Voice: [TONE]. Write in the third person, avoid buzzwords, and do not invent any fact I did not give. Return the three versions labeled clearly.
I run [BUSINESS OR NEWSLETTER] for [AUDIENCE] who struggle with [PROBLEM]. Brainstorm 12 lead magnet ideas I could build in under a weekend, such as checklists, templates or mini guides. Return a table with: idea, format, why my audience would want it, and effort (low, medium, high). Then pick the top 3 and explain your choice in one line each.
Help me write a code review checklist for a team working in [LANGUAGE AND FRAMEWORK]. We care most about [PRIORITIES, e.g. readability, security, tests]. Return a checklist of 15 to 20 items grouped under headings like Correctness, Tests, Security, Readability and Performance. Each item should be one short, checkable question. Add a short note on what a reviewer can safely skip on small changes.
My question is: [QUESTION]. My background: [LEVEL]. Without inventing sources, suggest a reading path of 8 well known books, papers or reputable sources you are confident exist. Order them from easiest to hardest. For each give the title, author, why it helps with my question, and what to skim or skip. Tell me clearly if you are unsure about any item so I can check it.
Plan the week of my launch for [PRODUCT OR PROJECT] on [LAUNCH DAY]. Fixed commitments: [MEETINGS AND DEADLINES]. Work hours: [HOURS]. Must-do tasks: [TASKS]. Build a day by day schedule with time blocks, buffers for surprises and one 30 minute break each day. Put the hardest task in my best energy window: [WHEN]. Return a simple table and name the two tasks I could drop if things go wrong.
Plan first, do not edit yet. I want to move the Claude API code in this repo to the newest API version using the /claude-api api-version command. Step 1: list every file that calls the Claude API and the version it uses. Step 2: run the command and show me the proposed changes as small diffs. Step 3: run the existing tests and tell me what failed. Do not touch .env files, keys or lockfiles. Wait for my approval before applying each group of changes.
Run /claude-api managed-agents-secure for the Managed Agents setup in this repo. It compares my agent settings with Anthropic's security guide and changes nothing. Then summarize the results in a table: setting, current value, what the guide recommends, and risk (low, medium, high). Do not edit any file or print any secret values. End with a prioritized list of fixes I can approve one at a time.
I want Write, Edit and NotebookEdit to refuse paths outside my working directories. Look up the permissions.blockWritesOutsideWorkingDirectories setting in the Claude Code docs, then propose the smallest change to .claude/settings.json in this repo. Show me the diff before saving, explain what will be blocked, and tell me how to test it with one safe example. Do not change any other permission rule.
Fast mode for Opus 4.8 is deprecated and will be removed on November 30, 2026. Search this repo's scripts, docs and Claude Code settings files for references to Opus 4.8 or fast mode. Do not open .env files or print secrets. Return a table of file, line and what it does, then propose changes to move to Opus 5.5 as small diffs. Wait for my approval before editing anything.
ultrathink. I need to choose between [OPTION A] and [OPTION B] for [FEATURE] in this codebase. Read only the files that matter: [PATHS]. Compare them on complexity, risk, testability and how hard they are to undo. Do not edit any files. Return a short recommendation, the 3 strongest reasons, the main risk, and a step by step plan with the tests I should write first.
I want to control how much effort subagents use in Claude Code. Read the Claude Code docs for the CLAUDE_CODE_SUBAGENT_EFFORT environment variable and tell me its allowed values; do not guess. Then recommend a value for my work: [TYPE OF WORK, e.g. quick searches and test fixes]. Show how to set it for one terminal session only, not globally, and how to unset it again.
Write an architecture decision record for the change in commit [COMMIT] or branch [BRANCH]. Read the diff and related files, then fill in: context, decision, options we did not choose, consequences, and how to revert. Mark anything you are guessing with [CHECK] instead of inventing a reason. Save it as docs/decisions/[NUMBER]-[SHORT-NAME].md and change no other file.
I have two exports: [FILE A] and [FILE B] that should describe the same [THINGS, e.g. customers]. Write a read only Python script that matches rows on [KEY COLUMN] and reports rows only in A, rows only in B, and rows where [COLUMNS] differ. Output a new report file and never modify the originals. Run it on a 20 row sample first and show me the results before the full run.
Plan first. In [FILE], convert [FUNCTION] from callbacks to async and await without changing its behavior. List every caller you find. Make the smallest diff possible, update the callers, and add or adjust tests to cover success, failure and a timeout. Run the test suite and show me the output. If anything is unclear, ask before editing.
Search the code for every environment variable this app reads and write a table for the README: name, where it is used, what it does, whether it is required, and a safe example value such as your-value-here. Never open .env files and never print real values. Mark any variable whose purpose you cannot confirm with [CHECK]. Show me the README diff before saving.
I have linked my accounts in Personal Finance in Claude (beta, needs a Pro, Max or Ultra plan, US only). Using only what is shown there, review my spending for [MONTH]. Return: 1) a table of spending by category with totals, 2) recurring charges and subscriptions I should double check, 3) three categories where spending rose the most compared with the previous month, 4) three small, realistic changes that could save money, each with a rough monthly amount. Say clearly what you could not see, do not guess numbers, and remind me this is general information, not financial advice.
Using what you remember about my work and projects (needs Memory turned on; Monthly recap is a beta feature for Free, Pro and Max on web and desktop), help me look back on [MONTH]. Return: 1) the main projects I worked on, 2) wins worth remembering, 3) things that kept slipping, 4) patterns in how I work that you can see from our chats, and 5) three focus areas for next month. If you do not have enough memory to answer a part, say so instead of guessing, and ask me up to three questions to fill the gaps.
Here is my draft of [DOCUMENT TYPE] for [AUDIENCE]: [PASTE DRAFT]. Do not rewrite it from scratch. Edit it in place: keep my structure and voice, fix unclear sentences, cut repetition and tighten the opening. After editing, give me a short list of the five most important changes you made and why, and flag any claim that needs a source. If something is fine as it is, leave it alone.
First, answer this quick question in two sentences: [QUICK QUESTION]. Then, in the same conversation, take on this larger task: prepare a [REPORT OR PRESENTATION] about [TOPIC] for [AUDIENCE]. If you can use Cowork for it (available on Pro and Max), plan the steps first and show me the plan before you start. Use only the files and connectors I have shared, list any information you are missing, and finish with a one-paragraph summary plus the deliverable in [FORMAT].
Using Claude Sonnet 5.5, write a three-email follow-up sequence after a demo of [PRODUCT OR SERVICE] with [PROSPECT ROLE] at [COMPANY TYPE]. What they cared about: [THEIR TOP TWO PRIORITIES]. Email 1 (same day): thank them and recap what they said. Email 2 (day 3): share one useful resource and one proof point. Email 3 (day 8): a polite, low-pressure check-in with a clear next step. For each email give a subject line, a body under 120 words and one call to action. Tone: warm, direct, no pressure, no hype.
If you have access to Claude Fable 5.1, use it for this research task. Question: [MARKET OR INDUSTRY QUESTION] for [MY BUSINESS TYPE] in [REGION]. Work in steps: break the question into sub-questions, answer each one, and mark every claim as sourced, reasoned or uncertain. Return: a one-paragraph answer, a table of key findings with sources, the three biggest risks to my plan, and a list of what I should verify myself before making a decision. Do not invent statistics or sources.
Using Claude Haiku 5.5 for speed, sort this list of customer feedback: [PASTE FEEDBACK, ONE ITEM PER LINE]. Return a table with the original text, a theme (use at most eight themes), sentiment (positive, neutral or negative) and urgency (low, medium or high). Then list the top three themes by count, one short quote that shows each, and one suggested action per theme. Do not merge items that mean different things.
My goal is vague: [GOAL]. Help me make it concrete. Ask me up to five short questions first, then wait for my answers. After that, return: 1) the goal restated as a clear outcome with a date, 2) what success looks like in numbers or checks, 3) the three next actions, each under 30 minutes, 4) one thing that could block me and how to handle it. Keep the whole answer under 250 words.
Below is a transcript of an interview with a customer: [PASTE TRANSCRIPT]. Pick the three most useful quotes for a short case study or social post. Keep the customer's exact words, only trim filler, and never change the meaning. For each quote give the context, the point it proves and a suggested one-line caption. Then list anything I must confirm with the customer before publishing, such as permission to use their name, company or numbers.
I run [BUSINESS TYPE] and want to win back customers who have not bought in [TIME PERIOD]. My audience: [AUDIENCE]. Brainstorm ten ways to re-engage them that take under two hours each to set up and cost little or nothing. For each idea give a one-sentence description, the channel, a sample opening message under 40 words, and how I would measure whether it worked. Rank the top three by effort versus likely result.
Run /usage and read the warnings it shows. For each warning, explain in plain English what it means and which of my habits probably caused it (for example very long sessions or heavy subagent use). The one-line fixes can be applied by pressing f, so list them first and let me choose which ones to apply. Do not change any settings yourself. End with a short checklist of three habits that would keep me under my [5-hour LIMIT] more often.
Our test suite is slow and I want to keep working while it runs. Start [TEST COMMAND] in the background and use the Monitor tool to watch its output. Report back only when it finishes or a test fails, with the failing test name and the first useful lines of the error. Do not change any code. After it finishes, summarize the slowest five tests and suggest, without applying, two safe ways to speed them up.
I have a bug that I have not been able to explain: [BUG DESCRIPTION] in [FILE OR MODULE]. Before you start, tell me which effort level you would use and why, and let me set it with /effort. Then investigate in plan mode: list your top three hypotheses, the evidence for each, and the smallest check that would confirm or rule it out. Do not edit files until I approve one hypothesis. Then fix it with the smallest diff, add a test that failed before the fix, and run the whole suite.
I often leave long Claude Code sessions open and come back later. Explain what idle compaction does (a conversation over 200K tokens left idle for about 54 minutes is compacted before the one-hour prompt cache expires) and how I can turn it on or off in /config or with the idleCompaction setting in settings.json. Show me my current value first. Recommend whether to keep it on for my usual work of [TYPICAL WORK], and only change a setting after I confirm.
One test fails now and then: [TEST NAME]. Plan first and tell me which files you will read. Run that test 20 times to see how often it fails and capture the error. Find the real cause, such as timing, shared state, test order or random data. Fix the cause with the smallest diff. Do not skip, retry-wrap or delete the test. Run the test 20 times again, then the full suite, and show me the before and after results and the diff.
Run the project's linter and group the warnings by rule. Pick the single rule with the most warnings that is safe to fix, [RULE NAME OR LEAVE BLANK FOR YOU TO CHOOSE]. Plan first: tell me the rule, how many warnings there are, the files you will touch and why the fix is safe. Wait for my approval, then fix them in small groups without changing behaviour or disabling any rule. Run the tests and the linter after each group and stop if anything breaks. Show me the final diff summary.
Write or update the Quick Start section of README.md. Read package.json (or the build files) and any existing docs to find the real install, run, test and build commands. Only include commands that exist, and run the safe ones (install, test, build) to confirm they work. Do not invent environment variables or features. List anything unclear as a question to me at the end. Show me the diff before you finish, and touch no other files.
I have a contact export at [FILE PATH] with phone numbers in mixed formats. Plan first. Write a small script that reads the file and writes a new file called [OUTPUT FILE] with numbers in [FORMAT], without changing the original. Numbers that cannot be fixed with confidence must go to a separate review file, not be guessed. Print a dry run summary with counts of fixed, unchanged and needs review rows, and show five before and after examples. Add a test for the main cases. Do not delete or overwrite any data.
Review how [APP OR MODULE] talks to its database. Using only the code and the schema files (do not connect to any live database), find queries that are likely slow: queries inside loops, missing filters, unbounded selects and filters on columns that look unindexed. Do not edit anything. Return a table with the file, the query, why it may be slow, a suggested index or rewrite, and the risk of the change. Keep it to the ten most important items and say how I could measure each one safely.
Create a small script called [SCRIPT NAME] that prints a release checklist. It should read the latest git tag, list commits since that tag grouped by type, point out commits with no message body, and list the checks to run before release (tests, build, changelog updated). The script must only read from git and never tag, push or change anything. Plan first, add a short usage note to the docs, test it on this repo, and show me the full diff before finishing.
In ChatGPT Work, pick GPT-6.1 Terra from the model list under Advanced (it is rolling out on Plus, Pro, Business, Enterprise and Edu plans and is not available in Chat). Research [COMPETITOR] for [MY COMPANY], using the files I attach and public sources, and cite every claim. Deliver a finished two-page brief as a document with these sections: what they sell, published pricing, who they target, three strengths, three weaknesses and what changed in the last 90 days. End with a table of claims you could not verify. Ask me before taking any action beyond research.
Create a dot named [NAME] to keep [PROJECT] moving (dots are rolling out to eligible Pro and Business Premium accounts; create one in the ChatGPT mobile app, desktop app or a desktop browser). Each weekday at [TIME] [TIME ZONE] until [END DATE], check [CONNECTED PLUGINS, e.g. Slack and Google Drive] for new activity on the project. Send routine progress to [CHANNEL] and anything that needs my decision to [OTHER CHANNEL]. Each update: a three-bullet summary, open risks, and decisions needed with your recommended option. Confirm the schedule back to me before the first run, and ask before sending messages or changing files on my behalf.
Create a scheduled task that runs when a new Gmail message arrives from [SENDER OR DOMAIN] (event-triggered tasks need Gmail connected and are on eligible plans). For each email: summarize it in two sentences, list any dates, amounts and requests, and draft a reply in my tone for me to review. Never send anything yourself. Before turning it on, test it here on this sample email: [PASTE SAMPLE] and show me the exact output format each run will produce.
In ChatGPT Work, use @[PLUGIN, e.g. Google Drive] to read the files in [FOLDER] and build a six-slide deck reviewing [TEAM]'s week for [AUDIENCE]. Slides: 1) headline result, 2) numbers versus last week, 3) what shipped, 4) what slipped and why, 5) risks, 6) asks for leadership. Keep each slide to one idea and at most four bullets, use only figures found in the files, and add a final note listing each figure's source file. Return the finished file for me to review.
Use the files in this project's Sources (past proposals, reports and emails for [CLIENT]) to write a one-page house style sheet I can follow when writing for them. Cover: tone in three adjectives with an example sentence each, words and phrases they use often, words to avoid, how they format headings, numbers, dates and lists, and how long their paragraphs usually are. Quote a short example from the files for each rule. Return it as a clean document with headings, then suggest two lines I could add to the project instructions.
Something went wrong at work: [WHAT HAPPENED, WHEN, WHO WAS AFFECTED]. Here is the timeline as I know it: [PASTE NOTES]. Write a blameless review that focuses on systems, not people. Sections: summary in three sentences, impact, timeline, contributing factors, what went well, and three to five follow-up actions with an owner role and a due date placeholder. Ask me up to three questions first if key facts are missing. Keep it under 600 words.
A customer asked for this feature: [PASTE REQUEST]. Our decision is [YES / NO / LATER] because [REASON]. Write a short, warm reply that thanks them, gives the decision plainly in the first two sentences, explains the reason without jargon, and offers one practical workaround or next step. No promises about dates unless I give one. Return a subject line and an email under 150 words, plus a one-line internal note I can log in our tracker.
I run [BUSINESS TYPE] serving [CUSTOMERS], with an average sale of [AMOUNT] and a budget of [BUDGET] per month for rewards. Brainstorm 12 referral program ideas, from simple to creative. For each give: how it works in one sentence, the reward, cost per referral, and the main risk. Then pick the three best for a business my size and write a one-paragraph launch plan for the top one. Return the ideas as a table.
Here is a sample JSON response from [API NAME]: [PASTE JSON]. Write a typed data model for it in [LANGUAGE, e.g. TypeScript or Python with dataclasses]. Mark fields optional when the sample suggests they can be missing, use clear names, and add a parse function that validates the input and returns helpful errors. Include three small unit tests: a valid response, a missing optional field and a wrong type. Explain any guesses you made about field types.
Help me estimate the market for [PRODUCT] in [REGION] from the bottom up, not with a big top-down number. Step by step: define the customer, estimate how many exist, what share could buy, how often and at what price. Show each assumption in a table with a low, likely and high value and where I could check it. Then give the resulting range and the two assumptions that move the answer most. Mark every number that is your estimate rather than a cited figure.
Write a Python script that sends [TASK DESCRIPTION] to grok-4.7 on the xAI API with reasoning effort set to xhigh (the levels are low, medium, high and xhigh; high is the default) and asks for structured output that matches this JSON schema: [SCHEMA]. Read the API key from an environment variable, never hard-code it. Add a timeout, retries with backoff, and a --dry-run flag that prints the request without sending it. Validate the response against the schema and explain each part in short comments.
Here is code from my app that calls the xAI image API: [PASTE CODE]. The model grok-imagine-image-quality was retired on November 2, 2026, and requests to it and to grok-imagine-image-pro are now served by grok-imagine-image-2.0 at low quality. Find every reference to the old names, explain what the silent routing means for my output and costs, and propose an explicit switch to grok-imagine-image-2.0 with a quality setting I choose on purpose (check the current docs for allowed values). Return a table of file, line, current value and suggested value, then a small diff and the tests I should run.
My app uses Grok through the xAI API for [USE CASE] and its users are [AUDIENCE]. Help me use the guidelines array (added in October 2026 on Chat Completions and Responses requests) to set how nsfw, violence and profanity are handled. Propose a setting for each category with a one-line reason, show the request change in [LANGUAGE], and write three test prompts per category so I can check the behavior. Remind me to confirm the exact allowed values in the docs before shipping.
I want to build a voice assistant for [USE CASE] using grok-voice-3.0 on the xAI API (released in October 2026; grok-voice-latest now points to it and grok-voice-2.0 is deprecated). Before any code, write a one-page plan: the three main user journeys, what the assistant must never say or do, when it hands off to a human, what to log and what not to store, how to test it with ten real phrases, and a short migration note in case we currently use grok-voice-2.0. Return it as a checklist with open questions at the end.
Search recent posts on X about [PRODUCT OR LAUNCH] from the last [NUMBER] days. Group the reactions into praise, complaints, questions and confusion. For each group give a rough share of posts, two short paraphrased examples (no usernames), and what it tells us. Flag anything that looks like spam or coordinated posting. End with the three questions we should answer in our FAQ this week. Return a table plus a five-line summary.
Here is our policy update: [PASTE TEXT]. Rewrite it for customers who will skim it on a phone. Start with one sentence on what changes and when, then a short list of what it means for them, what they need to do (if anything) and where to ask questions. Keep legal meaning intact, flag any sentence you were unsure how to simplify, and stay under 200 words. Return the rewrite and a list of the changes you made.
Write a renewal reminder email for [PRODUCT OR SERVICE]. The customer's plan renews on [DATE] at [PRICE]. Give them three clear choices: renew as is, change plan, or cancel, each with one line on how. Be friendly and direct, no pressure tactics or fake urgency. Return two subject lines and an email under 140 words with a short P.S. that mentions one useful thing they may have missed: [FEATURE OR TIP].
Turn these release notes into a short, honest changelog post for customers: [PASTE NOTES]. Lead with the change people will notice most, explain each update in one plain sentence about what it means for them, group small fixes into one line, and mention any known issue openly with a workaround. No hype words. Return a title, the post under 250 words, and a 260-character version for X.
We spend about [AMOUNT] per [MONTH OR YEAR] on [COST, e.g. software seats or shipping]. Brainstorm 15 ways to lower it without hurting quality for [CUSTOMERS OR TEAM]. Include quick wins, negotiation ideas and process changes. For each, estimate effort (low, medium, high), likely saving as a range, and one risk. Then rank the top five by saving per hour of effort and return everything as a table.
Two stakeholders gave conflicting feedback on [PROJECT]. Person A ([ROLE]) said: [PASTE]. Person B ([ROLE]) said: [PASTE]. Separate what each actually needs from how they phrased it, find where they agree, and name the real point of conflict. Offer three options that could satisfy both, with the trade-off of each, and draft a short neutral message I can send to both to agree on a path. Return the analysis as short sections.
Using Gemini 4 Argon (rolling out in the Gemini app to Google AI Pro and Ultra subscribers), analyze the attached financial report for [COMPANY OR TEAM]. I need to decide [DECISION]. Return: a five-sentence summary, the ten numbers that matter most in a table with page references, three trends with what is driving each, red flags or unusual items, and questions I should ask the finance team. Keep figures exactly as written in the report and say clearly when you are inferring.
Using Gemini 4 Argon (Google AI Pro and Ultra), build a presentation deck on [TOPIC] for [AUDIENCE] from these scattered sources: [PASTE NOTES, LINKS AND FILE NAMES]. Aim for [NUMBER] slides with one message per slide, a clear storyline (problem, insight, plan, ask), and short speaker notes for each slide. Use only facts from my sources and list any slide that needs a number I have not given you. Show me the outline first and wait for my OK before building the full deck.
In the Gemini macOS app, click Antigravity at the top (English only, for eligible accounts 18 and over in supported regions) and give the agent this task: build [SMALL TOOL, e.g. a script that renames exported invoices by date and client] in [LANGUAGE] inside the folder [FOLDER]. First show me a short plan for approval. Then write the code, add tests, run them, and notify me when it is ready for review with a summary of the changes. Do not touch files outside that folder, install global packages, or read any secrets.
Create a skill called [NAME] that turns my rough notes into my weekly report (Skills in Gemini chat are rolling out to users 18 and over). The steps: group notes into wins, progress, blockers and next week; keep each bullet under 20 words; add a one-line headline at the top; flag anything that sounds like a risk; and end with three priorities for next week. Use it whenever I paste notes and say 'weekly report'. Test it now on these notes: [PASTE NOTES].
Open Gemini with Alt + Space in the Gemini app for Windows (Windows 10 or later). Here is an email thread I need to answer: [PASTE THREAD]. Draft a reply that answers every question asked, confirms [KEY DETAIL], and proposes [NEXT STEP] with two time options. Keep it under 120 words, friendly and clear. Then give me a one-line version I could send from my phone.
Here is our internal feature spec: [PASTE SPEC]. Rewrite it as an update for customers who are not technical. Explain what is new, who it helps, how to start using it in three steps, and any limits they should know about. Remove internal names, ticket numbers and jargon. Keep it under 250 words and return a headline, the update, and a list of anything in the spec you left out on purpose.
New hires on our [TEAM] take about [TIME] to become productive. Here is our current onboarding: [DESCRIBE STEPS]. Brainstorm 12 ways to shorten that without overloading people, covering the first day, first week and first month. For each idea give the effort to set up, who owns it and how we would measure it. Then pick the three with the best payoff and draft a simple first-week schedule using them. Return a table and the schedule.
My spreadsheet total for [WHAT IT MEASURES] is [AMOUNT], but the source system says [OTHER AMOUNT]. Here are my formulas and a sample of the rows: [PASTE]. Walk through the most likely causes in order, such as hidden rows, text stored as numbers, duplicates, date filters and rounding, and tell me exactly how to check each one. Then give a corrected formula if one is wrong. Return a numbered checklist I can work through in ten minutes.
Write a Google Apps Script for my Google Sheet [SHEET NAME] where each row is [WHAT A ROW IS] with columns [LIST COLUMNS]. Every Monday at 9 am it should total [METRIC] for the last seven days, list the top five rows by [COLUMN], and email a short plain summary to [MY EMAIL PLACEHOLDER]. Add a test function that logs the email instead of sending it, explain how to set the time-driven trigger, and keep the code commented and easy to change.
I need a new [ROLE] to start on [START DATE]. Work backwards to build a hiring timeline: job post, sourcing, screening, interviews, decision, offer, notice period and onboarding prep. Use realistic durations for [COUNTRY OR INDUSTRY], show the latest date each step must begin, and mark where we have no slack. Return a dated table and a short list of the three steps most likely to slip, with one way to protect each.
In the Codex CLI (0.164.0 or later), run /presets and save the following into slot [NUMBER] so I can reuse it: 'Review the uncommitted changes in this repo. List bugs, missing tests and unclear names, ordered by severity, with file and line. Suggest the smallest fix for each but do not edit files. Run the existing test command and report the result. Finish with a yes or no on whether this is ready to commit.' Then run the preset once on my current changes and show me the output.
Codex keeps failing on network steps in this project. Run codex doctor --network-only (Codex CLI 0.166.0 or later) and explain the results to me in plain English: what passed, what failed and the most likely cause. List the fixes in order of least to most invasive for me to apply myself. Do not change proxy, firewall or security settings, and do not print any tokens or keys that appear in the output.
Use /model to switch to GPT-6.1 Terra with a high reasoning effort (Codex CLI 0.164.0 added inline arguments for model, effort and speed; Terra is in Codex on Plus, Pro, Business, Enterprise and Edu plans). Then read [MODULE OR FOLDER] and write a refactor plan to [GOAL, e.g. split it into smaller services]. Include the files affected, the order of small safe steps, tests to add first, and risks. Make no edits until I approve, then do step one only, run the tests and show me the diff.
Main task: [DESCRIBE CODING TASK] in [PROJECT]. Work on it with small diffs and run the tests after each change. While you work, I will use /side for quick questions such as 'what does this config flag do' so the main thread stays focused; answer those briefly and do not change files from the side conversation. When the main task is done, summarize what changed, what you tested, and anything from the side questions I should follow up on.
Create a scheduled task with a GitHub event trigger for new issues in [REPO] (event-triggered tasks need GitHub connected and an eligible plan). For each issue: summarize it in two sentences, suggest labels from this list: [LABELS], check for likely duplicates and link them, and draft a friendly first reply asking for any missing details such as version and steps to reproduce. Do not post, close or relabel anything yourself; put your suggestions in this chat for me to approve. Test it first on issue [NUMBER].
In [PROJECT], I want to ship [CHANGE] behind a feature flag called [FLAG NAME], off by default. First find how the repo already handles config or flags and write a short plan: files to change, where the flag is read, and how to test both paths. Wait for my OK. Then implement it with the smallest diff, add tests for flag on and flag off, run the full test suite, and show me the diff. Do not change unrelated code or any secrets.
Add end-to-end tests for the signup form at [ROUTE] using the test framework this repo already uses (check before choosing). Cover: successful signup, missing required fields, invalid email, password too short and a duplicate account. Use test data only and never real accounts or production URLs. Plan the test cases first and show me, then write them, run them, and report any that fail with your best guess at the cause. Do not change app code unless I approve it.
Our team often deals with [ISSUE, e.g. a stuck job queue]. Read the related code in [FOLDERS] and the existing docs, then write a runbook in docs/runbooks/[NAME].md: symptoms, how to confirm the cause, safe step-by-step fixes, when to escalate, and how to verify recovery. Only include commands that exist in this repo, mark any destructive step clearly and never include real credentials. Show me the draft before saving.
Upgrade [PACKAGE] from [CURRENT VERSION] to [TARGET MINOR VERSION] in [PROJECT]. First read its changelog and list the changes that could affect us, with the files that use them. Wait for my OK, then update only that package and its lockfile, fix any breakages with small diffs, run the full test suite and the build, and show me the diff with a short summary. Do not upgrade other packages.
Before I change [FEATURE OR FIELD], read the code and map how that data moves through [PROJECT]: where it enters, every function and file that reads or writes it, where it is stored, and where it leaves the app (APIs, emails, exports). Do not edit any files. Return a numbered flow with file paths, a simple text diagram, and a list of places a change could break something, ranked by risk.
Using GPT-Image-2.6 with SVG output through the Image API, create a simple flat icon of [OBJECT] for a [APP TYPE] web app. One centered symbol, two colors only, [#HEX1] and [#HEX2], rounded strokes of even width, no gradients, no shadows and no text. Clean geometric shapes that stay clear at 24 pixels, square canvas with even padding on all sides.
Using GPT-Image-2.6 with animated GIF output through the Image API, create a short looping animation for a product update email: a [PRODUCT TYPE] app window on a soft [COLOR] background where a checklist ticks off three items one by one, then resets. Flat, friendly illustration style, gentle motion, no people, no logos, and no text other than the three short item labels '[ITEM 1]', '[ITEM 2]', '[ITEM 3]' rendered exactly.
Edit the attached screenshot of [PAGE] using the attached annotation layer (markup-guided edits in GPT-Image-2.6 through the Image API; markup cannot be combined with a mask). Where I circled the header, make it [CHANGE]. Where I drew an arrow, move the [ELEMENT] there. Where I crossed out, remove that element and fill the space naturally. Keep every other part of the page, the fonts and the colors exactly the same.
Using Nano Banana 2.1 at a 1:4 aspect ratio, create a tall infographic banner for a blog sidebar titled '[TITLE]'. Five stacked sections, each with a simple icon and a short label: '[POINT 1]', '[POINT 2]', '[POINT 3]', '[POINT 4]', '[POINT 5]'. Flat illustration style, white background, a calm palette of [COLOR 1] and [COLOR 2], even spacing, clear sans serif text rendered exactly as written, no other words.
Use the attached [NUMBER] reference photos of my [PRODUCT] (Nano Banana 2.1 accepts up to 10 object images) and create a realistic lifestyle photo of it on [SURFACE] in [SETTING]. Keep the product's shape, colors, label and proportions exactly as in the references. Soft natural window light from the left, shallow depth of field, eye-level angle, 4:5 aspect ratio, no people and no added text. In the next turn I will ask you to change only the background, so keep everything else steady.
Using Nano Banana Pro for high-fidelity text, create a chalkboard-style menu board for a small cafe called '[CAFE NAME]'. Sections 'Coffee', 'Tea' and 'Bakes', each with three items and prices exactly as follows: [LIST ITEMS AND PRICES]. Hand-lettered look but fully readable, small doodles of cups and pastries in the margins, warm wood frame, front-on view, 3:4 aspect ratio. Check that every price and spelling matches my list.
Edit these [NUMBER] product photos into one clean catalogue image (grok-imagine-image-2.0 multi-image editing takes up to 5 source images): place the [PRODUCTS] side by side on a seamless light grey background, evenly spaced and at the same scale, with soft studio lighting and matching shadows. Keep each product's colors, labels and shapes unchanged. No text, no props, wide landscape framing with room above for a headline.
Create a concept image for a rebrand moodboard for [BUSINESS TYPE] that wants to feel [THREE ADJECTIVES]. A styled still life of everyday objects from the business, [OBJECTS], arranged on a textured paper surface. Color palette of [COLORS], soft directional light, gentle shadows, editorial photography style, top-down angle, no logos, no people and no text.
Using Ideogram 4.5, design a wide webinar announcement banner. Headline: '[WEBINAR TITLE]'. Subline: '[DATE] at [TIME] [TIME ZONE]'. Small button-style label: 'Save your seat'. Modern, minimal layout with the text on the left and an abstract shape illustration on the right, palette of [COLOR 1], [COLOR 2] and off-white, bold sans serif headline, plenty of empty space. Render all text exactly as written and nothing else.
Using Ideogram 4.5, design a front label for a small-batch [SAUCE TYPE] bottle called '[BRAND NAME]'. Include the product name '[PRODUCT NAME]', the line '[FLAVOR DESCRIPTION]' and '[VOLUME]' in readable type. Hand-drawn illustration of [INGREDIENT] in the center, vintage letterpress style with a [COLOR] and cream palette, shown flat and front-on as a printable label, portrait orientation. No other text.
Gemini Omni 1.2 Flash, 8 seconds, 16:9. Single continuous shot, no scene cuts: a [PRODUCT] sits on a matte [COLOR] turntable in a bright studio and rotates one full slow turn while the camera holds still at eye level. Soft even key light with a gentle rim light, clean reflections, realistic materials. Audio: calm ambient background music and a faint mechanical hum, no dialogue, no text on screen.
Using first and last frame in Gemini Omni 1.2 Flash (this works for 3 to 10 second videos), start from the attached 'before' photo of [ROOM OR SPACE] and end on the attached 'after' photo. 6 seconds, 9:16. Over the clip, clutter fades away and items slide into their new places in a smooth, believable way while the camera slowly pushes in. Bright daylight, calm satisfying mood. Audio: light whooshes and a soft chime at the end, no dialogue.
Gemini Omni 1.2 Flash, 12 seconds, 9:16, single continuous shot. Overhead view of hands on a clean desk. [0-4s] the hands open a notebook to a blank page. [4-8s] they write three short checkbox lines with a pen. [8-12s] they tick the first box and set the pen down. Warm morning light, steady camera, realistic hand motion. Audio: pen scratching, page turning and soft lo-fi music, no dialogue, no readable text.
Using grok-imagine-video-1.5 image-to-video, animate the attached photo of [PRODUCT] into a 10 second clip at [ASPECT RATIO]. Slow push in toward the product as soft light sweeps across it from left to right, a few dust particles drifting in the light, background gently out of focus. Keep the product's shape, colors and label unchanged. No on-screen text.
Using grok-imagine-video-1.5 with the attached reference images of our mascot [MASCOT DESCRIPTION] (it accepts up to 14 reference images), create a clip of about 8 seconds at [ASPECT RATIO]: the mascot walks into a tidy home office, waves at the camera, then sits at a desk and opens a laptop. Camera tracks sideways at the mascot's height. Bright, friendly 3D animation style, keep the mascot's colors and proportions exactly as in the references. No text on screen.
Extend my attached clip of [SCENE] from its last frame using Grok Imagine video extension. Continue the same camera move, [DESCRIBE MOVE], for [EXTRA SECONDS] more seconds as [WHAT HAPPENS NEXT, e.g. the camera rises to reveal the city skyline]. Keep lighting, color grade, motion speed and style exactly matched so the join is invisible. No new characters and no text.
In Runway Agent, use Seedance 2.5 Draft Mode for a quick 480p draft first, then enhance the version I pick. Scene: close-up of hands slicing fresh [VEGETABLE] on a wooden board in a sunny home kitchen, then sliding the pieces into a sizzling pan. Slow push in, shallow depth of field, warm natural light. 8 seconds. Native audio: knife taps, sizzle and soft kitchen ambience, no dialogue, no faces, no text.
Seedance 2.5 on Runway, 20 seconds, single continuous take. A smooth gimbal walk-through of a small independent [SHOP TYPE]: enter through the front door, glide past neatly stocked shelves, pause on [HERO PRODUCT] on the counter, then turn to the window where afternoon light pours in. Warm, inviting mood, realistic textures, no people facing the camera, no readable signs. Native audio: door bell, quiet room tone and soft acoustic music.
Runway Gen-4.5 image-to-video at the 1584:672 widescreen ratio, [DURATION] seconds (pick from the durations Runway offers). Starting from my attached landscape photo of [LOCATION], add gentle natural motion only: clouds drifting slowly, grass and leaves moving in a light breeze, and a very slow push forward. Keep the composition, colors and horizon exactly as in the photo, no new objects, no people and no text, so it loops calmly behind a website headline.
Using Runway Aleph 2.0 on my attached clip (input must be 2 to 30 seconds at 30 fps or lower; the output keeps its resolution up to 1080p), restyle the scene of [SCENE] as a snowy winter evening: light snow falling, frost on surfaces, cool blue tones with warm glowing windows. Keep the camera movement, timing, people's motion and layout exactly the same. No added text or logos.
Using the iCloud Mail plugin (available on all ChatGPT plans on web, desktop and iOS), look at emails in my inbox from the last [NUMBER] days that I have not replied to. Ignore newsletters and receipts. Return a table with sender, subject, what they need and how urgent it seems. Then draft a short reply for the top [NUMBER] in my usual tone: friendly, direct, under 100 words each. Do not send anything; I will review and send myself.
Using the iCloud Calendar plugin, look at my calendar for [DATE RANGE]. I need [NUMBER] hours of focused time for [PROJECT], in blocks of at least 90 minutes, between [START TIME] and [END TIME]. Suggest the best blocks in a table with day, time and what meeting, if any, could be moved to make room. Do not create, move or delete any events; give me the list so I can add them myself.
In Work, create a presentation in Space (for eligible Pro, Business and Enterprise users with Space access). Use the attached example deck for structure and style, and my notes for content: [PASTE NOTES]. Ten slides for [TARGET CUSTOMER]: the problem, who we help, how it works, two short customer examples, pricing summary, objections and answers, and a clear next step. Max 30 words per slide, speaker notes for each, and only the numbers I gave you. List any claims you think need a source.
Using the GPT-6 Pro option in the Chat tab (eligible Pro users), research the market for [PRODUCT TYPE] in [REGION]. Split the work into parts in parallel: market size estimates from public sources, the top five competitors and their published pricing, customer complaints from reviews, and regulation that could matter. Cite every claim. Combine it into one brief with a summary table, three opportunities, three risks and a list of numbers you could not confirm.
I am trying Texting your dot (beta for Pro users in the U.S., over iMessage or RCS). Text me once each weekday at [TIME] about my goal: [GOAL, e.g. send two sales follow-ups before lunch]. Keep each text under 25 words, vary the wording, and ask me one short question I can answer with a number. On Fridays, send a short recap of my answers for the week. Do not text me about anything else unless I ask.
I saved a photo of our [PRODUCT] as a reference image named @[NAME] in ChatGPT Images. Brainstorm six packaging directions for it, then create one image for each: [DIRECTIONS OR LET CHATGPT CHOOSE, e.g. minimal kraft paper, bold color block, premium matte black]. Keep the product shape and logo position from @[NAME] the same in every image, plain background, soft studio light. After the images, give a two-line note on who each direction would appeal to.
Build a ChatGPT Site for [EVENT NAME] on [DATE] at [VENUE]. Pages: a home page with the date, time, place and a short description, a sign-up form that collects name, email and [ONE QUESTION], and a thank-you page. Store sign-ups in the site's database and give me a simple admin view that only I can see. Clean, readable design that works on phones. Before publishing, list what is stored and who can see it.
Rewrite our refund policy so customers can understand it in one minute: [PASTE POLICY]. Keep every rule and time limit exactly as it is; only change the wording. Use plain words, short sentences and these sections: who can get a refund, how long they have, how to ask, how long it takes, and exceptions. Under 200 words. Then list any parts of the original that were unclear or that might contradict each other.
I need to decide whether to hire someone for [ROLE] or outsource the work. Details: the work involved [TASKS], expected hours per week [HOURS], budget [BUDGET], how sensitive the work is [NOTES] and how fast I need results [TIMELINE]. Compare hiring full time, part time, a freelancer and an agency in a table on cost, speed, quality control, risk and flexibility. Recommend one option, say what would change your answer, and give me a 30-day plan to get started.
I have uploaded an audio recording of a call with [CUSTOMER] about [TOPIC] (audio uploads need a paid ChatGPT plan). Transcribe and summarize it. Return: a five-line summary, decisions made, open questions, follow-ups with owner and date if said, and three short direct quotes that show what the customer cares about most, with rough timestamps. Do not add anything that was not said on the call.
Our Claude Enterprise organization is about to use project tags (beta, for eligible Enterprise organizations) to see spend by the codes we already use. Here are our Claude projects with a one-line description each: [PROJECT LIST]. Here are our cost codes or client-matter numbers: [CODE LIST]. Return: 1) a table mapping each project to one code with a short reason, 2) projects that could fit two codes, with the question I should ask to settle each one, 3) projects that fit no code, 4) a three-sentence note I can send project owners asking them to confirm their tag by [DATE]. Do not invent codes that are not on my list.
I use Personal Finance in Claude (beta, Pro, Max or Ultra plans, US only) with my accounts linked. I am thinking about [PURCHASE] for about [AMOUNT] in [MONTH]. Using only the balances and spending shown there, tell me: 1) my average monthly spending over the last three months, 2) how much is usually left after regular bills, 3) whether this purchase fits without dipping into [SAVINGS GOAL], and 4) two ways to make room for it, with rough amounts. Return a short table plus a yes, not yet or no answer with one line of reasoning. Say what you could not see, do not guess numbers, and note that this is general information, not financial advice.
I am using Claude Duet (research preview on Pro and Max plans). Here are my notes from this week's meetings: [PASTE NOTES]. Pull out every follow-up that is mine, with who it is for and the due date if one was said. Return a checklist ordered by due date, then a short list of follow-ups that belong to other people that I may want to nudge. Ask me before setting any reminders, and flag items where the owner or date is unclear instead of guessing.
I am an admin on a Claude Enterprise plan. We are turning on some of the new security and admin controls: [WHICH CONTROLS, e.g. security center, centralized management] (some are in beta). Write a short internal announcement for [AUDIENCE] that explains, in plain words: what is changing, the date [DATE], what people will notice, what they do not need to do anything about, and who to contact with questions [CONTACT TEAM]. Use only the details I give you about each control. Keep it under 200 words with a subject line and three short sections.
A customer wants to cancel [PRODUCT OR SERVICE]. Their message: [PASTE MESSAGE]. Write a reply that thanks them, confirms we will cancel if they still want to (and how), asks one honest question about what went wrong, and offers [ONE CONCRETE OPTION, e.g. a pause or a plan change] without pressure. Under 130 words, warm and direct, no guilt or discounts I have not listed. Give two subject lines and the email body.
Using Claude Opus 5.5 with web search on, research [REGULATION OR RULE CHANGE] and how it affects a [BUSINESS TYPE] in [COUNTRY OR REGION]. Use official or primary sources first and cite every claim. Return: a five-line summary, key dates in a table, what we must do, what is optional, open questions that are still unclear, and a short list of sources with dates. Mark anything you could not confirm from a primary source, and remind me to check with a qualified adviser.
Make a five-slide deck in Claude Slides from this quarterly memo: [PASTE MEMO]. Slides: 1) headline result in one sentence, 2) three key numbers with a short note each, 3) what went well, 4) what did not and what we are changing, 5) the decision or support we need from the board. Max 25 words per slide, plain headings, and add speaker notes of two to three sentences per slide. Use only numbers from the memo and list any you had to leave out.
I am launching [SERVICE] for [TARGET CUSTOMER]. My costs are roughly [COSTS] and competitors charge about [COMPETITOR PRICES]. Brainstorm 15 ways to package it into tiers, then pick the three best and return them as a table: tier name, who it is for, what is included, what is left out on purpose, and a suggested price range with your reasoning. Add the one risk of each tier and a question I should test with five real customers before launch.
Build an interactive Artifact: a quote calculator for my [BUSINESS TYPE]. Inputs: [INPUTS, e.g. number of rooms, service level, rush delivery yes or no]. Pricing rules: [RULES]. Show a live total, a short breakdown of how it was worked out, and a reset button. Keep the design clean and readable on a phone, label every field clearly, and add a small note that the quote is an estimate. After building it, list the pricing rules you applied so I can check them.
Here are my team's recurring meetings with length, how often, who attends and what each is meant to achieve: [MEETING LIST]. For each one, score it from 1 to 5 on clear purpose, decisions made and whether it could be async. Return a table, then recommend which meeting to cut, which to shorten and which to keep, with the hours saved per month. Finish with a short message I can send the team proposing a four-week trial of the changes.
Help me choose a tier of the new X Subscription, which puts Grok, Grok Bot, Cursor and X Premium on one plan. The tiers are Free, Plus ($8 a month), Premium ($30, 4x Plus usage), Super ($100, 15x) and Ultra ($200, 50x). Here is how each person on my team uses these tools in a normal week: [USAGE PER PERSON]. Return a table with a suggested tier per person and the reason, the total monthly cost, and the one person whose tier I should watch after a month. Ask me questions if my usage notes are too vague to decide.
@[DATA BOT NAME] For [METRIC] over the last [NUMBER] weeks, break the numbers down by [DIMENSION, e.g. region or plan]. Return a short table, one chart, and three sentences on what changed most and the likely reason. Say which tables and filters you used so I can check them, and flag any week with missing or odd data instead of smoothing it over. (Written for a Team Bot set up like xAI's Data Bot in Grok Bot, with access to our warehouse.)
Write a Python script that calls the xAI API with grok-imagine-image-2.0 to create a 21:9 website banner from this description: [BANNER DESCRIPTION]. Leave quality on its default of auto. Add an optional edit mode that accepts up to 5 source images, so I can pass in product photos. Read the API key from an environment variable, never hard-code it, save results with a timestamped filename, and add a --dry-run flag that prints the request instead of sending it. Explain each part in short comments.
Write a small Python function that asks Grok on the xAI API to answer [QUESTION TYPE] using the Web Search tool with allowed_domains set to these sites: [UP TO 5 DOMAINS]. Note in a comment that allowed_domains and excluded_domains each take up to 5 entries and cannot be used together. Return the answer with the source links it used, read the API key from an environment variable, and add one example call and a simple test that checks the request includes the domain list.
Create a Grok Bot routine that runs every Monday at [TIME] (check that your plan includes Grok Bot). Using my connected Google Calendar and Gmail, prepare a short briefing: this week's meetings with one line of prep each, emails from [IMPORTANT PEOPLE OR DOMAINS] still waiting on my reply, and deadlines mentioned in the last week. Keep it under 200 words in three sections. Read only: do not send emails, accept invites or change my calendar.
My app sends user messages to Grok through the xAI Responses API. Show me how to add the safety_identifier field to each request so a policy violation can be traced to one of my end users without sending personal data. Use a one-way hash of our internal user ID, not an email or name. Give me a small code change in [LANGUAGE], a note on how it differs from the older user field, and a unit test that checks the field is set and never contains raw IDs.
Write a short email to [CONTACT NAME] at [PARTNER COMPANY] inviting them to co-host a webinar on [TOPIC] for [AUDIENCE] around [DATE RANGE]. Say why it is a good fit for both audiences in one line, what we would handle (registration, slides, promotion) and what we would ask of them (one speaker, one email to their list). Under 150 words, friendly and specific, with a clear yes or no question at the end and two subject line options.
Here is our product update: [PASTE UPDATE]. Write three versions for X: 1) a single post under 200 characters, 2) a post of about 600 characters with a short list of what changed, 3) a five-post thread that explains who it helps and how to try it. Plain, honest tone, no hype words, no invented numbers, at most one emoji per post. End each version with a simple call to action: [ACTION, e.g. try it in settings].
I am running a 60-minute customer advisory board for [PRODUCT] with [NUMBER] customers from [CUSTOMER TYPE]. Brainstorm 25 open questions across these themes: what they use most, what frustrates them, what they would pay more for, and where the market is going. Then pick the eight best questions, put them in a sensible order for the session, and add a follow-up probe for each. Avoid leading or yes or no questions.
Rewrite this long Slack update into five bullets that a busy reader can take in within 20 seconds: [PASTE UPDATE]. Order: the result, what changed, what is blocked, what I need from whom, and the next date to watch. Each bullet under 20 words, keep names and numbers exactly as written, and add one bold line at the top with the single thing people must know. Then list anything you cut so I can check nothing important was lost.
I have attached [DOCUMENT NAME] as a PDF. Open it so I can preview and edit it in this chat. Make these edits: tighten the introduction to three sentences, fix grammar and spelling throughout, make every heading follow the same style, and turn [SECTION] into a short numbered list. Do not change any figures, names or dates. When done, give me the edited file to download and a list of every change you made, grouped by page.
I have uploaded a photo of my sketch for a small [APP TYPE, e.g. shift sign-up sheet] app. Using Canvas, read the sketch and build a working version I can test in the preview. Keep the layout close to my drawing, label every button and field clearly, make it usable on a phone, and store test data only in the page. After it runs, list what you guessed from the sketch so I can correct it, and suggest three small improvements I can ask for next.
I run [BUSINESS NAME], a [BUSINESS TYPE] in [TOWN]. Using the Gemini app's new small business tools with Nano Banana 2.1, create three promo images for [OFFER OR EVENT]: a square social post, a vertical story and a wide web banner. Use my brand colors [COLORS] and this short line rendered exactly: '[TEXT]'. Clean, friendly style with plenty of space around the text, no stock-looking people, no other words. Then write a 40-word caption for each.
Switch on the tasks toggle in the chat window (Google AI Pro and Ultra) and keep working on this while I am away: build a list of [NUMBER] [TYPE OF ORGANIZATION, e.g. industry events] in [REGION] for [DATE RANGE] that fit [CRITERIA]. For each, return name, date, location, cost if published, why it fits and the official link. Put it in a table sorted by date, mark anything you could not confirm on an official page, and do not register, buy or contact anyone.
Open the student hub at gemini.google.com/students and start an Immersive exploration of [TOPIC] for someone with [LEVEL, e.g. no background] who needs it for [GOAL]. Start with the big picture, then go one layer deeper at a time: key ideas, how they connect, a worked example and common mistakes. At each layer ask me one quick check question before going on. Finish with a one-page summary and five terms I should know.
Using my connected apps from the Customize menu (for example OpenTable; most apps are English and US only), help me plan a team dinner for [NUMBER] people in [CITY] on [DATE] with a budget of about [BUDGET PER PERSON]. Needs: [DIETARY NEEDS], near [AREA], quiet enough to talk. Suggest three options in a table with cuisine, price range, available times and why it fits. Do not make a booking until I pick one and say yes.
Write a short email to [VENDOR CONTACT] at [VENDOR] turning down their pitch for [PRODUCT OR SERVICE]. Thank them for their time, give one honest reason [REASON, e.g. budget is set until next year], and say when it might make sense to talk again [TIMEFRAME]. No vague promises. Under 100 words, warm and clear, with a subject line.
I have attached our project budget and the actual spend so far for [PROJECT]. Compare them line by line. Return: a table of the lines that are over budget by more than [PERCENT], what is driving each overspend based on the data, costs that are likely to keep rising, and three options to bring the total back in line with the trade-off of each. Keep all figures exactly as they appear in the files and say when you are making an assumption.
I run a [BUSINESS TYPE] in [NEIGHBORHOOD OR TOWN]. Brainstorm 20 ideas for partnering with nearby businesses that share my customers but do not compete, such as joint offers, shared events or referral swaps. Then pick the five most practical for a tiny budget and, for each, give the type of partner to approach, what each side gets, a first step I can take this week and a two-line opening message.
I have uploaded quotes from [NUMBER] suppliers for [ITEM OR SERVICE]. Build a comparison table with price per unit, total cost for [QUANTITY], delivery time, payment terms, minimum order, warranty and anything unusual in the small print. Then rank them for my priority, [PRIORITY, e.g. lowest total cost with delivery under two weeks], and list questions I should ask each supplier before deciding. Quote figures exactly and flag anything missing from a quote.
I have several Codex tasks running on this repo. Open the agent command center with codex agents --no-daemon (Codex CLI 0.167.0 or later) and go through the ones marked unread. For each, give me one line on what it changed, whether its tests passed, and whether it needs my input. Return a table sorted by what needs me first. Do not merge, push or approve anything; just report.
/worktree Start this task in a managed Git worktree so my main checkout stays untouched: [CHANGE, e.g. replace the date library in the reports module]. Plan first and list the files you expect to change. Make the change in small steps, run [TEST COMMAND] after each one, and stop if more than [NUMBER] files need edits so we can talk. At the end show me the full diff and the commands to review the worktree, but do not merge it.
Set up a Codex Cloud environment for this repo: install dependencies, run [TEST COMMAND] and confirm it passes. Write down the steps as the Install script and a short Start skill that explains how to run the app and the tests. Do not put any secrets or tokens in either one; list the environment variables I need to add myself. When everything works, tell me it is ready so I can select Publish.
Read the tests for [MODULE OR PACKAGE] and the public functions it exports. Write a short usage guide with one realistic example per public function, based only on what the tests show actually works, plus the common errors and what causes them. Plan first and show me the outline. Put the guide in [DOCS FILE] without changing any code, and run any example snippets that the project can test so we know they are correct.
/ps List the background terminals still running in this session. For each, tell me in one line what command it is running, how long it has been going and whether anything in our current task still needs it. Recommend which ones to stop, but wait for my yes, then use /stop only on the ones I approve. Never stop a process that is writing to a database or running a migration without warning me first.
I want this Codex CLI (0.165.0 or later) to use the built-in Google Cloud Vertex AI provider. Read the Codex docs and show me the smallest config change, using model_provider = "gcp", plus any other settings the docs say are needed. Show the diff before saving. Do not write credentials or project secrets into the config; tell me which ones I need to set up myself and how to check that the connection works.
/config Search my preferences for [SETTING AREA, e.g. approvals, sandbox or notifications]. Explain each setting you find in one plain line, show its current value, and mark which changes need a restart (Codex CLI 0.163.0 or later shows this). Suggest at most three changes for my workflow, [DESCRIBE WORKFLOW], and wait for my yes before changing anything. Do not loosen any sandbox or approval setting.
Our calls to [EXTERNAL SERVICE] in [FILE OR MODULE] fail sometimes with timeouts. Plan first: show where requests are made and how errors are handled now. Then add retries with exponential backoff and jitter for timeouts and 5xx responses only, a maximum of [NUMBER] attempts, and a clear log line on each retry without logging request bodies or keys. Keep the diff small, add tests for success after a retry and for giving up, and run the test suite.
The CSV files in [FOLDER] have the same data with different column names, for example 'E-mail', 'email' and 'Email Address'. Write a script that reads them, proposes one standard name per column and writes a mapping table for me to review first. After I approve, write cleaned copies to [OUTPUT FOLDER] and never overwrite the originals. Run it as a dry run first, show the mapping and row counts per file, and add a small test with sample headers.
/goal The build and all tests in [PACKAGE OR FOLDER] pass with [BUILD COMMAND] and [TEST COMMAND]. Work in small steps: run the build, fix the first error with the smallest change, and rerun. Do not change test expectations without explaining why, do not touch lock files, CI config or secrets, and stop and ask me if a fix needs changes outside [FOLDER]. Finish with a summary of every change and why.
/claude-api latency-optimize (Claude Code 2.1.319 or later). Look at the Claude API calls in [PATH OR FEATURE] and find where users wait the longest. Try faster settings against my eval at [EVAL COMMAND OR FILE] and report each one as a table: setting changed, latency before and after, and whether the eval score held. Do not change model choices in production config or touch API keys. Recommend the one change worth keeping and show it as a small diff for me to approve.
I run Claude Code in the terminal without watching it and it stalls on permission prompts. Look up the permissions.denyInsteadOfPrompting setting in the Claude Code docs (added in 2.1.319) and explain what it does for terminal sessions, subagents and teammates. Then propose the smallest change to this repo's .claude/settings.json to turn it on, show the diff before saving, and keep every existing allow and deny rule as it is. Finish with one safe way to test that a blocked call is denied and the turn continues.
Open /tasks and look at the Earlier in this session row (Claude Code 2.1.319 or later). Find the subagent that worked on [EARLIER TASK], reopen it and ask it: [FOLLOW-UP QUESTION, e.g. which files did you skip and why]. Bring its answer back here as a short summary with file paths. Do not let it make new edits; if a change is needed, list it for me first.
/advisor opus. Then plan the migration of [COMPONENT] from [OLD LIBRARY OR VERSION] to [NEW ONE]. Read the files that use it, list every call site, and write a step by step plan with tests to add first. Ask the advisor to check the plan for risky steps before you start. Do step one only, run [TEST COMMAND], show me the diff and wait for my go-ahead before the next step. Turn the advisor off with /advisor off when we finish.
/import codex. Before anything is written, show me what will come across from my OpenAI Codex setup on this machine: instruction files, MCP servers, commands, subagents and skills. For each item, say where it will land in Claude Code and flag anything that looks out of date or duplicated. Do not import any secrets or tokens; if a config contains one, tell me which file so I can handle it myself. Finish with a short checklist to confirm everything works.
/team-onboarding. Generate a team onboarding guide from my Claude Code usage over the past 30 days. Then edit it so a new teammate on [PROJECT] can follow it on day one: setup steps, the commands and skills I use most and why, three example prompts that work well in this repo, and the mistakes to avoid. Keep it under two pages, plain English, and remove anything personal or any file paths outside this repo.
/code-review high on my current branch. List the findings ranked by severity with file and line, and a one-line reason each. Do not change any files yet. Wait for me to pick the findings to fix, then make the smallest change for each one, run [TEST COMMAND] after every fix, and show me the combined diff at the end. Never edit test expectations just to make a test pass.
/skill-doctor (Claude Code 2.1.252 or later). Read the report on what each of my skills costs in context and how often it gets used. Return a table: skill, context cost, how often used, and your suggestion (keep, shorten its description, or turn off). Explain the top three suggestions in one line each. Do not delete or edit any skill; I will make the changes myself.
In [CSV PATH], customers appear more than once with small differences in name, email case and spacing. Write a small script that finds likely duplicates and writes a review file to [OUTPUT PATH] listing each group, the record it would keep and why. Do not change the original file. Run it as a dry run, show me ten example groups and the total count, and only produce a cleaned copy after I approve the rules. Add a test with five tricky sample rows.
Add a GET [ROUTE, e.g. /health] endpoint to this app that returns status and version and checks [DEPENDENCY, e.g. the database] with a short timeout. Plan first: tell me which files you will touch and how it fits the existing routing. Keep the diff small, never include secrets or connection strings in the response, add a test for the healthy case and the dependency down case, run the test suite, and show me the result.
Using gpt-image-2.6-sunburst (made for detailed visual work) at 1536x1024 with high quality, create a clean technical cutaway illustration of a [PRODUCT, e.g. reusable water filter bottle] showing its inside parts. Side view, centered, with five thin leader lines pointing to parts labelled exactly: '[PART 1]', '[PART 2]', '[PART 3]', '[PART 4]', '[PART 5]'. Flat colors on a plain off-white background, soft even lighting, crisp outlines, no other text, no logos.
Using gpt-image-2.6-flare (made for fast iteration) with complexity set to low, create a rough hero image concept for a landing page about [PRODUCT OR SERVICE]. Landscape 1536x1024. A simple scene of [SUBJECT, e.g. a small team around a laptop] on the right third, empty space on the left for a headline, soft daylight, friendly semi-flat illustration style, limited palette of [COLORS]. No text in the image. I will pick a direction and redo it at a higher setting.
FLUX 3 Image, 16:9, 4k. Use my reference images: [PRODUCT 1], [PRODUCT 2] and [PRODUCT 3]. Arrange them on a light oak shelf in a bright, minimal bathroom: [PRODUCT 1] in the left box, [PRODUCT 2] in the center box, [PRODUCT 3] in the right box (add your bounding boxes here). Keep each product's shape, label and colors exactly as in its reference. Soft morning window light from the left, gentle shadows, shallow depth of field, photo-real, no added text.
Using FLUX 3 Image Klein, edit the attached photo of my shop window for [SEASON OR HOLIDAY]. Keep the storefront, sign and products exactly where they are. Add [DECORATIONS, e.g. warm string lights, pine branches and a light dusting of snow on the ledge], change the lighting to early evening with a warm glow from inside, and keep it photo-real. Do not change or add any text, and leave people out of the scene.
Nano Banana 2.1, aspect ratio 4:1, 2K. Use my reference photos of [NUMBER, up to 10] products and lay them out in one tidy row on a seamless [COLOR] background for a website strip. Even spacing, all products at the same scale, soft top light with small natural shadows, clean e-commerce photo style. Keep every product's shape, color and label exactly as in the references. No text, no props.
Nano Banana 2.1, aspect ratio 1:8, 2K. A tall, scrollable step-by-step guide titled '[TITLE]' with [NUMBER] steps stacked from top to bottom. Each step has a simple flat icon, a bold step number and a short label rendered exactly: '[STEP 1]', '[STEP 2]', '[STEP 3]', '[STEP 4]'. Clean flat style, white background, one accent color [COLOR], generous spacing between steps, easy to read on a phone. No other text.
Wide panoramic view of a calm modern city skyline at blue hour, soft lights in office windows, a thin band of warm light on the horizon, gentle reflections on a river in the foreground, lots of clean sky at the top for event branding, cinematic and uncluttered, no text, no logos, no people --ar 4:1 --hd --v 8.2
Editorial still life photo: a neat stack of paper receipts held by a brass clip, a calculator and a small potted succulent on a matte sage green desk, shot from 45 degrees, soft diffused window light from the right, muted natural colors, subtle film grain, magazine style, lots of space on the left for a headline, no readable text, no brands --ar 3:2 --v 8.2
Using Recraft V4.1 with vector output, create a flat illustration for a [APP TYPE] onboarding screen: a person sitting at a desk ticking off a checklist while a friendly plant grows beside them. Simple shapes, even line weight, three colors only, [#HEX1], [#HEX2], [#HEX3], on a transparent or plain white background, no text, no gradients. Keep shapes clean so the SVG is easy to edit (the SVG link expires after about 24 hours, so download it right away).
Ideogram 4.5 with the background set to Transparent. A round sticker style badge for [BRAND OR EVENT] that reads exactly '[BADGE TEXT]' in bold rounded capitals around the top edge, with a simple [ICON, e.g. coffee cup] in the center. Thick white outline around the whole badge, flat colors [COLORS], no shadows, no extra words. Centered with even padding, crisp edges suitable for print and web.
Kling 4.0, 30 seconds, 16:9, 1080P. One continuous shot inside a small neighborhood bakery at dawn: the camera starts on flour being dusted over dough, slowly pulls back past a baker shaping loaves, glides along a counter of fresh bread and ends facing the front window as the first customer opens the door. Warm golden light, gentle steam, calm and inviting mood. Native audio: soft oven hum, paper bags rustling, a door bell, no dialogue, no text on screen.
Kling 4.0 Flash, 12 seconds, 9:16, 720P. A hand holds a phone over a desk; on screen a [APP TYPE] app shows a simple list that sorts itself into neat groups. The camera slowly pushes in toward the phone, then tilts up to a relaxed person smiling at the result, soft daylight from a window. Native audio: light tap sounds and a short upbeat music sting at the end, no voiceover, no readable text.
Gemini Omni 1.2 Flash, 12 seconds, 16:9, 720p. Use my reference images: up to three of [CHARACTER A] and up to three of [CHARACTER B], keeping their faces, clothes and colors the same. Scene: the two meet at a whiteboard in a bright office, Character A points to a simple diagram and Character B nods and adds a sticky note. Slow side tracking shot at eye level, soft natural light. Native audio: quiet office ambience and marker squeaks, no dialogue, no on-screen text.
Gemini Omni 1.2 Flash. Extend my attached [LENGTH]-second clip of [PRODUCT SCENE] by [3 TO 10] seconds at the end (total length can reach 30 seconds). Continue the same camera move and lighting as [WHAT HAPPENS NEXT, e.g. the camera rises to show the product on a kitchen table set for breakfast]. Keep colors, motion speed and style matched so the join is not visible. Native audio continues the same ambience. No new people, no text.
FLUX 3 Video, 8 seconds, 16:9, fhd. Start keyframe: my attached photo of [PRODUCT] in its closed box on a white table. End keyframe: the same product standing next to the open box. In between, hands gently lift the lid and place the product beside it, camera slowly orbiting a quarter turn. Soft studio light, clean white background, realistic materials. Audio on: soft cardboard sounds and a light click, no music, no text.
FLUX 3 Video, 10 seconds, 21:9, qhd, audio set to false for a silent clip. Slow aerial drift over rolling green hills at early morning with thin mist in the valleys, soft low sun, calm and steady motion with no sudden changes so it loops smoothly. No people, no buildings, no text. Keep the center of the frame calm so a headline can sit on top.
Luma Ray3.2, 10 seconds, 16:9, 1080p. Smooth steady walkthrough from the front door of a bright, tidy [ROOM TYPE, e.g. one bedroom apartment] into the living room, then a gentle turn toward large windows with afternoon light. Natural colors, wide lens, slow walking pace, no people. Ray3.2 does not create audio, so add music in editing. No text on screen.
Seedance 2.5, 25 seconds in a single generation. Handheld style one take through a small woodworking workshop: start on a craftsperson's hands sanding a chair leg, move past shelves of tools and planks, and end on a finished chair under a window. Warm afternoon light, sawdust floating in the sun, relaxed real-world pace. Audio generated with the video: sanding, soft radio music in the background, birds outside, no dialogue, no text.
Seedance 2.5. Part one, [UP TO 30] seconds: a close-up of [PRODUCT] on a desk as a hand switches it on and the camera slowly circles it. Then extend it once to show the product in use in [SETTING], and a second time for a calm closing shot of it back on the desk. Keep lighting, colors and the product look the same across all parts. Audio generated together with the video: soft ambience and product sounds, no dialogue, no text.
Using grok-imagine-video-1.5, make a [DURATION, up to 15] second clip. Pin my attached images as frames: the first frame is [PRODUCT] covered by a cloth, the middle frame is the cloth halfway off, and the last frame is the product fully revealed under a soft spotlight. Smooth, slow motion between them, camera holding still at a slight low angle, dark studio background, subtle dust in the light. Keep the product exactly as in the images. No text.
In ChatGPT Work, choose GPT-6.1 Terra (available on Plus, Pro, Business, Enterprise and Edu plans; not in regular Chat). We are rolling out a new [POLICY, e.g. expense approval rule] to [NUMBER] staff on [DATE]. Here is the policy text: [PASTE POLICY]. Write a rollout plan with: a two-sentence summary anyone can understand, a week-by-week timeline, who needs to know what and when, the three questions people will ask most with short answers, and a short announcement message under 150 words. Return it as headed sections with no jargon.
Texting your dot is in beta for ChatGPT Pro users in the U.S. (iMessage, or RCS on Android). Each time I text you a photo of a receipt this month, add it to my running expense log: date, merchant, amount, currency and a category from this list: [CATEGORIES]. If a photo is blurry or a field is unclear, text me back one short question instead of guessing. When I text 'summary', reply with totals per category and the three biggest single expenses. Keep every reply under 60 words.
When my dot finishes each step of [TASK, e.g. preparing the weekly client report], send me a notification with one line on what you did and the exact next step you plan to take. I will reply right from the iOS notification (needs dot access on ChatGPT for iOS) with 'go', 'wait' or a short change. Do not move to the next step until I reply 'go'. If I say 'wait', remind me once after [TIME]. At the end, send a three-bullet recap of what was done and anything still open.
@Visualize Here is my pricing table: [PASTE TABLE OF PLANS, PRICES AND LIMITS]. Build an interactive calculator where I can enter [INPUTS, e.g. number of users and monthly usage] and see the cheapest plan, the monthly and yearly cost, and how much the next plan up would cost. Add a short note under it explaining the logic in plain words, and list any rows in my table that look inconsistent. (Visualizations are a preview that is still rolling out on web, desktop and mobile.)
I am sending you my frontmost spreadsheet window with Appshots (ChatGPT desktop app on macOS or Windows; your organization must allow it). Look at the visible formulas and totals. List every cell that looks wrong, why you think so, and the corrected formula. Then suggest one change to the layout that would make mistakes like this easier to spot next time. Return a table with columns: cell, problem, fix.
I have created a ChatGPT project for hiring a [ROLE]. I have added the job description, our interview scorecard and [NUMBER] anonymized candidate summaries as files. Using only those files, build a comparison table of candidates against each scorecard criterion with a one-line reason per score, flag where my notes are thin, and suggest the two questions to ask each finalist in the next round. Do not guess facts that are not in the files; mark them as 'not in notes'.
Set up a scheduled task that runs every [DAY] at [TIME]. Each time, suggest three topic ideas for my newsletter about [NICHE] for an audience of [AUDIENCE]. For each idea give: a working headline under 10 words, the one question it answers for the reader, and a three-point outline. Avoid topics from this list I have already covered: [PAST TOPICS]. Keep the whole message short enough to read in one minute.
Write an email to a candidate who interviewed for [ROLE] and was not selected. Their strengths were [STRENGTHS]; the gap was [GAP]. Keep it warm, honest and under 150 words. Thank them for their time, give one specific strength and one practical piece of feedback, do not promise future roles unless I say so, and end on a respectful note. Give me two versions: one more formal, one more personal. Add a subject line for each.
My product is [PRODUCT] and [PERCENT] of trial users never complete [KEY ACTION]. Here is our signup to first-use flow: [DESCRIBE STEPS]. Brainstorm 15 possible reasons they stall, grouped into: confusion, effort, trust and timing. For each reason suggest one quick way to test if it is true (a question, a metric or a small experiment). Finish with the three tests you would run first and why.
Here is my signup form code in [LANGUAGE OR FRAMEWORK]: [PASTE CODE]. Add validation for these fields: [FIELDS AND RULES, e.g. email format, password length, required company name]. Validate on the client for fast feedback and repeat the same checks on the server. Show friendly error messages next to each field. Return the changed code with comments on each new part, plus five test cases (inputs and expected result) I can run to confirm it works.
Claude Duet (research preview on Pro and Max plans) works as a proactive agent, so treat this as an ongoing job. I am onboarding a new client, [CLIENT TYPE], over the next [NUMBER] weeks. Here is my checklist: [PASTE CHECKLIST]. Keep track of which items are done, remind me of anything due in the next two days, and when an item is blocked, draft the short message I would need to send to unblock it. Never send anything yourself. Start by giving me a status table: item, owner, due date, status.
Using Personal Finance in Claude (beta, Pro, Max and Ultra plans, US only) with my linked accounts, list every recurring charge from the last [NUMBER] months. Return a table: merchant, amount, how often, total per year and the last date it was charged. Flag charges that look like duplicates, ones whose price went up, and ones I have not obviously used. Suggest which three to review first. This is for my own review, not financial advice, so do not recommend investments.
My organization uses project tags to track spend by cost code (a beta for eligible Enterprise organizations). Here are this month's totals by tag, plus last month's: [PASTE TOTALS]. Write a one-page memo for [AUDIENCE, e.g. finance lead] that shows the top five tags by spend, the biggest month-on-month changes with a likely reason I should confirm, and any tags that look mislabeled. Use a short table, then three bullet recommendations. Mark every guess as a guess.
Use Claude Opus 5.5. I have uploaded a supplier contract for [SERVICE]. Read it and list the clauses I should look at closely: auto-renewal, price changes, liability caps, termination notice, data handling and exclusivity. For each, quote the clause in under 20 words, explain in plain English what it means for a small business, and suggest one question to ask the supplier. Return a table. Add a note that this is not legal advice and that a lawyer should review anything high risk.
Turn on web search and use Research (available on Pro, Max, Ultra, Team and Enterprise plans). Investigate what makes [TYPE OF BUYER] in [MARKET OR REGION] start looking for [PRODUCT CATEGORY]. I want: the five most common buying triggers, where they look for options first, the objections they raise, and the words they use to describe the problem. Cite a source for every claim and mark anything you could only find one source for. Finish with three ideas for messaging I could test.
I have created a Project for my client [CLIENT NAME OR CODE] and added our contract summary, brand guide and past reports. Write the project instructions I should paste in so every chat in this Project: uses the client's tone, follows their brand terms, checks the files before answering, and says 'not in the files' rather than guessing. Then give me a list of five more documents worth adding and a sample first question to test it.
A [CLIENT OR PARTNER] has come back with a counteroffer: [PASTE THEIR TERMS]. I want to accept, but only if [CONDITIONS, e.g. payment within 30 days and a fixed scope]. Write a reply under 180 words that sounds pleased and confident, states the conditions clearly as part of the yes, and proposes the next step with a date. Give me a subject line and one shorter version I could send from my phone.
I am running a [LENGTH] offsite for a team of [NUMBER] people in [TEAM TYPE]. Our goals are [GOALS]. Brainstorm 12 exercises that fit those goals, mixing reflection, planning and lighter energy-boosters. For each give: name, time needed, materials, the steps in three lines, and what the team should have at the end. Then suggest an order for the day with breaks, and flag any exercise that would not work remotely.
Here are my notes from an interview with a customer, [CUSTOMER TYPE], who used our [PRODUCT OR SERVICE]: [PASTE NOTES]. Write a case study of about 500 words with: a headline that states the result, the situation before, what they tried, why they chose us, what changed, and a short closing quote taken only from my notes. Do not invent numbers or quotes; if a number is missing, leave a [NUMBER NEEDED] marker. Add three pull quotes for social posts.
Create an Artifact (available on all plans, including Free) that shows my project as an interactive timeline. Here are the tasks with start date, end date, owner and status: [PASTE TASKS]. Show each task as a bar, color by status, let me filter by owner, and highlight any task that overlaps a dependency or is past its end date. Add a small summary at the top: tasks done, in progress and late. Keep the design clean and readable on a laptop screen.
I want to prototype a speech-to-speech receptionist for [BUSINESS, e.g. a dental clinic] using grok-voice-3.0 on the xAI API (released October 2026; the grok-voice-latest alias now points to it). Plan it before writing code: list the five call types it must handle, the questions it should ask for each, when it must hand over to a human, and what it must never do (give medical advice, take payments). Then write a small, well-commented starter script in [LANGUAGE] and a test script of eight sample calls I can run myself.
Grok Voice 2.0 is deprecated and the upgrade path is grok-voice-3.0 or grok-voice-latest at the same price. Here is my voice app code: [PASTE CODE OR FILE LIST]. Find every place that sets the model name, explain whether I should pin grok-voice-3.0 or use the latest alias for my case, [USE CASE], and show the smallest change as a diff. Then give me a short checklist to test the switch: greetings, interruptions, long answers, and a fallback if a call fails.
I run [APP], a learning app used by students aged [AGE RANGE]. xAI's custom moderation controls let me set how Grok handles nsfw, violence and profanity through a guidelines array. Draft clear, plain-language rules for each of those three areas that suit my audience, with one example of what is allowed and what is not for each. Format each rule as a short sentence I can adapt for the guidelines array, and remind me to check the exact field format in the xAI docs before shipping.
I will transcribe [NUMBER] recorded sales calls with grok-voice-transcribe-2.0, the default speech-to-text model on the xAI API, and paste the transcripts here: [TRANSCRIPTS]. Find every objection the prospect raised. Group them into themes, count how often each appears, quote the clearest example of each in under 20 words, and note how our rep answered. Return a table, then the three objections we should prepare better answers for, with a suggested answer for each.
Using my Gmail and Google Calendar connector (connectors are available to all Grok users), look at my meetings for tomorrow. For each external meeting, give me: who is attending, the last email thread with them in one line, any open questions or promises I made, and two things I should ask. Return one short card per meeting in time order. Do not send or reply to anything.
I have uploaded our expense spreadsheet for [PERIOD]. Check it for entries that look unusual: duplicates, round numbers that look estimated, weekend charges, amounts far above the usual for that category, and missing receipts or notes. Return a table of flagged rows with the reason for each and how confident you are. Then list the three checks I should add so these get caught automatically next month.
Write a short pitch email to the host of [PODCAST NAME], a show about [TOPIC] for [AUDIENCE]. I want to talk about [MY TOPIC] because [WHY IT MATTERS NOW]. My relevant experience: [EXPERIENCE]. Keep it under 150 words, mention one specific episode I liked, offer three possible episode angles as bullets, and end with an easy yes or no question. Give me two subject lines.
I am launching [PRODUCT OR FEATURE] on [DATE] for [AUDIENCE]. Plan seven days of posts for X: two before launch, launch day, and four after. For each day give the goal, a post under 280 characters, the best format (single post, thread or reply to my own post) and one idea for an image. Keep the tone [TONE], no hype words, and include one post that answers the most likely objection.
I want to survey customers of [PRODUCT] to learn [GOAL, e.g. why they renew or leave]. Brainstorm 20 questions, then cut them to the best 10. For each kept question, say what it measures, the answer format (scale, multiple choice or open text), and rewrite any that might push people toward an answer. Order them so the survey takes under five minutes, and add one open question at the end.
Here are [NUMBER] anonymized customer interview transcripts: [PASTE OR UPLOAD]. Build a one-page persona sheet with: goals, daily frustrations, the tools they use now, what triggers them to look for a solution, and how they judge success. Back each point with a short quote and the interview number. Point out where interviews disagree, and list three questions to ask in the next round of interviews.
Use Gemini 4 Argon (for Google AI Pro and Ultra subscribers). Here are my business numbers for the last [NUMBER] months: [PASTE REVENUE, COSTS AND CASH BALANCE]. Build a 12-month cash forecast with three scenarios: cautious, expected and strong. State every assumption in a table so I can change it, show the month cash would drop below [THRESHOLD] in each scenario, and list the three levers that matter most. Explain it in plain words for someone who is not an accountant.
I want to use the Customize menu in Gemini (on web, mobile and the desktop apps) to set how you respond. Based on how I work, [DESCRIBE YOUR WORK AND WHAT ANNOYS YOU IN LONG ANSWERS], write the response style text I should paste in: answer first, then reasons, bullet points when there are more than three items, no filler, and ask one question if my request is unclear. Keep it under 120 words, then show me a before and after example on a sample question.
Using Gemini's small business tools with my accounting app connected through connected apps (for example Xero), give me a snapshot of [MONTH]: revenue, biggest expense categories, unpaid invoices older than 30 days, and how each compares with the month before. Return a short table and three plain-English takeaways. If any figure cannot be read from the connected app, say so instead of estimating. Do not change anything in the app.
Using Universal Cart in the Gemini app (rolling out in the U.S.), add these office supplies for a team of [NUMBER]: [LIST OF ITEMS AND QUANTITIES]. Compare prices across retailers, tell me which items are cheaper elsewhere, and set price drop alerts on anything over [AMOUNT]. Give me a table with item, best price, store and delivery estimate. Do not check out; I will review and pay myself.
For personal accounts, Gems convert to skills and become read-only on November 17, 2026, and are removed on December 17, 2026. Here are the instructions and files from my Gem called [GEM NAME]: [PASTE INSTRUCTIONS AND FILE LIST]. Rewrite them as a clear skill: a one-line purpose, step-by-step instructions, the files it needs, and three example requests to test it. Keep the files under the 100 MB skill limit and note that skills do not currently work with Canvas or Deep Research.
Use Deep Research. I am thinking of hiring [NUMBER] [ROLES] in [CITY]. Research typical salary ranges, common benefits, how long hiring usually takes, and any local employment rules I should know about. Also use my uploaded file [FILE, e.g. our current pay bands] to compare. Show the research plan to me first so I can edit it. In the report, cite sources for every number and mark ranges where sources disagree.
I have uploaded our [POLICY DOCUMENT, e.g. new travel policy]. Create an Audio Overview that explains it for staff who will listen on their commute. Focus on: what changed, what people must do differently, the deadline, and who to ask. Keep the tone friendly and practical. After that, give me a written list of the five key points in the same order so I can share it alongside the audio.
Write an email to [SUPPLIER] asking for volume pricing on [PRODUCT]. We currently order [QUANTITY] every [PERIOD] and could commit to [NEW QUANTITY] over [TERM]. Keep it friendly and businesslike, under 150 words, mention how long we have been a customer, ask for pricing at two quantity levels, and request a reply by [DATE]. Add a subject line and a short follow-up to send if they do not reply in a week.
Our team of [NUMBER] in [TEAM TYPE] wants a quarterly award that celebrates [VALUE, e.g. helping others]. Brainstorm 15 award names that are warm, not cheesy, then pick the best five. For the winner, suggest simple criteria, how nominations should work in under five minutes per person, and a small, low-cost prize idea. Keep it inclusive so quieter work gets noticed too.
Here is my FAQ page: [PASTE FAQ]. Rewrite each answer so the first sentence directly answers the question, followed by at most two sentences of detail. Merge questions that repeat each other, reword questions the way a customer would ask them, and flag any answer that seems out of date or contradicts another. Return the new FAQ, then a short list of what you merged or flagged.
Use GPT-6.1 Terra (available in Codex on Plus, Pro, Business, Enterprise and Edu plans; needs Codex CLI 0.159.0 or later). In [FILE OR MODULE], the function [FUNCTION NAME] has grown too long. First read it and its callers, then propose a plan to split it into smaller functions with no change in behavior. Wait for my OK. Then make the change in small steps, run [TEST COMMAND] after each step, and show me the final diff with a one-paragraph summary. Do not touch other modules.
I have an unloaded Codex thread where you were [TASK, e.g. updating API docs]. Using codex queue --resume (Codex CLI 0.166.0 or later), queue this follow-up so the thread picks up where it left off: 'Finish the remaining sections, run the docs build with [COMMAND], and list any broken links.' When it finishes, report what changed, whether the build passed, and anything that needs my decision. Do not push or merge.
Codex CLI 0.163.0 added a /keymap leader key (default Ctrl+X). I mostly use these actions: [LIST, e.g. switch model, open review, start plan, export]. Suggest a leader key and short follow-up keys for each that do not clash with my terminal or editor shortcuts, [EDITOR AND TERMINAL]. Show me exactly what to set with /keymap, then a one-line cheat sheet I can keep next to my screen. Do not change any other settings.
Run /review against the base branch [BRANCH, e.g. main]. Focus only on error handling: unhandled exceptions, missing checks on user input, network calls without timeouts, and errors that are swallowed silently. For each finding give the file and line, why it matters, and a suggested fix as a small diff. Sort by risk. Do not apply the fixes yet; wait for me to choose which ones to keep.
Run /init to generate an AGENTS.md scaffold for this repo. Then fill it in using what the repo actually contains: how to install dependencies, the exact test, lint and build commands from [PACKAGE FILE OR MAKEFILE], the folder layout in a few lines, and coding conventions you can see in the code. Run each command once to confirm it works and note any that fail instead of guessing. Keep the file under 80 lines.
Work in the read-only sandbox mode so nothing is changed. Read through [FOLDER OR WHOLE REPO] and map how errors are handled: where they are caught, logged, shown to users or ignored. Return a short report with a table of patterns found, examples with file paths, inconsistencies between modules, and the three changes that would give the biggest improvement. Do not edit any files.
Using Codex Cloud, start three separate tasks for these bugs: 1) [BUG 1], 2) [BUG 2], 3) [BUG 3]. For each task: reproduce the bug with a failing test first, make the smallest fix, run [TEST COMMAND], and write a short summary of the cause and fix. Keep each change limited to the files it needs. Do not merge anything; I will review each one on its own.
Add a dark mode toggle to [APP OR COMPONENT]. Plan first: list the files you will change and how theme colors are defined today. Default to the user's system setting, let them override it with the toggle, and remember the choice between visits. Check text contrast in both themes. Run [TEST COMMAND] and [LINT COMMAND], then show me the diff and two screenshots or a description of what to check by hand.
I have a large CSV export at [PATH] with a date column called [COLUMN]. Write a script that splits it into one file per month in a new output folder, without changing or deleting the original. Run it first in a dry run that only prints how many rows would go to each file. After I confirm, run it for real and produce a check report: row counts per file, total rows versus the original, and any rows with missing or invalid dates.
In [FILE], the call to [API OR FUNCTION] is slow and is called repeatedly with the same inputs. Propose a caching approach (in memory with an expiry of [TIME] unless you see a better fit) and wait for my OK. Then add it with a clear way to turn it off, write tests for cache hit, cache miss and expiry, run [TEST COMMAND], and report the before and after timing from a simple local benchmark.
Open /permissions and look at the Recently blocked tab (Claude Code 2.1.314 or later). Summarize what was blocked this week, why, and whether each block was helpful or just slowed me down. Suggest specific allow or deny rule changes for the ones that were safe and repetitive, and keep blocks on anything that touches secrets, deletes files or pushes code. Show the proposed rule changes for my approval before applying any.
Our pull request [PR LINK OR NUMBER] changes [AREA, e.g. payment retries]. Claude Code's Code Review now offers Quick, Standard (the default) or Deep levels. Explain which level fits this change and why, then draft the review request I should post. After the review comes back, summarize the findings by severity, propose the smallest fix for each real issue, and run [TEST COMMAND] after each fix. Do not push until I approve.
My pull request [PR LINK OR NUMBER] is still a draft and I do not want automatic Code Review comments yet. Claude Code 2.1.307 added a @claude review stop comment for this. Write the exact comment to post now, a one-line note for my teammates explaining why reviews are paused, and a checklist of what to finish before I ask for a review again: [WHAT IS LEFT TO DO]. When I say the draft is ready, summarize the diff in five bullets so the reviewer knows where to look first.
Open /tasks and look at the Earlier in this session row (Claude Code 2.1.319 or later). For each finished background task, tell me in one line what it did, whether it succeeded, and anything it left for me to do. Then list any task that failed with the most likely reason and a suggested next step. Return a short table, sorted with anything needing my attention first. Do not rerun anything without asking.
/subtask Read the application logs in [LOG PATH] from [TIME RANGE] and find out why [SYMPTOM, e.g. some uploads fail with a timeout]. Group errors by type, count them, find the first occurrence, and link each group to the code path that produces it. Report back with a short summary, the top three suspects with evidence, and a suggested next check for each. Do not change any code or config.
/compact Keep: the goal of this session, every decision we made and why, the files we changed, any failing tests and their error messages, and the open questions I still need to answer. Drop: exploration that led nowhere and long command output. After compacting, show me a five-line summary of where we are so I can check nothing important was lost.
I want to compare two approaches to [FEATURE]. Start two sessions with claude --worktree, one named [NAME A] for approach A ([DESCRIBE A]) and one named [NAME B] for approach B ([DESCRIBE B]). In each, plan first, make the smallest working version, and run [TEST COMMAND]. Then give me a comparison table: lines changed, test results, complexity and risks. Do not merge either one; I will choose.
In [SCREEN OR COMPONENT PATH], find every user-facing string that is hard-coded. Plan first: list the strings and the keys you would give them in our translation files at [PATH], following the existing naming style. After I approve, move them over, keep the English text exactly the same, run [TEST COMMAND] and [LINT COMMAND], and show me the diff. Only change this one screen.
The folder [FOLDER PATH] has scanned invoice PDFs with random file names. Write a small script that reads each file's invoice date and supplier name (from the text layer, or tell me which files have none) and proposes a new name in the format YYYY-MM-DD_supplier_amount.pdf. Run it as a dry run first and write the old and new names to a mapping CSV for me to review. Only after I approve, rename the files in place, keep the mapping CSV as an undo record, and never delete anything.
We need a new optional column [COLUMN NAME] of type [TYPE] on the [TABLE] table. Using our existing migration tool and style in [MIGRATIONS PATH], write the migration and its rollback. Plan first and show me the SQL or migration code. Then run it against the local development database only, run [TEST COMMAND], and confirm the rollback works by running it and the migration again. Do not run anything against staging or production.
Using gpt-image-2.6-sunburst at 1024x1536 with complexity set to high (it helps with dense text and complex layouts), create a one-page cheat sheet titled '[APP NAME] Shortcuts'. Four labelled sections in a two by two grid: '[SECTION 1]', '[SECTION 2]', '[SECTION 3]', '[SECTION 4]', each listing five shortcuts as rounded key caps followed by a short action label: [SHORTCUT LIST]. Flat design, dark navy background, white and teal text, even spacing, no logos, no extra text.
Using GPT-Image-2.6 Flare with SVG output, create a simple badge for a newsletter section called '[SECTION NAME]'. A rounded rectangle with a small flat icon of [ICON, e.g. a lightbulb] on the left and the section name in bold sans serif on the right. Two flat colors only: [COLOR 1] and [COLOR 2], no shadows, no gradients, clean shapes that scale cleanly from small to large sizes.
Edit my attached flyer using markup-guided editing (supported on GPT Image 2.5 and 2.6 models). I have drawn on it: the red circle marks the headline to move to the top center, the blue arrow shows where the photo should go, and the crossed-out box should be removed. Keep all other text exactly as it is, keep the same colors and fonts, and keep the output the same size as the original.
Using Nano Banana 2.1 at 2K, 16:9, use my attached images as references: image 1 is our mascot character, image 2 is our product [PRODUCT]. Show the mascot standing in a bright, tidy corner shop holding the product at chest height, smiling at the viewer. Keep the mascot's colors and shape and the product's label exactly as in the references. Soft daylight from a window on the left, shallow depth of field, cheerful illustrated 3D style, no added text.
Using Nano Banana 2.1 video-to-image, take the frame at [TIMESTAMP] from my attached product video and turn it into a clean still at 2K, 1:1. Keep the product exactly as shown, remove motion blur, replace the background with a plain warm grey studio sweep, and add a soft shadow under the product. Even, soft studio lighting. No text, no logos added.
Using FLUX 3 Image with custom width 1200 and height 630, create a share image for a blog post titled '[POST TITLE]'. Left half: a calm editorial photo of [SUBJECT, e.g. a laptop on a wooden desk beside a notebook]. Right half: solid [COLOR] panel with space left clear for text to be added later. Natural morning light, muted colors, sharp focus, realistic photography style, no text or logos in the image.
Using FLUX 3 Image with my room photo as the first reference and resolution set to match_input (so the edit keeps the same size as the original), restyle the room as a bright, modern [ROOM TYPE]: light oak floor, white walls, simple linen sofa, two indoor plants and a round rug. Keep the windows, doors and room shape exactly the same. Soft daylight, realistic interior photography, no people, no text.
Using Ideogram 4.5 with Background set to Transparent, design a price tag graphic for an online shop. A tilted tag shape with a small hole and string at the top, bold text reading '[DISCOUNT, e.g. 20% OFF]' and smaller text below reading '[DATES]'. Flat colors: [BRAND COLOR] tag with white text, crisp edges, no shadows, no background.
Using Ideogram 4.5 at 2K (it accepts prompts as text or JSON), create an event ticket with this layout: {"background": "[COLOR] with a subtle paper texture", "left": "event name '[EVENT NAME]' in bold condensed type", "right": "date '[DATE]', time '[TIME]' and venue '[VENUE]' stacked in small caps", "edge": "perforated tear-off stub reading 'ADMIT ONE'", "style": "flat, modern, clean"}. Landscape aspect ratio, all text spelled exactly as given, no other words.
Using Recraft V4.1 with vector SVG output, create a simple stylized map illustration of a delivery area for a local business. A soft grid of streets, a highlighted shaded zone in [BRAND COLOR], a pin icon at the center for the shop, and three small icons for [ICONS, e.g. bike, van, parcel] around the edge. Flat shapes, limited palette of four colors, no real place names, no text.
Using Gemini Omni 1.2 Flash (in the Gemini app it is rolling out to Google AI Ultra subscribers), make a 15 second 9:16 video. Draft it at 720p first, then upscale to 1080p once I like it. Overhead shot of hands making [DISH] on a wooden counter: chopping, stirring, then plating, with a quick cut on each step. Camera slowly pushes in on the final plate. Bright, warm kitchen light, cheerful mood. Native audio: light acoustic music, knife taps and a sizzle, no voice, no text on screen.
Using Gemini Omni 1.2 Flash conversational editing, take the product clip we just made of [PRODUCT] on a white table. Keep the product, its motion and the camera move exactly the same, but change the background to [NEW SETTING, e.g. a sunny balcony with plants] and warm up the lighting to match late afternoon sun. Keep the same length and 16:9 aspect ratio. Keep the soft background music.
Using Gemini Omni 1.2 Flash with my attached 3 second motion clip as a motion reference, make a 10 second 16:9 video at 720p of [SUBJECT, e.g. a ceramic mug on a shelf]. Copy the camera move from the reference: a slow arc from left to right while rising slightly. Soft window light, calm minimal mood, shallow depth of field. Native audio: quiet room tone and a faint clink at the end. No text.
Using veo-3.1-generate-001 on Google Cloud, 8 seconds, 16:9, 1080p, with sound. A smooth tracking shot follows a traveler's rolling suitcase across a bright hotel lobby with stone floors and tall plants, ending as the suitcase stops at the front desk. Late morning light through large windows, relaxed and welcoming mood. Sound: soft footsteps, suitcase wheels, distant chatter and a desk bell. Write the prompt in English only.
Using veo-3.1-fast-generate-001 on Google Cloud, 6 seconds, 9:16, 1080p, with sound. Close-up of a florist's hands wrapping a bouquet of [FLOWERS] in brown paper and tying it with twine on a wooden workbench. Camera slowly tilts up from the twine to the full bouquet. Soft natural light, gentle and fresh mood. Sound: paper rustling and twine pulling tight, no music, no text.
Using Seedance 2.5 timestamp-level editing on my attached [LENGTH] second clip of [SCENE, e.g. a barista making coffee], change only the moment from [START TIME] to [END TIME]: [CHANGE, e.g. the cup should be white instead of red]. Keep everything before and after exactly the same, including camera motion, lighting and the generated audio. Return the full clip at the same resolution.
Using Seedance 2.5 (audio and video are generated together), make a 12 second 1080p clip of [PRODUCT] slowly rotating one full turn on a small turntable in front of an even green background. Camera locked off at eye level, soft even studio lighting with no green spill on the product, crisp edges. Generate a quiet motor hum as audio. No text, no other objects.
Using Luma Ray3.2, make a 20 second 1080p clip with native HDR. A slow dolly forward across a rooftop garden at sunset: raised planters, string lights turning on one by one, a small table set for two, and the city skyline glowing behind. Gentle breeze moving leaves, warm golden light fading to blue hour by the end. Calm, romantic mood. No people, no text.
Using grok-imagine-video-1.5 reference-to-video (up to 720p) with reference_audios to give two speakers preset voices, make a 12 second 16:9 scene: two cartoon shop owners, a baker and a florist, chatting across a sunny street. Line 1, baker: '[LINE 1]'. Line 2, florist: '[LINE 2]'. Camera holds a medium shot, then slowly pushes in on both. Bright, friendly, storybook style. Keep characters original, no text on screen.
Using grok-imagine-video-1.5 image-to-video at native 1080p, animate my attached photo of [SHOP NAME OR TYPE] storefront into a 10 second 16:9 clip. Keep the building and sign exactly as in the photo. Add gentle motion: awning fluttering, leaves drifting past, people's shadows passing on the pavement, and the window lights flickering on. Camera does a slow push-in. Warm late afternoon light, inviting mood, no added text.
I am a ChatGPT [ENTERPRISE, EDU OR HEALTHCARE] workspace admin. From November 18, 2026, members get dots by default unless we opt out, and billing for enabled dots starts the same day. Our workspace: [NUMBER] members, teams [LIST TEAMS], and these concerns: [CONCERNS, e.g. local computer access, Slack use]. Using the admin permissions Use dots, Add dots to Slack and Microsoft Teams, Allow local computer access and Use custom rules for dots, recommend which groups should get which permission at first, a two-week pilot plan, what to tell staff, and a decision checklist for whether to opt out. Return a table plus a short staff announcement.
I am attaching a photo of [PRODUCT DISPLAY, e.g. my market stall] and I have marked up the areas I want changed using photo markup in ChatGPT Images 2.6. Change only what is marked: [CHANGES, e.g. remove the tape on the table edge, make the sign read 'Fresh Today']. Keep everything else exactly as it is: the products, their labels, lighting, angle and colours. If a marked change would distort a product, tell me instead of guessing.
I started a task earlier: [TASK, e.g. a comparison of five payroll providers for a 20 person company]. On ChatGPT for iOS (1.2026.300 or later), follow-ups steer the running task by default, so treat this message as a change of direction, not a new task: [NEW INSTRUCTION, e.g. drop provider X, add UK support as a must have, and cap the budget at [AMOUNT] a month]. Keep the work you have already done that still applies, tell me in two lines what changed in the plan, and return the final result as a comparison table with sources.
I am sharing a photo of a whiteboard from today's [MEETING TYPE] to my dot from another app on iOS (dots are on Pro 100, 200 and 500, Business Premium and eligible Enterprise, Edu and Healthcare plans). Turn it into tidy notes: the decisions made, open questions, and a task list with an owner and due date for each if they are written down. Mark any word you could not read as [UNCLEAR] rather than guessing, then draft a short recap message I can paste into our team chat.
Write an email to [CLIENT NAME] asking them to approve a change order on [PROJECT]. The change: [WHAT CHANGED AND WHY]. Impact: [EXTRA COST] and [TIMELINE CHANGE]. Options they can pick: [OPTIONS, e.g. approve, approve a smaller version, or keep the original scope]. Keep it under 180 words, lead with what they need to decide and by when ([DATE]), show the cost and timeline in a short list, and keep the tone calm and helpful. Give me two subject lines.
I want to quote this statistic in a [PRESENTATION OR ARTICLE]: '[STATISTIC]', which I saw in [WHERE YOU SAW IT]. Search the web and trace it back to the original source. Tell me who first published it, when, how it was measured (sample size, region, method), and whether later sources changed or exaggerated it. If you cannot find the original, say so plainly. End with a one-line version I can safely use, with the citation.
Our [CHANNEL, e.g. email or paid social] campaign for [OFFER] missed its target. Goal: [TARGET]. Result: [RESULT]. Here is the data: [PASTE NUMBERS BY STEP, e.g. reach, clicks, sign ups, sales] and the creative and audience details: [DETAILS]. Work out which step of the funnel broke down most, list the three most likely causes with the evidence for each, and suggest one small test per cause that I can run in the next two weeks. Return a short diagnosis paragraph, then a table.
I start as [ROLE] at [TYPE OF COMPANY] on [DATE]. What I know so far: [WHAT YOU KNOW ABOUT THE TEAM, GOALS AND PROBLEMS]. Write a plan split into days 1 to 30 (learn), 31 to 60 (contribute) and 61 to 90 (lead), with three to five concrete goals in each, the people I should meet and what to ask them, and one quick win I could deliver early. Keep it realistic for someone also doing the day job. Return a table per phase.
I run [BUSINESS, e.g. a neighbourhood bakery] with about [NUMBER] regular customers who mostly buy [TYPICAL PURCHASE]. Brainstorm 15 loyalty perks that cost me little but feel generous, mixing rewards, recognition and convenience. For each: what the customer gets, my rough cost, how easy it is to run without new software, and one risk. Then pick the top three and write a short in-store sign for each. Return it as a table, then the signs.
Here is a sample of a JSON export from [TOOL]: [PASTE 3 TO 5 RECORDS]. Write a Python script that reads the full file from [FILE PATH], flattens nested fields into columns, keeps these fields only: [FIELDS], converts dates to YYYY-MM-DD, and writes a CSV next to the original without changing it. Explain each part in plain English, list any fields that look inconsistent in my sample, and show me how to run it on Windows and Mac.
Use Claude Fable 5.2 (on paid plans; on Pro and standard Team seats it uses usage credits). I am attaching my business plan for [BUSINESS OR PROJECT] and the spreadsheet behind it: [ATTACH FILES]. Read both in full, then: 1) list every place where the plan and the numbers disagree, 2) name the five assumptions the whole plan depends on and rate each as solid, shaky or untested, 3) suggest the cheapest test for each shaky or untested one, and 4) end with the three questions an investor is most likely to ask. Return it as a table followed by short headed sections.
I am a Claude Enterprise admin and I checked the Security center (beta), which compares our chat, Cowork and Claude Code settings with Anthropic's recommended setup. Here are the controls that did not pass, with their notes: [PASTE RESULTS]. Our constraints: [CONSTRAINTS, e.g. small IT team, some staff need web search]. Group the failed controls by risk, suggest an order to fix them, say who should own each and how long it is likely to take, and flag any change that could disrupt people's daily work so we can warn them first. Remember Security center is guidance, not a compliance certificate. Return a table plus a short note I can send to leadership.
I have a Smart reports summary from Claude Enterprise that groups our team's work into workstreams with friction points and recommendations: [PASTE SUMMARY]. Use it only to improve how the team works, not to judge any one person. Pull out the three workstreams where people seem to struggle most, what is likely causing the friction, and one practical fix for each (a template, a short training, a shared Project or a better prompt). Then draft a 30-minute team session agenda to share these fixes. Return headed sections and keep it under 400 words.
We are setting up pooled group budgets in Claude Enterprise, where each group shares one monthly budget and admins get email alerts at 50%, 75%, 95% and 100%. Here is last quarter's usage by department and what each team uses Claude for: [PASTE DATA]. Propose a starting monthly budget per group with a one-line reason, say what we should do when a group hits 75% and 95%, and list three signals that a budget is too low or too high. Return a table and a short, friendly announcement for team leads.
Write an email telling existing customers of [PRODUCT OR SERVICE] that the price goes from [OLD PRICE] to [NEW PRICE] on [DATE]. The honest reasons are: [REASONS]. Customers on [PLAN] keep the old price until [DATE]. Be clear in the first two sentences, explain what they get for the new price, give a simple way to ask questions or change plan, and avoid sounding defensive or salesy. Give me two versions: a short one under 120 words and a fuller one under 220 words, each with three subject line options.
Turn my notes on [PROJECT] into a one-page brief for a new teammate who starts on [DATE] and has no background. Notes: [PASTE NOTES]. Use these headings: Why this matters, What done looks like, What is already decided, Open questions, Who to ask about what, First three tasks. Keep each section to two to four short lines, cut anything they do not need in week one, and mark any point in my notes that seems to contradict another one.
Help me set up a simple monthly routine to keep an eye on [NUMBER] competitors in [MARKET]: [LIST COMPETITORS]. Tell me what to check each month (pricing pages, changelogs, job posts, reviews, social posts), roughly how long each check should take, and the warning signs that mean I should look closer. Then give me a reusable one-page template to fill in each month with a short 'what changed and does it matter' section. Return the routine as a checklist and the template as a table.
Customers of [PRODUCT] who downgraded from [HIGHER PLAN] to [LOWER PLAN] gave these reasons: [PASTE REASONS OR SURVEY ANSWERS]. Brainstorm 15 ideas to win some of them back, grouped into: fix the product, fix the price or packaging, and fix the communication. For each idea give the effort (low, medium, high), the likely impact, and how I would know within a month if it worked. Then pick the three I should try first and say why. Return it as a grouped table.
Write a quarterly newsletter for the [NUMBER] clients of my [TYPE OF BUSINESS]. This quarter: [WHAT HAPPENED, e.g. new service, results, team news]. Coming up: [WHAT IS NEXT]. Make it warm and useful, not a sales pitch: open with one practical tip they can use this week, then the updates in short sections with headings, then one clear invitation (to book a call or reply with a question). Keep it under 450 words and give me three subject lines.
I send about [NUMBER] invoices a month for [BUSINESS] and keep making the same mistakes: [LIST MISTAKES, e.g. wrong PO number, missing hours, old rates]. Build a short pre-send checklist (ten items at most) in the order I would naturally check things, with a one-line reason for each item. Then suggest two small habits or template changes that would stop the most common mistakes happening at all. Return it as a numbered checklist I can print.
In Grok Bot (included on Premium, Super and Ultra plans; Pages is rolling out gradually and needs desktop 0.60.0 or phone 1.14.0 or later), make a Page from my sales notes this week: [PASTE NOTES OR ATTACH FILE]. Lay it out as a simple dashboard: deals won and lost with value, the three biggest open deals and their next step, common objections, and a short 'focus for next week' list. Use only numbers from my notes and mark anything missing as unknown.
Grok Bot gives my account its own email address. Draft an update to my [NUMBER] suppliers (up to 50 recipients per message) about [CHANGE, e.g. new delivery hours from [DATE]]. Include what is changing, why, what they need to do, and who to contact with questions, in under 150 words, friendly and clear. Show me the draft and the recipient list first, and do not send anything until I reply 'send'.
In Grok Bot, create a 6 second 9:16 video at 720p from my attached product photo [ATTACH PHOTO] of [PRODUCT]. The camera slowly circles the product on a clean [COLOR] surface while soft light sweeps across it, ending on a still front view. Calm, premium mood. Keep the product's shape, label and colours exactly as in the photo, add no text and no people. Save it to my Library so I can find it later.
I generate product images through the xAI API with grok-imagine-image-2.0, which takes a quality setting of low, medium or auto. Write a small [LANGUAGE] script that reads prompts from [PROMPTS FILE], makes one low quality draft per prompt at 1k for review, saves them with clear file names, and then, only for the prompts I list in [APPROVED FILE], renders a final version at 2k with quality set to [MEDIUM OR AUTO]. Read the API key from an environment variable, never print it, and log the count of images made at each setting.
A new rule, [RULE NAME], affects [INDUSTRY] from [DATE]. Search recent posts on X and the web and find the questions and worries people keep raising about it. Group them into themes, give two short example posts for each theme with links, and note which questions the official guidance already answers (link it) and which are still unclear. Finish with five questions my customers are likely to ask me, with short, accurate answers.
My [BUSINESS] has a margin of [MARGIN]% and I need it at [TARGET]% within [TIMEFRAME]. Current prices: [PRICES]. Main costs: [COSTS]. Customer situation: [NOTES, e.g. loyal but price sensitive]. Compare raising prices against cutting costs: the effect on margin, the risks, how fast each works, and how customers might react. Be blunt about which option is weaker. Return a side-by-side table and a recommended order of moves for the next 90 days.
I am attaching [NUMBER] product images from my online shop selling [PRODUCT TYPE]. Write alt text for each: under 125 characters, describe what matters to a shopper (item, colour, material, key detail), no 'image of', no keyword stuffing, and no claims you cannot see. Return a table with image number, alt text and a slightly longer description (under 300 characters) for the product page.
We are hiring a [ROLE] at [COMPANY TYPE], [LOCATION OR REMOTE]. What makes it a good job: [HONEST HIGHLIGHTS]. Must haves: [REQUIREMENTS]. Write three versions of an X post: one under 200 characters, one under 280, and a five-post thread with the details. Make it human and specific, no buzzwords, no exaggeration, include how to apply ([HOW TO APPLY]), and suggest one image idea for the post.
Every year [MONTH] is my slowest month at [BUSINESS], with sales about [PERCENT]% below average. Brainstorm 20 promotion ideas that bring people in without training customers to wait for discounts: events, bundles, collaborations, limited items and content ideas. Rate each for cost, effort and likely effect, then pick the best three and give me a simple week-by-week plan for one of them.
Write a small [LANGUAGE] script that reads a list of URLs from [FILE], checks each one with a timeout of [SECONDS] seconds, and prints a table of URL, status code, response time and OK or FAIL. Retry a failed URL once before marking it failed, and exit with a non-zero code if any fail so I can use it in a scheduled job. Only send simple GET requests, explain each part briefly, and show how to run it on a schedule with cron.
Using Gemini Omni 1.2 Flash in the Gemini app (rolling out to Google AI Ultra subscribers), make a 15 second video explaining how [PRODUCT] works in three quick steps: [STEP 1], [STEP 2], [STEP 3]. Clean tabletop setting, close shots of hands using the product, a gentle camera push-in on each step, bright natural light and a friendly mood. Add soft background music and natural sounds, no voiceover, no text. Then suggest one follow-up edit I could ask for to make it clearer.
Using Nano Banana 2.1 in the Gemini app, mock up three different sign ideas for the front of my [TYPE OF SHOP] called '[SHOP NAME]': 1) a painted wooden sign, 2) a minimal metal letter sign, 3) a bold hanging blade sign. Show each on the same brick shopfront in daylight. Spell the name exactly as written, no other text. Then give me one sentence on the feel of each option and which would read best from across the street.
In the Gemini app's new business landing page for small business owners (rolling out globally), help me plan next month's promotions for [BUSINESS]. What I sell: [PRODUCTS OR SERVICES]. Dates that matter: [DATES]. Budget: [BUDGET]. Build a week-by-week plan with one main promotion per week, the channel for each, a short post caption, and what to measure. Keep it doable for one person in about [HOURS] hours a week and return it as a table.
Use Gemini 4 Argon (for Google AI Pro and Ultra subscribers). Our contract with [VENDOR] for [SERVICE] renews on [DATE]. Attached: the current contract summary, last year's usage and costs, and two alternative quotes [ATTACH FILES]. Compare staying, renegotiating and switching: total cost over [YEARS] years including switching effort, risks, and what we would lose or gain. List the three points I should push on if we renegotiate, and draft a short, polite email opening that negotiation.
We promised [CLIENT] that [DELIVERABLE] would be ready on [DATE] and we missed it because [HONEST REASON]. New date: [NEW DATE]. What we are doing to make it right: [ACTIONS OR GOODWILL GESTURE]. Write an email that owns the mistake in the first line without over-apologizing, gives the new date with confidence, explains what changes to stop it happening again, and offers a quick call. Under 170 words, warm and professional, with two subject lines.
Write a welcome email for a new client of my [SERVICE BUSINESS]. They signed up for [PACKAGE]. In the first week we need them to: [STEPS, e.g. fill in a form, book a kickoff call, share logins through our secure tool]. Make it friendly and short, with the steps as a numbered list with deadlines, what happens after each step, and who to contact. Under 200 words, plus a two-line text message version for clients who prefer SMS.
My team of [NUMBER] at [TYPE OF COMPANY] is considering a four-day work week. Research what trials and studies have found, with links to the original sources, then write a balanced brief: likely benefits, risks, which kinds of roles struggle, and what successful trials did differently. Mark anything based on a small or self-reported study. End with a simple three-month pilot design we could run, including what to measure.
I am attaching my draft [DOCUMENT TYPE] and the feedback from [NUMBER] reviewers [ATTACH OR PASTE]. Group the feedback into themes, mark where reviewers disagree, and sort every point into must change, worth considering and skip, with a one-line reason. Then give me a revision plan in the order I should work, with an estimate of effort for each step. Return it as a table, then the plan.
My Google Sheet of invoices has these columns: [COLUMNS, e.g. A invoice number, B client, C amount, D due date, E paid date]. Write a formula for a new 'Status' column that shows 'Paid', 'Due soon' (due within 7 days), 'Overdue' or 'Open', and a second formula that totals the overdue amount. Explain each formula in plain words, add conditional formatting rules to colour the statuses, and tell me how to handle blank rows.
I lead a team of [NUMBER] [ROLES]. Skills we need to build this quarter: [SKILLS]. We can spare [MINUTES] minutes every [FREQUENCY]. Plan a 12-week training calendar: the topic for each session, who could run it (team members teaching each other where possible), a short pre-read or exercise, and a quick way to check it stuck. Keep sessions practical and tied to real work. Return a table by week and a short message to announce the plan.
Using inline arguments for /model and /permissions (Codex CLI 0.164.0 or later), set the model to [MODEL, e.g. gpt-6.1-sol], reasoning effort to [EFFORT] and a permission profile that allows edits only inside this repo. Then confirm the settings back to me in one line. Task: [TASK, e.g. add CSV export to the reports page]. Plan first: list the files you expect to touch and the tests you will run, and wait for my OK. Then implement in small steps, running [TEST COMMAND] after each.
Memory v2 is on by default for fresh profiles in Codex CLI 0.165.0 and later. Open /memories and summarize what you remember about this repo and how I like to work. Flag anything outdated, wrong or too personal, and suggest a short, accurate set of memories instead (build and test commands, code style, things to avoid). Do not delete anything yourself: list the changes and wait for me to approve each one.
Codex 0.165.0 and later lets supported models change reasoning effort during a conversation. Start at [LOW OR MEDIUM] effort: read [FILES] and summarize how [FEATURE] works and where the bug [BUG DESCRIPTION] could come from. If your first two hypotheses fail to reproduce it, tell me and suggest switching to a higher effort before going further. Do not edit code until we agree on the cause; then make the smallest fix, add a regression test and run [TEST COMMAND].
Comment @codex security review on pull request [PR NUMBER] (Codex Security Review is available on Enterprise, Business, Edu and Pro plans). When it finishes, summarize every finding in a table: severity, file, what an attacker could do, and the suggested fix. Then plan fixes for the high and medium items only, each as its own small commit with a test, and wait for my OK before changing code. Never paste secrets or tokens into comments or logs.
Add an 'Export CSV' button to the table in [COMPONENT OR PAGE]. Plan first: tell me where the table's data comes from, whether the export should include only the filtered rows (it should), and which files you will touch. Then implement it with proper escaping for commas, quotes and line breaks, a file name like [NAME]-YYYY-MM-DD.csv, and a test for the CSV builder. Run [TEST COMMAND] and [LINT COMMAND], and show the diff.
Our app shows dates wrong for some users in other time zones. Read [DATE UTILITY FILE] and its callers, then list the cases most likely to break: midnight boundaries, daylight saving changes, users ahead of and behind UTC, and date-only values. Write table-driven tests for each case first and show me which ones fail. Wait for my OK before fixing anything, then make the smallest fix that makes them pass and run the full [TEST COMMAND].
Read the schema and migrations in [SCHEMA OR MIGRATIONS FOLDER] and write docs/data-dictionary.md: one section per table with its purpose, each column's name, type, whether it can be empty, and a plain English description, plus how tables relate to each other. Only describe what the schema and code show; mark guesses with TODO. Do not connect to any real database and do not read .env files. Show me the draft before saving.
In [LOGS FOLDER] there are log files from the last seven days. Write a small script that reads them without changing them, groups errors by message pattern, counts them per day, and lists the top ten with the first and last time seen and an example line. Save the output as [REPORT FILE].md. Run it, show me the report, and point out which errors look related to recent commits in git log. Do not print any secrets or personal data that appear in the logs; mask them.
The endpoint [ENDPOINT] is slow and I suspect it makes one database query per item in a loop. Read the handler and the data access code, confirm whether that is happening, and explain it in two or three sentences. Then propose a fix (for example, one batched query or eager loading) and wait for my OK. Implement it, add a test that checks the number of queries if our setup allows, run [TEST COMMAND], and show before and after query counts.
Set up a pre-commit check for this repo that runs our existing formatter and linter ([FORMATTER] and [LINTER]) on staged files only. Plan first: check what tools and config already exist so you do not add duplicates, and tell me which files you will add or change. Then set it up, document how to install it in the README in three lines, and show me it working on a deliberately badly formatted test file that you then remove. Do not reformat the whole codebase.
Switch to Claude Fable 5.2 with /model claude-fable-5-2 (needs Claude Code 2.1.321 or later and a paid plan; on Pro it uses usage credits). Bug: [DESCRIBE BUG AND HOW TO REPRODUCE]. Before editing anything, read the code paths involved, list your top three hypotheses with the evidence for each, and propose the smallest fix for the most likely one. Wait for my OK. Then make the fix, add a test that fails before it and passes after, run [TEST COMMAND], and show me the diff. Do not refactor unrelated code.
In Claude Code 2.1.319 or later, MCP tool calls that a server runs as a task move to the background on their own. Start the [MCP SERVER] tool to [LONG TASK, e.g. export last month's analytics]. While it runs, help me with [SECOND TASK] in this repo. When the background task finishes, tell me, summarize its result in five bullets, and point out anything that looks incomplete or failed. Do not write the result anywhere until I say where it should go.
I want to run [JOB, e.g. a nightly dependency report] unattended at [TIME]. Run `claude auth status` (Claude Code 2.1.318 or later shows the loginExpiresAt date for a stored claude.ai sign-in) and tell me in plain words when my sign-in ends. If it ends before my next planned runs over the coming [NUMBER] weeks, tell me when I should sign in again and add a short reminder note to [NOTES FILE]. Do not print or copy any tokens or credentials, and do not change my auth settings.
Claude Code 2.1.317 and later asks before a web or shell tool call sends your account email address to the network. I want the repo itself to be just as careful. Search the scripts, CI config and tooling in this repo for places that send an email address, git author details or other personal data to an outside service (analytics, error reporting, webhooks, API calls). Do not run any of these scripts and do not open .env files. Return a table: file, line, what is sent, where it goes, and whether it looks necessary. Then propose small diffs to remove or anonymize the unnecessary ones and wait for my approval.
The component [COMPONENT FILE] has grown past [NUMBER] lines. Read it and its tests first, then propose a split into smaller components with names, props and which state lives where. Wait for my OK. Then do it in small steps: move one piece at a time, keep behavior and styling exactly the same, and run [TEST COMMAND] and [LINT COMMAND] after each step. If tests are thin, add a couple of render tests before you start. Finish with the diff summary and anything you were unsure about.
The app reads settings from [CONFIG SOURCE, e.g. environment variables and config.yaml] in many places. Plan first: list every setting, where it is read, its type and default. Then add one small config module that loads and validates all of them at startup and gives a clear error naming the bad setting. Update the call sites to use it, add tests for valid and invalid configs, and run [TEST COMMAND]. Never print secret values in errors or logs, and do not change any actual secret files.
Look at the pull requests merged into [BRANCH] since tag [TAG] using git log and the PR titles. Write a user-facing changelog entry for version [VERSION]: group changes into New, Improved and Fixed, write each line in plain words about what the user notices (not the code), leave out internal refactors and test-only changes, and link each line to its PR number. Show me the draft first; only after I approve, add it to the top of [CHANGELOG FILE].
I have a product catalog export at [FILE PATH] with likely duplicates (same product with slightly different names, SKUs or spacing). Write a small script that finds probable duplicates, explains why each pair matched, and writes a review file listing proposed merges. Do a dry run only and show me the first 20 proposals. Do not change the original file; once I approve, write the cleaned version to a new file next to it and print a count of rows before and after.
Our background jobs in [JOBS FOLDER] log with plain print statements, so failures are hard to trace. Plan first: list each job and what it logs now. Then switch them to structured logs using [LOGGER, e.g. the existing logging library] with a job name, run id, duration and outcome on every run, keeping messages short. Never log secrets or personal data. Add a test that checks one job emits the expected fields, run [TEST COMMAND], and show the diff in small, reviewable pieces.
Read the repo's deployment and database setup ([RELEVANT FILES OR FOLDERS]) and draft a restore runbook in docs/restore.md: where backups come from, the exact order of steps to restore into a fresh environment, how to check it worked, and who to tell. Only describe commands that exist in this repo or its docs, mark anything you are unsure of with TODO, and do not run any restore, migration or delete command yourself. Show me the draft before saving it.
Start with gpt-image-2.6-flare (OpenAI's model for fast iteration) at 1536x1024 and make five quick concepts for a pricing page illustration for [PRODUCT]: three stacked cards labelled '[PLAN 1]', '[PLAN 2]' and '[PLAN 3]', the middle card slightly raised with a small 'Most popular' ribbon. Flat vector style, soft shadows, a calm palette of [BRAND COLORS] on a light background, no other text. Once I pick one, recreate it with gpt-image-2.6-sunburst at the same size for the final, keeping the layout and spelling exactly the same.
Using gpt-image-2.6-sunburst at 2560x1440 with complexity set to high, draw a clean top-down office floor plan for our move on [DATE]. Rooms and zones: [LIST, e.g. 'Quiet zone', 'Meeting room A', 'Kitchen', 'Team desks']. Each zone gets a pale fill colour, a clear label in a simple sans serif font, and small flat icons (desk, sofa, coffee cup). Add a legend in the bottom right and a north arrow. Thin grey walls, white background, even lighting, no people, no extra text beyond the labels I gave.
Using Nano Banana 2.1 (gemini-nano-banana-2.1, which accepts PDF input) with my attached one-page report [ATTACH PDF], create a 1:4 tall summary graphic at 2K. Title at the top: '[TITLE]'. Below it, the four most important numbers from the report as large figures with a one-line label each, then a simple bar chart of [METRIC], then a closing line: '[TAKEAWAY]'. Use only numbers that appear in the PDF. Flat editorial style, off-white background, navy and coral accents, generous spacing, crisp readable text.
Using Nano Banana 2.1 with my [NUMBER] attached product photos as object references (it can mix up to 14 reference images), place all the products in one neat lineup on a light oak shelf, arranged from smallest to largest, each product facing forward with its real label, shape and colour kept exactly as in the photos. Soft morning window light from the left, gentle shadows, a plain warm white wall behind. 16:9 at 4K. No added logos, no extra text, no people.
A quiet editorial still life for a feature on [TOPIC, e.g. slow mornings]: a ceramic mug, an open paperback face down, a pair of reading glasses and a sprig of eucalyptus on a linen tablecloth, shot from a 45 degree angle, soft side light from a nearby window, muted sage and cream palette, fine film grain, shallow depth of field --v 8.2 --hd --ar 3:2 (the --hd mode renders natively at 2K and takes about four times as long and costs four times as much)
Poster for a community event: the words '[EVENT NAME]' in big hand-lettered style across the top and '[DATE AND PLACE]' in small caps at the bottom, a bold flat illustration of [SCENE, e.g. a bicycle parade] in the middle, risograph print look with three inks (teal, tomato red, mustard) on cream paper --v 8.2 --ar 2:3. If any letters come out wrong, use Rerun (Thinking) on the job, which Midjourney is testing on the alpha site to improve prompt accuracy and typography.
Using FLUX 3 Image Klein (Black Forest Labs' open weights version of FLUX 3 Image), create a concept image of a small [TYPE OF SPACE, e.g. dental clinic waiting room]: pale wood benches along one wall, rounded plants in terracotta pots, a low reception desk in sage green, large windows with sheer curtains, and warm afternoon light across a terrazzo floor. Eye-level wide shot, architectural photography style, calm and welcoming mood, no people, no signage text.
Using Ideogram 4.5 with up to five of my brand images as references [ATTACH REFERENCES], design a conference name badge, portrait layout. Top band in my brand colour with the text '[EVENT NAME]'. Large centred placeholder name 'Alex Example' with the job title 'Product Lead' underneath, and a small row at the bottom reading '[DAY 1] | [DAY 2]'. Clean sans serif type, plenty of white space, simple geometric shapes picked up from the references. Set Background to Transparent, 2K.
Using grok-imagine-image-2.0 with aspect ratio 9:19.5 and resolution 2k, create a minimal phone lock screen wallpaper. One word in large, calm serif letters in the lower third: '[FOCUS WORD, e.g. FINISH]'. Behind it, a soft abstract landscape of rolling hills in [COLOR 1] and [COLOR 2], solid flat shapes, no gradients, no sun glare. Leave the top third clear for the clock. No other text, no logos.
Using Recraft V4.1 Vector (recraftv4_1_vector) with Styles matched from my [NUMBER] reference illustrations (between 1 and 10), create three spot illustrations in exactly that style for a pricing page: 1) a small paper plane for '[PLAN 1]', 2) a hot air balloon for '[PLAN 2]', 3) a rocket for '[PLAN 3]'. Same line weight, same palette, same corner rounding, centred on a transparent canvas with no text. Download the SVG links soon, since they last about 24 hours.
Using Kling 4.0 (in early access; multi-shot is on by default), make a 20 second 16:9 video at 1080p with stereo sound, in three shots. Shot 1: wide shot of [BAKERY NAME]'s shopfront at dawn as the lights flick on. Shot 2: close-up of hands shaping dough on a floured bench, slow push-in. Shot 3: a warm tray of bread placed on the counter, camera rises to show the shop opening. Soft golden light, cosy mood. Sound: birdsong, then gentle kitchen sounds, light acoustic guitar. No text on screen.
Using Kling 4.0 Flash for a quick draft (3 to 20 seconds, 720p), make a 10 second 9:16 clip: a bright, modern studio where a small group follows an instructor through a [CLASS TYPE, e.g. kettlebell] move, camera on a slow orbit around the group, then a quick cut to a close-up of a water bottle being set down. Energetic but friendly mood, natural daylight, upbeat drum beat with footstep and breath sounds. Original people only, no logos, no text.
Using gemini-omni-1.2-flash at 4K and 24 fps (a Google AI subscription is required; features vary by tier and country), make a 12 second 16:9 hero video: a slow dolly forward through an open-air hotel terrace at sunrise, past linen-covered breakfast tables, toward a calm sea view. Light curtains moving in the breeze, warm low sun, peaceful mood. Native audio: soft waves, distant birds, faint cutlery clinks, no music, no voice, no on-screen text.
Using Pika H3 Flex with up to 12 references [ATTACH PRODUCT PHOTOS AND A STYLE IMAGE], make a 15 second video of [PRODUCT] on a bright kitchen counter: a hand reaches in, picks it up and uses it once, then the camera slowly pulls back to show the whole counter. Clean, bright, friendly look matching the style image. Ask for the audio as separate stems (music, sound effects, ambience) so I can mix them later. No voiceover, no text.
Using MiniMax H3 (up to 15 seconds at 2K with native stereo sound), make a 12 second clip: overhead to side angle move around a potter's wheel as wet clay rises into a bowl, then a slow rack focus to shelves of finished glazed pots behind. Late afternoon light through dusty windows, earthy browns and blues, calm and focused mood. Sound: the wheel humming, water dripping, soft radio music far in the background. No people's faces in focus, no text.
Using veo-3.1-generate-001 on Google Cloud Vertex AI with first and last frame images: first frame [ATTACH IMAGE OF CLOSED PRODUCT BOX], last frame [ATTACH IMAGE OF PRODUCT SET UP ON A DESK]. 8 seconds, 16:9, 1080p, with audio. The box lid lifts, the product glides out and settles into place on the desk as the camera gently arcs to the right. Bright, clean studio light, satisfying mood. Sound: soft cardboard slide, a light click, quiet ambient room tone.
Using Luma Ray3.2 (ray-3.2), 10 seconds, 16:9, 1080p, with keyframe images placed along the clip [ATTACH 3 TO 5 KEYFRAMES: warehouse shelf, van, front door]. A small brown parcel travels from a warehouse shelf onto a conveyor, into a delivery van, and finally onto a doorstep, with smooth tracking camera movement linking each step. Clean, slightly stylised look, bright daylight, cheerful mood. Keep HDR off (10 second clips do not support it). No text, no logos.
Using grok-imagine-video-1.5 (text to video at native 1080p, with audio on), set duration to 15 seconds and aspect ratio 9:16. A barista demonstrates one tip: [TIP, e.g. warming the cup before pouring]. Shots flow naturally: close-up of the cup being rinsed with hot water, then the espresso pour, then latte art forming. Warm cafe lighting, relaxed mood, shallow depth of field. Sound: steam wand hiss, cups clinking, soft lo-fi music. Original people, no text on screen.
Using FLUX 3 Video (preview), set duration to 20 seconds, aspect ratio 16:9, resolution fhd, with audio on and multishot. Shot 1: wide view of a garden centre greenhouse in the morning, sprinklers misting rows of plants. Shot 2: close-up of hands repotting a [PLANT]. Shot 3: a family walking out with a trolley full of plants, camera tracking beside them. Fresh, sunny, green mood. Sound: birds, water spray, light upbeat acoustic music. No text, no brand names.
Using Dreamina Seedance 2.5 through BytePlus ModelArk, ratio 21:9, 1080p, duration 25 seconds, generate_audio on. A one-take, slow handheld move through a small bike repair shop: tools hanging on a pegboard, a mechanic truing a wheel on a stand, a customer test riding out the open door into a sunny street. Warm tungsten light inside, bright daylight outside, honest and friendly mood. Sound: ratchets, a spinning wheel ticking, street sounds. Original people only, no logos, no text.
I use ChatGPT dots (needs access to dots, which roll out gradually to eligible accounts). Help me set up a recurring job for my dot. Every [DAY] at [TIME] it should gather [SOURCES, e.g. my calendar, my task list, my shared inbox], then write a one page summary of [WHAT I NEED, e.g. open decisions, overdue items, meetings to prepare for]. First ask me up to five questions about what matters most. Then return: 1) the exact instruction to give my dot, 2) what it should never do without asking me, 3) a short checklist to review its first report.
I am deciding whether to use GPT-6.1 Terra (available in ChatGPT Work and Codex on Plus, Pro, Business, Enterprise and Edu plans) for this task: [TASK]. The inputs are [FILES, SCREENSHOTS OR WEBSITES]. Tell me whether the job needs visual reasoning or computer use, what could go wrong, and what I should check by hand. Return a short table with columns: step, what the model does, what I verify. End with a one line recommendation.
I am reading this email thread on my phone in ChatGPT: [PASTE THREAD]. Write a reply from me, [NAME], to [CUSTOMER NAME] about [ISSUE]. Keep it under 120 words, warm and direct, with one clear next step and a date of [DATE]. Then give me two shorter alternatives I can send if I have less time. Do not promise anything I have not listed here: [WHAT I CAN OFFER].
Here is the transcript of a team call: [PASTE TRANSCRIPT]. Return: 1) decisions made, each with who owns it, 2) open questions nobody answered, 3) follow ups with a due date if one was mentioned (say 'no date' if not), 4) anything people disagreed about. Quote the exact line for each decision so I can check it. Do not add anything that was not said.
I want three matching images made in ChatGPT to explain [CONCEPT] to [AUDIENCE]. Before generating, write a three frame storyboard: what changes in each frame, the on screen words (max [N] words), the colour palette using [BRAND COLOURS], and the style. Then give me one final image prompt for each frame that keeps the look consistent. Ask me to approve before anything is generated.
Rewrite the policy below so a new [ROLE, e.g. warehouse hire] can follow it on day one. Keep every rule, but use short sentences, active verbs and a reading age of about [AGE]. Return: 1) the rewritten policy with headings, 2) a list of rules that were unclear and how you resolved them, 3) three questions a new hire might still ask. Policy: [PASTE POLICY]
I use ChatGPT on iPhone and can open my dot from a Home Screen widget and Apple Shortcuts actions (Messaging, Dictation, Call; needs dot access). Suggest 10 small daily habits for [GOAL, e.g. running a small shop] that I can start in under ten seconds from a widget or shortcut. For each give the trigger, the exact first message I send, and what a good reply looks like. Mark the three easiest to start this week.
I started a long task in ChatGPT: [DESCRIBE TASK]. While it runs, I want to change direction without starting again. Write five short follow up messages I could send to steer it, for these cases: it is too long, it is going off topic, I want a different format, I need it to check a source, and I want it to stop and summarise. Keep each message under 20 words and tell me when to use it.
I must choose between [OPTION A] and [OPTION B] by [DATE]. My goals are [GOALS], my limits are [BUDGET, TIME, PEOPLE]. Do not pick for me yet. First list the five facts that would change the decision and ask me for any you need. Then score both options from 1 to 5 against my goals in a table, show your reasoning in one line each, and give a final recommendation with the biggest risk and how to test it cheaply.
Check this claim before I share it with [AUDIENCE]: [CLAIM]. Search the web and use only reliable, primary or official sources. Return: verdict (true, partly true, false, unclear), the evidence with a link and the date for each source, what is missing, and a safe one sentence version I can post. If you cannot confirm it, say so plainly.
I have linked my accounts to Personal Finance in Claude (beta, Pro, Max and Ultra plans in the US only). Using my balances and spending, answer: 1) where did my money go last [MONTH], grouped into five to eight categories, 2) which subscriptions or repeat charges look new, 3) what is my average monthly spend on [CATEGORY]. Show the numbers in a table, say what you could not see, and do not give investment advice. End with three questions I should ask myself.
I am trying Claude Duet, the research preview for Pro and Max plans where Claude works as a proactive agent. Help me set the rules for it. My work is [JOB]. List what it may do on its own (for example drafting, sorting, reminding), what it must ask me first (anything sent to other people, anything that spends money), and what it should never touch: [SENSITIVE AREAS]. Return a short set of rules I can paste in, plus a five minute test to check it follows them.
I am using Claude Haiku 5.5 for high volume writing. Write [NUMBER] short first drafts of [TYPE, e.g. product descriptions] from the list below. Use one consistent voice: [VOICE DESCRIPTION]. Keep each under [WORDS] words, no hype, and flag any row where the data is missing instead of guessing. Return a table with the item, the draft and a flag column. Data: [PASTE LIST]
Compare Report A and Report B below. Return: 1) a one paragraph summary of what changed, 2) a table of numbers that differ with the old value, the new value and the page or section, 3) claims that appear in only one report, 4) anything that looks inconsistent and needs a human check. Do not guess missing numbers. Report A: [PASTE OR ATTACH]. Report B: [PASTE OR ATTACH].
Write a follow up email to [NAME], who owes me [THING] by [DATE]. This is the [FIRST/SECOND/THIRD] chase. Keep it under 90 words, friendly, and state the exact thing I need and the date I need it. Give me three versions: warm, neutral and firm. Add one subject line for each. Do not blame them or sound sarcastic.
The same problem keeps happening: [DESCRIBE]. Here is what I know: [TIMELINE, EXAMPLES, WHO IS INVOLVED]. Ask me up to six questions first. Then use a 'five whys' chain to find the likely root cause, list two alternative causes, and suggest one cheap test for each. Finish with a fix I can start this week and a way to tell if it worked.
Turn my talk notes into a one page handout for [AUDIENCE]. Notes: [PASTE NOTES]. Return: a title, a three sentence summary, five key points each with a plain example, a short checklist they can use tomorrow, and one question to think about. Use headings and short lines, under [WORDS] words in total.
Suggest 20 names for [PRODUCT OR PROJECT] that suit [AUDIENCE]. Rules: easy to say aloud, easy to spell, no more than [N] syllables, no real brand names, and no meaning that is rude in common languages. Group them into four styles, mark your top five, and give a one line reason for each. Remind me to check trademarks and domain availability myself.
Explain the script below to someone who does not code. Return: what it does in two sentences, a line by line walk through in plain English, what files or data it changes, what could go wrong, and a safe way to test it on a copy first. Do not change the code. Script: [PASTE SCRIPT]
I have attached my style guide: [ATTACH]. Edit the draft below to follow it. Return the edited draft, then a list of each change with the rule it follows. Do not change facts, numbers or names. If a rule in the guide clashes with the draft's purpose, flag it instead of choosing. Draft: [PASTE DRAFT]
My app uses xAI Speech to Speech with the model grok-voice-2.0, which is deprecated. xAI says to switch to grok-voice-3.0 or grok-voice-latest at the same price. Here is the relevant code: [PASTE CODE]. List every place the model name appears, explain the difference between pinning grok-voice-3.0 and using the grok-voice-latest alias (the alias upgrades automatically), and recommend one for [MY CASE]. Give the smallest change and a test I can run without spending money.
xAI retired grok-imagine-image-quality and grok-imagine-image-pro, and requests are now served by grok-imagine-image-2.0-low at a lower price. Write me a checklist and a search plan to find every use of these names in my project: code, config files, docs and cost reports. Explain what changes in my billing and what I should test. My stack is [LANGUAGE AND FRAMEWORK]. Return steps I can follow, not code that deletes anything.
I want to animate a still image of [SUBJECT] with grok-imagine-video-1.5 (image to video, up to 15 seconds per xAI docs). Write the motion prompt: what moves, the camera move, the mood, and what must stay unchanged (logo, face, text). Give a version for [DURATION] seconds and a shorter safer version. List three things to check in the result before I publish.
Search X for what people are saying about [TOPIC] in the last [DAYS] days. Return: the three main opinions with two example posts each (link them), questions people keep asking, any claims that look wrong, and the accounts that seem well informed. Say how confident you are and where the sample is thin. Do not name private individuals.
Someone asked me for [REQUEST], which I cannot do because [REASON]. Write a reply that says no clearly, keeps the relationship, and offers [ALTERNATIVE] if I have one. Give me a short version of 60 words and a longer one of 120 words. No excuses, no over apologising.
Design a 20 minute weekly review for someone who works as [ROLE]. Include: what to look at, five questions to ask, how to pick the top three priorities for next week, and what to drop. Return it as a checklist I can paste into a note. Ask me two questions about my work first if you need them.
I am stuck on this decision: [DECISION]. Be direct and friendly. Ask me five blunt questions, one at a time, and wait for my answers. After the fifth, tell me what my answers suggest, what I am avoiding, and one small step I can take today.
Cut the text below to a post of [CHARACTERS] characters or less for X, keeping the main point and one concrete detail. Give me three versions: plain, punchy and curious. Do not use hashtags, emojis or clickbait. Text: [PASTE TEXT]
Here is a question customers keep asking: [QUESTION]. Suggest a series of 10 posts or short videos that answer it from different angles for [PLATFORM]. For each: title, the first line, and what the viewer learns. Mix beginner and advanced ideas and avoid anything I could not honestly say.
Write a [LANGUAGE] script that renames files in [FOLDER] to the pattern YYYY-MM-DD_original-name using each file's modified date. It must default to a dry run that only prints what would change, never overwrite an existing file, and write a log I can use to undo it. Show the script and how to test it on a copy.
Gemini Skills are saved, reusable instructions for a specific task. Help me write one for [TASK I REPEAT]. Ask me what good output looks like, then return: a skill name, the instructions, the inputs I will give each time, the output format, and three rules it must never break. Also tell me how to test it with one real example.
Using Gemini 4 Argon (available to Google AI Pro and Ultra subscribers), build a [NUMBER] slide deck for [AUDIENCE] from these sources: [LINKS OR FILES]. Start with an outline and the one message each slide must land. Then write the slide text and speaker notes. Mark any claim you could not find in the sources so I can check it.
I use the Gemini app on macOS and can start a coding agent with Google Antigravity (English, personal accounts and eligible Workspace accounts aged 18+, where Antigravity is supported). I want a prototype of [APP IDEA] for [USER]. Before it builds, write the brief: pages, what each does, sample data, what is out of scope. Ask the agent to test its code and tell me what to review.
I have connected [APPS, e.g. calendar, mail, drive] to Gemini through Customize. Prepare me for my meeting with [PERSON OR COMPANY] on [DATE]. Pull together: past emails and files that mention them, open action items, what they last asked for, and three questions I should ask. Only use what is in my connected apps, and list each source you used.
I use the Gemini app on Windows (Alt + Space opens it, Windows 10 or later). List 10 quick tasks I can do without leaving my current window, for example [MY WORK TOOLS]. For each give the exact prompt to paste, what I should check, and a task I should not hand over without reviewing. Group them by time saved.
Turn these rough notes into a client update email for [CLIENT]: [NOTES]. Structure: one line on status, what was done, what is next, anything I need from them with a date. Keep it under 150 words, calm in tone, and flag any note that sounds like a promise I should confirm first.
My [METRIC] dropped by [AMOUNT OR PERCENT] between [DATE A] and [DATE B]. Data I have: [PASTE OR ATTACH]. List the most likely causes, ranked, with the data that would confirm or rule out each. Ask me for anything missing. Then suggest two checks I can do today and one longer test.
Reformat the report below so a busy reader gets the point in 60 seconds. Return: a three bullet summary, restructured headings, a table for any numbers, and bold for decisions needed. Keep every fact and number unchanged and tell me if you removed anything. Report: [PASTE REPORT]
I want to test [NEW OFFER] for [AUDIENCE] without spending more than [BUDGET]. Suggest eight tests, from a simple poll to a fake door page. For each: what I do, how long it takes, the signal that means 'go', and the signal that means 'stop'. Rank them by speed and by how reliable the result is.
Explain [TOPIC] for someone who knows [BACKGROUND]. Use only current, reliable sources and list them with links and dates. Return a short overview, the main points of disagreement, what is still uncertain, and three further reading links. Say clearly if something may be out of date.
I use Codex CLI. Help me plan three independent tasks to run in parallel from the agent command center (codex agents --no-daemon): [TASK A], [TASK B], [TASK C]. For each, state the files it may touch, the tests that prove it works, and how to avoid conflicts between them. Do not let any task touch secrets, delete data or push to main. Return a plan I approve before anything starts.
In Codex CLI I can keep reusable prompts and slash commands in /presets slots. Draft three presets for my repo [REPO DESCRIPTION]: one for a safe code review, one for writing tests for a changed file, and one for a short release note. Each should say what to inspect, what to return, and what it must not do. Keep each under 120 words and make them easy to edit.
Codex cannot reach the network from my machine: [ERROR OR SYMPTOM]. Walk me through a diagnosis using codex doctor --network-only. Tell me what each result means, the likely causes (proxy, VPN, DNS, certificates), and the order to check them. Only suggest read only commands first, and ask before changing any setting.
I left a Codex thread unfinished: [WHAT IT WAS DOING]. Help me resume it safely with codex queue --resume. First summarise the state: what was changed, what tests were run, what is left. Then list the files changed so far and ask me to confirm before it continues. Keep diffs small and run the tests before and after.
Use /config search in Codex CLI to review my settings. Goal: [GOAL, e.g. safer permissions, quieter output]. List the settings to check by category, what each does, the safest value, and what I give up by changing it. Do not change anything until I say so, and show the before and after for each change.
In [REPO], the form at [PATH] accepts bad input. Plan first: list the fields, the rules (required, length, format), and the error messages. Then make the smallest change to validate on the client and the server, add tests for good and bad input, and run the test suite. Show the diff summary. Do not change unrelated files.
Review the diff of [BRANCH OR PR] against main. Do not edit code. Return a list of: unclear names, dead or unused code, missing tests, and risky changes, each with file and line and a suggested fix. Rank by importance and keep it under 15 items.
Read the repository and write a README that matches what is really there. Include: what it does, how to install, how to run, how to test, folder map and how to contribute. Check every command by reading scripts and config, and mark any command you could not verify. Do not invent features. Show the draft before saving.
Take the CSV at [PATH] and write a script that cleans it: trim spaces, fix date formats to YYYY-MM-DD, normalise column names, and flag duplicate rows. Write the cleaned data to a new file, never overwrite the original, and produce a short report with counts of each fix. Run it on a sample first.
The test [TEST NAME] fails about one run in [N]. Plan first: read the test and the code it covers, list likely causes (timing, shared state, random data, network). Reproduce it by running the test repeatedly, then make the smallest fix and run it [N] times to show it is stable. Do not skip or delete the test.
I run Claude Code in a script with no one to answer prompts. Explain the setting permissions.denyInsteadOfPrompting, which denies a call that would wait on a permission prompt so the turn continues. Show how to add it to my project settings, which calls it will deny, and how to design the task so it still finishes. Give a short test plan I can run on a throwaway repo.
Set up the permissions.blockWritesOutsideWorkingDirectories setting for my project so Write, Edit and NotebookEdit refuse paths outside the working directories. Show me the settings file change, how to check it works with a harmless test, and what legitimate tasks it might block, such as writing to [SHARED FOLDER]. Do not change any other setting.
My app calls the Claude API and feels slow: [DESCRIBE, e.g. a chat endpoint takes too long to start answering]. Use /claude-api latency-optimize to review how we call it. First read the code at [PATH]. Return: where time goes, the top three changes (for example streaming, caching, smaller prompts), and a small diff for the first one. Measure before and after.
I use subagents for simple checks in Claude Code. Explain how to set CLAUDE_CODE_SUBAGENT_EFFORT, what values it accepts according to the docs, and when a lower effort is a bad idea. Then propose which of my subagents ([LIST]) could run at lower effort, and a way to compare results on three real tasks before I commit to it.
Before a long unattended Claude Code job, run claude auth status and read loginExpiresAt. Tell me in plain words whether my login lasts long enough for a job that takes about [HOURS] hours. If not, give me the steps to renew it first. Also show how to read credential_expires_at from the claude -p JSON output in a script and stop early with a clear message.
In [PATH], the call to [SERVICE] fails now and then. Plan first, then add a retry with exponential backoff and a cap of [N] tries, only for errors that are safe to retry (timeouts, 429, 503). Add tests with a fake client, log each retry without printing secrets, and run the tests. Keep the diff small.
Plan first: search [PATH] for every outgoing HTTP call. List them with the current timeout (or none). Then add a sensible default timeout of [SECONDS] seconds through one shared helper, with a clear error message on timeout and no secrets in logs. Add tests using a slow fake server, run the suite, and show a short diff summary.
Read the markdown files in [FOLDER]. Build a decision log in docs/decisions.md: date, decision, who decided, why, and the source file. Skip anything that is not a decision, and list unclear items separately. Do not edit the original notes. Show me the first ten entries before writing the file.
Plan first: find the components in [PATH] and list common accessibility issues (labels, focus, contrast, keyboard use). Add an automated check to the existing test setup, fix the three most serious failures with small diffs, and run the tests. Summarise what still needs a manual check with a screen reader.
The page at [ROUTE] loads slowly. Do not guess. Find how it loads data and assets, measure with the tools already in the project, and list the three biggest costs with numbers. Fix only the largest one with a small diff, then measure again and show the change.
Create a clean flat illustration of a friendly paper-craft fox mascot for a small accounting firm, three quarter view, standing on a plain off white background. Soft studio lighting, simple shapes, palette of deep green, warm orange and cream. No text, no logos. Keep the fox's face, ears and proportions simple and consistent so I can reuse this image as a reference for other poses.
Design a landscape chalkboard menu for a small cafe called [CAFE NAME]. Render exactly this text, spelled correctly: [LIST OF ITEMS AND PRICES]. Hand lettered white chalk on a matte black board, a thin wooden frame, small doodles of coffee cups in the corners, soft overhead lighting, slight chalk dust. Clean readable layout with clear hierarchy.
A split image of the same living room, left side empty with bare walls and a grey floor, right side staged with a [STYLE] sofa, a round rug, a plant and warm lamps. Same camera angle, same window and same light on both sides, realistic photography style, natural daylight, crisp detail. Small labels 'Before' and 'After' in clean sans serif at the top.
Using the uploaded product photo, keep the product, its label and its shape exactly the same. Place it on a pale stone counter beside a folded linen cloth and a small glass of water, morning window light from the left, soft shadow, shallow depth of field. Natural colours, no extra text, no added logos. Square crop.
A vertical infographic with four numbered steps showing how to [PROCESS, e.g. recycle used batteries safely]. Flat vector style, each step has a simple icon and a short line of text: [STEP TEXTS]. Calm blue and yellow palette, lots of white space, clean sans serif lettering, readable at phone size. No photographs, no brand names.
Use FLUX 3 Image Klein, an open weights model, for a local test. Prompt: a matte ceramic mug on a wooden desk beside a notebook and a pencil, soft window light, 50mm lens look, shallow depth of field, calm neutral tones, photoreal. No text, no logos. I will run it on my own machine to compare against a hosted model.
Use several reference images: image 1 is my shop front, image 2 is a seasonal wreath, image 3 is a chalk sign. Combine them: place the wreath on the shop door and the sign beside it, keep the building, windows and street unchanged, golden hour light, realistic photo style. Keep the sign text exactly: [SIGN TEXT].
Design a friendly owl mascot for a study app in clean vector style: simple geometric shapes, flat colours, a limited palette of navy, teal and sunny yellow, bold outline, centred on a transparent looking plain background. Front view, round glasses, a small book under one wing. No text. Make it easy to scale down to an app icon.
Create a set of six matching line icons for a settings screen: profile, notifications, privacy, billing, help, language. Same stroke weight, rounded corners, single colour dark grey on white, simple and legible at small sizes, evenly spaced in a 3 by 2 grid. No text labels.
A quiet morning kitchen seen from a low angle, steam rising from a pot of tea on a wooden table, sunlight through linen curtains, a half read paperback, soft muted colours, gentle film grain, wide editorial composition with space on the right for a headline. Calm, warm mood. No people, no text. --ar 16:9
Use Veo 3.1 first and last frame. First frame: my closed [PRODUCT] box on a clean white table. Last frame: the box open with the product standing upright. Smooth slow push in, soft studio light, gentle paper rustle and a soft click as the lid opens. Duration [DURATION]. No logos, no text, no people.
Use Veo 3.1 Ingredients to video with my reference image of a [OBJECT]. Show it on a kitchen counter as morning light moves across it, slow handheld camera drifting to the right, quiet room tone and a soft clink. Keep the object's colour, shape and markings exactly as in the reference. Duration [DURATION], 16:9.
Take my existing clip of [SCENE] and use Veo 3.1 scene extension to continue from its last second. Continue the same motion: the camera keeps slowly moving forward, the light stays the same, and a person walks out of frame. Ambient street sound continues. Keep the look and colour identical so the join is invisible.
Kling 4.0 shot: a courier on a bicycle races down a narrow city street at dawn, the camera starts behind and swoops up over the rooftops then follows from the side. Fast action, motion blur on the wheels, cool blue light with warm window glow. Original character, no logos. Duration [DURATION], 16:9.
Kling shot: a woman in a green cardigan sits at a desk, types, looks up and smiles at a colleague off screen. Medium shot, gentle push in, soft daylight, quiet office sounds. Keep her face, hair and clothes the same throughout. Original person, no logos, no text. Duration [DURATION], 16:9.
Animate my uploaded image of [SUBJECT] with grok-imagine-video-1.5. Motion: the subject slowly turns toward the camera, leaves in the background sway, a soft light shift. Camera: very slow push in. Keep the subject's face and colours unchanged. No text overlays. Duration [DURATION] (up to 15 seconds per xAI docs).
Use grok-imagine-video-1.5 reference to video with my mascot reference image. Scene: the mascot waves, walks across a sunny park path and sits on a bench. Friendly cartoon motion, gentle camera pan, light music and birdsong. The mascot must keep its exact look. Duration [DURATION], vertical 9:16 for a short clip.
Runway shot: slow close up of hands sanding a wooden bowl, wood dust floating in warm light, a lathe in the soft background, calm documentary look with shallow depth of field. Camera drifts slowly to the right. Sound of sanding and a quiet workshop. Original hands, no logos, no text. Duration [DURATION].
Use Luma to make a [DURATION] product ad for [PRODUCT]: a clean studio shot with a slow orbit around the product on a soft grey surface, gentle highlights, subtle sound. Then I will use Luma Variants to resize and translate the static ad versions into other formats, keeping the logo, headline and call to action intact.
Gemini Omni Flash 1.2 scene: two colleagues talk by a window in a bright meeting room. Woman: 'Did the numbers come in?' Man: 'Yes, and they look good.' Medium two shot, slow push in, natural room tone, consistent faces and clothes. Original people, no logos, no text. Duration [DURATION], 16:9.
Using the iCloud Mail and Calendar plugins in ChatGPT (connect them first; they work on the web, desktop app and iOS), find the latest email from [SENDER] about [TOPIC] and check my calendar for [DATE RANGE]. Draft a reply that answers their questions, proposes two meeting times that are actually free, and keeps a [TONE] tone. Return the draft only. Do not send anything or change my calendar until I say so.
I am using a locked chat in ChatGPT (more options menu, then Lock chat) for a private topic: [TOPIC]. Help me plan it. Ask me up to five questions first, then return a one page plan with: goal, three milestones with dates, what could go wrong, and the single next action for today. Keep the language plain and do not suggest I share anything with other people.
I saved a reference photo in ChatGPT (saved reference images) and named it [NAME]. Using @[NAME], create [NUMBER] image concepts for [CAMPAIGN OR POST], each in a different setting: [SETTING 1], [SETTING 2], [SETTING 3]. Keep the subject's key details the same each time. For each concept, give a one line caption I can use and the aspect ratio I should request.
With ChatGPT Images 2.6, I will upload a simple sketch of [CHARACTER OR OBJECT]. Make a looping GIF where [SIMPLE ACTION, for example the character waves]. Keep the style flat and friendly, use a plain background in [COLOUR], and keep the loop short. After it is made, suggest two speed changes I could try and one caption for sharing on [PLATFORM].
I am a business owner preparing to claim my business in ChatGPT Business Hub (web sidebar, needs identity verification and approval). Business name: [NAME]. What we do: [DESCRIPTION]. Website: [URL]. Draft: a 50 word business description, a list of ten facts customers ask about most, and a plain list of what to check is accurate before I publish. Only use facts I give you, and flag anything you are unsure of.
(Needs a Pro plan) Use GPT-6 Pro in the chat tab and let multiple agents work on different parts of this problem in parallel: [PROBLEM]. Split it into three parts, say what each agent is handling, then merge the results into one recommendation. Return: the recommendation, the evidence behind it, what each agent found, and the one thing I should check by hand.
I will talk through my thoughts with ChatGPT Voice (GPT-Live) and then paste the transcript here. Turn the transcript into a clear [EMAIL / MEMO / POST] for [AUDIENCE]. Keep my meaning and my voice, cut repeats and filler, and put the main point in the first line. Return the clean version and a short list of anything I said that is unclear or may be wrong: [TRANSCRIPT]
I stay signed in to two ChatGPT accounts (Settings, then Switch account): one for [WORK] and one for [PERSONAL]. Help me decide the rules for what goes in each, so memory and chats stay clean. Return a short table of task types, which account to use, and why, plus a five minute weekly habit to keep both tidy. Keep it simple and practical.
(Slides is rolling out to eligible Pro, Business and Enterprise users with Space access.) I need a presentation about [TOPIC] for [AUDIENCE] that lasts [MINUTES] minutes. Before building anything, brainstorm five different angles. For each, give a one line story arc, the opening slide idea, and the risk. Then recommend one and list the slide titles for it.
Select GPT-6.1 Terra in Work or Codex (available on Plus, Pro, Business, Enterprise and Edu as it rolls out). Review this script for [PURPOSE]: [PASTE CODE]. First explain in plain words what it does. Then list bugs and edge cases in order of risk, and suggest the smallest fix for each. Show changed lines only, and say how I can test each fix safely without touching real data.
(Claude Duet is a research preview for Pro and Max plans.) I am starting [NEW ROLE OR PROJECT] on [DATE]. Act as my proactive helper for the first week. Ask what you need, then propose a day by day plan with one priority per day, the people I should meet, and a short end of day check in question. Tell me what you will keep an eye on, and ask before you take any step on my behalf.
(Personal Finance in Claude is a US beta on Pro, Max and Ultra plans; link accounts only if you are comfortable.) Look at my last three months of spending and tell me where the biggest gap is between what I earn and what I spend. Return a short table of the top five categories, one change per category I could try this month, and a note on what you could not see. Do not move money or give investment advice.
Use Claude Haiku 5.5 to rewrite this email so it is half the length and easy to read on a phone: [PASTE EMAIL]. Keep every date, number and commitment exactly as written. Return three versions: friendly, neutral and firm. Under each, list anything you cut so I can put it back if needed.
Compare [VENDOR A] and [VENDOR B] for [NEED]. Use only the pages and files I give you: [LINKS OR FILES]. Return a table with price, features, limits, support and anything missing, and mark each cell as stated, implied or unknown. End with a recommendation for a business that [SITUATION], and three questions to ask each vendor before buying.
A client, [NAME], asked for [DISCOUNT] on [PROJECT]. Our usual price is [PRICE] and my lowest acceptable price is [FLOOR]. Draft three replies: hold the price, trade the discount for something specific (for example [TRADE]), and split the difference. Keep each under 150 words, warm and clear, and list the risk of each approach in one line.
Here is a customer story: [PASTE NOTES]. Turn it into a LinkedIn post of about [WORDS] words and a short newsletter blurb of three sentences. Start with the problem the customer had, include one real number only if it appears in my notes, and end with a simple question. Do not invent quotes or results. Tell me what to check with the customer before posting.
My plan includes monthly API credits for the Claude Platform (linked through a Console organization). My work is [JOB] and my team is [SIZE]. Brainstorm eight small automations or tools I could build, each with the problem solved, rough effort (hours), and what data it needs. Rank the top three and suggest a safe first test that costs very little.
My team keeps missing deadlines on [PROCESS]. Here is how it works today: [STEPS]. Ask me five sharp questions, then give me a ranked list of likely causes, a quick way to test each, and the smallest change that would help most. Be direct and do not blame individuals. End with a one line summary I can share with my manager.
Explain what this script does in plain words for someone who does not code: [PASTE SCRIPT]. Then list the risks of running it (for example overwriting data), and suggest a safer version with a dry run option and clear comments. Keep the behaviour the same. Return the explanation, the risk list and the new script in that order.
Here are my notes for this week: [NOTES]. Write a handover note for [COLLEAGUE] who covers for me from [DATE]. Include: what is done, what is in progress, what is blocked and why, deadlines in date order, who to ask for what, and three things they must not do. Keep it to one page and use plain headings.
I am building [PROJECT] and need to choose between grok-4.7, grok-4.6 and grok-build-0.1 on the xAI API. Check the current docs.x.ai models page and tell me the context window of each and which one fits [TASK]. Return a small table with model, context window, best use and one caution. If a detail is not on the page, say so instead of guessing.
I want to try grok-voice-3.0 (Speech to Speech) for [USE CASE]. Plan a five day test: day by day goals, ten sample calls to try, what a good call sounds like, what to log, and the stop signs that mean I should pause. Keep cost low and use no real customer data. Return a table I can paste into a spreadsheet.
Rewrite this announcement for X: [PASTE TEXT]. Give me five versions: one sentence, a post under 280 characters, a three post thread, a friendly version, and a no hype version. Keep every fact. Mark any claim that needs a source before I post.
Search X for what people are saying about [TOPIC] over the last 30 days. Return: the three main themes, one strong example post per theme (summarised, not copied), who is driving each theme, and what is still unclear. Separate facts from opinions and tell me how confident you are in each theme.
I met [NAME] at [EVENT] and we talked about [TOPIC]. Write a follow up email under 120 words that reminds them who I am, adds one useful thing ([RESOURCE OR IDEA]), and suggests a small next step. Give me two subject lines and a version for LinkedIn. Keep it warm and not pushy.
Write three prompts for grok-imagine-image-2.0 for [CAMPAIGN]. Each should describe subject, setting, composition, lighting, style and any text to render in quotes. Make them clearly different: [STYLE 1], [STYLE 2], [STYLE 3]. Add a note on what to change if the first result is too busy.
I want quick draft clips with grok-imagine-video-1.5-lite before using the full model. My business is [BUSINESS]. Brainstorm ten draft clip ideas, each with the shot, the camera move and one line of what it should communicate. Mark the three best to test first and what I would look for before spending more.
Here are [NUMBER] support messages: [PASTE]. Group them into themes, count each theme, and tell me which two themes are costing us the most goodwill. For each, suggest one fix we could ship this week and one longer term fix. Quote a short phrase from the messages as evidence, and flag anything that looks like a one off.
Write a [LANGUAGE] script that reads [FILE].csv and reports rows with missing values, duplicate IDs in the column [ID COLUMN], and dates in the wrong format. It must only read the file and print a report to the screen, never change or delete anything. Explain each part in plain words and show a tiny test file I can try it on.
Plan my Monday. Fixed commitments: [MEETINGS]. Must do: [TASKS]. Energy pattern: [HIGH AND LOW TIMES]. Return an hour by hour plan with two deep work blocks, a buffer for surprises, a 15 minute shutdown at the end, and the one task I can drop if the day goes wrong. Keep it realistic.
I connected apps in Gemini through Customize ([APP 1], [APP 2], [APP 3]). Look at my day for [DATE] and prepare me: list meetings with a one line prep note each, flag clashes, find the best 90 minute focus block, and list emails that need a reply today. Do not send, accept or change anything. Tell me which app each fact came from.
Help me create a Gemini Skill that writes my weekly update. My update normally includes: [SECTIONS]. My tone is [TONE]. Write the skill instructions, the questions it should ask me each week, and a sample output using made up details. Then tell me what to test before I rely on it. Gems are being replaced by skills, so keep it in skill form.
(Gemini 4 Argon is available to Google AI Pro and Ultra subscribers.) I need to decide: [DECISION]. Options: [OPTIONS]. Constraints: [BUDGET, TIME, PEOPLE]. Use Gemini 4 Argon to reason through it step by step. Return: the criteria that matter most, a scored comparison, the biggest unknown for each option, and the cheapest test that would reduce that unknown.
I use the Gemini macOS app and want Antigravity to build a small tool: [TOOL DESCRIPTION]. Before it starts, write the brief: what it should do, what it must not do (no deleting files, no network calls to unknown sites), the test steps to prove it works, and what to show me at review time. Keep the scope small enough for one session.
Research [NEW RULE OR TREND] and how it affects [TYPE OF BUSINESS]. Return a one page brief: what changed and when, who it applies to, what we must do, and what is still unclear. Cite the source for every fact and prefer official pages. Mark anything you could not confirm so I can check it myself.
Write three short emails asking a happy customer for a review of [PRODUCT OR SERVICE]: one right after delivery, one a week later, and a last gentle nudge. Each under 90 words, with a clear single link placeholder [REVIEW LINK], and no pressure or incentives that break platform rules. Add a subject line for each.
Rewrite this policy for busy staff: [PASTE POLICY]. Put the rule in one sentence at the top, then who it applies to, what to do, what not to do, and who to ask. Use short lines and plain words. Keep the legal meaning the same and list any sentence you changed in a way that could alter the meaning.
My business is [BUSINESS], with [TEAM SIZE] people and a budget of [BUDGET]. Brainstorm eight customer event ideas for [MONTH] that use things we already have (space, skills, customers, stock). For each: the idea, effort in hours, cost, how to promote it, and one way to measure success. Rank by effort versus likely benefit.
Our website enquiries fell from [OLD NUMBER] to [NEW NUMBER] per week since [DATE]. Things that changed: [CHANGES]. Give me a ranked list of possible causes, the quickest way to check each (what to look at in analytics or the site), and what would prove it is not that cause. Do not assume anything I did not tell you.
Turn these notes into a task list: [NOTES]. For each task give an owner, a due date (use [DEFAULT DUE RULE] if none was said), and a one line definition of done. Flag anything with no clear owner, and list decisions made separately from tasks. Return it as a table I can paste into a spreadsheet.
I manage Codex for a small team. Help me plan managed network constraints under [permissions.network] in config.toml. First read our current config and docs and explain in plain words what each option does. Then propose the narrowest rules that still let us work: [ALLOWED SITES]. Make no edits yet. Return a plan, the exact lines you would add, and how to test they block everything else.
I will use Codex CLI and expand patch details during approval prompts. Task: [TASK]. Work in small steps: show a plan, then make one small patch at a time, and explain each patch in two sentences before I approve it. Run the tests after each patch. Do not touch secrets, delete data or push anything. Stop and ask if a change spreads past [FILES OR FOLDER].
Bug report: [DESCRIPTION]. First write a failing test that reproduces it in [TEST FILE] and run it to show it fails for the right reason. Then make the smallest fix, rerun the tests and show the diff. Do not change unrelated files or skip any test. Summarise what you changed and what you verified.
I have markdown notes in [FOLDER] named by date. Write a small script that reads notes from the last 7 days and prints a summary with headings, open tasks (lines starting with '- [ ]') and the date of each note. It must only read files and print the result. Add a short README with usage, plus one test using sample notes.
Find places in [FOLDER] where the same logic for [BEHAVIOUR] is copied. List them first and wait for my approval. Then create one shared helper, switch each call site in a separate small commit, and run the tests after each switch. Keep behaviour identical, do not rename public functions, and report anything that differs between the copies.
The build for [PROJECT] takes [TIME]. Measure first, change nothing: run the build with timing, list the five slowest steps, and suggest one low risk improvement for each. Then ask which one I want and implement only that one on a new branch, with before and after timings. No dependency upgrades and no deleting caches I did not name.
Find the user facing error messages in [FOLDER]. List them in a table with file, current text and a proposed plain English replacement that says what happened and what to do next. Wait for my approval, then update the strings only, keep any error codes, run the tests and show the diff. Do not change logic.
Add a [--FLAG-NAME] option to [COMMAND] in [FILE] that [BEHAVIOUR]. Default behaviour must stay the same. Plan first, then implement in the smallest diff, add tests for both with and without the flag, update the help text and README, and run the full test suite. Report any test you could not run.
Write a script that cleans [FILE] (trim spaces, fix date formats to [FORMAT], remove exact duplicate rows) and writes the result to a new file named [FILE]_clean. The original must never be changed. Print a summary of how many rows were changed. Add a dry run mode that only reports, and tests using a small sample file.
Scan [FOLDER] read only for hard coded URLs, timeouts, limits and names that should be settings. List each with file, line and a suggested setting name. Do not edit anything. Then propose a plan to move the top five into one config file with safe defaults, and the tests that would prove nothing changed.
claude-fable-5-2 is now the default Fable model, and /model claude-fable-5-1 switches back. For the task [TASK], run the same plan on both models: first with claude-fable-5-2, then after /model claude-fable-5-1. Compare the plans and the diffs for correctness and size, and recommend which to use for [TYPE OF WORK]. Make no commits.
We use Claude Code on Vertex and fast mode is available in the global, us and eu regions (it falls back to standard speed if Vertex refuses it). Fix [BUG] with the smallest diff: plan first, edit, run [TEST COMMAND]. If fast mode falls back, tell me and continue at standard speed. Do not touch secrets or push.
Help me add a deniedMcpServers entry to our Claude Code settings to block [SERVER URL OR NAME]. Read our current settings, explain how URL entries match (including Anthropic provided servers), show the exact change as a diff, and tell me how to confirm it is blocked. Do not edit any file until I approve.
Our machine must not fetch feature flags. Explain what CLAUDE_CODE_DISABLE_FEATURE_FLAGS does and how it differs from turning off telemetry. Show how to set it for [SHELL OR SERVICE], how to confirm it is active, and the one thing that might behave differently. Make no changes until I approve the plan.
I want to use claude remote-control --settings [FILE] so every session it starts uses the same settings. Review [FILE] before I run it: list each setting, flag anything risky (broad permissions, bypass modes), and suggest the safest version. Return the reviewed file as a diff and the exact command to run. Do not start anything.
Use a forked subagent to find unused exports in [FOLDER]. It should only read code, list each export with file and why you think it is unused, and mark anything used through dynamic imports or tests as uncertain. Do not delete anything. Report back with a table and a plan for removing the safe ones in small commits.
Before I refactor [FUNCTION] in [FILE], write characterization tests that lock in what it does today, including odd edge cases. Run them and show they pass on the unchanged code. Then propose a refactor plan in small steps, wait for my approval, and rerun the tests after each step. Do not change behaviour.
Read the repo and rewrite README.md for a new teammate. Include what the project does, how to run it in under five commands (verify each by running it or say you could not), folder map, how to run tests, and common errors. Keep the existing sections that are still correct. Show the diff and list anything you could not verify.
Review [SCRIPT] and make it safe to run twice. Identify steps that are not idempotent (appending, creating duplicates, overwriting), propose fixes, and add a dry run mode and clear logging. Show the plan first. Implement in a small diff, test it by running it twice on sample data, and confirm the second run changes nothing.
Search the repo read only for TODO and FIXME comments. Group them by area, estimate effort (small, medium, large) and risk, and write a prioritized backlog in BACKLOG.md with file and line for each. Do not change any source file. Flag TODOs that look outdated, and ask me before deleting any comment.
ChatGPT Images 2.6: make a looping GIF from my uploaded sketch of [MASCOT]. The mascot waves hello twice, then pauses, then loops smoothly. Flat vector look, soft [COLOUR] background, thick clean outlines, no text, no logos. Keep the character's outfit and proportions the same in every frame. Ask for a slower playback speed if the wave feels rushed.
Using my saved reference image @[PRODUCT NAME] in ChatGPT, create a product photo for [SEASON]. Place the product on [SURFACE] with [SEASONAL PROPS], soft window light from the left, shallow depth of field, calm and clean mood. Keep the product's shape, colour and label exactly as in the reference. No added text. Aspect ratio [ASPECT RATIO].
Flat, friendly illustration of a small [TYPE OF SHOP] storefront at morning: open sign in the window, [PRODUCT] displayed outside, a customer walking in. Palette: [COLOUR 1], [COLOUR 2], warm cream background. Clean shapes, no tiny details, readable at thumbnail size. Render the shop name '[SHOP NAME]' on the sign in clear lettering. Aspect ratio [ASPECT RATIO].
Using Nano Banana Pro with my three reference photos of [PERSON A], [PERSON B] and [PERSON C] (people who gave permission), create a candid team scene around a table with coffee and laptops in a bright office. Keep each person's face and hairstyle faithful to their photo. Natural daylight, 35mm look, relaxed expressions. No logos and no text. Aspect ratio [ASPECT RATIO].
Use Nano Banana 2 Lite for quick drafts. Create four rough concept images for a [PRODUCT OR SPACE] in four moods: [MOOD 1], [MOOD 2], [MOOD 3], [MOOD 4]. Same composition each time: centred subject, simple background, soft light. Keep detail low, since these are drafts. After I choose one, I will ask for a refined version in a follow up message.
Edit my uploaded photo of a cluttered desk using Nano Banana 2. Step one: remove loose cables and paper piles but keep the laptop, plant and mug. Step two: warm the lighting slightly. Step three: straighten the horizon line. Do not change the laptop screen content or add any text. After each step, wait for my next instruction.
Create a packaging mockup for [PRODUCT]: a [BOX / BAG / BOTTLE] on a pale [COLOUR] surface, soft studio light, subtle shadow. Use the uploaded reference for the label colours and layout. Front text reads '[PRODUCT NAME]' in a clean sans serif. Sharp edges, realistic material texture, no extra logos. Output size [WIDTH] by [HEIGHT].
Editorial photo of a [ROOM TYPE] in [STYLE]: palette limited to [COLOUR 1], [COLOUR 2] and [COLOUR 3] (use hex codes if you can: [HEX 1], [HEX 2], [HEX 3]). Wide angle, natural window light, one plant, clean surfaces, lived in but tidy. No people, no text. Calm, believable and ready for a website header.
Soft watercolor illustration of a person reading by a window on a quiet morning, steam from a cup, warm light, loose brushwork, lots of calm empty space on the right for a headline. Muted palette of [COLOUR 1] and [COLOUR 2]. No text, no faces in detail. Use the aspect ratio [ASPECT RATIO] and keep the style consistent for a blog series.
Retro travel poster style illustration for [EVENT] in [PLACE]: bold flat shapes, limited palette of [COLOUR 1], [COLOUR 2], [COLOUR 3], strong sun and horizon, simple lettering at the top reading '[EVENT NAME]'. Print poster feel, textured paper grain. Keep the layout simple with space for date and venue added later. No real brands.
Veo 3.1 shot: close up of [PRODUCT] on a wooden table, hands enter frame and pick it up, slow push in, soft morning light from a window. Native audio: gentle room tone and the quiet sound of the product being lifted. Calm, tidy mood, no text, no logos. Duration [DURATION], aspect ratio [ASPECT RATIO], resolution [RESOLUTION].
Veo 3.1: inside a small [TYPE OF SHOP], a customer asks, 'Do you have this in blue?' The owner smiles and answers, 'Let me check the back.' Medium two shot, steady camera, then a slow push in on the owner. Warm light, shop ambience and soft footsteps as native audio. Original people, no brand names. Duration [DURATION], aspect ratio [ASPECT RATIO].
Veo 3.1 establishing shot of a coworking space at opening time: door unlocking, lights turning on one bank at a time, a barista setting out cups, early sunlight across empty desks. Slow dolly forward through the room. Native audio: keys, soft hum of lights, a distant kettle. No text or logos. Duration [DURATION], aspect ratio [ASPECT RATIO].
Use grok-imagine-video-1.5 image to video with my product photo of [PRODUCT]. Animate: the product rotates slowly on a [COLOUR] surface, soft light sweeps across it, tiny dust motes drift in the air. Keep the product's shape, label and colour unchanged. No added text. Duration [DURATION], aspect ratio [ASPECT RATIO]. Give me a one line note on what to change if the motion looks too fast.
Draft with grok-imagine-video-1.5-lite before the full model: overhead shot of hands chopping [INGREDIENT] on a board, then sliding it into a pan, steam rising. Steady camera, warm kitchen light, sizzle sound if the model supports audio. Duration [DURATION], aspect ratio [ASPECT RATIO]. If it works, I will rerun the same prompt on grok-imagine-video-1.5 for the final.
Grok Imagine video: slow looping abstract background of soft [COLOUR] shapes drifting and blending, subtle depth, gentle motion that works behind text. Start and end frames match for a seamless loop. No faces, no text, no logos. Calm mood. Duration [DURATION], aspect ratio [ASPECT RATIO].
Kling: macro slow motion of a barista pouring milk into a latte, the pattern forming into a leaf, steam curling in side light. Camera starts wide and glides to a close top-down view. Warm, cosy mood, shallow depth of field, realistic fluid motion. No text, no logos. Duration [DURATION], aspect ratio [ASPECT RATIO].
Kling: smooth forward tracking shot through a tidy warehouse aisle, shelves of labelled boxes on both sides, a worker scanning a parcel in the distance, soft overhead light. Steady camera speed, clean realistic look, no readable brand names. Duration [DURATION], aspect ratio [ASPECT RATIO].
Runway: animate my uploaded landscape photo of [PLACE]. Gentle cloud drift, light movement in the grass, slow push in. Keep the scene's colour and composition exactly as in the photo and avoid adding people or objects. Quiet, steady, suitable behind text. Duration [DURATION], aspect ratio [ASPECT RATIO].
Runway: from my uploaded flat lay photo of [ITEMS], create a slow orbit around the arrangement, items stay still while soft light shifts across the surface. Keep every item's shape and colour true to the photo. Clean, minimal, no text. Duration [DURATION], aspect ratio [ASPECT RATIO].
I use ChatGPT Work with GPT-6.1 Terra selected from the model list (rolling out on Plus, Pro, Business, Enterprise and Edu, depending on your plan and region). Plan my next week of client work. My clients and deadlines: [CLIENTS AND DEADLINES]. My fixed commitments: [MEETINGS AND BLOCKED TIME]. My daily working hours: [HOURS]. Return a day by day table with columns: Day, Task, Client, Time needed, Priority (High, Medium, Low). Then list the three tasks most at risk of slipping and one way to protect each. Ask me up to three questions first if anything is unclear.
Use ChatGPT Slides (rolling out to eligible Pro, Business and Enterprise users with Space access) to create a presentation from the notes below. Audience: [CLIENT NAME AND ROLE]. Goal of the deck: [GOAL, e.g. approve the next phase]. Notes: [PASTE NOTES]. Create 8 slides: title, where we are, what we finished, what is next, risks, decisions needed, timeline, and next steps. Keep each slide to a short heading plus at most 4 bullets. Suggest one chart where numbers would help. After the deck, give me 3 speaker note lines for each slide in plain English.
I have connected the iCloud Mail and Calendar plugins in ChatGPT. Look through my inbox from the last [NUMBER] days and find emails that need a reply from me. Group them as: Urgent today, This week, Can wait, and Just FYI. For each one in the first two groups give: sender, one line summary, what they want from me, and a suggested reply length. Do not send anything or change my calendar. Finish with a short list of any events mentioned in those emails that I should check against my calendar.
Our team disagrees about priorities: [DESCRIBE THE DISAGREEMENT]. Positions: [PERSON OR ROLE A WANTS X], [PERSON OR ROLE B WANTS Y]. Constraints: [TIME, BUDGET, PEOPLE]. Without taking sides, restate each position fairly, find what both sides care about, list 3 options (including a compromise) with pros and cons, and suggest a short agenda for a 30 minute meeting to decide. Include two neutral questions I can ask to move things forward.
Rewrite the policy below as a plain English explainer for [AUDIENCE, e.g. new hires]. Keep every rule accurate and do not add rules that are not in the text. Policy: [PASTE POLICY]. Return: a two sentence summary, a short list of what people must do, what people must not do, three common questions with answers, and who to contact: [CONTACT ROLE]. Reading level: about age 14. Mark any part of the policy that is unclear so I can check it with [OWNER].
Help me compare three suppliers for [PRODUCT OR SERVICE]: [SUPPLIER A], [SUPPLIER B], [SUPPLIER C]. My must haves: [MUST HAVES]. My budget: [BUDGET]. Search the web for each supplier's current pricing, terms and reviews, and give me the source link for every claim. Return a comparison table, a short note on what you could not confirm, and a recommendation with the two biggest risks of that choice. Do not guess prices; write 'not found' instead.
I run [BUSINESS TYPE] with about [NUMBER] regular customers. Budget per customer: [BUDGET]. Brainstorm 20 ways to thank loyal customers that feel personal, not like a discount. Group them by effort (5 minutes, an hour, a day). For the top 5, give a short example message I could send and one way to see if it worked. Avoid anything that needs personal data I do not already have.
Using ChatGPT Images 2.6 GIF creation (rolling out in ChatGPT), I want a short looping GIF for my launch of [PRODUCT]. Audience: [AUDIENCE]. Mood: [MOOD]. First give me 3 loop concepts, each with a one sentence description of the motion and what stays still. I will choose one. Then write the exact request to send to make that GIF, including style, colours [BRAND COLOURS], background and any short text. Keep the loop simple so it plays smoothly and add a plain alt text line for accessibility.
My spreadsheet in [EXCEL OR GOOGLE SHEETS] shows wrong totals. Here is what it should do: [EXPECTED RESULT]. Here is what happens: [ACTUAL RESULT]. The formulas involved: [PASTE FORMULAS]. A few sample rows: [PASTE SAMPLE ROWS WITHOUT PRIVATE DATA]. Walk me through the most likely causes in order, such as numbers stored as text, hidden rows, mixed ranges or rounding. For each cause give a quick check I can do in under a minute and the fix. End with a corrected formula.
Help me prepare for a conversation about [SALARY OR RATE INCREASE]. My role: [ROLE]. My results in the last [PERIOD]: [ACHIEVEMENTS WITH NUMBERS]. What I want: [TARGET]. What I would accept: [MINIMUM]. Build a one page plan: my three strongest points with proof, five likely objections with calm replies, a short opening line, and a fallback offer if the answer is no. Keep the tone confident and kind. Do not invent facts about my company or the market; ask me for anything missing.
I am using Claude Sonnet 5.5. Run a weekly review with me. First ask me five short questions about what went well, what stalled, what I learned, what drained my energy and what I must not forget. Wait for my answers. Then return: a three line summary of the week, the top three priorities for next week with a first step for each, one habit to stop and one to keep, and a short list of things to hand off or drop. Use plain language and no more than 250 words.
I used Claude Meetings (beta for Team and Enterprise plans) to take notes in a Google Meet call. Using the notes below, write a follow up email to the attendees. Notes: [PASTE MEETING NOTES]. Attendees: [NAMES]. Include: a two line recap, decisions made, action items as a list with owner and due date, and open questions. If an owner or date is missing from the notes, write [TBC] rather than guessing. Tone: [TONE]. Keep it under 200 words and give me a subject line.
I am trying Claude Duet, a research preview app for Pro and Max plans where Claude works as a proactive agent. Help me decide what to hand to it first. My typical week: [DESCRIBE WEEK]. Tools I use: [TOOLS]. Things I never want done without my approval: [LIMITS]. List 8 tasks that suit a proactive agent, each with: what it would do, what I must approve first, how I would check its work, and a risk level. Then rank them and suggest a safe two week trial plan.
Rewrite the report below for busy executives at [COMPANY TYPE]. Keep all numbers exactly as given and do not add claims. Report: [PASTE REPORT]. Return: a headline that states the main finding, a summary of 5 bullets, the three numbers that matter most with a plain meaning for each, one recommended decision, and a list of anything in the report that looks inconsistent or unsupported. Aim for one page, about 300 words.
Below are notes from [NUMBER] customer interviews about [TOPIC]. Find the main themes. Notes: [PASTE NOTES WITH NAMES REMOVED]. Return: the top 5 themes with a one sentence description, how many interviews mention each, two short quotes for each theme, and one surprising finding. Then list three questions I should ask in the next round. Only use what is in the notes; if something is unclear say so.
Write the FAQ page for my business, [BUSINESS NAME], which offers [SERVICES] to [CUSTOMERS]. Facts you may use: [PRICES, HOURS, LOCATION, POLICIES]. Do not add any facts that are not listed. Write 12 questions people really ask, each answered in 2 to 3 plain sentences, ordered from most to least common. Tone: [TONE]. Return the result as clean text with the question in bold. Flag any question where you need more details from me.
I need to talk to [ROLE, e.g. a coworker] about [ISSUE]. What happened: [FACTS]. What I want to change: [OUTCOME]. How I feel: [FEELINGS]. Help me plan. Give me an opening line, three points to cover in order, two questions to understand their side, how to respond if they get defensive, and a closing line that agrees next steps. Keep language calm and specific, with no blame. Offer to role play it with me afterwards.
Create a study plan for [CERTIFICATION NAME]. Exam date: [DATE]. Hours I can study per week: [HOURS]. My current level: [LEVEL]. Topics I find hard: [TOPICS]. Ask me to paste the official exam outline if I have it, and base the plan only on that outline. Return a week by week plan with topics, practice tasks and a short self test at the end of each week. Add two catch up days and a final week for review.
A customer sent this message: [PASTE MESSAGE]. The facts from our side: [WHAT HAPPENED]. What we can offer: [OFFER]. What we cannot do: [LIMITS]. Write a reply that acknowledges the problem, takes responsibility only where we are at fault, states what happens next and when, and keeps a calm, kind tone. Give me two versions: one short (under 100 words) and one fuller (about 180 words). Do not promise anything not listed above.
I am using Claude Haiku 5.5 for quick, low cost tasks. Clean up the list of notes below. Fix typos, merge duplicates, and label each item with one tag from this set: [TAGS]. Notes: [PASTE NOTES]. Return a table with columns: Cleaned note, Tag, Original line number. Do not change the meaning of any note. Put anything you cannot tag at the end under 'Needs review'.
Use Grok 4.7 to stress test my plan. Business idea: [IDEA]. Customer: [CUSTOMER]. How we make money: [REVENUE MODEL]. Costs: [COSTS]. Assumptions: [ASSUMPTIONS]. Act as a sharp but fair investor. List the 7 weakest points, ranked, each with why it matters, how to test it cheaply in under two weeks, and what result would change your mind. Then give a verdict in two sentences. Do not invent market data; if you cite a number, say where it came from.
I want a Grok Bot (available on SuperGrok, Cursor Pro and Cursor Teams plans) to help me chase late invoices. Write its instructions. It should read my list of unpaid invoices from [SOURCE], draft a friendly reminder for each one that is more than [DAYS] days late, and put the drafts in one list for me. It must never send anything, never change an invoice and never share client details outside the draft. Add a checklist for reviewing its first five drafts.
I want to share a Team Bot in Grok Bot so my whole team works from the same context. Our team does [WORK]. Write a brief for the bot with: who we are, who our customers are, our tone of voice [TONE], the files and apps it should use [FILES AND APPS], what good work looks like, and what it must ask a human about first. Return it as a clear document with short headings and under 400 words. End with 5 test requests I can try to see if the bot understood the brief.
Grok Build Mode (early beta for SuperGrok Heavy on grok.com, iOS and Android) can create interactive dashboards. I want one for [PURPOSE]. My data fields are: [FIELDS]. Sample rows: [SAMPLE ROWS, NO PRIVATE DATA]. Design the dashboard: the three most useful charts, a filter for [FILTER], one summary number at the top and a simple colour scheme. Write the exact request to give Build Mode, and list what I should check once it is built, such as wrong totals and mobile layout.
I use the Grok add-on for Google Workspace in Google Sheets. My sheet has columns: [COLUMNS]. Problems I see: [PROBLEMS, e.g. mixed date formats, duplicate emails, extra spaces]. Give me a step by step clean up plan that I can run in order: formulas or steps to trim spaces, standardise dates, flag duplicates in a new column and highlight blank required cells. Do not delete any rows; mark them instead so I can review. End with a short check that the row count is unchanged.
Research [COMPETITOR] using only public sources. Cover: who they sell to, their main message, pricing if public, recent announcements and what customers praise or complain about. Search the web and X for recent posts, and give a link for each claim. Return a table plus a short summary of where they look strong and where we can stand out: our product is [OUR PRODUCT]. Write 'not found' when you cannot confirm something.
Turn this idea into 5 short posts for X: [IDEA]. Audience: [AUDIENCE]. Voice: [VOICE]. Each post must stand on its own, under 270 characters, with a different angle: a bold opening, a story, a tip, a question, and a closing takeaway. No hashtags, no emoji, no hype words. After the posts, give me two alternative hooks for the first post and tell me which one you would pick and why.
Plan a [LENGTH] team offsite for [NUMBER] people from [TEAM TYPE]. Goals: [GOALS]. Budget: [BUDGET]. Location type: [LOCATION TYPE]. Return an agenda with times, session goals, who leads each (use roles), materials needed and a short energiser between sessions. Add a pre-work message for attendees and a one page follow up template for decisions and owners. Keep it realistic, with breaks.
Brainstorm 25 name ideas for [PRODUCT OR BUSINESS]. What it does: [DESCRIPTION]. Audience: [AUDIENCE]. Feel: [FEEL]. Avoid: [WORDS TO AVOID]. Group the names by style (descriptive, invented, playful, short). For your top 5 give a one line reason and a list of checks I must do myself: domain availability, trademark search in [COUNTRY], social handles, and how it sounds said aloud. Do not claim any name is free or safe to use.
Write a short thank you email to [INTERVIEWER NAME] after my interview for [ROLE] at [COMPANY]. Things we discussed: [TOPICS]. One thing I want to add or clarify: [POINT]. Why I am excited: [REASON]. Tone: warm and professional, under 120 words, no clichés. Give me a subject line and a second, even shorter version. Do not invent details about the interview.
I want to create a Skill in the Gemini app (available to users 18 and over, with wider access coming) that checks my writing against my style guide. My style rules: [STYLE RULES]. Write the Skill instructions: what to check, how to mark problems, what output to return (a list of issues with line, rule and a suggested fix) and what not to change, such as quotes and names. Keep it under 300 words and add a short sample text I can use to test it.
I am using Gemini 4 Argon (available to Google AI Pro and Ultra subscribers). I need a second opinion on this decision: [DECISION]. Options: [OPTIONS]. What matters most to me: [CRITERIA]. Constraints: [CONSTRAINTS]. Score each option against my criteria in a table, explain the scores in one line each, then say which assumption would change the answer most. List what I should find out before I decide. Be direct and do not simply agree with me.
Gemini now has a Customize option on web, mobile and desktop apps. Help me write my preferences so answers fit how I work. My job: [ROLE]. How I like answers: [LENGTH AND STYLE]. Words and habits to avoid: [AVOID]. Topics I often ask about: [TOPICS]. Return a short block I can paste in, written in the first person, under 120 words, plus 3 test questions that would show whether it works. Do not include private details such as addresses or account numbers.
I will upload a long document: [DOCUMENT TYPE, e.g. contract draft or research paper]. Read it all, then return: a five line summary, the key decisions or conclusions, numbers and dates as a table, risks or red flags, and open questions I should ask the author. Quote the page or section for each point so I can check it. If something is not in the document, say so instead of filling the gap. This is a summary only and not legal advice.
Help me write the [SECTION NAME] section of a funding application for [FUNDER]. My organisation: [ORGANISATION]. The project: [PROJECT]. The need: [NEED WITH EVIDENCE]. Word limit: [WORD LIMIT]. Criteria they score on: [CRITERIA]. Write a draft that answers each criterion in order, uses only the facts I gave, and uses [ADD EVIDENCE] where proof is missing. Then give me a checklist of what the reviewer will look for.
Brainstorm 10 activities for a lesson on [TOPIC] for [AGE GROUP], class size [NUMBER], lesson length [MINUTES] minutes. The class has mixed abilities. For each activity give: the goal, materials, steps, how to make it easier, how to stretch stronger learners, and a quick way to check understanding. Keep materials cheap and common. Mark the 3 best for a first lesson.
Create a monthly budget review for [HOUSEHOLD OR SMALL BUSINESS]. Income sources: [INCOME]. Main spending areas: [CATEGORIES]. Goals: [GOALS]. Give me a 20 minute step by step routine, a table template with columns: Category, Planned, Actual, Difference, Note, and five questions to ask myself each month. Do not give investment advice; just help me organise and notice patterns.
Write a public reply to this review of [BUSINESS NAME]: [PASTE REVIEW]. What actually happened according to our records: [FACTS]. What we will do: [ACTION]. Tone: calm, thankful and short. Do not argue, share private details or blame the customer. Return two versions under 80 words each, and one line inviting them to contact [CONTACT METHOD].
Turn these three articles into an outline for a newsletter issue for [AUDIENCE]: [LINKS OR PASTED SUMMARIES]. Return: a subject line with two alternatives, a short intro, one section per article with a takeaway in my voice [VOICE], a 'what to do this week' section and a closing line. Do not copy sentences from the articles; summarise in your own words and link each source. Keep it under 400 words.
Here is a Python script that fails: [PASTE SCRIPT]. The error message: [PASTE ERROR]. What I expected: [EXPECTED]. Explain in plain English what is going wrong, show the smallest fix as a diff, and explain why it works. Then list two other things in the script that could break later and how to guard against them. Do not rewrite the whole script and do not add libraries unless needed.
I am using Codex with GPT-6.1 Terra. Task: move our settings from [OLD FORMAT, e.g. JSON] to [NEW FORMAT] in [FILE PATH]. Read how the settings are loaded, write a plan, and wait for my approval. Then add the new loader while keeping the old format working as a fallback, add tests for both, and run [TEST COMMAND]. Do not touch real credentials or .env files, do not delete the old file and keep each change small.
Codex keeps failing to connect during [TASK]. Using Codex CLI 0.166.0 or newer, run `codex doctor --network-only` and read the output. Explain each problem in plain English, say which items are configuration, connectivity or WebSocket related, and propose the smallest fix for each. Do not edit config.toml until you show me the exact change and I approve it. Do not print or copy any tokens or keys that appear in the output; mask them.
Before we end this session, write HANDOFF.md at the project root so the next Codex session can continue. Include: the goal, what is finished, what is half done, files changed, commands to run the tests, decisions made and why, and the next three steps. Check each statement against the repository and mark anything unverified with [CHECK]. Do not include secrets, tokens or personal paths. Do not commit the file.
The call to [API OR FUNCTION] in [FILE PATH] feels slow. Add timing logs around it using the project's existing logging approach. Log duration, a request identifier and the outcome, but never request bodies, tokens or personal data. Add a test that checks the log line is written. Run [TEST COMMAND], show me the diff and suggest, without applying, two ideas to speed it up.
Open the agent command center with `codex agents --no-daemon` (Codex CLI 0.167.0 or newer) and review my recent tasks. List each task, whether it finished, failed or has unread results, and what I need to do next. Group them into: ready to merge, needs my review, blocked. For anything ready to merge, summarise the diff in three lines and note which tests ran. Do not merge, push or change any branch.
Find settings that are hardcoded in [FILE OR FOLDER], such as URLs, limits and file paths. List them first and wait for my choice. Then move the chosen ones into a config file at [CONFIG PATH] with clear names and sensible defaults, load it in one place, and keep behaviour identical. Add a test for the loader and run [TEST COMMAND]. Do not move secrets; leave them as environment variables.
Read this repository and write or update README.md so it matches what the code really does. Cover: what the project is, how to install it, how to run it, how to run tests, configuration options (read them from the code, do not guess), and a short project layout. Run the commands you document and fix the README if they fail. Do not change any code files and do not include secrets or personal paths.
The test [TEST NAME] fails sometimes. Run it [NUMBER] times with [TEST COMMAND] to confirm it is flaky and record how often it fails. Read the test and the code it uses and give me the most likely cause (timing, shared state, order, randomness). Propose a fix and wait for my approval. Then apply the smallest change, rerun the test [NUMBER] times and report the results. Do not skip or delete the test.
Add input checks to the form handler in [FILE PATH]. Fields: [FIELDS AND RULES]. First list what checks already exist. Then plan the changes, add the missing checks with clear error messages for users, and add tests for valid input, missing fields, wrong types and very long values. Run [TEST COMMAND]. Keep the diff small, do not change the database schema and do not log personal data.
Read the changes on branch [BRANCH] compared to [BASE BRANCH]. Write a pull request description with: what changed and why in plain English, a list of files grouped by purpose, how it was tested (run [TEST COMMAND] and report the result), risks, and what I should look at most closely. Point out anything that looks unrelated to the goal [GOAL]. Do not push or open the pull request; just give me the text.
Code Mode is an experimental, opt-in feature in Claude Code 2.1.323 or newer where Claude writes JavaScript to call its tools. Read the Code Mode page in the Claude Code docs, then explain in plain English what it changes and when it helps. Then, on this task: [TASK THAT CALLS MANY TOOLS], tell me how I would try it safely on a test branch, what to compare against a normal run (time, number of steps, correctness) and how to turn it off again. Do not change any settings until I say yes.
My MCP server [SERVER NAME] runs long tool calls as tasks. In Claude Code 2.1.319 or newer these move to the background and report when finished. Call the tool [TOOL NAME] with these inputs: [INPUTS]. While it runs, continue with [SIDE TASK, read only]. When the result arrives, summarise it in 5 bullets and list anything that failed. If I set CLAUDE_CODE_DISABLE_MCP_TASKS, explain how the behaviour would differ. Do not change any files.
Switch to Claude Fable 5.2 (claude-fable-5-2). Plan a migration of our tests from [OLD RUNNER] to [NEW RUNNER]. Read the config and a sample of tests, list differences that will break (setup, mocks, assertions) and propose an order of 5 or fewer small steps. Wait for my approval. Then do the first step on a new branch, run both runners and compare results. Do not remove the old runner until I say so.
Run `/claude-api latency-optimize` (Claude Code 2.1.319 or newer) on this project. It should find where our Claude API code makes people wait. Scope: [FILES OR FOLDER]. Before changing anything, list the slow spots it found and the settings it wants to try. Only try changes against our eval command [EVAL COMMAND], compare before and after, and keep each change in its own small commit. Do not commit if quality drops.
I run Claude Code on a long task where nobody is there to answer permission prompts. Explain the setting `permissions.denyInsteadOfPrompting` (Claude Code 2.1.319 or newer): what it does and how it affects subagents. Then look at my project settings and suggest the smallest settings.json change so denied calls do not stall the run, plus an allow list for only these safe commands: [SAFE COMMANDS]. Show the diff and wait for my approval.
I am about to install a plugin from [PLUGIN SOURCE]. Before installing, run `claude plugin validate --strict` on the plugin folder at [PATH] (Claude Code 2.1.323 or newer). Report any errors, check the `engines` field in plugin.json against my Claude Code version, and list every hook, command and permission the plugin asks for in plain English. Tell me if anything looks risky. Do not install it.
Read this repository's issue history and structure, then create .github/ISSUE_TEMPLATE/bug_report.md plus a short docs/triage.md. The template asks for: what happened, what was expected, steps to reproduce, version, and logs (with a reminder to remove secrets). The triage doc gives a checklist for severity, ownership and when to close as not reproducible. Base the wording on the project's real components. Show the files and do not commit.
Here is a failing CI log: [PASTE LOG, REMOVE SECRETS]. Find the first real error, not the noise after it. Explain the cause, find the code involved, and propose the smallest fix. Reproduce locally with [COMMAND] if possible. Apply the fix on a new branch named fix/[SHORT NAME], run the tests, and show me the diff. Do not push, force anything or change CI secrets.
Audit this project's dependencies. List packages that are outdated or flagged by [AUDIT COMMAND], grouped by risk: patch, minor, major. For each major upgrade, read its release notes and list breaking changes that affect our code. Propose an upgrade order in small steps with a test run after each. Write the plan to docs/upgrade-plan.md. Do not upgrade anything or edit lockfiles yet.
Read the folder [NOTES FOLDER] and the repository, then write docs/HANDOVER.md for the person taking over [PROJECT]. Include: what the project does, how to run it, where important code lives, open tasks, known bugs, decisions made and why, and who to ask about what (use roles only). Cite the file for every claim. Mark anything you could not confirm with [CHECK]. Do not include secrets or personal data.
Using ChatGPT Images 2.6: a handmade ceramic mug in [COLOUR] with a small steam trail, on a light oak kitchen table, soft morning window light from the left, shallow depth of field, a folded linen cloth and a few coffee beans nearby. Square crop, clean negative space on the right for text. Style: warm, natural, editorial product photo. No text, no logos, no hands.
In ChatGPT, use my saved reference image @[NAME] (saved reference images are available in ChatGPT Images 2.6). Create a friendly flat illustration of the same character as a barista behind a counter, keeping the outfit and hairstyle exactly the same as the reference. Then, in the same chat, change only the background to a rainy street window view. Style: simple vector look with soft shadows, colour palette [PALETTE]. No text.
Using GIF creation in ChatGPT Images 2.6: a friendly round character giving a thumbs up with a small bounce, the loop repeats smoothly. Flat colours from [PALETTE], thick simple outline, plain [BACKGROUND] background so it works in chat apps. No text, no sparkles. Keep it short and simple, with playback speed [SPEED].
Create a vertical infographic poster titled '[TITLE]' for [AUDIENCE]. Three sections with large clear headings: '[HEADING 1]', '[HEADING 2]', '[HEADING 3]', each with one short line of text and a simple flat icon. Layout: top title, three stacked sections, small footer text '[FOOTER]'. Style: clean, modern, [COLOUR PALETTE], plenty of spacing. All text must be spelled exactly as written and easy to read. Model: Nano Banana 2.1.
I am attaching [NUMBER] reference images (Nano Banana 2.1 accepts up to 14 reference images in total). Combine their colour palette, materials and mood into a single moodboard for [PROJECT], arranged as a neat grid with small gaps. Keep the products and objects recognisable from the references. Style: calm, editorial, soft natural light. Aspect ratio 16:9. No text or logos.
Edit the attached photo of [SUBJECT]. Keep the subject, their pose, clothing and lighting exactly the same. Replace only the background with [NEW BACKGROUND], matching the light direction and colour temperature so it looks natural. Keep edges clean around hair and fine details. Do not add text, objects or extra people. Output at the same aspect ratio as the original.
A square social media tile for [BRAND]. Large bold headline text reading '[HEADLINE]' centred, in a thick rounded sans serif font, [TEXT COLOUR] on a solid [BACKGROUND COLOUR] background. Small supporting line '[SUBLINE]' below it. A simple flat illustration of [OBJECT] in the bottom corner. Minimal, high contrast, lots of margin. Make sure the text is spelled exactly as written.
Cinematic street photograph at dusk in the rain, a quiet [CITY TYPE] street with shop signs reflected in wet pavement, a lone figure with an umbrella walking away, steam from a grate, teal and amber colour palette, 50mm lens look, shallow depth of field, soft grain. Aspect ratio [ASPECT RATIO]. No readable text, no logos, no watermark.
A clean studio render of a [PRODUCT, e.g. skincare bottle] on a pale grey seamless background, soft diffused lighting from above, subtle reflection on the surface, centred composition with room around the product. The label reads '[BRAND NAME]' in a simple sans serif font and '[PRODUCT NAME]' below it. Realistic materials, sharp focus, neutral colours with one accent colour [ACCENT]. Model: FLUX 3 Image Klein.
Using Imagine Image 2.0 in Grok: an editorial illustration for a blog post about [TOPIC]. Central subject: [SUBJECT]. Style: flat shapes with a textured paper feel, limited palette of [PALETTE], gentle depth with overlapping layers. Wide composition with empty space on the left for a title. No text, no logos, no real people.
Gemini Omni Flash: a cosy [TYPE] café in the early morning, steam rising from a cup in the foreground, a barista wiping the counter in the soft background, camera makes a slow push in on the cup. Warm window light, calm mood. Sound: quiet room tone, soft cup clinks and a gentle acoustic guitar. One voice says in a warm tone: '[LINE]'. Duration 8 seconds, aspect ratio 16:9, resolution 720p.
Gemini Omni Flash, image to video: use the attached photo of [PRODUCT] as the first frame. The product stays the same shape and colour. Camera slowly orbits left to right while soft light moves across the surface and tiny dust specks float in the air. Clean [BACKGROUND] background, premium minimal mood, soft ambient sound. Duration 6 seconds, aspect ratio 9:16 (portrait), resolution 1080p.
Gemini Omni Flash with reference images: I attach 3 images of one character (front, side and full body) and 1 image of the setting. Shot: the character walks into [SETTING] and looks up at [OBJECT], camera tracking from the side at walking pace, then a gentle push in on their face. Keep the face, hair and clothing the same as the references. Natural ambient sound, no dialogue. Duration 10 seconds, aspect ratio 16:9.
Imagine Video 1.5 with References in Grok: use my attached logo image and product image as references. Opening shot for a brand explainer: the product sits on a clean [COLOUR] surface, the camera slowly pulls back to reveal the logo behind it on the wall, soft studio lighting, subtle motion in the background. Keep the logo shapes and colours accurate. Calm confident mood. Duration [DURATION], aspect ratio [ASPECT RATIO], resolution up to 1080p.
Imagine Video 1.5 with References in Grok: I attach a voice reference clip that I own and a still image of the scene. Scene: a [SETTING] with warm light, a plant gently moving in the breeze, camera static with a very slow zoom. A narrator says in the reference voice: '[LINE]'. Keep the delivery friendly and slow. No music. Duration [DURATION], aspect ratio [ASPECT RATIO].
Grok Imagine video: close up of [DISH] on a rustic wooden table, sauce being poured over it in slow motion, steam rising, camera slowly tilting down from the garnish to the plate. Warm side lighting, shallow depth of field, rich colours. Sound of gentle pouring and a quiet kitchen. No people's faces, no text. Duration [DURATION], aspect ratio [ASPECT RATIO].
Kling, image to video from my attached photo of an empty [ROOM TYPE]: smooth slow dolly forward through the room, keeping the walls, windows and floor exactly as in the photo. Soft natural daylight, gentle drifting dust in the light beams, calm steady movement, no people, no added furniture, no text. Duration [DURATION], aspect ratio [ASPECT RATIO].
Kling, image to video from my first image of [BEFORE STATE]. If the Kling version I picked offers an end frame option, also use my last image of [AFTER STATE] (if it does not, skip it and describe the change in words). Create a smooth transition as if time passes, with soft light changes and a subtle camera push in. Keep the main subject in the same position. Natural, believable motion only, no text, no morphing faces. Duration [DURATION], aspect ratio [ASPECT RATIO].
Runway: a wide establishing shot of [LOCATION, e.g. a misty mountain lake] at sunrise, camera slowly rising from the water surface to reveal the peaks, mist drifting across the lake, birds crossing in the distance. Soft golden light, calm and awe inspiring mood, cinematic colour, natural motion. No text, no people. Duration [DURATION], aspect ratio [ASPECT RATIO].
Runway, image to video from my attached flat illustration of [SCENE]. Keep the art style, colours and shapes exactly as drawn. Add gentle looping motion only: clouds drifting, leaves swaying, small lights twinkling. The camera stays locked. No new objects, no text. Calm, cheerful mood. Duration [DURATION], aspect ratio [ASPECT RATIO].