Copy. Paste. Prompt.

Create a detailed blog post outline for the topic: "[YOUR TOPIC]"

Include:
- A compelling H1 title (under 60 characters)
- 5-7 H2 sections with brief descriptions
- 2-3 H3 subsections under each H2
- A meta description (under 160 characters)
- 3 internal linking opportunities
- Suggested word count for each section

Target audience: [YOUR AUDIENCE]
Tone: [informational/conversational/professional]

Write a cold email to [RECIPIENT ROLE] at [COMPANY TYPE].

Context:
- I'm offering: [YOUR PRODUCT/SERVICE]
- Their likely pain point: [PAIN POINT]
- Something specific I noticed about them: [PERSONALIZATION DETAIL]

Rules:
- Under 150 words
- No more than 3 sentences in the opening paragraph
- Ask exactly ONE question at the end
- Sound like a human, not a salesperson
- No "I hope this finds you well"

Rewrite the following text in a [TARGET TONE] tone.

Original text:
"""
[PASTE YOUR TEXT]
"""

Requirements:
- Preserve ALL factual information
- Match the new tone consistently
- Keep approximately the same length
- Highlight any phrases that changed significantly

Target tone options: professional, casual, academic, enthusiastic, empathetic, authoritative, humorous

Write landing page copy for [PRODUCT/SERVICE] using the PAS (Problem-Agitate-Solution) framework.

Product: [DESCRIPTION]
Target customer: [WHO THEY ARE]
Main pain point: [THEIR BIGGEST PROBLEM]
Key differentiator: [WHAT MAKES YOU DIFFERENT]
Price point: [PRICE OR RANGE]

Include:
1. Hero headline (under 10 words) + subheadline
2. Problem section (3 bullet points of pain)
3. Agitation (make the pain feel real)
4. Solution reveal (your product)
5. 3 key benefits (not features)
6. Social proof placeholder
7. CTA button text + supporting text
8. FAQ section (4 questions)

Write a newsletter issue from these raw notes:

Topic: [TOPIC]
Key points:
- [POINT 1]
- [POINT 2]
- [POINT 3]

Format:
- Catchy subject line (under 50 chars, no clickbait)
- Opening hook (1-2 sentences, personal or surprising)
- 3 sections with headers
- Each section: insight + example + takeaway
- Closing CTA
- Total length: 500-700 words
- Tone: smart but approachable

Convert the following rough notes into clean technical documentation:

"""
[PASTE ROUGH NOTES, CODE COMMENTS, OR BULLET POINTS]
"""

Documentation style: [API reference / tutorial / guide / README]
Audience technical level: [beginner / intermediate / advanced]

Include:
- Clear section headers
- Code examples where relevant
- Prerequisites section
- Common pitfalls / troubleshooting
- Related resources section

Convert this idea into a Twitter/X thread (8-12 tweets):

Idea: [YOUR IDEA OR ARTICLE SUMMARY]

Rules:
- Tweet 1: Hook that creates curiosity (no "Thread:" or "🧵")
- Each tweet: ONE clear idea, under 280 characters
- Use concrete numbers and examples
- Include a counterintuitive insight by tweet 3
- Tweet before last: the key actionable takeaway
- Last tweet: CTA + restate the core idea
- No hashtags in the body, only tweet 1 if any

Review this code and provide feedback:

```[LANGUAGE]
[PASTE CODE]
```

Review for:
1. **Bugs**: Logic errors, edge cases, null/undefined risks
2. **Performance**: Time/space complexity, unnecessary operations
3. **Security**: Input validation, injection risks, data exposure
4. **Readability**: Naming, structure, comments needed
5. **Best practices**: Language idioms, patterns, anti-patterns

For each issue:
- Severity: 🔴 Critical / 🟡 Warning / 🔵 Suggestion
- Line number(s)
- What's wrong
- How to fix it (with code example)

Create a regex pattern for: [DESCRIBE WHAT YOU WANT TO MATCH]

Examples of strings that SHOULD match:
- [EXAMPLE 1]
- [EXAMPLE 2]

Examples that should NOT match:
- [EXAMPLE 3]
- [EXAMPLE 4]

