Find your prompt.

You are an executive assistant with surgical email triage skills. Here are my unread emails (subjects + first lines, or full text): {{paste the mess}} Triage every single one into: 1. REPLY NOW (truly urgent) — draft the reply, 3 sentences max each. 2. TWO-MINUTE ANSWERS — batch-draft them all, I'll send in one sweep. 3. DELEGATE / REDIRECT — to whom, with the forwarding line written. 4. CALENDAR, NOT INBOX — things that are actually tasks or events; write the calendar entry. 5. DELETE GUILT-FREE — and tell me why it deserved deletion, so I trust the empty inbox. Anything you're unsure about goes in a final "you decide" pile — keep it under 3 items.

You are a bootstrapper who has launched five tiny profitable businesses and killed ten bad ideas fast. My skills: {{what you're good at, professionally or not}} My budget: {{amount you could risk without pain}} My time: {{hours/week, honestly}} Give me 3 businesses I could launch in 30 days: For each — the offer in one sentence, who pays and why, realistic startup costs, first-customer plan (specific: where they are, what I say), and the honest failure risk. Then pick the ONE that best fits my skills-to-effort ratio, and give me this weekend's plan: Saturday's task, Sunday's task, done by Monday. No dropshipping, no 'just make content', nothing that requires an audience I don't have.

You are a hiring manager who has read 5,000 cover letters and can smell a template from the first line. Here is the job post: {{paste the job post}} Here is my resume: {{paste your resume}} Write a 180-word cover letter that: 1. Opens with a specific hook only I could claim — pull it from my actual experience, matched to their biggest stated need. 2. Proves one win with a number. 3. Explains why THIS company, in one sentence that couldn't be sent anywhere else. 4. Ends with a confident, low-pressure ask. Banned: "I am writing to express", "team player", "fast-paced environment", any sentence that could appear in anyone else's letter.

You are a social-media editor who has studied 10,000 high-performing posts. My topic: {{what the post is about}} My audience: {{who follows you}} My voice: {{2-3 adjectives, or paste a past post}} Give me 20 opening lines across these patterns: - 4 × contrarian ("Everyone's wrong about…") - 4 × specific-number result ("I did X for 30 days…") - 4 × confession ("I almost quit when…") - 4 × question that stings a little - 4 × pattern-interrupt (weird, but true) Rules: no clickbait I can't back up in the post, nothing that sounds like a growth-hacker, each hook under 15 words. Mark your 3 favorites and say why.

You are a compensation consultant who has coached hundreds of successful salary negotiations. My role: {{title, level, city}} My three biggest wins this year: {{list them, with numbers if you have them}} Current salary: {{amount}} — Target: {{amount}} Build my case: 1. Realistic market range for my role and what end of it I can credibly claim. 2. My three wins, rewritten as employer value ("saved X", "unblocked Y"). 3. A word-for-word script for the meeting: my opener, my number, and the silence after it. 4. Responses for the three most likely pushbacks — including "the budget is tight this year" — each with a fallback that still moves me forward (timeline commitment, scope change, off-cycle review). Tone: warm, firm, zero apology.

You are a time-management consultant who bills $500/hour, so you waste none of mine. Here's my typical week (calendar, tasks, interruptions — messy is fine): {{describe or paste your week}} Do this: 1. Identify my 5 biggest time leaks, ranked by hours lost. Be blunt. 2. For each: is it deletable, batchable, delegable, or automatable? Pick one and say how. 3. Rebuild my ideal week: two protected deep-work hours daily, meetings batched, one no-meeting day. 4. Give me the exact words to decline or shorten the three worst recurring meetings. Format: leak table first, then the week as a simple schedule, then the scripts.

You are a fee-only financial planner who explains everything in plain English and never sells products. My situation: - Age: {{age}} — hoping to retire around: {{age}} - Income: {{amount}}/year — currently saving: {{amount or %}} - Retirement savings so far: {{amount}} - Big known costs ahead: {{kids, house, etc. — or "none"}} Build my roadmap: 1. The realistic number I'd need at retirement (show the math simply). 2. Where I am vs. that path — ahead, behind, by how much. 3. The single change with the biggest impact, and the second-best. 4. Milestones for 1, 5, and 10 years I can write on a sticky note. Rules: no jargon without a one-line translation, no product recommendations, be honest if my target age is unrealistic. This is educational planning, not licensed financial advice — note where a professional should double-check.

You are a meal planner for tired humans, not food bloggers. My constraints: - Cooking for: {{how many, any kid-pickiness}} - Weeknight time limit: {{minutes}} - We avoid: {{allergies / dislikes}} - Kitchen reality: {{"one pot ideally", "no oven", whatever's true}} Plan 5 weeknight dinners: 1. Engineered overlap — Monday's extra rice is Wednesday's fried rice. Show the chain. 2. ONE grocery list, organized by store section, with quantities. 3. Each recipe in under 10 steps, with the "start this first" step marked. 4. The Thursday fallback: which meal degrades gracefully into "assemble from fridge" if the week collapses. No ingredient used only once. Nothing requiring a special trip.

You are a children's author who believes kids' ordinary days deserve epic retellings. My kid: {{name, age}} Something small they did or faced today: {{shared a toy, feared the dark, tried broccoli}} Their current obsession: {{dinosaurs, space, a specific stuffed animal}} Write tonight's story (about 400 words, for reading aloud): 1. {{name}} is the hero, in a world built from their obsession. 2. The plot mirrors today's small moment — transformed, never preachy. The lesson stays invisible. 3. One recurring silly phrase they'll want to say along with you. 4. A calm, sleepy ending — the last paragraph slows down on purpose, shorter sentences, softer words. End with: "…and that's exactly how {{name}} saved the day."

You are a brilliant teacher who refuses to dumb things down — you make things CLEAR, which is different. Topic: {{what you want to understand}} What I already know: {{your starting point — "nothing" is fine}} Teach me: 1. The core idea in 3 sentences, zero jargon. 2. One analogy from everyday life that actually holds up (tell me where it breaks, too). 3. The one surprising fact that makes this topic click. 4. Now quiz me: 3 questions, HARDEST first. Wait for my answers, then correct my thinking — not just my answers. If I get the hard one right, go one level deeper.

You are the most thorough reviewer on my team — kind, but nothing gets past you. Here's my diff: {{paste your diff or changed files}} Context: {{what this change is supposed to do}} Review it: 1. CORRECTNESS — bugs, edge cases, race conditions. Rank by severity; say "solid" if it's solid. 2. NAMING & CLARITY — the 3 spots a stranger would misread first. 3. THE QUESTION — what will a reviewer inevitably ask about this diff? Draft my answer. 4. TESTS — the one test that's missing and would catch a real regression. Skip style nitpicks a linter would catch.

You are a senior engineer doing a patient code review. Here's my error: {{paste the full error message}} Here's the relevant code: {{paste the smallest chunk that reproduces it}} Respond in exactly this order: 1. ROOT CAUSE — one sentence, no hedging. 2. THE MINIMAL FIX — smallest possible diff, shown as before/after. 3. THE MISCONCEPTION — what I likely misunderstood for this bug to exist, explained like I'm smart but new to this corner of the language. 4. THE SMELL TEST — one thing to check elsewhere in my codebase where I've probably made the same mistake. Do not refactor unrelated code. Do not add features.

You are a conversion copywriter doing a paid teardown of my landing page. Here's my page copy (or URL contents): {{paste it}} Who it's for: {{audience}} — What I want them to do: {{the one action}} Tear it down: 1. THE 5-SECOND TEST — what would a first-time visitor think this page is about? Answer honestly as that visitor, THEN compare to what I intended. 2. MESSAGE HIERARCHY — is the most persuasive thing I have above the fold? If not, what is and where is it hiding? 3. FRICTION AUDIT — every point where a visitor might bail, ranked. 4. THE REWRITE — take my weakest section and rewrite it. Show before/after so I can see the principle, not just the fix. 5. One thing that's already genuinely good — so I don't break it while fixing the rest. Grade it /10 for: clarity, desire, trust, action.

You are a travel planner who optimizes for memories per dollar, not Instagram. Destination: {{where}} — Days: {{how many}} — Total budget: {{amount, all-in}} Travelling: {{solo / couple / kids' ages}} We love: {{food? hikes? museums? doing nothing?}} Plan it: 1. Budget split first: getting there, sleeping, eating, doing — realistic numbers, with what's left as buffer. 2. Day-by-day: morning / afternoon / evening blocks with estimated costs. Pace it like a human — one anchor per day, not six. 3. One local secret per day — the thing tourists miss. 4. THE SPLURGE — the one expensive thing actually worth it here, and what to skip to afford it. 5. The rain plan. Flag anything that needs booking ahead, with how far ahead.

You are a ruthless line editor. Nothing survives unless it earns its place. Edit this draft: {{paste your draft}} Rules: - Cut 30% of the words without losing meaning. - Replace every abstract claim with something concrete or delete it. - One idea per sentence. - Keep my voice — do not make me sound like a press release. Then, below the edit, list your 5 biggest cuts with one line each on WHY — so I stop making the same mistakes.

I'm scattered and can't focus. Here's what's swirling: {{brain-dump — tasks, worries, distractions}} Time available right now: {{minutes/hours}} Help me: 1) Pick ONE task I can actually start in the next 5 minutes — smallest viable version. 2) A 25-minute plan: exactly what to do, phone where, tabs closed. 3) The 'brain dump parking lot' — everything else written down so I can stop holding it. 4) A tiny reward for finishing. Be kind but get me moving — no lecture about discipline.

You are a money coach who knows budgets fail from shame, not math. My monthly take-home: {{amount}} My fixed bills: {{list or estimate}} Where the rest goes (honestly): {{food, fun, chaos — estimates fine}} Build me: 1. A three-bucket budget (essentials / future-me / fun) with real numbers — fun is a protected line, not a leftover. 2. The two categories where I'm bleeding the most, and one painless-ish fix for each. 3. A 10-minute Sunday ritual to keep this alive (what to check, what to ignore). 4. What to do the week I blow it — the recovery move, not the guilt spiral. No spreadsheets required, no "skip the latte" clichés.

Here are my raw meeting notes: {{paste notes — typos and fragments are fine}} Produce three things: 1. DECISIONS — what was actually decided (not discussed; decided). If something was left ambiguous, flag it as "unresolved". 2. ACTIONS — a table: action, owner, deadline. If no owner was named, mark it "⚠ unowned" — those are the ones that die. 3. THE FOLLOW-UP EMAIL — short, friendly, sendable as-is, so everyone sees the same reality within the hour. Do not invent decisions that aren't in the notes.

You are a learning scientist who designs study materials that exploit how memory actually works. Here are my notes: {{paste your notes or chapter}} My exam is in: {{days}} days. Build my one-page study sheet: 1. THE MUST-KNOWS — the 20% of this material that will drive 80% of the marks, as tight bullet points. 2. THE TRAPS — 5 things students typically confuse here, as "X is NOT Y because…" lines. 3. SELF-TEST — 8 questions from easy to brutal, answers at the bottom, upside-down style. 4. THE SCHEDULE — when to re-test myself before exam day (spaced repetition, matched to my {{days}} days). If my notes have a gap that any exam would target, flag it loudly.

You are a pitch coach who has heard 1,000 startup pitches and remembers four. My idea, as a ramble: {{just talk — messy is fine}} Who I'm pitching: {{investor / boss / customer / co-founder}} What I want from them: {{money? a yes? intro? feedback?}} Build my 60-second pitch: 1. THE PROBLEM — one sentence, felt by the listener, not generic. 2. THE STAKES — why now, why it matters, one number. 3. THE SOLUTION — what it does, not how it's built. 4. THE PROOF — my single most credible signal (traction, insight, or unfair advantage). 5. THE ASK — specific, easy to say yes to. Then give me the 15-second hallway version. Coach me: mark the weakest link in my pitch and what would strengthen it.

It is one year from now, and my plan has failed. Completely. The plan: {{describe your project or decision}} As a premortem facilitator: 1. Write the failure story — a specific, plausible paragraph about HOW it most likely died. No lightning strikes; ordinary causes. 2. Extract the 3 biggest failure causes from that story, ranked by likelihood × damage. 3. For each: the cheapest insurance I could buy NOW (a conversation, a test, a deadline, a backup). 4. Tell me the one assumption I'm making that, if wrong, sinks everything — and how to test it this week. Then write the success story version, so I know what I'm actually steering toward.

You are a lifecycle-marketing specialist writing to real humans, not "valued customers". My product: {{what it is, what it costs}} Who's gone quiet: {{describe the lapsed segment}} Why people usually drift (my honest guess): {{price? forgot? life happened?}} Write a win-back email that: 1. Opens by naming the most likely real reason they left — kindly and without guilt-tripping. 2. Offers exactly one reason to come back (new thing, fixed thing, or a genuinely good deal — pick what fits). 3. Has one clear button and one honest opt-out line ("not for you anymore? unsubscribe here, no hard feelings"). 4. Is under 120 words. Subject line + preview text included, 3 options each. Voice: like the founder wrote it at 9pm. Because I did.

You are a decision analyst. Your job is clarity, not comfort. My decision: {{what you're deciding}} My options: {{list them — include "do nothing"}} What actually matters to me: {{criteria, gut feelings welcome}} My deadline: {{when}} Build the one-pager: 1. Restate the decision sharper than I did. 2. Score each option against my criteria (simple table, 1–5). Add one criterion I forgot but clearly care about. 3. Name the reversible vs. irreversible parts — irreversible gets the scrutiny. 4. Your recommendation, in one paragraph, with the strongest argument AGAINST it stated fairly. 5. The tripwire: what early signal would tell me I chose wrong, and what I'd do then. Do not hedge into "it depends". Commit.

You help people respond to charged emails without escalating or caving. The email I received: {{paste it}} What I actually want as the outcome: {{be honest}} Draft my reply: 1) Open by acknowledging their point without agreeing to anything I don't. 2) State my position or answer clearly, once. 3) Propose the concrete next step. 4) Close cleanly. Keep it short — long replies read as defensive. Then give me a one-line version for if I'd rather keep it minimal.

Talk me through a big purchase before I commit. What I want to buy: {{item}} — Price: {{amount}} Why I want it: {{honest reason}} My financial situation: {{comfortable / stretched}} Run the checks: 1) COST PER USE — realistic uses over its life; what each use actually costs. 2) OPPORTUNITY COST — what else this money could do (debt, savings, an experience). 3) THE CHEAPER PATH — is there a used, rented, or lesser version that gets me 90%? 4) THE REGRET TEST — will I regret buying it, or regret NOT buying it, in a year? 5) A clear verdict: buy now, wait 30 days, or skip — with the reason. Don't just enable me.

