Prompt Library

You are my strategic thinking partner. I'm the CEO of [company description]. Here's my current situation: [describe context]. I need to make a decision about [topic]. Don't validate my thinking — challenge my assumptions. Ask me the questions I'm not asking myself.

Explain [concept] to me like I'm a smart businessperson who has never studied this field. Use analogies from running a business. No jargon. If there are multiple schools of thought, tell me which one is most practical.

I'm about to start a complex project with Claude. Here's what I need to accomplish: [goal]. Here are all the documents and context I have: [list them]. Help me decide: 1) What context is essential vs. nice-to-have, 2) What order to provide information, 3) Whether I should use one long conversation or break into multiple sessions.

This prompt isn't giving me good results: [paste your prompt]. The output I'm getting: [describe the problem]. What I actually want: [describe ideal output]. Rewrite my prompt to get better results, and explain what was wrong with the original.

I need help choosing between Claude Chat, CoWork, and Code for this use case: [describe what you want to do]. My technical level: [beginner/intermediate/advanced]. My team size: [number]. How often I'll do this task: [frequency]. Which product should I use and why?

Help me build a prompt using the RCTFC framework. Here's what I need: [describe task]. Walk me through each element: 1) Role — who should Claude be? 2) Context — what background is needed? 3) Task — what specifically should it do? 4) Format — how should the output look? 5) Constraints — what should it avoid? Then combine them into one clean prompt I can copy.

I want to set up a Claude Project for [use case]. I'll be using this [frequency]. The key documents I have: [list documents]. Help me: 1) Write the project instructions, 2) Decide what goes in project knowledge vs. conversation, 3) Create a starter prompt I can reuse each session.

I need to choose the right Claude model for this task: [describe task]. Key factors: Speed matters: [yes/no]. Accuracy is critical: [yes/no]. I'll run this [frequency]. Cost sensitivity: [high/medium/low]. Recommend Opus, Sonnet, or Haiku and explain the trade-off.

I'm about to share the following information with Claude: [describe what you'll share]. My industry: [industry]. Compliance requirements: [any regulations]. Review this for security concerns: 1) Is any of this too sensitive to share? 2) What should I redact or anonymize? 3) What's my risk level? 4) Any compliance issues?

I have a complex task that will require multiple back-and-forth exchanges: [describe task]. Help me plan the conversation: 1) What's the best opening prompt? 2) What follow-up questions should I expect to answer? 3) Where should I course-correct if it drifts? 4) What's the ideal number of turns? Map out the conversation flow.

I need Claude to output in a very specific format. Here's an example of what the output should look like: [paste example]. Now here's my actual request: [describe what you need]. Generate the output matching that exact format — same structure, same level of detail, same style.

Here's a prompt I use regularly: [paste prompt]. Audit it for common AI prompting mistakes: 1) Am I being too vague? 2) Am I giving enough context? 3) Am I asking for too much at once? 4) Am I constraining the output format? 5) Am I including examples? Score it 1-10 and give me the improved version.

I want Claude to remember my preferences across conversations. Here's what I always want it to know: Company: [company]. My role: [role]. Writing style: [describe]. Key preferences: [list]. Format this as a Claude Project instruction set I can paste once and never repeat.

Draft an email to [recipient + context]. Goal: [what you want them to do]. Tone: professional but warm. Constraints: Under 150 words. No fluff, no "I hope this finds you well." Lead with value or a specific ask. End with a clear, low-friction CTA.

Repurpose this content into multiple formats. Original: [paste content]. Create: 1) LinkedIn post — hook + 3 key insights + CTA (under 1300 chars), 2) Twitter/X thread — 7 tweets with thread hook, 3) Email newsletter intro — 3 paragraphs that tease the key insight, 4) YouTube video script outline — hook, 3 main points, CTA. Maintain the same voice and key message across all formats.

Here is the transcript from my [meeting type] meeting: [paste transcript]. Extract: 1) Key decisions made (bullet points), 2) Action items — who, what, by when (table format), 3) Open questions that need follow-up, 4) Topics tabled for next meeting, 5) One-paragraph executive summary. Then draft a follow-up email I can send to attendees.

Write a decision memo for [topic]. Context: [background]. Options considered: [list options]. My recommendation: [your lean]. Audience: [who will read this]. Structure: Situation, Options, Analysis, Recommendation. Keep it to one page. Use data where possible, flag assumptions clearly.

Edit this writing to match my voice. Here's the draft: [paste draft]. Here are 3 examples of my writing that represent my voice: [paste examples]. Edit the draft to sound like me — same sentence length patterns, same level of formality, same vocabulary. Don't change the substance, just the voice.

Write a 3-email cold outreach sequence. Target: [describe ideal recipient]. What we offer: [product/service]. Key differentiator: [what makes us different]. Email 1: Pattern interrupt + value. Email 2: Case study or social proof. Email 3: Breakup email. Each email under 100 words. Subject lines included.

Create an outline for a [length]-minute presentation on [topic]. Audience: [who]. Goal: [what you want them to think/do after]. Include: 1) Opening hook (first 30 seconds), 2) Key sections with talking points, 3) One story or analogy per section, 4) Transition phrases between sections, 5) Closing CTA. I want them to leave remembering [one key takeaway].

I need to send a difficult message. Situation: [describe]. Recipient: [who and relationship]. What I need to communicate: [the hard part]. What I want to preserve: [relationship, deal, etc.]. Draft a message that is direct but empathetic. No passive aggression. No softening the message to the point of ambiguity.

