Stop Writing AI Prompts From Scratch

You are a Twitter ghostwriter for a thought leader. Convert this blog post into a 7-10 tweet thread that: 1. Opens with a contrarian hook (no "Thread:" or numbers) 2. Each tweet is standalone valuable (under 280 chars) 3. Uses short sentences, line breaks between ideas 4. Ends with a soft CTA to the full post 5. Tone: confident but conversational, not corporate Blog post: [PASTE BLOG POST]

You are an expert cold email copywriter. Write a personalized cold email for: Prospect: [NAME] at [COMPANY] Their role: [TITLE] Something specific about them: [RECENT POST/ACHIEVEMENT/COMPANY NEWS] What I sell: [YOUR PRODUCT/SERVICE] Desired outcome: [BOOK A CALL/START TRIAL/etc.] Rules: - Subject line under 6 words, no clickbait - Opening line references THEIR specific situation (not "I saw your LinkedIn") - Body is 3 sentences max - One clear CTA (question, not demand) - No "I hope this finds you well" or "I'd love to pick your brain" - Tone: peer-to-peer, not salesperson-to-prospect

Act as a competitive intelligence analyst. Analyze [COMPETITOR NAME] based on publicly available information: 1. **Positioning**: What is their core value prop? Who do they serve? 2. **Pricing**: What's their pricing model? Any free tier? 3. **Strengths**: What do customers praise in reviews? 4. **Weaknesses**: What do customers complain about? 5. **Content Strategy**: What topics do they create content about? 6. **Gaps**: What are they NOT doing that represents an opportunity? Format as a concise brief (bullet points, not essays). End with 3 specific actions I should take based on this analysis. My company: [YOUR COMPANY/PRODUCT]

You are writing a newsletter for [AUDIENCE]. The topic this week is: [TOPIC] Structure: 1. **Hook** (1-2 sentences): Start with a surprising stat, contrarian take, or relatable story 2. **The Insight** (3-4 paragraphs): The core lesson. Use specific examples, not generic advice. 3. **The Takeaway** (2-3 bullet points): Actionable steps the reader can do TODAY 4. **P.S.**: Soft plug for [YOUR PRODUCT/SERVICE] Style rules: - Write at 8th grade reading level - Short paragraphs (2-3 sentences max) - Use "you" more than "I" - No jargon unless you define it - Total length: 400-600 words

Generate a production-ready REST API endpoint: Framework: [Express/FastAPI/Next.js API routes] Endpoint: [METHOD] /api/[RESOURCE] Purpose: [WHAT IT DOES] Requirements: 1. Input validation with descriptive error messages 2. Proper HTTP status codes (201 for create, 404 for not found, etc.) 3. Error handling with try/catch 4. TypeScript types (or Python type hints) 5. Rate limiting middleware setup 6. Example request/response in comments 7. No over-engineering — keep it simple and readable Do NOT add features I didn't ask for. No ORM setup, no database migrations, no auth middleware unless specified.

Write a LinkedIn post about [TOPIC] for my audience of [AUDIENCE]. Format rules: - First line: hook that stops the scroll (pattern interrupt, bold claim, or question) - Use line breaks between every 1-2 sentences - Include a personal story or specific example (not generic advice) - End with a question that invites comments - Add 3-5 relevant hashtags at the bottom - Length: 150-200 words (the sweet spot for LinkedIn) - NO corporate jargon, NO "I'm thrilled to announce", NO "Let's connect" - Tone: like texting a smart friend, not writing a press release My perspective/angle: [YOUR UNIQUE TAKE ON THIS TOPIC]

Create a detailed product launch checklist for: Product: [PRODUCT NAME AND DESCRIPTION] Launch date: [DATE] Budget: [BUDGET OR "bootstrapped"] Audience: [TARGET AUDIENCE] Organize into phases: 1. **Pre-Launch (2 weeks before)**: Build anticipation 2. **Launch Day**: Maximum impact 3. **Post-Launch (1 week after)**: Sustain momentum For each task include: - Specific action (not vague "create content") - Tool recommendation (free options preferred) - Time estimate - Priority (must-do vs nice-to-have) Focus on tactics that work for small teams. Skip anything requiring a large budget or team. I'd rather do 5 things well than 20 things poorly.

Estimate the market size for this business idea: Idea: [DESCRIBE YOUR PRODUCT/SERVICE IN 1-2 SENTENCES] Target customer: [WHO BUYS THIS] Geography: [WHERE - US, Global, etc.] Provide: 1. **TAM** (Total Addressable Market): The entire market if everyone who could buy, did 2. **SAM** (Serviceable Available Market): The segment you can realistically reach 3. **SOM** (Serviceable Obtainable Market): What you can capture in Year 1 For each, show your math: - Number of potential customers × average revenue per customer - Cite any public data sources (market reports, census data, industry stats) - Flag assumptions clearly End with: "Bottom line: Is this a $1M, $10M, or $100M opportunity?" and a 1-sentence recommendation.

You are a sales strategist. Generate responses for every common objection to: Product: [YOUR PRODUCT/SERVICE] Price: [PRICE] Target buyer: [WHO MAKES THE PURCHASE DECISION] For each objection: 1. **Acknowledge** (validate their concern in 1 sentence) 2. **Reframe** (shift perspective to value/outcome) 3. **Evidence** (social proof, data, or case study) 4. **Bridge** (transition back to next step) Cover these objections at minimum: - "It's too expensive" - "I need to think about it" - "We're using [competitor] already" - "I need to check with my team" - "Does it work for [my specific situation]?" - "What if it doesn't work?" Keep each response under 4 sentences. Conversational tone, not scripted.

I have a bug. Help me diagnose it systematically. Error message: [PASTE ERROR] Language/Framework: [e.g., Python/FastAPI, TypeScript/Next.js] What I expected to happen: [EXPECTED BEHAVIOR] What actually happened: [ACTUAL BEHAVIOR] What I already tried: [LIST ATTEMPTS] Your approach: 1. First, explain what the error message means in plain English 2. List the 3 most likely causes (ranked by probability) 3. For each cause, give me a specific diagnostic step (a command to run, a line to check, a value to log) 4. Once I run those, I'll tell you the results and we narrow down Do NOT give me a fix yet. Help me UNDERSTAND the bug first. I want to learn, not just copy-paste a solution.