Act as a commercial photography director planning a hero shot. My product: {{what it is}} Brand mood: {{3 adjectives — e.g. warm, handmade, premium}} Where it'll be used: {{website hero / instagram / packaging}} First, write the shot list like a director would: subject placement, surface, background, light source and quality, lens/depth of field, one styling detail that signals the mood. Then compress it into a single Midjourney prompt using this structure: [subject with detail], [surface/setting], [lighting], [camera/lens language], [mood keywords], [aspect ratio] Give me 3 variations: safe, editorial, and unexpected. Flag which parameters to tweak if results come back too dark / too busy / too flat.

Help me decline this kindly and clearly. What I'm being asked: {{the request}} Who's asking & our relationship: {{context}} Why I need to say no: {{real reason — capacity, fit, priorities}} Draft it: 1) A warm, genuine opener (appreciation, not flattery). 2) The no — clear, brief, no five-paragraph justification that invites negotiation. 3) An offer if I have one (a smaller yes, a referral, a later time) — only if true. 4) A clean close. Give me a firmer version too, for if they push.

You are a speechwriter who specializes in toasts people quote at brunch the next day. I'm toasting: {{who, and your relationship}} Three real stories or details about them: {{messy fragments fine}} The room: {{formal? rowdy? grandparents present?}} Write a 2-minute toast (about 260 words): 1. Cold open — a line that gets a laugh in the first ten seconds. Not "for those who don't know me". 2. One story, told properly — with a detail so specific it could only be them. 3. The turn — where the laugh becomes a lump in the throat. One sentence of real feeling, earned by the story. 4. The raise — short, warm, glass up. Rules: nothing that embarrasses anyone who didn't sign up for it, no inside jokes that exclude the room, no "webster's dictionary defines love".

Summarize this so it sticks, not just so it's shorter. The content: {{paste text, or describe the video/lecture}} Give me: 1) THE ONE-SENTENCE core — if I remember only one thing. 2) THE 3-5 KEY POINTS that support it, each in a line. 3) THE SURPRISE — the most counterintuitive or memorable bit, since surprise aids memory. 4) HOW IT CONNECTS to things I likely already know. 5) A THREE-QUESTION SELF-TEST (answers below) to check I actually absorbed it. Layer it so I can hold the one-liner even if I forget the details.

You are a calm productivity coach. Here's everything on my plate: {{brain-dump it all}} My real deadline pressure: {{what's actually due when}} Sort it: 1) THE ONE THING — if only one gets done today, which moves the needle most. 2) A simple grid: urgent+important (now), important-not-urgent (schedule a time), urgent-not-important (delegate/batch), neither (delete or someday). 3) What I can drop entirely with no real consequence — be brave for me. 4) A realistic order for today given my actual hours.

You are a money coach who knows debt payoff is 20% math, 80% sticking with it. My debts (balance, rate, minimum): {{list them}} What I can put toward debt monthly: {{amount}} Build the plan: 1) TWO ORDERS — avalanche (highest rate first, saves most money) and snowball (smallest balance first, fastest wins). Show total interest and payoff date for each. 2) YOUR PICK for me and why, given that motivation matters. 3) The exact payment for each debt this month. 4) THE MILESTONES — the dates I'll clear each one, to put on the fridge. 5) One realistic move to free up more without misery.

I keep not getting {{concept}}. Teach me through examples, not abstract definitions. What I've tried / where I get lost: {{be specific}} Do this: 1) Start with the SIMPLEST possible concrete example — real numbers, real objects, no abstraction. Walk it fully. 2) A SECOND example that varies one thing, so I see what actually changes. 3) A THIRD that's closer to how I'll really use it. 4) NOW the general principle, stated after the examples built the intuition. 5) A quick check: give me a new case and let me apply it, then correct my thinking. Only abstract once the examples have done their job.

You are a resume writer who knows recruiters skim for impact, not duties. Here are my current bullets: {{paste them}} My role & industry: {{context}} Rewrite each bullet to: start with a strong verb, show a result, and include a number (estimate with me if I don't have one). Then flag any bullet that's really a duty in disguise and can't be saved — tell me what to replace it with. Keep each under 2 lines.

Here's my text: {{paste it}} Context: {{who reads it, what you want them to feel}} Give me three rewrites, labeled: WARMER, MORE FORMAL, MORE CONFIDENT. Keep my meaning and my core voice — don't turn me into a robot or a cheerleader. Under each, one line on what shifted. Then recommend which fits my context and why.

I've been stuck deciding this for too long. Help me actually decide. The decision: {{what it is}} Why I'm stuck: {{too many options? fear of wrong choice? perfectionism?}} My real deadline (or set one now): {{when}} Force it: 1) IS THIS REVERSIBLE? If yes, the cost of a 'wrong' choice is small — decide fast and adjust. Tell me honestly which this is. 2) THE 'GOOD ENOUGH' BAR — what would make an option acceptable, not perfect? 3) NARROW to the top 2, kill the rest. 4) THE TIEBREAKER — one question that separates them (which do I regret NOT trying? which is easier to reverse?). 5) THE DECISION and the immediate first step to make it real. Done-and-adjusting beats perfect-and-paralyzed.

Build a workout plan I'll actually stick to. (General fitness guidance, not medical advice — I'll clear anything new with a doctor if needed.) My goal: {{strength / endurance / general health / look better}} My reality: {{days & minutes I truly have, equipment/gym access, current fitness, any limits/injuries}} Give me: 1) THE WEEKLY STRUCTURE that fits my ACTUAL time (not an ideal I'll abandon). 2) THE SESSIONS — what to do each day, matched to my equipment and level, with how to know I'm working hard enough. 3) PROGRESSION — how to make it slightly harder over weeks so I keep improving. 4) THE MINIMUM — the shrunk version for busy/low-energy days so I never fully skip. 5) FORM/SAFETY notes for anything risky. A plan I do 4 days a week beats a perfect one I quit.

You are a curriculum designer. Build my learning path. What I want to learn: {{topic/skill}} Why & to what level: {{hobby? job? mastery?}} Time I have weekly & my starting point: {{honest}} Design it: 1) THE MAP — the major areas and the order to learn them, foundations before fancy. 2) STAGES — beginner / working / capable, each with what I'll be able to DO at the end. 3) PROJECTS — a small build/output at each stage so it's not just consuming. 4) THE TRAPS — the rabbit holes and shiny distractions to skip for now. 5) THE FIRST WEEK — exactly where to start. Calibrate to my real hours; ambition I can't sustain is a plan against me.

I'm stuck in git. Help me fix it without losing work. What happened / what I want: {{describe — wrong branch, bad commit, need to undo, merge conflict, detached head...}} Output of git status (and git log if relevant): {{paste}} Give me: 1) WHAT STATE I'm actually in, plainly. 2) THE SAFE FIX — exact commands in order, with what each does and why. Prefer non-destructive options; clearly flag anything that discards work before I run it. 3) HOW TO VERIFY it worked. 4) THE HABIT that prevents this next time. Assume I'll paste your commands literally — don't hand-wave.

You are a bio writer who makes professionals sound like humans worth meeting. My career story, rambled: {{just talk — jobs, turns, what you're proud of}} Who I want reading it: {{recruiters? clients? peers?}} Three words people use about me: {{ask a friend if unsure}} Write my About section (first person, ~120 words): 1. Open with what I actually do for people — not my title. 2. One line of how I got here that only I could write. 3. Proof: two concrete things I've done, with numbers if I gave any. 4. Close with what I want next and how to reach me. Banned: "passionate", "results-driven", "seasoned professional", third person.

You are a persuasion-savvy writer who knows busy people skim. What I'm asking for: {{the favor / decision / intro}} Who I'm asking: {{name, role, how well we know each other}} Why they might hesitate: {{your honest guess}} Write the email: 1. Subject line that states the ask plainly (no "quick question"). 2. First line: the ask, whole and specific — date, size, scope. 3. Two sentences of context max, aimed at their hesitation. 4. Make yes easy: offer a default ("if I don't hear back by Friday, I'll…") and an easy out ("if now's wrong, just say later"). 5. Under 110 words. Then write the 2-line follow-up for one week later.

Help me apply the regret-minimization frame to a decision. The decision: {{the big choice}} What's holding me back: {{fear, comfort, others' opinions, money}} Work it: 1) THE 80-YEAR-OLD VIEW — imagine me at 80 looking back. Which choice am I more likely to regret NOT making? Walk both futures. 2) SEPARATE the fears — which of my hesitations are about real, lasting downsides vs. temporary discomfort or others' judgment that won't matter in a decade? 3) THE REVERSIBILITY — if I try the scary thing and it fails, can I recover? Usually yes. 4) THE ASYMMETRY — is the upside life-changing and the downside survivable? 5) What the long view says, plainly. Optimize for a life without 'what if', not a year without discomfort.

You are a no-mercy personal finance auditor. Here are my recurring charges (from my statement, messy is fine): {{paste subscriptions and amounts}} For each one: 1. Verdict: KEEP (I clearly use it), KILL (be honest with me), or NEGOTIATE (retention deals exist). 2. The math: what each kill saves per year — then the total, in a sentence designed to shock me. 3. For every NEGOTIATE: the exact chat/phone script, including the magic words ("I'm planning to cancel — are there any offers on my account?"). 4. For every KILL: where the cancel button hides, if it's a known maze. 5. The one subscription I should probably ADD given what I keep (if any) — only if it replaces two others. End with: total yearly savings, and what that money becomes in 5 years at 7%.

You translate confusing documents into plain English for a smart non-expert. The text: {{paste it}} Give me: 1) THE GIST — what this says in 3 plain sentences. 2) WHAT IT MEANS FOR ME — the practical implications, especially anything that costs me money, time, or rights. 3) THE WATCH-OUTS — clauses or phrases I should question or clarify. 4) THE QUESTIONS — exactly what to ask the sender. Flag where I should get a professional if the stakes are high.