Turn these rough notes into a blog post: [paste notes]. Target length: [word count] words. Audience: [who]. Tone: [describe tone]. Structure: Hook → Problem → Solution → Proof → CTA. Include a compelling title and meta description. Don't pad with filler — if the notes don't support [word count] words, write shorter.

Write an internal announcement about [topic]. What happened: [details]. Why it matters: [impact]. What changes for the team: [changes]. Tone: transparent, confident, not corporate. This goes to [audience]. Keep it under 200 words. Start with the headline news, not preamble.

I just created this piece of content: [paste or describe]. Now help me build the distribution pipeline: 1) Substack post adapted from this (with newsletter-specific intro), 2) 5 Substack Notes (one per day for a week), 3) LinkedIn post, 4) Lead magnet CTA that connects to this topic. Match my existing voice: [describe voice or paste example].

I have a slide deck with these slides: [list slide titles/bullet points]. Write speaker notes for each slide: 1) What to say (conversational, not reading bullets), 2) Transition to next slide, 3) Any audience engagement moments (questions, pauses). Total talk time target: [minutes] minutes. Make it sound natural, not scripted.

Review this document and give me feedback: [paste document]. I wrote this for [audience] with the goal of [purpose]. Give me: 1) What works well (2-3 things), 2) What's unclear or weak (be specific), 3) Structural suggestions, 4) Line-level edits for the weakest paragraph. Be direct — I want honest feedback, not encouragement.

I need to create a comprehensive brand voice style guide for my company. Here are 5 examples of writing that represents our ideal voice: [paste examples]. Analyze these and create a style guide covering: tone attributes (3-5 with descriptions), vocabulary preferences, sentence structure patterns, phrases to use/avoid, and formatting conventions. Output as a document I can give to any AI tool or writer.

Create a campaign brief for [campaign goal]. Product/service: [what you're promoting]. Target audience: [describe]. Budget: [amount]. Timeline: [dates]. Channels: [list channels]. Include: 1) Campaign objective and KPIs, 2) Key message and value prop, 3) Channel-specific tactics, 4) Content needs by channel, 5) Measurement plan.

Generate 10 Meta ad variations for [product/offer]. Target audience: [describe]. Landing page: [URL or describe]. Pain point we solve: [describe]. Format for each: Headline (under 40 chars), Primary text (under 125 chars), Description (under 30 chars). Give me 5 pain-focused and 5 aspiration-focused variations.

Create an SEO content brief for the keyword: [target keyword]. Include: 1) Search intent analysis, 2) Recommended article structure (H2s and H3s), 3) Key questions to answer, 4) Related keywords to include naturally, 5) Recommended word count, 6) Internal linking opportunities for a site about [your topic area]. 7) Title tag and meta description.

Write a [number]-email welcome/nurture sequence. Subscriber context: [how they signed up]. Our product: [describe]. End goal: [desired action]. For each email: Subject line, preview text, body copy (under 200 words), CTA. Spacing: [frequency]. Tone: [describe]. Each email should build on the last — not repeat.

Create a 2-week social media content calendar. Platform: [platform]. Posting frequency: [times per week]. Content pillars: [list 3-4 pillars]. Brand voice: [describe]. For each post: Hook text, body, hashtags (if applicable), and best time to post. Mix content types: text, carousel ideas, video concepts, polls.

Write a case study from these interview notes/data: [paste notes]. Customer: [name/company]. Challenge they faced: [problem]. Solution (our product): [what they used]. Results: [metrics]. Format: Challenge → Solution → Results → Quote. Keep it under 600 words. Make the customer the hero, not us.

Write landing page copy for [product/offer]. Target visitor: [describe]. Main objection: [what stops them]. Key benefit: [#1 reason to buy]. Social proof available: [describe]. Structure: Hero headline + subhead, 3 benefit blocks, objection handler, testimonial placement, CTA. Conversion goal: [action].

Analyze this competitor's content strategy: [competitor name/URL]. Look at their: 1) Content themes and topics, 2) Posting frequency and channels, 3) Content formats they favor, 4) Engagement patterns, 5) Gaps they're missing. Then: What should we do differently? What can we learn? Where's the whitespace?

Write this week's newsletter issue. Topic: [main topic]. My take/angle: [your perspective]. Supporting points: [2-3 key points]. CTA: [what you want readers to do]. Format: Punchy intro (3 sentences max), 3 sections with headers, closing with CTA. Tone: conversational, not corporate. Under 500 words.

Audit this page for SEO: [paste page content or URL]. Target keyword: [keyword]. Check: 1) Title tag and meta description, 2) H1/H2 structure, 3) Keyword placement and density, 4) Internal linking opportunities, 5) Content gaps vs. top-ranking pages, 6) Technical issues I should flag for my developer. Give me a prioritized action list.

I want to improve [metric] on [page/email/ad]. Current performance: [current numbers]. Audience: [describe]. Generate 5 A/B test hypotheses using this format: "If we [change], then [metric] will [improve/increase] because [reasoning]." Prioritize by expected impact and ease of implementation.

Here's my brand voice style guide: [paste style guide]. For the rest of this conversation, write everything in this voice. To confirm you've got it, rewrite this generic sentence in my brand voice: "We offer a comprehensive solution that leverages cutting-edge technology to drive business outcomes."

