I want to ________.

Here are three samples of writing whose voice I want you to learn:

[PASTE 3 SAMPLES]

Study the sentence length, rhythm, vocabulary, and attitude. Describe the voice back to me in five bullet points. Then wait — I'll give you a writing task, and you'll do it in exactly that voice. Never drift into generic-assistant tone.

Here's a draft: [PASTE DRAFT]

Rewrite it with these rules:
- Cut it by 30%. Kill every sentence that repeats an idea.
- Replace every vague claim with a specific one (invent nothing — flag anything you can't make specific).
- First sentence must earn the second. If it doesn't, rewrite it until it does.
- No em-dash chains, no "delve", no "in today's fast-paced world".

Show me the rewrite only.

Write a cold email to [WHO] about [WHAT I OFFER].

Rules:
- 80 words max. Their problem in line one — not my name, not my company.
- One specific observation about them that proves this isn't a blast ([PASTE ONE FACT ABOUT THEM]).
- The ask is a question they can answer in one word.
- No "I hope this finds you well", no "quick question", no exclamation marks.

Give me 3 versions: direct, curious, and slightly cocky.

My offer: [DESCRIBE WHAT YOU SELL AND THE PRICE]

Attack it:
1. Name the three biggest reasons someone who NEEDS this still wouldn't buy.
2. For each, rewrite the offer so that reason dies (change framing, guarantee, price structure, or naming — not the product).
3. Then give me the single strongest version and one line on why it beats the original.

Be brutal. Flattery costs me money.

I want to build: [DESCRIBE THE IDEA IN ONE MESSY PARAGRAPH]

Turn it into a one-page spec:
- The job: who uses it and the one thing it must do well.
- The walkthrough: the user's first five minutes, step by step.
- The pieces: screens/parts needed for ONLY that walkthrough — cut everything else to a "later" list.
- The risk: the one assumption most likely to kill this.

Ask me a maximum of 3 questions first if anything blocks you. Otherwise, write it.

I hit this error: [PASTE THE FULL ERROR + THE CODE OR ACTION THAT CAUSED IT]

Do this in order:
1. Say what the error actually means in one plain sentence — no jargon.
2. Name the most likely cause in MY case, not the generic textbook cause.
3. Give the smallest possible fix — one change, not a refactor.
4. Tell me how to confirm it worked in under a minute.

If you need something I didn't paste, ask for exactly that one thing.

Here's a meeting transcript/notes: [PASTE]

Produce exactly three lists:
- DECIDED — what was actually agreed (not discussed — agreed).
- OWNED — every action item as "person → task → by when". If any of the three is missing, write FLAG.
- OPEN — questions raised and left unanswered.

Nothing else. If the meeting decided nothing, say that in one line at the top.

Every week I: [DESCRIBE THE REPEATED TASK, STEP BY STEP, TOOLS INCLUDED]

Map it for automation:
1. Break it into trigger → actions → final check.
2. For each step: can it run without me? Mark AUTO, ASSIST (AI drafts, I approve), or ME (only I can).
3. Recommend the simplest tool that wires the AUTO steps (Zapier / Make / n8n / a script) and why.
4. Estimate minutes saved per week.

Then give me the first step to set up tonight in under 30 minutes.