Here's a meeting on my calendar (or one I'm about to schedule): {{purpose, attendees, length}} Do this: 1) THE TEST — does this need to be synchronous? It does only if it needs real-time debate, sensitive/emotional content, or fast back-and-forth decisions. Judge honestly. 2) If NO: draft the async message that replaces it (context, the decision or input needed, a deadline to respond). 3) If YES: cut it to the minimum — who truly needs to be there, the tightest agenda, and the shortest length that works. 4) The one outcome that means it succeeded.

You are a content strategist. Plan my next 30 days. What I do & who follows me: {{context}} My 2-3 core themes: {{topics you want to be known for}} My channel(s) & posting frequency: {{e.g. LinkedIn 3x/week}} My voice: {{2-3 words}} Build it: a dated list where each post has — the theme, the format (story, how-to, contrarian take, question, behind-the-scenes), a written hook (first line), and the point. Balance the formats so it's not repetitive. Mark the 3 posts most likely to travel, and the one 'ask' post (for signups/sales) that's earned by the value around it.

Help me explain my business so simply a 10-year-old gets it — because if I can't, my customers are confused too. What my business does (in my normal jargon-y way): {{describe it}} Do this: 1) THE 10-YEAR-OLD VERSION — what I do, who I help, in words a kid understands, using something from their world. 2) THE JARGON I LEANED ON — the insider words I used that a normal customer wouldn't get, with plain replacements. 3) THE CLEAR PITCH — a grown-up but jargon-free one-liner built from the simple version. 4) THE TEST — the confused-face phrases to cut from my website/pitch. Simple isn't dumb; it's respect for the listener.

You are a practical financial coach. My monthly essential expenses: {{amount or estimate}} My income stability: {{steady job? freelance? one income?}} Current savings: {{amount}} — What I can spare monthly: {{amount}} Give me: 1) MY TARGET — how many months of essentials I actually need given my situation (not a generic '6 months'), with the dollar figure. 2) WHERE to keep it so it's safe and reachable but not tempting. 3) THE PLAN — a realistic monthly amount and the date I'd hit a starter fund (one month) then the full target. 4) What to pause (like extra debt payoff) while building the starter buffer, if anything.

Help me write something heartfelt for a card. Occasion: {{birthday / thank you / condolence / farewell / congrats}} Who it's for & our relationship: {{context}} A specific memory or thing I appreciate about them: {{even a small one}} Write it: 1) Open with something only I could say to them — reference the specific thing, not a generic sentiment. 2) The real feeling, in plain honest words (not Hallmark). 3) For hard occasions (condolence, goodbye): warmth without clichés or forced silver linings. 4) A closing that fits our relationship. Keep it short and true — a few real sentences beat a page of nice-sounding nothing. Give me a slightly shorter option too.

You explain payslips in plain English. Here's mine (or the line items I'm unsure about): {{paste — remove any ID numbers}} My country/region: {{for tax context}} Explain: 1) GROSS TO NET — walk from what I earned to what I got, line by line, in plain words. 2) EACH DEDUCTION — what it is, roughly why, and whether the amount looks normal. 3) THE FLAGS — anything worth questioning with payroll or checking against my contract. 4) THE LEVERS — deductions I might actually control (retirement %, benefits, tax withholding). General guidance only — flag where a professional should confirm.

Build me a realistic weekly meal framework. (General guidance, not medical advice.) My goal: {{more energy / weight / muscle / manage a condition — and any dietary needs}} My reality: {{cooking skill, time, budget, foods I hate, who I cook for}} Give me: 1) THE PRINCIPLES — the few simple rules that serve my goal (not a rigid diet), in plain terms. 2) A FLEXIBLE WEEK — breakfast/lunch/dinner patterns (not rigid recipes) I can rotate, built around foods I'll actually eat. 3) THE EASY WINS — the 2-3 swaps that matter most for my goal. 4) THE REALISTIC PART — how to handle busy days, eating out, and cravings without 'ruining' it. 5) One thing to discuss with a doctor/dietitian if relevant. Sustainable beats optimal.

Write my project status update. Raw situation: {{what's done, stuck, at risk}} Audience: {{manager / client / team}} — What I want them to think: {{on track? give me X?}} Structure it: 1) HEADLINE — one line on overall status (green/amber/red + the gist). 2) PROGRESS — the 2-3 things that moved, briefly. 3) RISKS — what could slip, and what I'm already doing about it. 4) THE ASK — what I need from them, if anything, specific. Keep it skimmable — bold the headline. No fluff, no burying the risk.

Proofread this for grammar, spelling, and clarity: {{paste it}} Return: 1) The corrected version. 2) A short list of what you changed. 3) THE PATTERN — the one or two mistakes I made more than once, each with the rule in one plain sentence and a trick to remember it. Don't rewrite my style — only fix what's actually wrong.

Help me build a habit that survives past week two. The habit I want: {{be specific}} Why it matters to me: {{the real reason}} When I've failed at habits before: {{what happened}} Design it: 1) SHRINK IT — the absurdly small version I can't fail (two minutes, one rep) so I build the identity first, not the intensity. 2) THE TRIGGER — anchor it to something I already do every day ('after I pour coffee, I…'). 3) THE FRICTION — remove one barrier to doing it, add one to skipping it. 4) THE SKIP PLAN — the rule for when I miss a day (never miss twice) so one lapse doesn't end it. 5) HOW TO GROW it once the tiny version is automatic. Consistency of a tiny thing beats intensity that burns out.

Help me get paid faster. What I'm invoicing for: {{work, amount}} Client relationship: {{new? ongoing? already late?}} Give me: 1) THE INVOICE ESSENTIALS — what to include so there's no excuse to delay (clear line items, due date, payment methods, terms). 2) THE SEND-WITH MESSAGE — friendly, professional, sets the expectation. 3) THE FOLLOW-UP SEQUENCE — the exact wording for: day-of-due reminder, 3-days-late nudge, and the firm-but-kind 'this is now overdue' message with a consequence. 4) One clause to add to future invoices to prevent late payment.

You write newsletter hooks that beat the inbox. This issue is about: {{topic}} My audience: {{who}} — My voice: {{2-3 words}} Give me: 1) Five subject lines across patterns (curiosity, specific-benefit, contrarian, question, plain-and-honest) — each under 50 characters, none clickbait I can't pay off. 2) Preview text for my top two. 3) The first two sentences of the issue that make them keep reading past the fold. Mark your favorite and why.

Turn my messy explanation of a task into a clean SOP others can follow. How I do it (rambling is fine): {{describe the task start to finish}} Produce: 1) TITLE + PURPOSE — what this achieves and when to run it. 2) PREREQUISITES — access, tools, info needed before starting. 3) STEPS — numbered, each an action with the expected result; flag decision points ('if X, then…'). 4) COMMON MISTAKES — the 2-3 places people mess this up. 5) DONE CHECK — how to know it worked. Ask me about any step where you had to guess.

Help me write a cold outreach message that gets a reply. Who I'm messaging & why them specifically: {{context — be specific, this is the whole game}} What I actually want: {{advice? a call? a collab? a job?}} Channel: {{DM / email / LinkedIn}} Write it: 1) A first line that proves I know THEM (something real they made or said), not a template opener. 2) One line of who I am, only what's relevant. 3) A small, specific, easy-to-grant ask — not 'pick your brain', not 'a quick 30 minutes' from a stranger. 4) A graceful out. Under 90 words. Then give me the even-shorter version.

Be my Socratic tutor for {{topic}}. My current level: {{beginner / some knowledge}}. Rules: 1) Don't lecture. Lead me to understanding by asking me one good question at a time, building on my answers. 2) When I'm wrong, don't just correct — ask the question that helps me SEE why. 3) When I'm right, push one level deeper. 4) Use a concrete example or analogy when I'm stuck, then return to questioning. 5) Every few exchanges, have me summarize what I've figured out in my own words. Start by asking what I already believe about {{topic}}.

You are an executive coach preparing me for my 1:1 with my manager. Since our last 1:1: {{wins, stucks, worries — brain-dump}} What I actually need: {{a decision? budget? feedback? visibility?}} Time: {{usually 30 min}} Build the agenda: 1. THE HEADLINE — one sentence of momentum to open with (managers repeat headlines upward). 2. THE DECISION — the one thing I need decided, framed with a recommendation, not an open question. 3. THE FLAG — one risk I'm raising early, with what I'm already doing about it. 4. THE GROWTH ASK — a question about my development (rotate: skills, scope, trajectory). 5. What NOT to spend time on (status that belongs in a message instead). Give me the exact opening sentence.

Help me address a tension with someone I live with. The issue: {{what's bothering me}} History: {{first time? recurring? already awkward?}} Our dynamic: {{friends? strangers? how conflict usually goes}} Guide me: 1) THE REAL PROBLEM — is it the dishes, or the feeling of being disrespected/taken for granted underneath? Name it. 2) THE TIMING & SETTING — when and how to raise it so it's a conversation, not an ambush or a passive-aggressive note. 3) THE SCRIPT — open with the shared goal (a home that works for both), state the specific behavior and its impact on me without character attacks, then propose a concrete fix. 4) THE FAIR ASK — a solution that works for both, not just me. 5) IF THEY GET DEFENSIVE — how to keep it collaborative. Fix the problem, keep the peace.

Here's a paragraph I'm not happy with: {{paste it}} It's for: {{email / essay / post / speech}} — and I want the reader to feel: {{convinced? moved? reassured?}} Give me three rewrites, labeled: 1. CLEARER — same length, every vague word replaced with a precise one. 2. SHORTER — half the words, none of the meaning. 3. WARMER — same content, but it sounds like a person who cares. Under each, one line on what you changed and why. Then tell me which version best fits the feeling I named — and whether my original had something worth keeping that all three lost.

You are a content strategist who believes in making one idea work five times. My idea: {{the insight, story, or lesson}} My voice: {{2-3 adjectives or paste a past post}} My channels: {{pick from: LinkedIn, X, newsletter, short video, carousel}} For each channel, adapt — don't repost: 1. LINKEDIN — story-first, line breaks for skimmers, ends with a question that invites experience-sharing (not "thoughts?"). 2. X/THREAD — the idea as 5-7 punchy beats, first tweet earns the click. 3. NEWSLETTER — the idea with one personal detail added, subject line included. 4. SHORT VIDEO — 45-second script: hook in first 2 seconds, one visual note per beat. 5. CAROUSEL — 7 slide texts, one thought each, last slide is the save-worthy summary. Mark which channel this idea is STRONGEST for, and which to skip.

You are a skeptical-but-fair startup advisor. Pressure-test my idea. The idea: {{what it is, who it's for, how it makes money}} Why I think people want it: {{your evidence — be honest if it's a hunch}} Do this: 1) THE CORE ASSUMPTION — the one belief that, if wrong, kills this. Name it plainly. 2) THE REAL CUSTOMER — who actually pays, and do they have this problem badly enough to switch? 3) THE 'WHY NOW / WHY YOU' — is there a real reason this works now, and a reason you can win? 4) THE CHEAPEST TEST — how to validate the core assumption this week WITHOUT building the product (conversations, a fake door, a pre-sale). 5) THE HONEST VERDICT — promising, needs reshaping, or a solution looking for a problem. Don't just cheerlead.

Help me build a regular expression. What I want to match (with examples that SHOULD and SHOULDN'T match): {{describe + examples}} Language/flavor: {{JS, Python, PCRE...}} Give me: 1) THE REGEX. 2) A PLAIN-ENGLISH breakdown, piece by piece, so I understand not just copy. 3) TEST CASES — run my examples against it and show pass/fail; add tricky ones I didn't think of. 4) THE GOTCHAS — where this will over- or under-match in the real world (unicode, edge whitespace, greedy vs lazy). 5) When regex is the WRONG tool here and I should parse instead.

You are a pricing consultant for freelancers who undercharge. My work: {{what you do}} Income I need per year (after tax, honestly): {{amount}} Billable reality: {{days/week I can truly bill, weeks of holiday}} What I charge now: {{rate, or "first time"}} Do the math out loud: 1. My true required day rate (account for non-billable time, tax, slow months, software, sick days). 2. Compare to my current rate: what I'm actually paying myself per hour. 3. Market check: the realistic range for my work at my level. 4. THE NEW RATE — one number, defensible. 5. Script me saying it: to a new client, and the harder one — the rate-raise email to an existing client, with the grandfathering line. No "it depends on value" hedging. Commit to numbers.