Research this company for my sales call tomorrow: [company name/URL]. I need: 1) Company overview and recent news, 2) Key stakeholders and their likely priorities, 3) Potential pain points based on their industry, 4) Three conversation starters based on their recent activity. Focus on actionable intel, not generic summaries.

Create a proposal for [client name] based on this context: [paste call notes or brief]. Our services: [describe]. Our pricing: [paste pricing structure]. Include: 1) Executive summary (3 sentences), 2) Understanding of their challenge, 3) Proposed solution with deliverables, 4) Timeline and milestones, 5) Investment and terms, 6) Why us, 7) Next steps. Professional but not stuffy.

Our prospects commonly say: "[objection]". Context: We sell [product/service] to [target market] at [price point]. Write 3 response options: 1) Direct reframe (confident, addresses head-on), 2) Story-based (use a hypothetical customer success), 3) Question-based (turn the objection into a discovery question). Each under 60 words.

Create a discovery call framework for selling [product/service] to [target buyer]. Include: 1) Opening (rapport + agenda setting), 2) 8-10 discovery questions in order (surface → deep), 3) Pain amplification questions, 4) Budget/timeline qualification, 5) Next step commitment language. Flag the 3 most critical questions.

Analyze this set of closed deals: [paste deal data — won/lost, size, industry, sales cycle, reason]. Find patterns: 1) What do wins have in common? 2) What do losses have in common? 3) Where do deals stall? 4) Optimal sales cycle length, 5) Top 3 actionable changes to improve close rate. Be specific with data.

Write a follow-up email after my [call type] with [contact name] at [company]. Key points discussed: [list]. They expressed interest in: [what]. Their concerns: [concerns]. Next step agreed: [next step]. Keep it under 150 words. Reinforce the key value point and make the next step frictionless.

Create a Statement of Work for this project: Client: [client]. Scope: [describe scope]. Deliverables: [list]. Timeline: [duration]. Price: [amount]. Include: 1) Project overview, 2) Scope of work (detailed), 3) Deliverables with acceptance criteria, 4) Timeline and milestones, 5) Investment and payment terms, 6) Assumptions, 7) Change order process.

Build a 5-touch outbound sequence targeting [title/role] at [company type]. Our value prop: [describe]. Channels: [email, LinkedIn, phone]. For each touch: Channel, timing, message copy, and subject line (if email). The sequence should escalate from value-first to direct ask. Include personalization placeholders.

Review this deal and tell me what's missing: Company: [company]. Contact: [name, title]. Current stage: [stage]. Deal size: [amount]. Time in pipeline: [duration]. Last activity: [describe]. Competition: [known competitors]. Score this deal 1-10 on likelihood to close and tell me the 3 most important things to do next.

Review my pricing page/structure: [paste or describe pricing]. Our target customer: [describe]. Competitors charge: [competitor pricing]. Evaluate: 1) Is the value clear at each tier? 2) Any pricing psychology mistakes? 3) Is the upgrade path obvious? 4) What would you change? 5) Suggest better tier names if current ones are generic.

Enrich this CRM contact/company data: [paste raw data]. For each record, add: 1) Industry classification, 2) Estimated company size, 3) Likely pain points based on industry/size, 4) Suggested outreach angle, 5) Priority score (1-10) based on fit with our ICP: [describe ICP]. Output as a table.

Create a competitive battle card for [competitor]. What we know about them: [info]. Our strengths vs. them: [list]. Their strengths vs. us: [list]. Include: 1) Quick comparison table, 2) Top 3 win themes, 3) Landmine questions to ask prospects, 4) Responses when prospect mentions them, 5) When to walk away.

Design a revenue operations dashboard. Data sources: [list tools — CRM, Stripe, analytics]. Key metrics I track: [list metrics]. Audience: [who sees this]. Create: 1) Dashboard layout with sections, 2) Each metric with calculation method, 3) Refresh frequency recommendation, 4) Alert thresholds, 5) What it would take to automate this with Claude Code.

I need to document this process as a standard operating procedure. Here are my rough notes: [paste notes]. Create a complete SOP with: 1) Purpose — why this process exists, 2) Scope — when this applies, 3) Prerequisites — what's needed before starting, 4) Step-by-step instructions with decision points, 5) Common issues and troubleshooting, 6) Quality checks. Use clear, concise language anyone can follow.

Generate a project kickoff document for: [project name]. Objective: [what we're trying to achieve]. Team: [who's involved]. Timeline: [expected duration]. Budget: [if applicable]. Include: 1) Project charter (1 paragraph), 2) Scope (in/out), 3) Milestones and deadlines, 4) RACI matrix, 5) Risk register (top 5), 6) Communication plan.

Here's our current process for [process name]: [describe steps, who does what, time per step]. Identify: 1) Bottlenecks — where does work pile up? 2) Redundancies — what's done twice? 3) Manual steps that could be automated, 4) Handoff failures — where does work fall through cracks? 5) Recommended improvements with expected time savings.

Write a knowledge base article for our team about [topic]. Current tribal knowledge: [paste what you know]. Audience: [who needs this]. Include: Title, summary, detailed instructions, screenshots needed (describe what to capture), FAQs section, related articles to link to. Write for someone doing this for the first time.

Help me evaluate tools for [use case]. My requirements: [list requirements]. Budget: [range]. Team size: [number]. Current tools we use: [list]. Tools I'm considering: [options]. Create a comparison matrix and recommend the best option with reasoning. Flag any integration concerns with our current stack.

