Don't know how to ask Claude? Start here.

Look at my website at [URL]. Tell me: (1) what you can tell about my product in 30 seconds, (2) the top 3 things that aren't clear, (3) the headline I should A/B test against, (4) one removable section that adds no value.

Compare my product (described in my knowledge base) to [Competitor URL]. Find: their pricing tiers, their target audience, the 3 features they brag about most, the 3 features I have that they don't. Output a positioning doc I can use to sharpen my pitch.

Research the [INDUSTRY] market right now. Output: (1) 5 biggest players and their positioning, (2) 3 emerging entrants worth watching, (3) the dominant business model and pricing range, (4) the 2 most underserved segments, (5) one thesis I should test.

Read the top 50 posts of the last month on r/[SUBREDDIT]. Extract: (1) the 5 most painful complaints, (2) the 3 products users keep recommending, (3) the language they use when describing what they wish existed. Format as quotes + frequency counts.

Write a 7-tweet launch thread announcing [feature/product]. Hook in tweet 1 must contain a specific number or contrarian claim. Tweets 2-6 each prove a single point with a tiny example. Tweet 7 is the CTA. Use my brand voice from the knowledge base.

Draft this week's newsletter on [TOPIC]. Format: punchy 1-line subject + 1-line preview, opening hook (40 words), 3 short sections with subheads, 1 link round-up of 3 reads, 1 CTA. Voice: warm, opinionated, no fluff. 450 words max.

Write a LinkedIn post about [TOPIC]. Hook line breaks on its own line. Use 2-3 line paragraphs. End with a single open-ended question. No hashtags or emojis. Under 250 words. Voice: confident, lived-in, no buzzwords.

Write a 60-second YouTube Short script on [TOPIC]. Format: [HOOK 0-3s] [PAYOFF 3-15s] [PROOF 15-45s] [CTA 45-60s]. Spoken style, not written. One idea per line. Add visual cue notes in [brackets].

Outline a 1500-word blog post on [TOPIC] for [AUDIENCE]. Include: working title with a number or contrarian claim, 1-line thesis, 5-7 H2 sections with 2-3 H3 sub-points each, 3 example anecdotes I can flesh out, the SEO keyword cluster.

Take [BLOG POST URL or paste]. Repurpose it into: (1) a LinkedIn post, (2) a 4-tweet thread, (3) a 60-second video script, (4) an email teaser, (5) 3 quote graphics. Keep the original idea but make each format native.

Draft 10 cold emails to these prospects: [paste list]. For each: subject line under 50 chars, opening line referencing something specific to their company (no 'I see you...'), body in 90 words max ending with a soft yes/no question. Use the value props from my knowledge base.

Design a 5-touch follow-up sequence after a cold email to [PROSPECT TYPE]. Spaced: day 0, 3, 7, 14, 21. Each touch <80 words, each unique angle (helpful resource / case study / question / breakup / soft re-open). No begging.

Draft a reactivation email for a user who hasn't logged in for 60+ days. Subject under 45 chars. Body: acknowledge time passed without guilt-tripping, surface ONE specific change they'd care about, single 1-click CTA. 100 words max.

Draft a partnership pitch email to [COMPANY/PERSON]. Format: 1-line credibility intro, 1 sentence on why them specifically, the win/win in 2 lines, the exact ask (call? intro? co-marketing?). 130 words max. Skip pleasantries.

I have a discovery call with [Company] tomorrow. Their site says [paste]. Generate 8 Josh-Braun-style permission-based discovery questions. Group them: situation (3), problem (3), implication (2). Format as a single page I can print.

I keep hearing this objection: '[OBJECTION]'. Give me 3 different reframes (validate, then redirect), 2 questions to draw out the real concern beneath it, and 1 walk-away line for when it's not a real objection.

I just demoed [PRODUCT] to [CONTACT NAME] at [COMPANY]. Their concern was [CONCERN], they liked [POSITIVE]. Draft a follow-up email that recaps in 3 bullets, addresses the concern with a specific resource, proposes a clear next step with a calendar link.

[CUSTOMER] is about to cancel. Their stated reason: [REASON]. Build me a 15-minute save-call script: openings that disarm, 4 questions to find the real reason, 3 retention offers ranked by margin impact, the line that asks for the save.

Generate my weekly review memo for the week of [DATE]. Include: 3 wins, 3 losses, 3 recommendations for next week, 1 single takeaway. Pull from my recent deployments + missions. Tone: blunt, not corporate.

I'm pricing [product] at $[X]/mo for [Y]. Tell me: (1) anchors comparable products use, (2) the price psychology this pivots on, (3) 3 tiers I should offer, (4) the ONE feature I should gate behind the highest tier so it forces upgrades.

Draft my [Month Year] investor update. Pull from: revenue + key metrics in my knowledge base, the deployments + missions from this month, the recent recommendations. Format: highlights, lowlights, asks, lessons learned. 600 words max.