You are a pragmatic daily planner. It's tonight; plan my tomorrow. Open loops in my head: {{everything — big, small, nagging}} Fixed commitments tomorrow: {{meetings, school runs, calls}} My energy pattern: {{morning person? afternoon slump?}} Give me: 1. THE ONE THING — if only one item gets done, which one makes tomorrow a win. Schedule it in my best energy window. 2. THE FIRST HOUR — exactly what I do before opening email. 3. Three-and-only-three other tasks, time-boxed into the real gaps. 4. THE PARKING LOT — everything else, written down so my brain releases it. 5. One thing on my list to delete entirely — be honest. Total plan must fit the hours I actually have.

You are a launch copywriter for people allergic to hype. What I made: {{the thing}} Who it's for and the itch it scratches: {{be specific}} The origin story: {{the moment you decided to build it}} Where I'm posting: {{LinkedIn / X / newsletter / all}} Write the announcement: 1. Open with the PROBLEM MOMENT — the scene that made me build this. Present tense, specific. 2. The turn: "so I made a thing." 3. What it does in two plain sentences — no feature list, no "revolutionary". 4. The honest ask: try it, tell me what breaks, share it with the one person who needs it. 5. P.S. with the link and one disarming admission (what it doesn't do yet). Tone: proud but human. Like telling a friend, slightly nervous, genuinely excited.

Help me turn a vibe into a mood board direction. The project: {{brand / room / event / product line}} The feeling I'm chasing: {{adjectives, references, a song even}} Anything fixed: {{must-have colors, constraints}} Produce: 1) THE DIRECTION — name it and describe the coherent aesthetic in 3 sentences. 2) THE PALETTE — 4-5 colors with hex and the role each plays. 3) THE TEXTURES & MOTIFS — materials, shapes, patterns that belong. 4) SIX IMAGE PROMPTS that together form a cohesive board (hero, texture, detail, atmosphere, etc.), all sharing the palette and mood. 5) WHAT DOESN'T BELONG — the tempting things that would break the vibe. Cohesion over collecting pretty things.

Help me write a one-page business plan I'll actually use. My business idea: {{describe it}} What I know so far: {{customers, pricing thoughts, competition}} On ONE page: 1) THE PROBLEM & who feels it. 2) THE CUSTOMER — specific, and where to find them. 3) THE OFFER — what I sell, and why mine over the alternatives. 4) THE MONEY — how I make it, rough price, what I need to sell to break even. 5) THE RISKIEST ASSUMPTION and how I'll test it first. 6) THE FIRST THREE STEPS. Keep it tight and honest — flag anywhere I'm hand-waving. A plan I revisit beats a deck I file away.

Be my rubber duck. I'm about to build something — poke holes before I waste a day. What I'm building & why: {{the goal}} My planned approach: {{how you intend to do it}} Constraints: {{stack, deadline, scale}} Respond: 1) PLAY IT BACK — restate my plan so I know you understood. 2) THE FLAWS — where this breaks, gets slow, or gets painful to maintain. Rank by likelihood. 3) THE SIMPLER PATH — is there a materially easier approach I'm overcomplicating past? 4) THE EDGE CASES I haven't mentioned. 5) THE FIRST STEP if the plan holds. Push back honestly — don't just validate me.

You are a consumer negotiation coach. People overpay because they don't know the dance. What I'm buying/renewing: {{the thing}} Their asking price: {{amount}} — What I've seen elsewhere: {{comps, or "help me find what to check"}} My walk-away power: {{can I actually leave? alternatives?}} Coach me: 1. THE REAL RANGE — what this actually sells for and what discount is normal to ask. 2. MY NUMBER — where to anchor, and why that exact number (odd numbers read as researched). 3. THE SCRIPT — my opener, their likely counter, my response, and where I stay silent. 4. THE EXTRAS — what to ask for when they won't move on price (delivery, warranty, fees waived, first month free). 5. THE WALK — the exact polite sentence for leaving, and why saying it often wins. Rehearse me: play the salesperson for 3 exchanges.

You are a friendly {{language}} conversation partner. My level: {{beginner / can order coffee / conversational}}. Rules of our chat: 1. Talk with me about {{today's topic — my day, food, travel plans}} — mostly in {{language}}, at my level plus a tiny stretch. 2. When I make a mistake: finish responding to WHAT I said first, then show the correction in brackets [like this → like this], briefly. Never lecture. 3. Feed me 2-3 natural phrases per exchange that native speakers actually use (not textbook forms), and re-use them later so I see them twice. 4. If I write in English, gently give me the {{language}} version and continue. 5. Every ~10 exchanges: quick recap — my 3 best phrases, my 1 recurring mistake, and tomorrow's topic. Start by greeting me and asking about my day.

You are a user researcher trained in the Mom Test: never ask questions that invite polite lies. What I'm trying to learn: {{the decision this research feeds}} Who I'm talking to: {{customers? churned users? prospects?}} Build my 30-minute interview guide: 1. OPENER — one question about their life/workflow, zero mention of my product. 2. FIVE CORE QUESTIONS — all about past behavior and specific stories ("walk me through the last time you…"), none about the future, none containing my idea. 3. THE MONEY QUESTION — how they currently pay/work around this problem (what they DO, not what they'd pay). 4. FOLLOW-UP PROBES — the three magic phrases for going deeper ("what happened next?", "why was that hard?", "what did you do about it?"). 5. BANNED LIST — the questions I'd naturally ask that would poison the data, and why. Then: how to spot a polite lie in their answers.

I'm stuck. Help me reframe the problem itself. How I currently state the problem: {{your framing}} What I've tried: {{approaches that didn't work}} Do this: 1) RESTATE it five different ways — as a different question, a different scale, from a different stakeholder's view, as an opportunity not a problem, and by questioning a hidden assumption in my framing. 2) THE HIDDEN ASSUMPTION — the thing I'm treating as fixed that might not be. 3) WHICH REFRAME opens the most new options, and what those options are. 4) THE REAL PROBLEM — after reframing, is the thing I've been solving even the right thing? Often the stuck-ness is the framing, not the problem.

Turn my notes into effective flashcards. My notes: {{paste them}} What I'm studying for: {{exam / skill / interview}} Make cards that: 1) Test one thing each — atomic, no card with five facts. 2) Ask for RECALL, not recognition (open questions, not 'is this true?'). 3) Include a few that connect ideas ('why does X cause Y?'), not just definitions. 4) Flag anything in my notes too vague to make a good card — that's a gap I should fill first. Format as Q on one line, A on the next. Aim for the 20% of cards that cover 80% of what matters.

We're doing the Feynman technique. I'll explain; you find my gaps. The topic I think I understand: {{topic}} Here's my explanation, as if teaching a newcomer: {{write your explanation — don't look anything up first}} Now: 1. GRADE the explanation: what I clearly understand vs. where I went vague, hand-wavy, or wrong. Quote my exact fuzzy phrases back to me. 2. THE GAPS — for each fuzzy spot, the precise question I couldn't answer. 3. PATCH one gap at a time: explain just that piece, then make me re-explain it in my own words before moving on. 4. When we're done, give me the 3-sentence version of the topic that I should be able to produce cold next week. Don't let me get away with borrowed phrases I can't unpack.

You help people say uncomfortable things with warmth and a spine. The situation: {{what happened, and what needs saying}} My relationship to them: {{friend / boss / family / vendor}} What I'm afraid of: {{their reaction? seeming rude? losing them?}} Draft the message: 1. Open warm and real — no throat-clearing paragraph. 2. Say the thing in one clear sentence. Not softened into fog. 3. One sentence of honest acknowledgment (their effort, the awkwardness, my part in it). 4. End with what happens next, stated kindly. Then give me a softer variant and a firmer variant of just the key sentence, so I can calibrate. Keep the whole thing under 100 words — long apologies read as guilt.

You are an executive coach building my 30-60-90 day plan for a new role. My role: {{title, team, company type}} What success looks like here: {{if you know}} My strengths & unknowns: {{honest}} Build it: DAYS 1-30 (learn) — who to meet, what to understand, questions to ask, no big moves. DAYS 31-60 (contribute) — first visible wins that build trust. DAYS 61-90 (own) — where I take real responsibility. For each phase: 2-3 concrete goals and how I'd show progress to my manager. End with the mistakes new people make in this kind of role.

My image prompt isn't working. Diagnose and fix it. My prompt: {{paste it}} What I got vs. what I wanted: {{describe the gap}} Tool: {{Midjourney / DALL-E / etc.}} Do this: 1) DIAGNOSE — why the prompt produced that (too vague, conflicting terms, missing style anchor, wrong emphasis, unrealistic combo). 2) THE REWRITE — a cleaner version with the fix, keeping what worked. 3) WHAT EACH CHANGE DOES — so I learn, not just copy. 4) THREE VARIANTS dialing different levers (more/less detail, different lighting, different framing). 5) THE ONE PARAMETER most likely to close the gap. Teach me to fish.

Review my code's comments — add what's missing, cut what's noise. My code: {{paste it}} Do this: 1) ADD comments only where they earn their place — the WHY behind a non-obvious choice, a constraint, a gotcha, a 'do not change this because…'. 2) FLAG comments that just restate the code ('// increment i') and should be deleted. 3) SUGGEST where a better name would remove the need for a comment entirely. 4) If any function needs a short doc-comment (purpose, params, gotchas), write it. Keep my style; don't over-comment.

Help me get legible text into an AI-generated image. What the image is & the exact text I need in it: {{describe + the words}} Tool: {{Midjourney / DALL-E / etc.}} Give me: 1) THE REALISTIC EXPECTATION — where each tool is decent vs. hopeless with text, and how much text is safe to attempt. 2) THE PROMPT TECHNIQUE — how to phrase it (quoting the text, keeping it short, specifying style/placement) to maximize legibility. 3) THE FALLBACK — when to generate the image WITHOUT text and add it after in a design tool instead (often the pro move). 4) THE PROMPT for my case, plus a text-free version to overlay. 5) The tweaks if the text comes out garbled. Legible over 'AI tried its best'.

You are a positioning strategist. Help me write the one sentence that explains my thing. What I do/offer: {{describe it}} Who it's really for: {{specific audience}} What makes it different: {{the honest edge}} What people currently use instead: {{the alternative}} Give me: 1) Five one-liners in the form 'I help [who] [achieve what] without [the pain of the alternative]' — varied, none jargony. 2) The clearest and the boldest, marked. 3) The one word in my draft that's vague ('solutions', 'platform', 'empower') and a concrete replacement. 4) The test: would my ideal customer instantly know if this is for them?

Help me prompt a visual for a social post. The post is about: {{topic}} — Platform: {{IG / LinkedIn / X / TikTok thumbnail}} Brand vibe: {{3 adjectives}} — Any text/logo overlay planned? {{yes/no}} Build: 1) THE CONCEPT — one strong visual idea that fits the message and stops the thumb (not a generic stock vibe). 2) COMPOSITION — leave space if text goes on top; think about the tiny-thumbnail test. 3) THE PROMPT with style, mood, color, aspect ratio right for the platform. 4) TWO ALTERNATES — a bold one and a clean one. 5) THE THUMBNAIL CHECK — will it read at small size? Optimize for stopping the scroll, not gallery-wall beauty.

Generate 'would you rather' questions. The crowd: {{kids / adults / mixed / a couple}} The vibe: {{silly / genuinely hard / deep / gross-out for kids / spicy for adults}} How many: {{count}} Give me questions that: 1) Are actually HARD to answer — real trade-offs, not obvious ones (a good 'would you rather' has no easy pick). 2) Match the crowd's vibe and stay appropriate for them. 3) Mix light and thought-provoking so it doesn't get samey. 4) Include a few that spark a story or debate, not just a one-word answer. Format numbered so I can read them out. Genuine dilemmas over easy picks.

Help me declutter my digital life without spending a whole weekend on it. What's overwhelming me: {{inbox? files? photos? notifications? apps? all of it?}} My setup: {{devices, main tools}} Give me: 1) THE BIGGEST DRAIN FIRST — which area is costing me the most attention/stress, to tackle first. 2) THE FAST WINS — the 20-minute actions with outsized payoff (kill noisy notifications, unsubscribe in bulk, one folder system). 3) THE SYSTEM — a simple structure (for files/email/photos) that's maintainable, not a perfect taxonomy I'll abandon. 4) THE MAINTENANCE — a 10-minute weekly reset so it doesn't rebuild. 5) THE DIGITAL BOUNDARIES worth setting (notification rules, app limits) for focus. Calmer attention over perfect organization.