Create an agenda for our [meeting type] meeting. Duration: [minutes]. Attendees: [who]. Topics to cover: [list topics]. For each topic: Time allocation, discussion leader, and expected outcome (decision, update, or brainstorm). Add a parking lot section. Total should fit within [minutes] minutes with 5 min buffer.

We're making this change: [describe change]. Impact: [who and how]. Timeline: [when]. Reason: [why]. Write a change management communication plan: 1) Announcement message (all-hands), 2) FAQ document (10 questions), 3) Manager talking points, 4) 30/60/90 day follow-up messages.

Write a post-mortem for this incident: What happened: [describe]. When: [timeline]. Impact: [who was affected, how]. Root cause: [what went wrong]. Include: 1) Timeline of events, 2) Root cause analysis (5 Whys), 3) What went well in the response, 4) What went poorly, 5) Action items with owners, 6) Process changes to prevent recurrence. Blameless tone.

I want to automate this workflow: [describe current manual process]. Tools involved: [list]. Triggers: [what starts the process]. I'm comfortable with: [no-code/low-code/code]. Design the automation: 1) Trigger → actions flow, 2) Tool connections needed, 3) Error handling, 4) How to test it, 5) Estimated setup time.

Create an onboarding checklist for a new [role] hire. Team: [department]. Tools they need: [list]. Key processes: [list]. People to meet: [list]. Create a day-by-day plan for their first 2 weeks: Day 1-2 (setup), Day 3-5 (training), Week 2 (shadowing + first tasks). Include who's responsible for each item.

Help me prepare a quarterly business review. Period: [quarter]. Key metrics: [list with current vs. target]. Wins: [list]. Misses: [list]. Next quarter priorities: [list]. Create: 1) Executive summary (1 paragraph), 2) Metrics dashboard table, 3) Wins with impact, 4) Misses with root cause and remediation, 5) Next quarter OKRs.

I want to connect [tool A] with [tool B]. Use case: [what I want to happen automatically]. Data that needs to flow: [describe]. Current setup: [how it works now]. Design the integration: 1) API endpoints or webhook approach, 2) Data mapping, 3) Error handling, 4) Testing plan, 5) Claude Code implementation outline.

I have monthly revenue data for the last 12 months: [paste data]. Create a variance analysis comparing: 1) Month-over-month changes with % and absolute, 2) Same-month-last-year comparison, 3) Running 3-month average trend. For any variance > 10%, provide a plain-English explanation of likely causes. Format as a board-ready summary.

I need a spreadsheet formula for: [describe what you want to calculate]. My data structure: [describe columns/rows]. I'm using [Excel/Google Sheets]. Give me: 1) The formula, 2) Plain English explanation of how it works, 3) Where to put it, 4) How to verify it's working correctly.

Write the financial narrative section for my board deck. Period: [quarter/month]. Revenue: [amount] ([change]% vs prior). Burn: [amount]. Runway: [months]. Key metrics: [list with values]. Write in confident-but-honest CEO voice. Highlight the story the numbers tell. Flag risks proactively. Under 300 words.

Here's my budget vs. actual for [period]: [paste data]. For each line item: 1) Variance ($ and %), 2) Is this a timing issue or a real miss? 3) Forecast impact for the rest of the year. Summarize: Total favorable/unfavorable variance, top 3 concerns, recommended actions. Format for a finance review meeting.

Build a financial model for: [describe the business or project]. Revenue drivers: [what generates revenue]. Cost structure: [major cost categories]. Time horizon: [months/years]. Assumptions: [list key assumptions]. Output as: 1) Revenue build (bottom-up), 2) P&L projection, 3) Cash flow, 4) Key ratios, 5) Sensitivity on top 3 variables.

Build a cohort analysis from this data: [paste customer data with signup dates and revenue]. Group by: [month/quarter] of signup. Track: [revenue/retention/usage] over [time periods]. Output: 1) Cohort table, 2) Trends I should worry about, 3) Best/worst performing cohorts, 4) What the data suggests about our business.

Run a scenario analysis on my business. Base case: [current metrics]. I want to model: 1) Bull case: [optimistic assumptions], 2) Bear case: [pessimistic assumptions], 3) Recession case: [worst case]. For each: Revenue, costs, cash flow, and runway impact. What's the decision I should make based on these scenarios?

Calculate unit economics for my business. Customer acquisition data: [CAC components and costs]. Revenue per customer: [ARPU and frequency]. Churn: [monthly/annual rate]. Gross margin: [percentage]. Calculate: LTV, LTV:CAC, payback period, and gross margin-adjusted LTV. Tell me if these metrics are healthy or concerning, and what lever to pull first.

Create a monthly financial reporting template for my [type] business. Revenue: [how I make money]. Key cost categories: [list]. Metrics I track: [list]. Audience: [who reads this]. Include: 1) Executive summary template, 2) KPI dashboard layout, 3) Revenue breakdown format, 4) Expense analysis format, 5) Cash flow snapshot, 6) Commentary prompts for each section.

Help me prepare a data room for fundraising. Stage: [seed/A/B]. Current metrics: [key numbers]. Documents I have: [list]. Create: 1) Data room folder structure, 2) List of missing documents, 3) Executive summary template, 4) Metrics sheet format, 5) FAQ document for due diligence. Flag anything that might raise red flags for investors.

Process these invoices/receipts: [paste or describe]. For each: 1) Extract vendor, date, amount, category, 2) Flag any duplicates, 3) Categorize by expense type, 4) Calculate totals by category, 5) Flag anything unusual (amount spikes, new vendors). Output as a table I can paste into my bookkeeping system.