My one goal this quarter is [GOAL]. Convert it into 1 Objective + 3 Key Results. KRs must be measurable, time-bound, ambitious-but-not-fantasy. Output: each KR with the metric, the baseline, the target, and the lead indicator I'd watch weekly.

I made [BET / DECISION] [TIMEFRAME] ago. Outcome was [OUTCOME]. Walk me through a postmortem: (1) what I expected, (2) what actually happened, (3) which assumption was wrong, (4) the cheapest experiment that would have surfaced this earlier, (5) the rule for next time.

Summarize the document I just uploaded into my knowledge base. Output: (1) one-sentence TLDR, (2) 5 key takeaways as bullets, (3) the 3 quotes worth remembering, (4) what action I should take after reading.

I uploaded [DOC A] and [DOC B] to my knowledge base. Where do they agree? Where do they directly contradict? Which one is more rigorous, and why? End with the synthesis line that I should remember.

From [BOOK NAME] in my knowledge base, extract every named framework, model, or step-by-step playbook. For each: 1-line definition, the situation it applies to, the page reference if available. Format as a reference card I can re-read in 60 seconds.

Review the diff at [GitHub PR URL]. Categorize feedback: blockers (must fix before merge), nits (style), suggestions (would be better). Be ruthless about correctness, lenient about style. Output as a markdown checklist.

I'm seeing this bug: [SYMPTOMS]. Stack trace: [PASTE]. Last thing I changed: [CHANGE]. Walk me through binary-search debugging: 5 hypotheses ranked by likelihood, the smallest test that would falsify each one, and where to add logging.

I want to build [FEATURE]. Constraints: [CONSTRAINTS]. Listen to my approach: [PASTE]. Then poke holes: 3 edge cases I missed, 2 cheaper alternatives, 1 thing I might be over-engineering. Be honest, not nice.

Read the diff: [PASTE]. Write a Conventional Commits message. Title under 72 chars. Body explains the why and the trade-offs, not the what. Add a BREAKING CHANGE footer if there is one. Stay under 5 lines for the body.

Explain this query: [PASTE]. Break down: (1) what each CTE/subquery does, (2) the join order in plain English, (3) the indexes that would help, (4) the obvious thing it's missing if any.

I have a meeting with [Person] from [Company] at [TIME] about [TOPIC]. Pull what we know about them from my knowledge base + recent emails (search the inbox). Output: (1) the one outcome that makes this meeting a win, (2) 3 questions I should ask, (3) 2 things to NOT bring up.

Look at the last 50 emails in my inbox. For each, output one of: REPLY (with a draft 1-liner), ARCHIVE (no action needed), SCHEDULE (add to calendar), DELEGATE (suggested owner). Don't moralize about the volume.

Here's everything in my head right now: [BRAIN DUMP]. Sort it into: (1) the ONE thing that matters most today, (2) 3 must-dos, (3) up to 3 nice-to-dos, (4) the 'don't even start today' list. Add time estimates for the must-dos.

I'm deciding between [OPTION A] and [OPTION B]. Stake: [STAKE]. Reversibility: [HIGH/LOW]. Walk me through: (1) the criteria that matter, weighted, (2) how each option scores on each, (3) the regret-minimization version of the answer, (4) what cheap test I could run before committing.

Read these messy meeting notes: [PASTE]. Extract: (1) decisions made (with the deciders), (2) action items with owner + due date, (3) open questions still unresolved, (4) the one thing the team forgot to discuss but should have.

A customer wrote: [paste their message]. They sound [angry/confused/frustrated]. Draft a reply that acknowledges their feeling, gives a clear answer, and ends with the next concrete action. Tone: empathetic but not groveling. Under 120 words.

We've answered this question 6 times: [QUESTION]. Write a help-center article. Format: 1-line TLDR, 'when this happens' section, step-by-step fix with screenshots-todo notes, 'still stuck?' section with the escalation path. Skim-friendly headings.

An angry customer wrote: [PASTE]. They're threatening [chargeback/social media/lawyer]. Draft a reply that: validates the specific thing they're upset about (no generic 'I understand'), takes ownership of what we got wrong, offers a concrete remedy with a deadline, and leaves a door open. Under 150 words.

Write a thank-you note to [PERSON] for [SPECIFIC THING THEY DID]. Be specific about the impact, not generic. 80 words max. Voice: warm, slightly casual, no business-speak.

Write me a 2-minute wedding toast for [BRIDE/GROOM] - my [RELATION]. Include: 1 short funny story, 1 sincere observation about who they are, 1 line about [PARTNER NAME] that's about both of them. End with a toast line. No clichés ('on this special day').

I need to tell [PERSON] [DIFFICULT MESSAGE]. Our relationship is [RELATIONSHIP]. Help me draft it: name the thing without softening it into mush, take ownership where I should, leave space for their reaction. Under 200 words. Don't add an apology if I shouldn't apologize.

Write a birthday message for [PERSON]. Things they care about: [INTERESTS]. Recent thing they did: [RECENT]. Make it feel like only I could have written it - no 'have a great year!' platitudes.