You are an operations lead who delegates so well tasks never boomerang back. The task I'm handing off: {{what it is}} To whom: {{their experience level with this kind of work}} My worry: {{what could go wrong or why I've been holding it}} Write the delegation brief: 1. THE OUTCOME — what done looks like, measurable, with the deadline. 2. THE WHY — one sentence of context that lets them make judgment calls. 3. GUARDRAILS — the 2-3 decisions they should NOT make alone. 4. RESOURCES — what they'll need and where it lives ({{links/people}}). 5. CHECK-IN — one milestone check, scheduled, so neither of us hovers. Then tell me: based on my worry, what's the one part I'm most likely to micromanage — and the sentence to say instead.

Help me fix my chaotic note-taking. My current mess: {{where notes live now, what goes wrong}} What I take notes on: {{meetings? ideas? learning? tasks? life?}} My tools: {{apps/devices I actually use}} Design a system: 1) ONE HOME — where capture happens so I stop scattering across apps. 2) THE STRUCTURE — a simple, low-effort way to organize (a few buckets, not a 40-folder taxonomy I'll abandon). 3) CAPTURE FAST — how to get a thought down in seconds without deciding where it goes yet. 4) FIND IT LATER — the tagging/naming habit that makes retrieval work. 5) THE WEEKLY 10-MINUTE tidy so it stays usable. Consistency I'll keep over a perfect system I won't.

Build me a trivia round to host. Theme(s): {{general / 90s / movies / a mix — or a custom theme for the group}} Players: {{how many, casual or competitive}} — Length: {{rounds/questions}} Difficulty: {{keep it fun / challenge them}} Produce: 1) QUESTIONS across a difficulty curve (some everyone gets, some that separate the field), grouped into rounds, with answers. 2) A FUN FORMAT twist — a picture round idea, a 'name that…' round, a wager/final-question mechanic. 3) THE CROWD-PLEASERS — a few questions with satisfying 'ohh!' answers. 4) SCORING that's simple to run. 5) A tiebreaker question. Format so I can read it straight off my phone. Fun and pace over obscurity.

You are a thoughtful-gift consultant. Generic gifts are banned. The person: {{relationship, age-ish}} Budget: {{range}} The occasion: {{birthday / thanks / just because}} Brain-dump about them: {{what they talk about, complain about, do on Saturdays, loved as a kid}} Work with me: 1. First, ask me 3 sharp questions I probably haven't considered (what do they buy the cheap version of for themselves? what did they mention once and drop?). 2. Then suggest 5 gifts, each with: the gift, why it's THEM (tied to something I said), and the one-line card note that shows the thought. 3. Include: one experience, one upgrade-of-something-they-cheap-out-on, one wildcard. 4. THE VETO CHECK — which suggestion risks missing, and for whom it would be wrong. Banned: candles, generic gift cards, "spa day" for someone you can't name a spa for, anything you'd grab at an airport.

You are a deliberate-practice coach. No fluff, no "just practice more". Skill I want: {{skill}} Time I really have: {{minutes/day, days/week}} Why now: {{the event, goal, or itch}} Starting point: {{honest current level}} Build the 30 days: 1. THE 20% — the sub-skills that produce 80% of results for a beginner. Name what we're deliberately IGNORING this month. 2. WEEKS 1-4 — each week: one focus, a daily drill (fits my minutes), and a visible END-OF-WEEK PROOF (something I can show someone). 3. THE FEEDBACK LOOP — how I'll know reps are correct, not just done (self-check, recording, rubric). 4. THE PLATEAU PLAN — what to do on the inevitable bad-progress days in week 3. 5. DAY 30 TEST — the concrete performance that proves the month worked. Calibrate everything to my actual minutes — a plan I can't keep is a plan against me.

Generate practice problems for {{topic}} at my level: {{describe what you can already do}}. Give me: 1) SIX problems, easy to hard, each slightly stretching beyond the last. 2) For each, a HINT I can peek at before the full solution. 3) WORKED SOLUTIONS at the bottom (so I try first) — showing the reasoning, not just the answer. 4) After I tell you how I did, diagnose my specific weak spot and generate 3 more targeting exactly that. Make them realistic to how this shows up in {{exam/real use}}, not artificial.

You are the game master for our dinner table. The table: {{who's here — ages, how well people know each other}} The vibe we want: {{silly? nostalgic? getting-to-know-you? gently deep?}} Any no-go zones: {{topics to avoid}} Run it: 1. Start with 3 WARM-UP questions anyone can answer instantly (funny, low-stakes, no wrong answers). 2. Then 5 MAIN questions matched to our vibe — each designed so the quietest person has something to say, and follow-ups that keep a good answer rolling. 3. One GAME ROUND — pick the best fit: "two truths and a lie", "most likely to…", "hot takes, mild edition", or a made-up game for THIS group. 4. THE CLOSER — one question that ends the night warm (best moment of the year so far, a thank-you to someone at the table). Format for reading aloud from a phone. If kids are present, everything works for them too.

Help me apologize in a way that actually repairs things. What I did: {{honestly}} To whom & our relationship: {{context}} What I'm tempted to say: {{if you have a draft}} Guide me: 1) THE REAL APOLOGY has: naming what I did (specifically, no 'if you were hurt'), acknowledging the impact on THEM, no excuses tucked in, and what I'll do differently. Draft it that way. 2) STRIP THE NON-APOLOGY — the 'but', the 'I'm sorry you feel', the justification that undoes it. Show me what to cut. 3) WHAT NOT TO EXPECT — I can't demand forgiveness; the apology is mine to give, not theirs to grant. 4) THE FOLLOW-THROUGH that makes words credible. Keep it honest and short — a real apology doesn't perform.

You are a conversation coach with a talent for playing difficult people realistically. The conversation I'm dreading: {{what needs to be said, to whom}} How they usually react: {{defensive? tears? counterattack? shutdown?}} My goal: {{what needs to be true when it's over}} My fear: {{what I'm most afraid they'll say}} Rehearse me: 1. First, my OPENER — help me craft two sentences that are honest without being an ambush. 2. Then role-play: you play THEM, realistically difficult (their style, not cartoon-hostile). I respond as me. Stay in character 3-4 exchanges. 3. Break: coach me — what I did well, where I got defensive or vague, the one phrase to keep in my pocket. 4. Round two: they bring my worst fear. Let me handle it. 5. Debrief: my strongest moment, the sentence to say if I freeze, and the exit line if it goes badly. Keep them human — hard conversations fail when we rehearse against monsters.

Turn my rough notes into a short, readable narrative. My notes: {{paste bullets}} It's for: {{a recap email / a post / an update}} — Tone: {{casual? professional?}} Write it as connected prose, not a list: an opening that sets the scene, the events in a sensible order with transitions, and a closing takeaway. Keep every fact from my notes; invent nothing. Under 250 words unless I said otherwise.

You are a reading coach who believes a book you can't use is a book you didn't read. The book: {{title}} What I remember most right now: {{brain-dump — scenes, ideas, quotes}} My current situation: {{work/life context where this could apply}} Debrief me: 1. From what I remembered, identify the 3 ideas that clearly landed — refine each into one crisp sentence. 2. THE APPLICATION — for each idea, one concrete way to use it in MY situation this month. Specific enough to schedule. 3. THE ARGUMENT — the book's weakest claim, so I hold it as a thinking tool, not gospel. 4. THE CONNECTION — how this book talks to something else I likely know (name 2-3 candidates and ask which I've read). 5. THE ONE-WEEK TEST — a question to ask me in a week; if I can't answer it, tell me which chapter to revisit. Work only from what I gave you plus general knowledge of the book — don't invent content.

You are a pragmatic business coach who's seen people leap too early and too late. My side income: {{monthly, and how steady}} My job income I'd give up: {{monthly, after tax}} My savings/runway: {{amount}} — My essential monthly costs: {{amount}} Analyze: 1) THE GAP — what my side income must reach to cover my real costs (remember: I lose benefits and pay my own tax). 2) THE RUNWAY — how many months my savings buy if I leap now. 3) THE TRIGGER — the specific milestone (income level, client count, months of buffer) that means it's actually safe, not just exciting. 4) THE BRIDGE — how to grow the gig while still employed. Be honest if I'm not close.

Help me request a testimonial that's actually useful. Who I'm asking & what I did for them: {{context}} Where it'll be used: {{website / proposal / social}} Give me: 1) THE ASK MESSAGE — warm, makes it easy, low-pressure. 2) THE MAGIC PART — 3-4 specific guiding questions I include so they write something concrete ('what was the situation before?', 'what changed?', 'what would you tell someone considering it?') instead of 'they were great.' 3) An offer to draft it for them to approve, for the busy ones. 4) A line on where a specific number or outcome would make it 10x stronger.

You are a direct-response copywriter. My product/offer: {{what it is, price, who it's for}} The main pain it solves: {{the problem}} My best proof: {{result, review, number, credential}} Write three ad variations, each a different angle: 1) PAIN — leads with the problem they feel. 2) ASPIRATION — leads with the after-state they want. 3) PROOF — leads with the result/social proof. Each: a scroll-stopping first line, 2-3 lines of body, one clear CTA. Keep claims honest and backable. Tell me which angle likely fits my audience best, and what to A/B test first.

You are a photography educator who can reverse-engineer any look. The look I love: {{describe a photo/photographer/film — "Wes Anderson symmetry", "90s film snapshots", "moody kitchen editorial"}} What I want to shoot in that style: {{your subject}} Deconstruct it: 1. THE RECIPE — what actually creates this look: light quality & direction, color grade, lens/framing habits, depth of field, composition rules, era/film artifacts. 2. THE VOCABULARY — the 10-12 exact terms that summon this style in image AI ("overcast softbox light", "Kodak Gold 200", "symmetrical one-point perspective"...). 3. THE PROMPT — my subject in this style, built from that vocabulary, with aspect ratio. 4. THREE VARIATIONS — same style, different: time of day, distance, mood. 5. THE TELL — the one element that, if wrong, breaks the style entirely (so I know what to fix when results feel off). Style notes only — no living artist's name pasted verbatim; teach me the ingredients instead.

Help me name something fun. What I'm naming: {{pet / band / character / boat / plant / team}} The vibe/personality: {{describe it — looks, energy, inside jokes}} Style I lean toward: {{cute / epic / punny / classic / weird}} Give me: 1) 20 NAMES grouped by style (a punny set, an epic set, a classic set, a wildcard set). 2) MY TOP 5 with a one-line reason each fits. 3) THE PAIRINGS — if it needs a matching set (two pets, a band + album), options that go together. 4) THE SAY-IT-OUT-LOUD test — which ones are fun to actually call out, since I'll say it a thousand times. Delight over trying-too-hard.

Help me get clear on what I actually value, for a decision I'm facing. The decision: {{the fork — job, move, relationship, path}} The options: {{list them}} Guide me: 1) Ask me 4-5 sharp questions that surface what I truly prioritize (not what I think I should) — about how I want to spend my days, what I'd regret, whose approval I'm chasing. Wait for my answers. 2) NAME THE PATTERN — from my answers, the 3 values that actually seem to drive me. 3) SCORE the options against THOSE values, not generic ones. 4) THE MISMATCH — where I'm tempted by an option that serves someone else's values, not mine. 5) The choice my own values point to, stated back to me. Help me choose my life, not the expected one.

Help me declutter without getting overwhelmed and quitting. What needs it: {{whole home? one room? category?}} My time & energy: {{honest}} — Why now: {{move? overwhelm? fresh start?}} Give me: 1) WHERE TO START — the one area that gives the biggest visible/emotional win first, for momentum. 2) THE DECISION RULE — a simple test for keep/toss/donate so I stop agonizing over each item. 3) THE PLAN — broken into sessions that fit my energy (not a 12-hour marathon), each with a clear stopping point. 4) THE STUCK CATEGORIES — sentimental items, 'might need it', paperwork — how to handle the ones that trap people. 5) HOW TO KEEP IT from creeping back. Progress over perfection — a cleared shelf beats a planned overhaul.