Help me organize for tax season. Business type: [entity type]. Revenue range: [approximate]. Deduction categories I know about: [list]. Questions I have: [list]. Help me: 1) Create a document checklist, 2) Identify deductions I might be missing, 3) Organize my data by category, 4) Draft questions for my accountant. Note: You're not giving tax advice, just helping me organize.

I need a competitive teardown of [competitor product]. Here's what I know about them: [context]. Our product does: [describe your product]. Analyze: 1) Key features (theirs vs. ours — table format), 2) Gap analysis, 3) Our advantages, 4) Effort estimate to close each gap (S/M/L/XL), 5) Which gaps are worth closing and why.

Write a PRD for this feature: [describe feature]. Problem it solves: [user pain]. Target user: [who]. Success metrics: [how we'll measure]. Include: 1) Problem statement, 2) User stories (5-8), 3) Requirements (must-have vs. nice-to-have), 4) Edge cases, 5) Technical considerations, 6) Launch plan, 7) Open questions.

Synthesize these user research interviews: [paste notes from multiple interviews]. Find: 1) Common themes (group by frequency), 2) Unexpected insights, 3) Contradictions between users, 4) Feature requests ranked by frequency, 5) Quotes worth sharing with stakeholders, 6) Recommended next steps. Present as an executive summary + detailed findings.

Translate this technical decision for non-technical stakeholders: [describe the technical decision]. Options considered: [list options]. Team recommends: [recommendation]. Help me explain: 1) What this means in business terms, 2) Impact on timeline and cost, 3) Trade-offs in language executives understand, 4) Why the alternatives were rejected. No jargon.

Facilitate a sprint retrospective. Sprint: [sprint number/name]. What we shipped: [list]. What didn't ship: [list]. Known issues: [list]. Generate: 1) "What went well" starter prompts, 2) "What could improve" starter prompts, 3) Discussion questions that dig into root causes, 4) Action item template with owners and due dates.

Help me prioritize these features: [list features with brief descriptions]. Criteria: 1) Impact on [key metric], 2) Engineering effort, 3) Customer demand, 4) Strategic alignment with [company goal]. Score each feature on these criteria (1-5) and create a prioritized list with the scoring matrix. Recommend the top 3 for next quarter.

Write release notes for this update: [list changes — features, fixes, improvements]. Audience: [customers/internal]. Tone: [excited/matter-of-fact/professional]. Format: 1) What's New (features), 2) Improvements, 3) Bug Fixes, 4) Breaking Changes (if any). Make features sound like benefits, not technical specs. Under 300 words.

Help me communicate our product roadmap. Audience: [who — board, team, customers]. Time horizon: [quarters]. Themes: [list major themes]. Key initiatives: [list]. Create a roadmap narrative that: 1) Connects to company strategy, 2) Groups by theme, not timeline, 3) Explains "why" not just "what", 4) Sets expectations without over-promising. Avoid specific dates.

Analyze these bug reports: [paste bug reports]. Find: 1) Patterns (common components, user flows, environments), 2) Severity distribution, 3) Root cause hypotheses, 4) Suggested fix priority, 5) UX improvements that might prevent categories of bugs. Output as a triage table + summary memo for the engineering team.

Write user stories for this feature: [describe feature]. Users: [list user types]. Include acceptance criteria for each story. Format: "As a [user], I want to [action] so that [benefit]." Acceptance criteria: "Given [context], when [action], then [result]." Cover the happy path and top 3 edge cases per story.

Review this API design: [paste endpoint specs]. Evaluate: 1) REST conventions compliance, 2) Naming consistency, 3) Error handling patterns, 4) Pagination approach, 5) Auth considerations, 6) Breaking change risks, 7) Missing endpoints for common use cases. Suggest improvements for each issue found.

Generate a stakeholder update for [project/initiative]. Status: [on track/at risk/behind]. Progress: [what shipped this period]. Blockers: [list]. Next steps: [plan]. Create updates for 3 audiences: 1) Executive summary (5 sentences), 2) Team update (detailed), 3) Customer-facing update (if applicable). Each at the appropriate level of detail.

Write a performance review for [name], [role]. My notes from this quarter: [paste notes]. Structure: 1) Overall rating and one-line summary, 2) Top 3 accomplishments with specific examples, 3) 2-3 growth areas with concrete improvement actions, 4) Goals for next quarter, 5) Development opportunities. Tone: direct but supportive. Be specific.

Generate a 1:1 agenda for my meeting with [name], [role]. What I know about their current work: [context]. Recent wins: [list]. Concerns: [any]. Include: 1) Check-in question (not "how are you"), 2) Their update time, 3) My feedback/coaching point, 4) Career development topic, 5) Action items from last time: [list]. Keep the whole meeting to 30 minutes.

Help me prepare for a difficult conversation. Who: [person and relationship]. Topic: [what needs to be discussed]. Why it's hard: [the uncomfortable part]. Desired outcome: [what I want after]. Help me: 1) Open the conversation (exact words), 2) Key points to make, 3) Anticipated responses and how to handle each, 4) How to close constructively.

Help me draft OKRs for [team/company]. Period: [quarter]. Company priorities: [list]. Current challenges: [list]. Draft 3-4 Objectives (qualitative and inspiring) with 3-4 Key Results each (quantitative and measurable). For each KR: Current baseline, target, and stretch target. Flag any KRs that might conflict with each other.