I need a name for [THING]. It does [WHAT IT DOES]. Adjectives I want: [ADJECTIVES]. Adjectives to avoid: [AVOID]. Output 20 candidates in a table: name, the feeling it evokes, one downside. Mix one-word, two-word, made-up, and metaphor names.

Help me build the narrative arc for [STORY/PITCH/TALK]. Use: setup, complication, resolution structure. For each phase give me 1 sentence. Then suggest 3 different endings - one safe, one bold, one weird.

I have this idea: [IDEA]. Help me see it from 5 different angles: (1) the skeptic's, (2) the customer's, (3) the competitor's, (4) the 10-years-from-now version, (5) the 'what if the opposite were true' version. One paragraph each.

Explain [CONCEPT] in language an 8-year-old would understand. Then explain it like I'm a college student. Then explain it like I'm an expert in an adjacent field. Spot the metaphor that's actually misleading.

I want to learn [SUBJECT]. Time available: [HOURS PER WEEK]. Goal: [OUTCOME]. Build me an 8-week plan: weekly themes, 1 primary resource per week, 1 weekly project, the test I should set myself at week 4 and week 8 to know I'm progressing.

Make 20 spaced-repetition flashcards from this material: [PASTE / DOC]. Format: [Question | Answer] one per line. Test recall, not recognition. Mix factual, conceptual, and applied questions.

I believe [OPINION]. Steelman the strongest case against this view - the version a smart honest opponent would actually argue. Then identify which 1-2 of those points actually deserve to update my belief.

My resume: [PASTE]. The job I'm applying to: [PASTE JD]. Rewrite my top 3 bullets to mirror their language without lying. Identify 1-2 missing skills I should mention if I have any experience. Suggest a 30-word personalized opener for the cover letter.

I have an interview at [COMPANY] for [ROLE]. Generate 6 likely behavioral questions. For each, suggest a STAR-format answer slot tied to my experience: [PASTE 3-5 EXPERIENCES]. End with 3 questions I should ask them.

They offered me [OFFER]. Market range: [RANGE]. My leverage: [OTHER OFFERS / NONE]. Write me 3 versions of the counter: (1) ambitious-and-warm, (2) moderate-and-firm, (3) safe-and-grateful. Each under 120 words. Anchor on numbers, not feelings.

A recruiter messaged me about [ROLE/COMPANY]. I am [INTERESTED / PASSIVELY OPEN / NOT INTERESTED]. Draft a reply that opens the door (or politely closes it) without burning the relationship. Under 80 words.

Build me a 4-week workout program. Goal: [GOAL]. Days available: [DAYS]. Equipment: [EQUIPMENT]. Experience level: [LEVEL]. Output a weekly grid + each day has the exercises, sets x reps, and a 1-line cue for form. Add a deload note for week 4.

Plan 7 days of meals for [PEOPLE]. Constraints: [DIETARY/CALORIE/BUDGET]. Output: shopping list grouped by aisle, a daily plan with prep time per meal, and 2 leftover-friendly meals. Keep it boring; we want adherence, not novelty.

My sleep has been [SYMPTOMS] for [DURATION]. Recent context: [STRESS/TRAVEL/CAFFEINE/SCREENS]. List 5 hypotheses ranked by likelihood, the cheap test for each (do for 5 days), and the bright line where I should see a doctor instead of optimizing.

Plan a [LENGTH] trip to [DESTINATION] for [PEOPLE]. Vibe: [VIBE - relaxed/adventure/foodie/family]. Budget: [BUDGET]. Output: daily plan with morning + afternoon + evening blocks, 1 reservation worth booking now, 1 thing tourists do that I should skip, and the local rule of thumb that saves money.

I'm in [NEIGHBORHOOD/CITY] tonight with [PEOPLE]. Mood: [HUNGRY/CELEBRATING/CASUAL]. Budget: [$/$$/$$$]. Pick me 3 spots: top choice + 1 backup + 1 wildcard. For each: why it fits, what to order, and the one thing to avoid.

Here's my last month of spending categorized: [PASTE]. Find: (1) the 3 categories I overspent on vs typical, (2) the 1 sneaky line item that adds up but feels small, (3) one structural change I should make, (4) the savings rate I'm actually hitting.

Explain [CONCEPT - 401k vs IRA / HSA / index funds / etc.] to me as if I have $X to deploy and live in [COUNTRY/STATE]. Skip the disclaimers; assume I understand this is general info. Give me the 80/20 rule + the most common mistake people make.

I need to give [PERSON - report/peer/boss] feedback on [ISSUE]. Their response style: [STYLE]. Help me draft it: 1 sentence on the situation, 1 sentence on the specific behavior, 1 sentence on the impact, 1 question opening dialogue. Direct, not cruel.

Convert this messy update [PASTE] into the standup format: yesterday / today / blockers. Cut hedging language. If I said 'mostly done', say what's left. If there's no real blocker, say 'none'.