You are a database engineer reviewing my SQL. The query: {{paste it}} Table sizes (rough): {{e.g. users 100k, events 10M — or "unknown"}} Explain: 1. IN ENGLISH — what this query returns, one sentence a PM would understand. 2. THE EXECUTION STORY — walk through what the database actually does, in order, like a narrated field trip. 3. THE SLOW PART — which step hurts at scale and at roughly what row count it starts hurting. 4. THE FIX — index, rewrite, or both. Show the exact CREATE INDEX / rewritten query, and the trade-off it introduces. 5. THE GOTCHA — one way this query silently returns wrong data (NULLs, duplicates from joins, timezone). If the query is actually fine, say so — don't invent problems.

You are a QA engineer with a gift for breaking things. My function: {{paste it}} What it's supposed to do: {{one sentence}} Attack it: 1. EDGE CASES — list every input class that could break it: empty, null, zero, negative, enormous, unicode, wrong type, boundary values. Mark which ones my code currently survives (read it carefully) vs. fails. 2. THE WEIRD ONE — the input I'd never think of that real users will absolutely send. 3. CONCURRENCY/STATE — if called twice at once or out of order, what breaks? 4. WRITE THE TESTS — for the 5 highest-risk cases, in {{test framework}}, with names that describe the behavior ("returns_empty_list_when..."). Rank findings by "will actually happen in production" — not by theoretical purity.

Help me build my brag doc for the last {{period}}. What I remember doing (messy, incomplete): {{dump projects, wins, help you gave others, fires you put out}} Organize it: 1) IMPACT — group by outcome, each rewritten as value ('shipped X → result Y'), with numbers where we can estimate them. 2) THE INVISIBLE WORK — mentoring, unblocking, glue work that never shows up but matters; name it. 3) GROWTH — skills I built. 4) THE GAPS — what a strong review would want that I'm missing, so I can go get it before review time. Prompt me for numbers where they'd strengthen a line.

You are a consultant who writes proposals that close because they sound like the client. My call notes: {{paste everything — verbatim quotes are gold}} My services & rough pricing: {{what you offer}} Build the proposal: 1. THE PLAYBACK — their situation and goals in THEIR words (pull exact phrases from my notes). This section wins or loses the deal. 2. THE PLAN — 3 phases max, each with: what happens, what they get, how long. 3. THE INVESTMENT — one recommended option, one lighter alternative. No menu of ten. 4. RISK REVERSAL — the guarantee, checkpoint, or small-start that makes yes safe. 5. NEXT STEP — specific and dated ("reply by Thursday, we start Monday"). One page. No "leverage", no "synergies", nothing I couldn't say out loud to their face.

You are a speechwriter. I have {{minutes}} minutes to speak at {{occasion}} for {{audience}}. What I want them to feel/do: {{the goal}} Raw material — stories, points, jokes: {{brain-dump}} Write it: 1) A cold open that earns attention in 15 seconds (no 'thank you all for being here'). 2) ONE story told with a specific detail. 3) The turn — where it means something. 4) A closing line short enough to quote. Mark where to pause. Then give me the 30-second version if I run short.

Help me think through the downstream effects of a decision. The decision/action: {{what you're considering}} What I expect to happen (first-order): {{the obvious result}} Go deeper: 1) SECOND-ORDER — 'and then what?' What happens as a result of the first result? People react, incentives shift, habits form. 2) THIRD-ORDER — and then what after that? 3) THE SLEEPER EFFECTS — the non-obvious ripples (on relationships, reputation, future options, my own behavior). 4) WHO ELSE is affected and how they'll respond. 5) THE REFRAME — knowing the full chain, is this still a good move, and what would I adjust? Most bad decisions look fine at first order.

Someone left a negative/hostile comment in public. Help me handle it well. The comment: {{paste it}} Where: {{platform}} — Is there a real grievance in it? {{honest}} Coach me: 1) RESPOND OR NOT — is this a genuine complaint (respond), a troll (usually don't feed), or a misunderstanding worth one clarifying reply? Decide. 2) If I respond: draft a calm, brief reply written for the AUDIENCE watching, not the commenter — acknowledge any real point, correct any falsehood once, offer to take it private if needed. 3) What NOT to do (defensive essays, deleting legit criticism, sarcasm). 4) The one-line version if brevity is safer.

You are a customer-experience lead famous for turning 1-star moments into loyalty. The complaint: {{paste it — public review or private message}} What actually happened: {{your honest side}} What I can realistically offer: {{refund / redo / discount / just an apology}} Write the reply: 1. Open by validating the specific frustration — their words reflected back, no "we apologize for any inconvenience". 2. Own what's ours, plainly. If something wasn't our fault, explain once, without defensiveness. 3. THE MAKE-RIGHT — concrete, immediate, slightly more generous than expected. 4. The forward move — what changes so it doesn't recur (only if true). 5. If public: keep it short, human, and take the details private with a direct contact. Then a version for if they're still angry after this — the second reply is where loyalty is actually won.

Help me write my monthly investor update. This month's reality: {{metrics, wins, what went wrong, what you're worried about}} What I need from investors: {{intros, advice, hires, nothing}} Structure it: 1) TL;DR — 2-3 lines: the number that matters, the mood, the one ask. 2) METRICS — the key ones, vs. last month, no vanity. 3) WINS — brief. 4) LOWLIGHTS — what went wrong and what I'm doing about it (honesty here builds more trust than hiding). 5) THE ASKS — specific and easy to act on. 6) A personal line. Keep it skimmable. Investors help founders who are honest and clear about the hard parts.

You are a pricing strategist who blends unit economics with buyer psychology. My product/service: {{what it is}} My costs: {{per unit/customer, roughly}} Competitors charge: {{range, or "niche - help me reason"}} My customers are: {{price-sensitive individuals? businesses? teams?}} Build the pricing: 1. THE FLOOR — my true break-even, so I never accidentally price below it. 2. THREE TIERS — named, priced, and differentiated by VALUE (not crippled features): which is the anchor, which is the decoy, which is the one I actually want people buying, and the psychology of why this works. 3. THE NUMBERS — exact prices with reasoning (charm vs. round pricing for MY audience). 4. THE PAGE COPY — one line under each tier that sells the upgrade. 5. STRESS TEST — what happens to my margin if I run a 20% discount; when discounting is self-harm. Tell me the single most common pricing mistake for my kind of product, and whether I'm making it.

You are a sharp essay editor focused on argument, not grammar. My draft: {{paste it}} What I'm trying to say: {{one sentence}} Do this: 1) State my actual thesis as your reader received it, and compare to my intent. 2) Map each paragraph to the claim it supports; flag any that wander. 3) Tell me the ONE structural move (reorder, cut, merge) that would most improve it. 4) Name the strongest sentence I already wrote so I don't lose it.

You are a naming strategist. What I'm naming: {{product/company/project}} What it does & the feeling I want: {{context + 3 adjectives}} Names I like / hate: {{examples}} Constraints: {{must have .com? one word? avoid X?}} Give me: 1) 20 NAMES across styles — descriptive, invented, metaphor, real-word, playful — grouped by style. 2) MY TOP 5 with one line each on why it works and its risk (hard to spell? too generic? bad meaning in another language?). 3) THE CHECKLIST before I commit — domain, trademark gut-check, say-it-out-loud test, social handles. Don't fall in love with clever over clear.

Help me build a DIY escape room / puzzle hunt at home. For: {{kids' party / adults / date night / family}} Space & supplies: {{rooms available, what I have — paper, locks, household stuff}} Time to play & to set up: {{context}} — Theme: {{spy / mystery / treasure / spooky}} Design it: 1) THE STORY — a simple premise and goal that ties the puzzles together. 2) THE PUZZLE CHAIN — 5-7 puzzles where each solution leads to the next, using stuff I have (ciphers, hidden clues, riddles, physical tasks), matched to the players' age. 3) THE SETUP GUIDE — exactly where to hide/place each clue. 4) THE HINT SYSTEM — how to unstick players without spoiling it. 5) THE FINALE — a satisfying payoff. Difficulty tuned so they struggle but win. Momentum over impossible.

You are a children's activity designer with a gift for making ordinary houses adventurous. The crew: {{kids' ages}} Available: {{cardboard? blankets? craft box? just furniture?}} Adult energy level: {{full co-player / set-and-check-in / survival mode}} Time to fill: {{hours}} Design today's mission: 1. THE STORY — a mission theme with stakes ("the floor is lava rescue", "museum heist", "restaurant critics are coming"). Kids are the heroes; give each a role and title. 2. THREE PHASES — build phase, action phase, and a finale with a payoff (ceremony, feast, treasure). Each phase timed, matched to my energy level. 3. THE MATERIALS LIST — only from what I said we have. 4. THE TWIST — one surprise to deploy when energy dips ("a mysterious letter arrives…"). 5. CLEANUP AS GAME — the reset built into the story ("the museum must reopen!"). Age-adjust so everyone has a real job — nothing where the little one just watches.

You are an AI-art director who solves the consistency problem. My character: {{describe them — or paste the prompt that made a version you loved}} I'll be putting them in: {{storybook / brand mascot / comic / social posts}} Build the system: 1. THE CHARACTER SHEET — a locked description block covering: face & age markers, hair, build, signature outfit, palette (hex), art style, and the 2-3 quirky details that make them THEM. Written to paste at the start of every prompt. 2. THE SCENE TEMPLATE — "[character sheet] + [scene], [pose/emotion], [lighting], [style tags]" with two filled examples. 3. CONSISTENCY TACTICS — per tool: seed reuse and reference-image workflow for Midjourney ({{--cref}} if available), what to repeat verbatim vs. vary. 4. THE DRIFT CHECK — the 3 features that drift most across generations, and the extra words that pin each one. Give me the final copy-paste block.

You are a senior engineer giving me a guided tour of code I've never seen. Here's the code (structure + key files): {{paste directory tree and/or main files}} What I need to do here: {{the task that brought me}} Orient me: 1. THE 30-SECOND MAP — what kind of app/library this is and its architectural shape (MVC? pipeline? event-driven?). 2. ENTRY POINTS — where execution starts, where requests/inputs come in. 3. THE MONEY PATH — trace the single most important flow end to end, file by file. 4. FOR MY TASK — which files I'll touch, in what order, and which files LOOK relevant but aren't (say why). 5. THE LANDMINES — anything with global state, hidden side effects, or "do not touch without tests". End with: the first small, safe change I could make to test my understanding.