Create a plan to roll out AI (Claude) to my team. Team size: [number]. Roles: [list roles]. Current AI usage: [none/basic/mixed]. Budget: [per seat per month]. Create: 1) Phased rollout plan (4 weeks), 2) Which product (Chat/CoWork/Code) for each role, 3) First use case per role, 4) Training materials outline, 5) Success metrics, 6) Common resistance points and responses.

Write a job description for [role title]. Reports to: [who]. Team: [department]. Key responsibilities: [top 3-5]. Must-have skills: [list]. Nice-to-have: [list]. Comp range: [range]. What makes this role unique: [your pitch]. Write it to attract A-players — lead with the impact, not the requirements list. Under 500 words.

Create interview questions for [role]. We're looking for: [key traits]. Culture values: [list]. For each question: 1) The question, 2) What you're evaluating, 3) What a great answer looks like, 4) Red flags to watch for. Include: 2 behavioral, 2 situational, 1 role-specific, 1 culture-fit, 1 problem-solving.

Help me decide what to delegate. Here's everything on my plate: [list all tasks/responsibilities]. My unique value: [what only I can do]. Team capabilities: [who can do what]. For each item on my list: 1) Keep / Delegate / Eliminate, 2) Who to delegate to, 3) What instructions they need, 4) How to verify quality. Prioritize delegation by time-freed impact.

Design a [length]-minute team meeting for [purpose]. Attendees: [number and roles]. Issues to address: [list]. Decisions needed: [list]. Create: 1) Agenda with time blocks, 2) Pre-read materials needed, 3) Discussion facilitation questions, 4) Decision-making framework for each decision, 5) Action item capture template. Keep it tight — no meeting bloat.

Draft an offer letter for [candidate name] for [role]. Compensation: [base + equity/bonus]. Start date: [date]. Benefits highlights: [list]. Reporting to: [who]. Tone: excited but professional. Include: role summary, comp details, benefits overview, start date, and next steps. Not a legal document — a compelling letter that makes them want to accept.

Audit my leadership communication. Here are my last 5 messages to my team: [paste messages]. Evaluate: 1) Clarity — is the message obvious? 2) Tone — motivating or draining? 3) Actionability — do people know what to do? 4) Consistency — am I contradicting myself? 5) What's missing? Give me specific rewrites for the weakest messages.

Create a growth plan for [name], [current role]. Their strengths: [list]. Growth areas: [list]. Career goal: [where they want to be in 12-18 months]. Create: 1) 90-day development plan, 2) Specific skills to build (with resources), 3) Projects that stretch these skills, 4) Mentorship or shadowing opportunities, 5) How to measure progress, 6) Check-in cadence.

Here are [X] emails I need to process: [paste emails]. For each one: 1) Priority: urgent / important / low / archive, 2) Suggested action: reply / delegate / defer / archive, 3) If "reply": draft a concise response matching my usual tone (professional but warm, direct, no fluff). Group by priority in your output.

I need to make a decision about [topic]. Context: [describe situation, constraints, stakeholders]. Walk me through: 1) Clarify — what exactly am I deciding? 2) Options — what are all viable paths? 3) Criteria — what matters most? 4) Analysis — pros/cons/risks for each option, 5) Gut check — what does my instinct say? 6) Decision — recommend a path with reasoning.

I need to learn about [topic] quickly. My current knowledge: [beginner/intermediate/advanced]. Time available: [hours/days]. Why I need this: [purpose]. Create: 1) Learning path (ordered list of sub-topics), 2) Key concepts I must understand, 3) Common misconceptions, 4) Practical exercises, 5) Resources to go deeper. Teach me the 20% that gives 80% of the value.

Help me process my weekly review. This week: Wins: [list]. Losses/misses: [list]. Open items: [list]. Meetings I had: [list]. Next week's priorities: [tentative]. Help me: 1) Extract lessons from wins and losses, 2) Identify patterns, 3) Decide what to carry forward vs. drop, 4) Create next week's top 3 priorities, 5) One thing to delegate or eliminate.

I just made (or am about to make) this decision: [describe decision]. Context: [why now, what prompted it]. Options I considered: [list]. What I chose and why: [your choice]. Confidence level: [1-10]. Create a decision journal entry with: 1) Decision statement, 2) Context summary, 3) Options matrix, 4) Reasoning, 5) Expected outcome, 6) Review date, 7) Pre-mortem: what could go wrong?

I need to research [topic] for [purpose]. What I already know: [current understanding]. Key questions I need answered: [list questions]. Time I have: [timeframe]. Create a research brief: 1) Structured summary of what I should know, 2) Answer each of my questions, 3) Things I didn't think to ask, 4) Sources to explore, 5) One-paragraph executive summary.

Help me prioritize my task list. Here's everything: [paste full task list]. My available hours this week: [hours]. Key deadlines: [list]. Highest-impact goal right now: [goal]. Sort into: 1) Do today (urgent + important), 2) Schedule this week, 3) Delegate, 4) Defer to next week, 5) Eliminate. For "delegate" — who should do it?

Summarize this [book/article]: [paste content or describe]. I care most about: [specific angle or question]. Give me: 1) One-paragraph summary, 2) Top 5 actionable takeaways, 3) Key quotes worth saving, 4) How this applies to [my situation/business], 5) What this author gets wrong or oversimplifies. Don't just summarize — tell me what to DO with this information.

