Rough drafts, rewritten side by side.

Write a short, polite email to my manager requesting two days off next week. Mention the project stays on track and offer a brief handoff note.

Task first, tone, and the one constraint that matters.

In a React form, clicking Submit sometimes throws Cannot read properties of null. Walk through likely causes and give a concrete fix with a short code snippet.

Context + expected vs actual + ask for a fix path.

Refactor the pasted TypeScript for readability without changing behavior. Prefer smaller functions, clear names, and note any risk areas in 3 bullets.

Goal, constraints, and what not to change.

Given the pasted auth helper, propose unit tests covering happy path, expired token, missing claims, and clock skew. Use concise AAA-style cases.

Function under test and failure modes named.

Summarize peer-reviewed findings on remote vs office productivity since 2019. Note sample sizes, main caveats, and list 5 takeaways for a product team.

Scope, sources, and output shape up front.

Draft a one-page decision memo: build vs buy a team prompt optimizer. Cover cost, privacy risk, time-to-value, and a clear recommendation with 3 risks.

Decision, options, and recommendation format.

Write a 90-word cold email to a B2B marketing lead about a free Chrome tool that rewrites rough AI prompts on-device. One benefit, one soft CTA to try it.

Audience, offer, and a single clear ask.

Draft a 120-word LinkedIn post arguing that AI prompt tools should run on-device by default. Direct tone, no hype, end with one question for comments.

Voice, length, and the point of the post.

Turn the pasted meeting notes into: (1) a 5-bullet summary, (2) owners + due dates for action items, (3) open questions. Keep names and dates as written.

Input format and deliverable format specified.

Write SQL to list the top 20 customers by revenue in the last calendar month. Assume tables orders(customer_id, amount, created_at) and customers(id, name). Return name + total.

Schema assumptions and exact output needed.

Build a 4-week system-design interview plan for a mid-level engineer with ~6 hours/week. Include weekly topics, practice prompts, and how to self-check.

Level, time budget, and measurable milestones.

Explain WebGPU to a web developer who knows Canvas/WebGL basics. Use one analogy, cover what it unlocks in the browser, and list two practical limits.

Audience level and analogy preference.