You are an interior designer who works with real rooms and real budgets. My room: {{size, windows, what's staying (bed, desk...), current vibe}} The feeling I want: {{calm? energizing? cozy? hotel-like?}} Budget reality: {{"paint and textiles" to "new furniture ok"}} Design it: 1. THE DIRECTION — name the style honestly achievable here, in two sentences. 2. THE FIVE MOVES — ranked by impact-per-cost: what to change first (usually: lighting, textiles, wall color, layout, one anchor piece). 3. PALETTE — 3-4 colors with where each goes (walls/textiles/accents), hex codes. 4. THE LAYOUT NOTE — one furniture-position change that makes the room feel bigger or calmer. 5. THE IMAGE PROMPT — a Midjourney/DALL-E prompt of MY room redesigned (my dimensions, my kept furniture, new direction) — interior photography style, natural light. Skip anything that requires a contractor.

Help me write a short, personal poem. For: {{person / occasion}} What I want to capture: {{a feeling, a memory, who they are}} Specific details about them/it: {{the more specific, the better}} Style: {{rhyming or free verse? playful or heartfelt?}} Write it: 1) Ground it in the SPECIFIC details I gave — a good personal poem could only be about THIS person. 2) Choose imagery over abstraction (show the thing, don't state the feeling). 3) If rhyming, keep it natural — no tortured lines to force a rhyme. 4) Keep it short and end on a line that lands. 5) Give me a free-verse and a rhyming version so I can pick. Specific and felt over generic and rhyming.

You are a root-cause facilitator. I brought a problem; you suspect it's a symptom. The problem as I see it: {{what keeps happening}} What I've already tried: {{attempts that didn't stick}} Facilitate: 1. Ask me "why does that happen?" — then WAIT for my answer. One why at a time, five levels deep. Push on vague answers ("it just does" isn't a cause). 2. At each level, note whether we've hit: a process cause, a people cause, or a structure/incentive cause. 3. When we reach bedrock, name THE REAL PROBLEM in one sentence and check: "if this were fixed, would the original symptom disappear?" 4. Flag the level where my previous fixes were aimed — and why they kept sliding off. 5. One fix at the root level: smallest change, biggest stick. Rule: causes are things that can be changed. "People are lazy" is never bedrock — keep digging.

You are a patient advocate who helps people use short medical appointments well. What's going on: {{symptoms, how long, what makes it better/worse}} My history that might matter: {{conditions, meds, family history}} What I'm worried it might be: {{say it — naming the fear matters}} The appointment: {{new issue? follow-up? how long}} Prepare me: 1. THE ONE-PAGER — my story organized as clinicians think: chief concern, timeline, what changes it, what I've tried, current meds. Chronological, specific ("6 weeks" not "a while"). 2. MY THREE QUESTIONS — ranked, so the important one gets asked first, including the direct version of my worry ("should we rule out X?"). 3. THE PHRASES — how to ask for what patients under-ask for: "what should make me come back sooner?", "what would you do if it were you?" 4. THE NOTES PLAN — what to write down before leaving (diagnosis words, next steps, red flags). This is preparation, not diagnosis — bring everything to the appointment.

You are a philosophy professor who believes you don't hold a view until you can defend its opposite. My position: {{what you believe about the issue}} The context: {{debate at work? essay? family dinner? deciding something?}} Run the exercise: 1. STEELMAN — the opposing view argued at full strength: its best evidence, its most reasonable version, the smart person's case for it. No strawmen, no "some people think". 2. THE STRONGEST POINT — the single opposing argument I most need an answer for. 3. MY POSITION, STRESS-TESTED — where my view held up, and where it needs repair or narrowing ("X is true, but only when Y"). 4. THE SYNTHESIS — is there a version incorporating the best of both? Or is this a true either/or? 5. If I'm debating: the respectful acknowledgment line that makes my counterpart actually listen. Do not just agree with me. If my position is weak, say so.

I'm moving to {{city}}. Help me land well in the first month. My situation: {{solo? family? remote work? knowing anyone there?}} What matters most to me: {{community? routine? exploring?}} Give me: 1) WEEK 1 ESSENTIALS — the boring-but-vital setup (admin, home basics, orienting) so life works. 2) THE ROUTINE ANCHORS — a few regular spots/habits to establish fast, because familiarity fights the disorientation. 3) MEETING PEOPLE — concrete ways to build a bit of community in a month (not 'join a club' — specific approaches for my situation). 4) THE EXPLORE LIST — how to learn the city without overwhelm, one area at a time. 5) THE LONELINESS PLAN — the hard weeks are normal; what helps. Feeling at home is built, not waited for.

Help me end a client relationship that's costing me more than it's worth. The situation: {{why — scope creep, low pay, disrespect, misalignment}} Contractual/practical ties: {{ongoing work, deposits, deadlines}} How much I want to preserve the relationship: {{burn it / stay cordial}} Give me: 1) THE TIMING & LOOSE ENDS — how to exit without leaving them (or me) in a mess: current deliverables, handoff, refunds if any. 2) THE MESSAGE — professional, kind, firm; states the end without a grievance list, offers a transition or referral if appropriate. 3) WHAT NOT TO SAY (the temptation to vent). 4) THE BOUNDARY/CONTRACT clause that prevents this type next time. Protect my reputation even as I leave.

Help me design a clean API before I lock it in. What it does & who calls it: {{internal service? public? a library?}} The main operations: {{list what callers need to do}} Constraints: {{stack, auth, versioning needs}} Design: 1) THE ENDPOINTS/SIGNATURES — named consistently, predictable, following the conventions of my ecosystem. 2) INPUTS & OUTPUTS — shapes, required vs optional, sensible defaults. 3) ERRORS — how failures are reported so callers can handle them. 4) THE FUTURE-PROOFING — what's likely to change, and how to design so v2 doesn't break v1 callers. 5) THE SMELL CHECK — anything here that'll be painful to live with. Prioritize caller experience over implementation convenience.

Help me use inversion on this. What I'm trying to achieve: {{the goal}} Where I'm stuck: {{context}} Do this: 1) INVERT IT — instead of 'how do I succeed?', ask 'how would I GUARANTEE failure here?' List the surest ways to wreck this. 2) THE AVOID LIST — turn each failure mode into a thing to actively prevent. 3) THE ALREADY-HAPPENING ones — which of these failure behaviors am I unknowingly doing right now? Be direct. 4) THE HIGH-LEVERAGE FIX — the one avoidance that matters most. 5) NOW forward — with the traps cleared, the simplest positive path. Sometimes avoiding stupidity beats seeking brilliance.

You are a family financial educator. My kid: {{age}} What prompted this: {{allowance? they want something? a teachable moment?}} Give me: 1) THE CONCEPT to focus on at their age (needs vs wants / saving / earning / delayed gratification — pick what fits). 2) HOW TO EXPLAIN IT in words they'll get, with an analogy from their world. 3) ONE ACTIVITY we can actually do this week (a jar system, a small earning task, a saving goal). 4) THE MISTAKE parents make here to avoid. 5) What this sets up for the next stage. Keep it playful, not preachy.

Help me write a parody of a well-known song. The original song: {{title & artist}} What the parody is about: {{person / team / occasion / inside jokes}} Key facts/jokes to work in: {{list them}} Do this: 1) MATCH THE METER — keep the parody lyrics singable to the original's rhythm and rhyme, verse by verse (this is what makes it work). 2) WEAVE IN the specific jokes/facts naturally, not forced. 3) Nail the CHORUS — the most memorable, most personalized part, since that's what everyone will sing. 4) Keep it clean/appropriate for {{the audience}}. 5) Mark the tune's section (verse/chorus) so I know where each part goes. Singability over cleverness that doesn't scan.

Help me get my first (or next) hire right. My situation: {{what the business does, where I'm stretched thinnest}} Budget & commitment: {{full-time? contractor? equity?}} Work through: 1) THE REAL ROLE — based on where I'm most bottlenecked, what should this person actually own (not a generic title)? 2) MUST-HAVE vs. NICE — the 2-3 things they must be genuinely great at, and what I can train. 3) THE RED FLAGS for this role specifically. 4) FIVE INTERVIEW QUESTIONS that reveal whether they can actually do the job (behavioral, not trivia), with what a great answer sounds like. 5) THE TEST TASK — a small paid trial that shows more than any interview. Hire for the bottleneck, not the org chart.

You are an open-source maintainer who knows a README is a landing page. My project: {{what it does, paste code structure or description}} Who lands here: {{beginners? teammates? potential users?}} Write the README: 1. ONE-LINER — what it does + who it's for, no jargon, under 15 words. 2. THE BEFORE/AFTER — the pain without it, the result with it (code or bullets). 3. QUICKSTART — the genuinely minimal path to first success, tested-looking, with expected output shown. 4. ONE REAL EXAMPLE — the most common use case, complete and copy-pasteable. 5. HONEST LIMITS — what it doesn't do / when not to use it. 6. Contributing + license, two lines. No badges wall, no table of contents for a 2-screen file, no "blazingly fast".

Give me a gentle, genuinely funny roast. About: {{me / a friend — name and relationship}} Their lovable flaws & running jokes: {{the quirks, habits, famous incidents}} The setting: {{birthday toast / just for fun / a card}} — How savage can I go? {{gentle / medium}} Write it: 1) 4-5 roast lines that are specific to THEM (not generic 'you're old' jokes) — the humor comes from the true detail. 2) Build to one bigger bit. 3) THE PIVOT — end warm, turning the roast into genuine affection (the best roasts are love in disguise). 4) Keep it kind — nothing that actually wounds or touches real insecurities. Specific and affectionate over mean and generic.

Help me choose between technical options without hype. The decision: {{e.g. Postgres vs Mongo, Next vs Remix, this library vs that}} My actual constraints: {{team skills, scale, timeline, existing stack, budget}} What matters most: {{speed to ship? scale? maintainability? hiring?}} Give me: 1) A short honest comparison against MY constraints — not a generic feature table. 2) THE DECIDING FACTOR — the one or two things that should actually drive this for me. 3) YOUR PICK and why, plus the strongest case for the runner-up. 4) THE REVERSIBILITY — how hard is this to change later? (Cheap-to-reverse decisions deserve less agonizing.) 5) The trap people fall into with this choice.

Help me prompt cover art. For: {{album / book / podcast / single}} — Title: {{if any}} The mood/genre & what it's about: {{context}} Style references I like: {{artists, eras, aesthetics}} Build: 1) THE CONCEPT — one strong visual metaphor for the mood, not a literal illustration of the title. 2) COMPOSITION — designed to leave room for title text and to read at thumbnail size (where most people see it). 3) THE PROMPT with style, palette, mood, and square aspect. 4) THREE DIRECTIONS — minimal, bold/graphic, and atmospheric. 5) THE THUMBNAIL TEST — does it still hit at 200px? Iconic over busy.

You are an automation-minded ops person. Here's a repetitive task eating my time: {{describe it — steps, how often, tools involved}} Analyze: 1) WHICH PARTS are automatable vs. genuinely need a human. 2) THE SIMPLEST FIX FIRST — a template, a saved reply, a keyboard shortcut, a filter — before any fancy tool. 3) THE REAL AUTOMATION — the specific tool/feature (spreadsheet formula, Zapier-style trigger, built-in rule) and the setup steps. 4) TIME SAVED per week, and whether the setup is worth it. Don't send me building something complex when a template would do.

I already code. Get me productive in {{new language}} fast. Languages I know well: {{list}} What I need to build in it: {{context}} Give me: 1) THE MAP — what transfers directly from what I know, so I don't relearn basics. 2) THE GOTCHAS — where my instincts from {{known language}} will actively mislead me (memory, types, concurrency, error handling). 3) THE IDIOMS — the 5-6 things that make code look native here vs. translated-from-my-old-language. 4) A TINY PROJECT that forces me through the core concepts, with what to notice. 5) The one tooling/setup thing that trips up newcomers. Skip 'what is a variable.'

Check my reasoning for bias. What I believe / how I'm reasoning about it: {{lay out your thinking on the topic or decision}} Do this: 1) THE LIKELY BIASES — which cognitive biases might be distorting this (confirmation, sunk cost, recency, anchoring, motivated reasoning, overconfidence...) and WHERE specifically in my reasoning each shows up. 2) THE STEEL-MAN of the view I'm dismissing. 3) THE MISSING EVIDENCE — what would I look at if I actually wanted the truth vs. to be right? 4) THE CLEANER TAKE — how the reasoning looks with the biases corrected. Be direct — I asked for this because I want the blind spot, not comfort.

Help me name things in my code better. The names I'm unsure about (with a line on what each does): {{paste variables / functions / files}} Language & conventions: {{context}} Do this: 1) RENAME each — clearer, following my language's conventions (camelCase/snake, etc.), revealing intent not implementation. 2) THE WHY for each change in a few words. 3) THE SMELLS — names that hint at a deeper problem (a function named with 'and' is doing two things; a boolean named badly inverts logic). 4) THE PRINCIPLE — the one naming rule I'm breaking most, so I fix it everywhere. Good names remove the need for comments.

Help me prompt a portrait of a character. Who they are: {{age, vibe, role, personality}} Style I want: {{realistic / painterly / anime / 3D / etc.}} Use: {{story / game / avatar / just for fun}} Build: 1) THE DESCRIPTION BLOCK — face and age markers, hair, expression, clothing, palette, the 2-3 details that make them THEM. 2) THE MOOD — lighting and setting that convey their personality. 3) THE FULL PROMPT in [subject], [appearance], [expression/mood], [setting/lighting], [style tags], [aspect] form. 4) VARIATIONS — three emotions or angles. 5) THE CONSISTENCY TIP — what to keep verbatim so future images match. Make the personality visible, not just the features.

Help me outline a {{length}} webinar/workshop. Topic & audience: {{context}} What I want them to do after: {{learn something / buy / book a call}} Build the arc: 1) THE HOOK (first 3 min) — why this, why now, the promise of what they'll leave with. 2) THE ONE BIG IDEA — the shift I want them to make. 3) THREE TEACHING BLOCKS — each a point + example + a small 'try it now' so it's not a lecture. 4) THE SOFT ASK — how to invite the next step as the natural conclusion of the value, not a bolted-on pitch. 5) Q&A prompts to seed if the room is quiet. Mark where people usually drop off and how to hold them.

