Write a reply to the email below. Tone: {professional but warm}. Goal: {decline the request without burning the relationship}. Keep it under {120} words. Don't apologise more than once.

Email:
```
{paste email here}
```

Write a cold email to {target_name}, {their_role} at {company}. I'm {your_name}, {your_role}. We help {what_you_help_with}. Hook: {something specific you noticed about them}. Keep it under 120 words. End with one specific question they can answer in one line.

Summarise the document below in three layers:

1. **TL;DR** - One sentence.
2. **Key points** - Bullet list, max 7.
3. **Action items** - What should I actually do based on this?

Document:
```
{paste here}
```

Write a Twitter post (max 280 chars) about: {topic}.

Tone: {casual, direct, mildly opinionated}. No hashtags. Include exactly {one} concrete detail or stat. Avoid AI-cliche phrases like 'in today's world' or 'unlock the power of'.

Rewrite the text below to sound more human and less AI-generated. Vary sentence length more. Use occasional contractions. Cut hedges ("may", "can be", "perhaps"). Keep the same factual content.

Text:
```
{paste here}
```

Edit the text below for clarity only. Don't change the voice or tone. Find: redundant phrases, unclear pronouns, sentences over 30 words, jargon without context. Return: the edited text + a numbered list of what you changed and why.

Text:
```
{paste here}
```

Review the code below. Focus on:
1. Bugs or logic errors
2. Security issues
3. Readability / naming
4. Performance issues that actually matter

Skip nitpicks (style, formatting). Be direct - Assume I'm a senior engineer.

```{language}
{paste code here}
```

Explain the code below at the level of a {junior developer who just learned the language}. Annotate each block with what it does and why. End with a one-paragraph summary of the overall design choice.

```{language}
{paste code here}
```

Translate the SQL query below into plain English a non-technical PM would understand. Don't include the table names - Just describe what we're getting and any filters / aggregations applied.

```sql
{paste SQL here}
```

Write a regex that matches: {describe what you want to match, with examples and counter-examples}. Return:
1. The regex itself
2. A line-by-line explanation
3. 5 test inputs with expected match / no-match results

Write {pytest} tests for the function below. Cover: happy path, edge cases (empty/None/large), boundary values, and at least one realistic failure mode. Use parametrize where it makes sense.

```python
{paste function here}
```

Refactor the function below for readability. Same behaviour, clearer code. Extract sub-functions only if it actually helps. Use early returns. Name variables for what they mean, not what they are. Briefly explain each change at the end.

```{language}
{paste code here}
```

I'm hitting this error:

```
{paste full stack trace here}
```

Code that produced it:
```{language}
{paste relevant code}
```

Tell me:
1. The most likely root cause (with reasoning)
2. The fix
3. Two other things that could cause this same error if I'm wrong about #1

I currently believe: {your_position}.

Steelman the opposing view in the strongest possible terms. Use 4-5 paragraphs. Don't strawman, don't write 'some say'. Make the strongest version of someone who actually disagrees with me. End with: 'A reasonable person might still disagree because…'

I'm choosing between these options:
1. {option_A}
2. {option_B}
3. {option_C}

My priorities (most important first): {priorities}.

Build a decision matrix. Rate each option (1-10) on each priority. Sum and recommend. Tell me which factor would change your recommendation if it shifted.

I'm about to {decision or project}. Run a pre-mortem: assume it's 6 months later and this failed badly. Walk me through the most likely failure modes, ranked by probability × impact. For each, give one specific thing I should do now to prevent it.

Apply the 5-Whys technique to: {problem}.

After each 'why', take the answer and ask 'why' again. Stop when you hit a root cause that's actionable. Then: propose two specific fixes, one tactical and one systemic.

Brainstorm 20 ideas for: {topic}.

Quantity over quality. Include some weird, impractical or risky ones. Group them at the end into: 'safe', 'medium', 'wild'. Don't number-pad - If you only have 12 good ones, give me 12.

Explain {topic} like I'm 12 years old and curious. Use one analogy from everyday life. Avoid jargon - If you must use a technical term, define it the first time.

Quiz me on {topic} with 10 multiple-choice questions. Mix difficulty (3 easy, 5 medium, 2 hard). Show me one question at a time. After I answer, tell me if I'm right and why. Track my score.

Compare and contrast {thing_A} and {thing_B}. Structure:

1. **What they have in common** - Bullet list
2. **Key differences** - Bullet list
3. **When to pick each** - One paragraph each
4. **Common mistakes** - What people get wrong about the difference

I want to learn {topic} starting from {current_level}. I have {hours_per_week} hours per week and a goal of {what_you_want_to_achieve} in {timeframe}.

Build me a week-by-week study plan. Include resources (books, courses, practice problems). Budget time for spaced review. End each week with a self-test.

Turn these meeting notes into a professional summary email. Sections:

1. **Decisions made**
2. **Action items** - Owner, deadline, what specifically
3. **Open questions** - What we still need to figure out
4. **Next meeting** - Date and agenda preview

Notes:
```
{paste notes here}
```

I'm prepping for a 1-1 with {my_manager}. My current focus: {what_you're_working_on}. Recent wins: {wins}. Recent struggles: {struggles}.

Help me prepare:
1. 3 things I should proactively share
2. 2 questions I should ask my manager
3. 1 ask (resource, decision, support) I should make

Rewrite this Slack message so it's more likely to actually get a reply. It's currently too long / vague / passive. Make it scannable, end with a clear ask with a deadline.

Message:
```
{paste message here}
```