Help me organize this information I've been collecting: [paste notes, bookmarks, ideas]. Categories I use: [list existing categories]. Create: 1) Organize by category (suggest new ones if needed), 2) Identify duplicates, 3) Flag items that need action vs. reference, 4) Suggest connections between ideas, 5) Create a file/folder structure.

Help me plan my day. Today's calendar: [paste or describe]. Yesterday's carryover: [unfinished items]. This week's #1 goal: [goal]. Energy level: [high/medium/low]. Help me: 1) Identify my 3 most important tasks, 2) Block time for deep work, 3) Prep for each meeting (1-2 sentences), 4) Identify what to decline or delegate, 5) Set an end-of-day review question.

Review this [contract type]: [paste contract or key terms]. I'm the [buyer/seller/party]. Flag: 1) Terms that are unusual or unfavorable, 2) Missing clauses I should request, 3) Liability or risk areas, 4) Termination provisions, 5) Auto-renewal traps, 6) Questions I should ask my lawyer. Note: This is for preparation, not legal advice.

Run a pre-mortem on this plan: [describe your plan]. Imagine it's 6 months from now and this has failed. Help me: 1) List the 10 most likely reasons it failed, 2) Rank by probability, 3) For each: early warning sign to watch for, 4) Preventive action I can take now, 5) The #1 thing most likely to kill this. Be brutally honest.

Help me build a CLAUDE.md file for my business. Company: [name and description]. My role: [title]. Key tools I use: [list]. Voice/tone: [describe]. Regular tasks: [list what I do weekly]. Create a CLAUDE.md that gives Claude Code full context about my business, my preferences, and my workflows. Structure it with clear sections.

Create a Claude Code skill file for this workflow: [describe the workflow]. Trigger: [when should this run]. Inputs needed: [what info it needs]. Output: [what it should produce]. Include: 1) The skill markdown file content, 2) Where to save it, 3) How to invoke it, 4) Example usage, 5) Variables/placeholders to customize.

I want to connect Claude Code to [service/tool]. API docs: [URL or paste key endpoints]. What I want to do: [describe use case]. Help me: 1) Set up authentication safely (env vars), 2) Write the first API call, 3) Parse the response, 4) Create a reusable skill for this integration, 5) Error handling basics.

I have data in [format] from [source]. I need to: [describe transformation]. Final output should be: [describe desired output]. Volume: [how much data]. Frequency: [how often]. Build a Claude Code workflow that: 1) Reads the data, 2) Cleans/transforms it, 3) Outputs in my desired format, 4) Can run on a schedule, 5) Handles errors gracefully.

I'm having trouble with my Claude Code setup in VSCode. Issue: [describe problem]. Operating system: [Mac/Windows/Linux]. What I've tried: [list attempts]. Error message (if any): [paste]. Help me: 1) Diagnose the issue, 2) Step-by-step fix, 3) Verify it's working, 4) Prevent it from happening again.

I create this report [frequency]: [describe the report]. Data sources: [where the data lives]. Current process: [how I do it now, time spent]. Automate this with Claude Code: 1) Pull data from sources, 2) Calculate metrics, 3) Generate narrative summary, 4) Format the output, 5) Save/send the report. Walk me through setup step by step.

Help me set up a file organization system using Claude Code. Current state: [describe the mess]. File types: [what kinds of files]. Volume: [how many]. Where they live: [folders/drives]. Design: 1) Folder structure, 2) Naming conventions, 3) Auto-sorting rules, 4) A Claude Code command to organize new files, 5) Regular maintenance script.

My Claude Code conversations keep losing context or getting confused. Project type: [what I'm working on]. Average conversation length: [turns]. Documents I reference: [list]. Help me: 1) Structure my CLAUDE.md for better context, 2) Decide what goes in project files vs. conversation, 3) When to start a new conversation, 4) How to hand off context between sessions.

I need a workflow that connects these tools: [list tools in order]. The flow: [describe what happens at each step]. Trigger: [what starts it]. End result: [final output]. Build this as a Claude Code skill that: 1) Handles each API connection, 2) Passes data between steps, 3) Logs progress, 4) Handles failures at each step, 5) Can be run with one command.

Audit my Claude Code setup for safety. My CLAUDE.md: [paste or summarize]. Tools I've connected: [list with permission levels]. Data Claude has access to: [describe]. Check: 1) Are permissions too broad? 2) Any sensitive data exposure risks? 3) Are API keys stored safely? 4) What should I restrict? 5) Recovery plan if something goes wrong.

I'm a non-developer using Claude Code for [use case]. Operating system: [OS]. Tools I need to connect: [list]. Set up my environment: 1) Essential terminal commands I need to know, 2) Git basics (just enough), 3) How to read error messages, 4) My first 5 commands to try, 5) What to do when stuck.

I have these individual Claude Code skills: [list existing skills]. I want to compose them into a system where: [describe the workflow that connects them]. Design: 1) How skills should call each other, 2) Shared data/context between skills, 3) A master skill that orchestrates the flow, 4) Error handling between skill handoffs, 5) How to test the composed system.

Build a content operations workflow with Claude Code. Content types: [what I create]. Publishing platforms: [where I publish]. Current process: [how I do it now]. Automate: 1) Content creation from outline, 2) Repurposing across platforms, 3) Scheduling/publishing, 4) Performance tracking, 5) Iteration based on data. Start with the highest-impact automation first.