You give balanced rent-vs-buy analysis, not dogma. Education only. My situation: {{city, rough rent vs. likely mortgage, how long I'd stay, savings for a down payment, job stability}} Reason it out: 1) THE TRUE COST OF BUYING — not just mortgage: taxes, maintenance (~1%/yr), insurance, closing costs, the opportunity cost of the down payment. 2) THE TRUE COST OF RENTING — including that rent buys flexibility and zero maintenance. 3) THE BREAK-EVEN — roughly how long I'd need to stay for buying to win here. 4) THE NON-MONEY FACTORS for my life. 5) A clear lean for MY situation, with the assumption that would flip it.

You are a brand creative director translating feelings into visual direction. My brand: {{name, what it does}} Personality: {{3-5 adjectives}} Loved logos: {{2-3 brands whose look you admire, and why if you know}} Absolute nots: {{colors/styles you refuse}} Develop three directions: For each — a name (e.g., "Quiet Confidence"), the concept in two sentences, shape language (geometric/organic, sharp/soft), a 3-color palette with hex codes and the feeling each carries, type suggestion (category + example font), and where it shines / where it risks falling flat. Then: write the image-generation prompt for direction #1 (flat vector style, single mark, white background) AND the one-paragraph brief I'd send a human designer. Honest note: which direction is trendy-now-dated-in-3-years, if any.

Help me plan a party I'll actually enjoy hosting. The occasion & vibe: {{what & the feeling}} Guests: {{how many, who}} — Budget & space: {{context}} My hosting energy: {{love it / nervous / first time}} Plan it: 1) THE VIBE in one line, so every choice serves it. 2) THE FOOD/DRINK plan — realistic amounts, what I can prep ahead, one thing I don't have to make myself. 3) THE FLOW — a loose timeline (arrival, peak, wind-down) and how to handle the awkward early bit. 4) THE HOST-FORGETS list — the details people miss (drinks accessible, music, a spot for coats, one activity if energy dips). 5) THE PREP TIMELINE — what to do the week before, day before, hour before, so I'm not frazzled when guests arrive. Prep so I can be present.

Help me write an image prompt for a product mockup. My product: {{what it is, key visual features}} Where it'll be used: {{listing / hero / deck}} — Vibe: {{3 adjectives}} Give me: 1) THE SHOT PLAN — angle, surface/setting, lighting, what's in focus, one styling detail that signals the vibe. 2) THE PROMPT — built from that, in the structure [subject + detail], [setting], [lighting], [camera language], [style], [aspect ratio]. 3) THREE VARIATIONS — clean/minimal, lifestyle/in-use, and bold/editorial. 4) THE FIX-ITS — what to change if the result looks too flat, too busy, or fake. Optimize for 'I'd click buy', not 'pretty'.

Help me analyze a competitor to find my opening. The competitor: {{name / describe them}} What I know about them: {{their offering, pricing, positioning, reviews}} My business: {{what you do}} Analyze: 1) THEIR STRENGTHS — what they genuinely do well (don't underestimate them). 2) THEIR WEAKNESSES — where customers complain, what's clunky, who they underserve. 3) THE GAP — the specific customer or need they're ignoring that I could own. 4) THE TRAP — don't just copy them; where would matching them be a losing game? 5) MY WEDGE — the sharpest angle to differentiate, in one sentence. Base it on their actual customers' complaints, not vibes.

Help me develop a short story. My seed: {{a line, a character, an image, a 'what if', or just a mood}} Length & tone I'm after: {{flash fiction? a few pages? funny? literary? genre?}} Develop it: 1) THE PREMISE — sharpen my seed into a one-line hook with inherent tension. 2) THE CHARACTER — who, and what they want vs. what's in the way (the engine of any story). 3) THE SHAPE — a loose beat outline: opening image, the turn, the complication, the ending that pays off the opening. 4) THE ENDING OPTIONS — two directions (one expected, one that subverts). 5) A killer FIRST LINE to start from. Give me the scaffold; I'll write the prose — unless I ask you to draft it.

Help me build a real customer persona, not a generic template. My product/service: {{what it is}} Who's bought or shown interest: {{whatever you know — even a hunch}} Build it: 1) THE SPECIFIC PERSON — one representative buyer with a name, situation, and the moment they realize they need something like mine. 2) THE PROBLEM in THEIR words — how they'd describe their pain (which becomes my marketing copy). 3) THEIR DAY & CONTEXT — where they are, what they're juggling, what they've already tried. 4) THE OBJECTIONS — why they'd hesitate to buy, and the honest answer to each. 5) WHERE THEY ARE — channels to actually reach this person. 6) THE ANTI-PERSONA — who I should NOT try to serve. Specific beats 'small business owners aged 25-55.'

Help me define my brand (or personal) voice so my writing is consistent. What I do & who I talk to: {{context}} Brands/creators whose voice I admire: {{2-3, and why}} Words that should NEVER describe me: {{e.g. corporate, salesy}} Produce: 1) THREE VOICE TRAITS, each with a one-line definition (e.g. 'Warm but not soft'). 2) A DO / DON'T table for each trait. 3) SIGNATURE MOVES — sentence habits, punctuation, words we favor and avoid. 4) BEFORE/AFTER — take one boring sentence and rewrite it in my voice. 5) A 'voice check' question I can ask of any draft.

Let's debate to sharpen my thinking on {{topic/question}}. My position: {{what you believe}} Rules: 1) You take the strongest version of the OPPOSING side — no strawmen. 2) Make your best argument, then let me respond. 3) When my response is weak or vague, name exactly where and press there. 4) Concede points I genuinely win — model honest debate. 5) After 3-4 rounds, step out of character: tell me where my reasoning was strongest, where it wobbled, and the one thing that would make my position more defensible. Play to make me better, not to win.

Help me think about this from first principles, not by analogy. The problem or thing I want to rethink: {{describe it}} How it's 'normally' done: {{the conventional approach}} Strip it down: 1) THE FUNDAMENTALS — what do we know to be actually true here, beneath the conventions? Break it to the base facts. 2) THE INHERITED ASSUMPTIONS — which parts of the 'normal' way are physics/reality vs. just tradition, habit, or 'because that's how it's always been'? Separate them. 3) THE REBUILD — starting only from the fundamentals, what would I design if the conventions didn't exist? 4) THE REALITY CHECK — which conventions exist for good reasons I shouldn't discard, and which are just cruft. 5) THE INSIGHT — the non-obvious move first-principles reveals. Question the 'obviously' before accepting it.

Design a tabletop RPG one-shot I can run (or that you run for us). System/vibe: {{D&D-style fantasy / sci-fi / cozy / horror-lite}} Players: {{how many, experience level}} — Time: {{hours}} Tone: {{heroic? funny? spooky? all-ages?}} Build it: 1) THE HOOK — a one-paragraph setup that drops them into action fast. 2) THREE SCENES — a social one, a puzzle/exploration one, and a climax, each with what could go right or wrong. 3) MEMORABLE NPCs — 3 with a quirk and a want, easy to voice. 4) THE TWIST — one surprise that recontextualizes things. 5) FLEX POINTS — how to speed up or stretch to fit our time, and what to do if players go off-script. Fun and momentum over rules-lawyering.

Help me prompt a set of icons that look like a family. What the icons represent: {{list the concepts}} Style: {{line / filled / flat / 3D / duotone}} — Where used: {{app / deck / site}} Build: 1) THE STYLE SPEC — stroke weight, corner style, fill approach, color, level of detail — the rules EVERY icon must follow to match. 2) THE SHARED PROMPT SKELETON — the fixed style part I paste for each, plus the [concept] slot. 3) THE PER-ICON PROMPTS for my list, each using the skeleton. 4) THE CONSISTENCY CHECK — what to verify across the set (weight, size, perspective). 5) The concept that's hardest to make match and how to handle it. Consistency over cleverness.

You are an exam strategist. Help me maximize my score, not just my knowledge. The exam: {{format — MCQ, essay, mixed; length; topics; how it's scored}} My strong & weak areas: {{honest}} Coach me: 1) TIME BUDGET — how to allocate minutes across sections given the marks, and the pace to hit. 2) THE ORDER — do I do easy-first for momentum and to bank points? 3) STUCK STRATEGY — what to do on a question I don't know (eliminate, flag-and-return, partial credit for showing work). 4) THE UNFORCED ERRORS — where students lose points they'd earned (misreading, running out of time, blank answers) and how to avoid each. 5) The night-before and morning-of plan. Assume I've studied — this is about execution.

Help me prompt a photorealistic scene. The scene: {{describe it}} Mood & time of day: {{context}} Use: {{background / stock-style / concept}} Build: 1) THE CAMERA LANGUAGE — camera/lens type, aperture/depth of field, angle, that photographers use to get realism. 2) THE LIGHT — quality, direction, source, time of day (this is what sells 'real'). 3) THE PROMPT combining subject, setting, camera, light, and film/rendering style. 4) THE AI TELLS to avoid — the words/combos that make it look fake or over-rendered, and what to write instead. 5) One variation with different light. Prioritize believable over dramatic.

You explain personal taxes clearly for a non-expert. This is education, not filing advice. My situation: {{country, employment type, rough income, big life stuff — kids, home, side income}} Explain: 1) HOW MY TAX ACTUALLY WORKS — brackets vs. effective rate, what 'moving up a bracket' really means (spoiler: not what people fear). 2) WHAT'S TAXED vs. not in my situation. 3) THE LEGIT LEVERS — common deductions/credits/accounts I might be missing, in plain terms. 4) THE QUESTIONS to bring to a tax pro to make that hour count. Flag clearly where rules vary and a professional should confirm.

You are a reflective coach running my annual review. Interview me — one question at a time, waiting for each answer. Cover, in order: 1. THE ENERGY AUDIT — what gave me energy this year, what quietly drained it (people, projects, habits). 2. THE REAL WINS — including ones I haven't given myself credit for. Push me on this; humans under-count. 3. THE PATTERN — reading my answers, name one pattern I probably can't see (be direct). 4. THE SUBTRACTION — what to STOP in the new year. At least one thing, named specifically. 5. THREE COMMITMENTS — sized to survive February: one habit, one project, one relationship. Each with a first step scheduled in week one. Then write "the letter" — 150 words from me-in-December-next-year, describing the year where the three commitments held. Present tense.

Help me decide whether to refactor this now. The code that bothers me: {{paste it}} Context: {{how often it changes, how central it is, deadline pressure}} Judge honestly: 1) IS IT ACTUALLY BAD, or just unfamiliar/ugly-but-fine? Be real. 2) THE COST of leaving it — bugs, slowdowns, onboarding pain — weighted by how often this code is touched. 3) THE COST of refactoring now — time, risk of new bugs, opportunity cost. 4) THE VERDICT — refactor now, refactor-when-you-next-touch-it, or leave it alone. 5) If refactoring: the smallest safe first step and the test to add first. Don't tell me to gold-plate code nobody touches.

Help me do rough expected-value thinking on a risky decision. The choice: {{option A vs option B, or do-it vs don't}} The possible outcomes & my rough sense of their odds: {{describe, guesses are fine}} Work it: 1) LAY OUT the outcomes for each option, with a rough probability and a value (money, time, happiness — whatever fits) for each. 2) THE NAPKIN EV — weight outcomes by odds to compare options, roughly. Show the math simply. 3) THE ASYMMETRY — is there a small-downside/huge-upside (or the reverse) that matters more than the average? 4) THE RUIN CHECK — any outcome so bad I can't recover, that I should avoid regardless of EV? 5) THE CALL, and the assumption most likely to flip it. Numbers to inform the gut, not replace it.

Help me test a pricing change safely. Current price & what I'm considering: {{from X to Y, or new tier}} Why: {{underpriced? new value? margin pressure?}} My business: {{product, customer type, volume}} Design the experiment: 1) THE HYPOTHESIS — what I believe will happen, specifically. 2) THE SAFE TEST — new price for new customers only? A/B on a segment? A grandfather clause for existing ones? Pick the lowest-risk way to learn. 3) THE METRICS — not just conversion: revenue per visitor, churn, support complaints. What result means 'raise it', 'hold', 'revert'. 4) THE DURATION — long enough to be real, short enough to bail. 5) THE ROLLBACK plan if it tanks. Protect existing revenue while you learn.