I'm setting OKRs for {team or project} for {Q1 / Q2 / etc}. Top-level goal: {goal}. Constraints: {team size / budget / time}.

Suggest 3 candidate Objectives. For each, propose 3 Key Results - Measurable, time-bound, ambitious-but-not-impossible. Flag any KRs that risk gaming.

Brainstorm 30 product name candidates for: {product description}. Mix of styles: invented words, descriptive compounds, metaphors, person names, abstract verbs. Include a 1-line tagline for each. End with your top 3 picks and why.

Write 5 different opening paragraphs for a story about: {premise}. Each should use a different technique: in-medias-res, dialogue-first, single haunting image, unreliable-narrator confession, sensory immersion. Each opening: 80-150 words.

Workshop my story logline.

Current logline: {your_logline}

1. What's working
2. What's confused or weak
3. Three rewrites - Each emphasising a different angle (character / conflict / theme)
4. Recommend one rewrite as the strongest, with reasoning

Generate 25 taglines for: {product / company}. Tone: {bold and witty}. Mix lengths: 3-word punchy, 7-word descriptive, 12-word storytelling. Include a couple of self-deprecating ones. Don't use the words {forbidden_words}.

I'm thinking about: {idea}. 

Roast it. Be honest, specific, slightly mean - But constructive. Find 5 weak spots in the idea. For each, suggest one way to fix or sidestep it. End with: 'Here's how I'd actually pitch this if I was forced to.'

Portrait of {a person or character description}, shot on {35mm film / Hasselblad medium format}, {golden hour / overcast / studio} lighting. Shallow depth of field, {bokeh background}. Mood: {melancholic / triumphant / serene}. Ultra-detailed skin texture, natural imperfections. No AI smoothing.

{Product name and brief description} on a clean white background. Studio lighting with soft contrast. Shot from {front / 3/4 angle / top-down}. Photorealistic. Suitable for {Amazon / Shopify / magazine ad}. No props, no background clutter. High resolution.

Exterior render of {building description: a 3-storey Scandinavian townhouse with floor-to-ceiling windows}. Style: {modern / brutalist / art nouveau}. Time of day: {golden hour}. Weather: {clear sky with a few clouds}. Surrounded by {mature trees / urban streetscape / landscaped garden}. Photorealistic architectural visualization, 16:9 ratio.

A sweeping fantasy landscape: {describe the scene, e.g. a floating island city above storm clouds, lit by twin moons}. Art style: {concept art / matte painting / oil painting}. Colour palette: {warm golds and deep purples}. Epic scale, tiny {figures / ships / creatures} for sense of size. No text, no watermarks.

Minimalist logo for {brand name}, a {brand description: B2B SaaS company for project management}. Style: {geometric / wordmark / icon-only}. Colour: {primary: #4f46e5 indigo, on white background}. Clean vector-style, simple solid fills, no heavy lighting effects. Transparent background (PNG). Works at 32px and 512px.

Close-up food photography of {dish description: a bowl of ramen with chashu pork and a soft-boiled egg}. Shot from {45-degree angle / top-down / side}. Lighting: {natural window light / warm restaurant ambient}. Styled with {minimalist props: dark ceramic bowl, chopsticks, steam rising}. Shallow DOF, mouth-watering, editorial quality.

Flat vector illustration of {scene: a person working from a coffee shop with a laptop}. Style: {modern flat / isometric / line art}. Colour palette: {pastel blues and greens, white background}. Solid colors, clean shapes, suitable for a {website hero / app onboarding screen / blog post header}. 16:9 aspect ratio.

Split image: left side shows {before state: a cluttered, outdated kitchen from the 1990s}. Right side shows {after state: the same kitchen renovated with handleless white cabinets and marble countertops}. Same camera angle, same lighting. Realistic photo style. Thin dividing line in the middle. No text overlay.

Short video (3-5 seconds): {product, e.g. a luxury perfume bottle} slowly rotating on a black reflective surface. Dramatic studio lighting, lens flare at the end. Camera: slow dolly-in. Motion: product rotates 180 degrees. Cinematic colour grade: high contrast, deep blacks. No text.

Timelapse of {scene: storm clouds rolling over a mountain range at sunset}. Duration: 4-6 seconds. Camera: static wide shot. Fast-moving clouds, shifting golden and purple light. Photorealistic. Smooth motion. No camera shake.

Seamlessly looping 2-second walk cycle of {character: a robot courier in a futuristic city}. View: {side profile / 3/4 front}. Style: {3D rendered / 2D cartoon / pixel art}. Background: {scrolling neon-lit street}. Smooth movement, consistent lighting throughout loop.

Close-up video of {a professional man in his 40s wearing a navy suit} speaking directly to camera. Background: {blurred office bokeh / solid studio backdrop}. Lighting: {soft key light from left, subtle fill}. Natural head movement, eye contact. Duration: 3-5 seconds. Photorealistic.

2-second logo reveal animation for {company name}. Style: {particles assembling into logo / quick fade with light sweep / elastic bounce in}. Background: {black / white / solid brand colour}. End on a clean hold for 1 second. No sound cues needed in prompt.

Aerial drone shot flying over {location: a coastal cliff with crashing waves below}. Duration: 4-6 seconds. Motion: {slow forward push / banking turn / rising reveal}. Time of day: {golden hour / blue hour}. Photorealistic, smooth gimbal-stabilized footage. No subjects in shot.

Looping abstract motion background (4 seconds). Style: {fluid ink drops / geometric morphing / particle wave}. Colour palette: {deep purple, electric blue, white accents}. Suitable as a {website background / presentation slide / video overlay}. No hard edges, smooth transitions, seamless loop.