Provide:
1. The regex pattern
2. A line-by-line explanation of each part
3. Test it against all examples above
4. Common edge cases it might miss
5. The pattern in [JavaScript/Python/Go] syntax

Help me debug this error:

Error message:
```
[PASTE ERROR MESSAGE]
```

Code that triggers it:
```[LANGUAGE]
[PASTE CODE]
```

What I've already tried:
- [ATTEMPT 1]
- [ATTEMPT 2]

Environment: [OS, language version, framework version]

Please:
1. Explain the root cause in plain English
2. Show the fix with code
3. Explain WHY the fix works
4. Suggest how to prevent this class of error in the future

Design a REST API for: [FEATURE DESCRIPTION]

Requirements:
- Resources involved: [LIST RESOURCES]
- Key operations: [CRUD, search, etc.]
- Authentication: [JWT/API key/OAuth]

For each endpoint provide:
1. HTTP method + path
2. Request headers
3. Request body (JSON schema)
4. Success response (with example)
5. Error responses (400, 401, 404, etc.)
6. Rate limiting recommendation
7. Pagination approach (if applicable)

Follow REST best practices. Use plural nouns, proper status codes.

Refactor this code to be more maintainable:

```[LANGUAGE]
[PASTE CODE]
```

Goals:
- Improve readability
- Reduce duplication
- Better error handling
- Add TypeScript types (if applicable)

Constraints:
- Don't change the public API/interface
- Keep the same behavior for all edge cases
- [Any other constraints]

Provide:
1. Refactored code
2. A numbered list of every change and why
3. Before/after comparison of key sections

Write unit tests for this function:

```[LANGUAGE]
[PASTE FUNCTION]
```

Testing framework: [Jest/Vitest/pytest/etc.]

Cover:
1. Happy path (expected inputs)
2. Edge cases (empty, null, undefined, zero, negative)
3. Boundary values (min, max, off-by-one)
4. Error cases (invalid input, thrown exceptions)
5. Type coercion cases (if applicable)

Aim for >90% branch coverage. Group related tests with describe blocks.

Write a SQL query for: [DESCRIBE WHAT YOU NEED]

Database: [PostgreSQL/MySQL/SQLite]

Tables involved:
[DESCRIBE YOUR SCHEMA OR PASTE CREATE TABLE STATEMENTS]

Requirements:
- [SPECIFIC REQUIREMENT 1]
- [SPECIFIC REQUIREMENT 2]

Provide:
1. The query with comments explaining each part
2. Expected execution plan notes
3. Index recommendations
4. Alternative approaches if performance matters

Write a conventional commit message for this change:

```diff
[PASTE GIT DIFF]
```