Help me identify which skills to build first. My role: [role]. My top 5 recurring tasks: [list]. Tools I use: [list]. Time spent on each task per week: [estimates]. Recommend the top 3 skills I should build, ordered by time-saved impact. For each: name, what it does, complexity to build (1-5).

Walk me through building my first Claude skill. I want it to: [describe what the skill should do]. Product: [Chat/CoWork/Code]. Steps: 1) Write the skill file (give me the actual content), 2) Where to save it, 3) How to test it, 4) Common first-timer mistakes to avoid, 5) How to iterate on it. Keep it simple — this is my first one.

Review this Claude skill file and improve it: [paste skill content]. What it's supposed to do: [describe intended behavior]. Issues I'm having: [describe problems]. Review: 1) Is the instruction clear and unambiguous? 2) Are there edge cases not handled? 3) Is the output format well-defined? 4) Suggested improvements. Give me the improved version.

Generate a skill template for [use case category]. Examples of tasks in this category: [list 3-5 tasks]. The template should: 1) Be customizable with variables, 2) Include clear input/output sections, 3) Have error handling instructions, 4) Work across [Chat/CoWork/Code]. Give me the template plus 3 example customizations.

I'm building skills for [department/function]. Show me the best design patterns for: 1) Skills that need external data, 2) Skills that produce long-form output, 3) Skills that require multi-step reasoning, 4) Skills that need human review before proceeding. For each pattern: example structure, when to use it, and common pitfalls.

I want to use this skill in Claude [Chat/CoWork]: [paste skill content or describe]. Help me: 1) Format it as Project Instructions, 2) Set up the project with right settings, 3) Add any needed knowledge files, 4) Create a test conversation to verify, 5) Share setup steps with my team.

Build a Claude Code skill that works with my filesystem. It needs to: [describe what files to read/write]. File location: [path]. File format: [type]. The skill should: 1) Find the right files, 2) Read and parse them, 3) [Transform/analyze/generate], 4) Write output to [location]. Include safety checks so it doesn't overwrite important files.

I want to connect these skills into a workflow: Skill 1: [describe]. Skill 2: [describe]. Skill 3: [describe]. Design the composition: 1) Execution order, 2) Data passing between skills, 3) Master orchestrator skill, 4) Error handling at each handoff, 5) How to run the whole chain with one command. Product: [Code].

Help me test this skill: [paste skill content]. Create: 1) 5 test cases covering normal use, 2) 3 edge cases (empty input, very long input, unexpected format), 3) Expected output for each test, 4) A testing checklist I can run through, 5) How to know when the skill is "good enough" vs. needs more work.

I want to create a shared skill library for my team. Team size: [number]. Roles: [list]. Common tasks across the team: [list]. Build: 1) Skill library folder structure, 2) 5 starter skills everyone needs, 3) Role-specific skills (1-2 per role), 4) Naming conventions, 5) How team members can contribute new skills, 6) Version control approach.

My skill needs dynamic variables. The skill: [describe what it does]. Variables needed: [list variable names and what they represent]. Some variables should have defaults: [which ones]. Design: 1) Variable syntax in the skill file, 2) How to prompt for missing variables, 3) Default values, 4) Validation rules, 5) Example invocation with and without variables.

I have a process that works in Claude [Chat/CoWork] and I want to move it to Claude Code for more power. Current process: [describe how you use it now]. What I wish it could also do: [additional capabilities]. Help me: 1) Convert the project instructions to a skill file, 2) Add file system capabilities, 3) Add automation potential, 4) Keep what works, enhance what's limited.

Design a content operations system for my business using Claude Code. Content types I create: [list]. Publishing schedule: [frequency per platform]. Team: [just me / team of X]. Current pain: [biggest bottleneck]. Design: 1) Folder structure, 2) CLAUDE.md content, 3) Key skills to build first, 4) Automation opportunities, 5) How to iterate weekly.

Set up Claude Code as my "virtual cofounder." My business: [describe]. Key decisions I face regularly: [list]. Data sources I have: [list]. I want Claude to: 1) Know my business context deeply, 2) Challenge my thinking, 3) Prepare analyses from real data, 4) Track decisions and outcomes. Design the CLAUDE.md and skill system to make this work.

Calculate the ROI of setting up Claude for my role. My role: [title]. Hours per week on these tasks: [list tasks with hours]. Hourly value of my time: [rate or salary equivalent]. Claude subscription: [cost/month]. Estimate: 1) Time saved per task (%), 2) Monthly hours recovered, 3) Dollar value of recovered time, 4) Break-even timeline, 5) What I should do with the freed-up time.

Audit my current workflow and show me the AI-augmented version. Current workflow: [describe step by step, with time per step]. Tools used: [list]. Pain points: [list]. For each step: 1) Current time, 2) AI-augmented time, 3) Which Claude product to use, 4) Specific prompt/skill for that step. Calculate total time saved.

Document our team's AI adoption as a case study. Before state: [how we worked before]. Implementation: [what we did]. After state: [results]. Timeline: [how long]. Write this as a case study: 1) Challenge, 2) Approach, 3) Implementation timeline, 4) Results (quantified), 5) Lessons learned, 6) What we'd do differently.

Design a complete Claude-powered business system. Business type: [describe]. Key functions to augment: [list]. Current bottleneck: [describe]. Budget for AI tools: [monthly]. Create a blueprint: 1) Which product for which function, 2) CLAUDE.md structure, 3) Top 10 skills to build (prioritized), 4) Implementation timeline (12 weeks), 5) Success metrics.