Rules:
- Format: type(scope): description
- Types: feat, fix, docs, style, refactor, test, chore
- Description under 72 characters
- Add body if change is non-obvious
- Add BREAKING CHANGE footer if applicable
- Reference issue number if provided: [ISSUE #]

Analyze these competitors for my business:

My business: [YOUR BUSINESS DESCRIPTION]
Competitors: [COMPETITOR 1], [COMPETITOR 2], [COMPETITOR 3]

For each competitor, analyze:
1. **Positioning**: How they describe themselves (tagline, hero copy)
2. **Pricing**: Tiers, free plan, enterprise
3. **Strengths**: What they do better than anyone
4. **Weaknesses**: Gaps, complaints, limitations
5. **Audience**: Who they're targeting
6. **Content strategy**: Blog, social, SEO approach

Then provide:
- Feature comparison matrix
- Gaps in the market I could exploit
- Positioning recommendations for my business

Convert these meeting notes into a structured summary:

Meeting notes:
"""
[PASTE RAW NOTES OR TRANSCRIPT]
"""

Output:
1. **Key Decisions** (numbered list)
2. **Action Items** (table: WHO | WHAT | BY WHEN)
3. **Open Questions** (things unresolved)
4. **Parking Lot** (mentioned but tabled)
5. **Next Meeting** agenda suggestions

Keep it under 1 page. Use bullet points, not paragraphs.

Generate OKRs for this goal:

Team: [TEAM NAME]
Goal: [HIGH-LEVEL GOAL]
Timeline: [QUARTER]
Current state: [WHERE YOU ARE NOW]
Desired state: [WHERE YOU WANT TO BE]

For each Objective (3 max):
- Make it inspiring and qualitative
- 3-4 Key Results each
- Each KR must be measurable with a specific number
- Include baseline and target
- Add confidence level (low/medium/high)

Also suggest:
- Leading indicators to track weekly
- Potential risks to each objective

Help me price my product:

Product: [DESCRIPTION]
Current price: [PRICE OR "not yet priced"]
Competitors' prices: [COMP 1: $X, COMP 2: $Y]
Target customer: [WHO]
Cost to deliver: [COST PER UNIT/CUSTOMER]
Current conversion rate: [IF KNOWN]

Analyze:
1. Value-based pricing recommendation
2. Competitive positioning (premium/match/undercut)
3. Tier structure (good/better/best)
4. Psychological pricing tactics
5. Launch pricing vs. steady-state pricing
6. Revenue projection at 3 price points

Write a job description for: [ROLE TITLE]

Company: [COMPANY NAME AND BRIEF DESCRIPTION]
Team size: [NUMBER]
Reports to: [ROLE]
Location: [REMOTE/HYBRID/ON-SITE]
Salary range: [RANGE]

Include:
1. Opening hook (why this role matters, not company history)
2. What you'll do (5-7 bullet points, start with verbs)
3. What we're looking for (requirements vs. nice-to-haves -- clearly labeled)
4. What we offer (concrete benefits, not vague perks)
5. How to apply

Rules:
- No "rockstar", "ninja", or "guru"
- No unnecessary degree requirements
- Use "you" language throughout
- Include salary range
- Gender-neutral language

Create a SWOT analysis for:

Business/Project: [DESCRIPTION]
Industry: [INDUSTRY]
Stage: [startup/growth/mature]
Key context: [ANY RELEVANT CONTEXT]

For each quadrant, provide 5-7 specific items (not generic):

**Strengths** - Internal advantages
**Weaknesses** - Internal limitations
**Opportunities** - External factors to exploit
**Threats** - External risks

Then provide:
- 3 strategies leveraging Strengths + Opportunities
- 3 strategies addressing Weaknesses + Threats
- Priority recommendation

Write a monthly investor update email:

Month: [MONTH/YEAR]
Key metrics:
- MRR: [CURRENT] (from [PREVIOUS])
- Customers: [COUNT]
- Burn rate: [AMOUNT]
- Runway: [MONTHS]

Highlights (good news):
- [HIGHLIGHT 1]
- [HIGHLIGHT 2]

Challenges (be honest):
- [CHALLENGE 1]

Asks (what you need help with):
- [ASK 1]

Format: Professional but warm. Under 500 words. Lead with metrics, then narrative.

Generate 5 unique story premises for a [GENRE] story.

Setting preferences: [TIME PERIOD/LOCATION]
Themes I'm interested in: [THEMES]
Tone: [dark/light/bittersweet/comedic]

For each premise include:
1. One-sentence logline (under 30 words)
2. Main character (name, flaw, want)
3. Central conflict
4. Stakes (what happens if they fail)
5. Twist potential (one surprising element)
6. Opening scene suggestion

Build a deep backstory for this character:

Name: [NAME]
Role in story: [PROTAGONIST/ANTAGONIST/SUPPORTING]
Age: [AGE]
The story needs them to: [KEY PLOT REQUIREMENT]

Generate:
1. **Core wound**: The defining childhood/past event
2. **Lie they believe**: The false belief born from the wound
3. **Ghost**: What haunts them (specific memory)
4. **Coping mechanism**: How they protect themselves
5. **Secret**: Something nobody knows
6. **Contradiction**: Behavior that clashes with their persona
7. **Pivotal relationship**: The person who shaped them most
8. **Sensory anchor**: A smell/sound/taste that triggers them
9. **What they'd die for**: Their non-negotiable
10. **Growth arc**: How the lie becomes truth by the end

Run a brainstorming session for: [PROBLEM/OPPORTUNITY]

Use these frameworks in sequence:

1. **First Principles**: Break the problem into fundamental truths. What must be true?
2. **Inversion**: What would make this problem WORSE? Now reverse those.
3. **Analogy**: What other industries solved a similar problem? How?
4. **Constraint Removal**: What if money/time/technology were unlimited?
5. **Worst Idea First**: What's the WORST way to solve this? What's useful in it?

For each framework, generate 3 ideas.
Then synthesize: pick the top 3 ideas overall and explain why.

Generate 20 brand name options for:

Business: [WHAT YOU DO]
Vibe: [modern/playful/premium/technical/warm]
Target audience: [WHO]
Must convey: [KEY ATTRIBUTE]
Avoid: [ANY WORDS/STYLES TO AVOID]

For each name provide:
- The name
- Why it works (1 sentence)
- Likely .com availability (common word = taken, unique = likely available)
- Pronunciation clarity (can someone say it after reading it once?)

Categories to explore:
- Compound words (Salesforce, YouTube)
- Invented words (Spotify, Figma)
- Real words repurposed (Slack, Notion)
- Abbreviations (IBM, AWS)
- Foreign words (Uber, Roku)

Polish this dialogue to sound more natural:

"""
[PASTE DIALOGUE]
"""

Character voices:
- [CHARACTER 1]: [AGE, personality, speech patterns]
- [CHARACTER 2]: [AGE, personality, speech patterns]

Rules:
- People interrupt, trail off, use filler words
- Remove "as you know" exposition
- Show subtext (what they mean vs. what they say)
- Each character should sound distinct (remove and you should still know who's talking)
- Keep it under [WORD COUNT] words

Build a world for a [GENRE] [story/game]:

Core concept: [HIGH-LEVEL IDEA]
Tone: [gritty/whimsical/epic/intimate]
Technology level: [medieval/modern/futuristic/mixed]

Generate:
1. **Geography**: 3 key locations with unique features
2. **Power structure**: Who rules and how
3. **Economy**: What drives trade and conflict
4. **Magic/Tech system**: Rules and limitations (crucial: what CAN'T it do?)
5. **Culture**: 2 contrasting societies with different values
6. **History**: 3 pivotal past events that shaped the present
7. **Current tension**: The conflict that starts the story
8. **Sensory details**: What does this world smell, sound, feel like?

Synthesize these sources into a literature review:

Topic: [RESEARCH TOPIC]
Sources:
1. [TITLE, AUTHOR, KEY FINDING]
2. [TITLE, AUTHOR, KEY FINDING]
3. [TITLE, AUTHOR, KEY FINDING]
[add more as needed]

Structure:
1. Overview of the research landscape
2. Key themes (group by theme, not by source)
3. Areas of agreement across sources
4. Areas of disagreement or debate
5. Gaps in the literature
6. Suggested future research directions

Academic tone. Use "Smith et al. (2024) found..." attribution style.

Explain [CONCEPT] at three levels:

1. **ELI5** (for a 5-year-old): Use a metaphor or story. No jargon.
2. **ELI15** (for a smart teenager): Some technical terms OK, focus on WHY it matters.
3. **Expert** (for a practitioner): Precise, technical, include edge cases.

For each level also include:
- One memorable analogy
- One common misconception
- One question that tests understanding

Give me the strongest arguments FOR and AGAINST: [DECISION/TOPIC]

Rules:
- Steelman both sides (make each argument as strong as possible)
- 5 arguments per side
- Include evidence or data for each point
- Flag which arguments are based on values vs. facts
- Rate each argument's strength: Strong/Moderate/Weak

Then:
- Identify the 1-2 arguments that should actually drive the decision
- What additional information would change the analysis?
- Your recommended decision and confidence level

Summarize this research paper/article:

"""
[PASTE ABSTRACT OR FULL TEXT]
"""

Provide:
1. **One-sentence summary** (under 25 words)
2. **Key finding** in plain English
3. **Method** used (brief)
4. **Sample size and population**
5. **Limitations** acknowledged by authors
6. **Limitations NOT acknowledged** (your analysis)
7. **Practical implications** (what should practitioners do differently?)
8. **Related questions** this raises (3 questions for future research)

Fact-check this claim:

"[PASTE CLAIM]"

Source: [WHERE YOU SAW IT]

Evaluate:
1. Is the core claim accurate?
2. Is the data/statistic being cited correctly?
3. Is important context being left out?
4. Is there a more accurate way to state this?
5. What's the original source of the data?
6. Any logical fallacies in how it's presented?
7. Confidence level in your assessment: High/Medium/Low

Important: If you're not sure, say so. Don't make up sources.

Analyze this data and provide insights:

Data:
"""
[PASTE CSV, TABLE, OR DESCRIBE THE DATA]
"""

Context: [WHAT THE DATA REPRESENTS]
Question I'm trying to answer: [YOUR QUESTION]

Provide:
1. **Summary statistics** (mean, median, range, etc.)
2. **Key patterns** (trends, outliers, correlations)
3. **3 actionable insights** (so what? what should we do?)
4. **Visualization recommendations** (what chart types to use)
5. **Caveats** (what this data CAN'T tell us)
6. **Follow-up questions** to investigate next

Write a formula for: [DESCRIBE WHAT YOU NEED]

Spreadsheet: [Excel/Google Sheets]
Data layout:
- Column A: [DESCRIPTION]
- Column B: [DESCRIPTION]
- [etc.]

Data starts on row [NUMBER]

Requirements:
- [SPECIFIC REQUIREMENT]
- Handle errors gracefully (no #N/A or #DIV/0!)

Provide:
1. The formula
2. Step-by-step explanation of each part
3. Example of what it returns
4. A simpler alternative if the formula is complex

Design a dashboard for: [ROLE/TEAM]

Business type: [B2B SaaS / E-commerce / Marketplace / etc.]
Stage: [Pre-revenue / Growth / Scale]
Current tools: [LIST]

Design:
1. **North Star Metric** (the ONE number that matters most)
2. **Daily metrics** (3-5 you check every morning)
3. **Weekly metrics** (5-8 for team review)
4. **Monthly metrics** (strategic, for leadership)
5. **Leading indicators** (predict future performance)
6. **Lagging indicators** (confirm past performance)

For each metric:
- Name and definition (unambiguous)
- Calculation formula
- Good/warning/bad thresholds
- Suggested visualization type

Design a survey to learn: [WHAT YOU WANT TO KNOW]

Audience: [WHO TAKES THIS SURVEY]
Distribution: [EMAIL / IN-APP / SOCIAL]
Target responses: [NUMBER]

Create:
1. **Screening questions** (1-2 to qualify respondents)
2. **Core questions** (8-12 max, mix of types)
3. **Demographic questions** (at the end, only what's needed)

For each question:
- The question text
- Answer type (multiple choice, scale 1-5, open text, ranking)
- Answer options (if applicable)
- Why this question is included
- Potential bias to watch for

Also include:
- Recommended survey flow
- Estimated completion time
- Sample size needed for statistical significance

Design an A/B test for: [WHAT YOU WANT TO TEST]

Current state: [CONTROL DESCRIPTION]
Proposed change: [VARIANT DESCRIPTION]
Primary metric: [WHAT YOU'RE MEASURING]
Current baseline: [CURRENT METRIC VALUE]
Minimum detectable effect: [HOW MUCH IMPROVEMENT MATTERS]

Provide:
1. **Hypothesis** (If we [change], then [metric] will [improve/increase] because [reason])
2. **Sample size calculation** (with assumptions)
3. **Test duration** recommendation
4. **Guardrail metrics** (what shouldn't get worse)
5. **Segmentation** plan (check results by segment)
6. **Decision framework** (when to call it, when to keep running)
7. **Common pitfalls** specific to this test

Convert this data from [SOURCE FORMAT] to [TARGET FORMAT]:

```
[PASTE DATA]
```

Requirements:
- [ANY FIELD MAPPING CHANGES]
- [NAMING CONVENTION: camelCase/snake_case/etc.]
- [NULL HANDLING: skip/default value]

Also provide:
- A script to automate this conversion (in [Python/JavaScript/etc.])
- Edge cases the script handles