Better prompts,
and better prompting.

Walk me through the methods section I'll paste below as if you're explaining it to a sharp reviewer from a neighbouring field. Define each technique in one plain sentence, flag any step missing a control or baseline, note whether the sample size is justified, and end with a short list of what someone would need to reproduce the study. Don't fill gaps with assumptions — flag them instead.

I'll paste a Python function that's O(n²) and crawls on lists over ~1M items. First tell me the most likely bottleneck, then give a faster version that keeps the exact same inputs, outputs, and public signature. State the new time and space complexity, call out any new dependency or trade-off, and add a one-line note on how to confirm the behaviour is unchanged.

Write 8 landing-page headlines for a time-tracking app aimed at freelance designers who feel guilty about unbilled hours. Lead with the outcome, keep each under 9 words, and mix the angles — lost income, professional pride, effortless habit. Avoid “effortless,” “seamless,” and “revolutionise,” and add one subhead option under your strongest pick.

Critique the landing-page mockup I'll attach as a senior product designer doing a 10-minute review. Focus on visual hierarchy, contrast, spacing rhythm, and whether the primary CTA is unmistakably the most prominent element. Give me 3 concrete changes ranked by impact, one quick win I can ship today, and flag anything that fails WCAG colour-contrast.

Write 3 user stories for adding saved search filters to our dashboard, in the “As a [user], I want [x], so that [y]” format. For each, add acceptance criteria as a testable checklist, name one edge case we'd otherwise miss, and note the analytics event we should fire. Keep each small enough to ship in a single sprint.

Draft a reply to a customer who's angry about being charged twice. Open by acknowledging the mistake plainly — no corporate hedging — confirm the refund lands in 5–7 business days, and explain in one sentence how we'll stop it recurring. Keep it under 100 words, warm and human, never defensive, and give them a direct way to reach me if it isn't resolved.

Pressure-test the 30-second pitch I'll paste for my B2B scheduling tool. First, ask me the 5 toughest questions a seed-stage investor would ask after hearing it. Then rewrite the pitch so it pre-empts the two biggest objections, makes the market size concrete, and ends on traction. Jargon-free and under 90 words — I should be able to say it in one breath.

Turn the four findings I'll paste into a single executive slide. Give me one headline insight (the “so what”), three supporting bullets of 12 words or fewer, and a recommended next step with a rough effort flag. The audience is a non-technical COO deciding whether to fund the project, so cut anything that doesn't change their decision.

Write a follow-up email to a prospect who went quiet two weeks after a demo. Reference the specific problem they raised — onboarding takes their team too long — and lead with a concrete way we shorten it. Offer one easy next step (a 15-minute call or a shared doc), keep it to four sentences, and don't sound needy or guilt-trippy.

Explain photosynthesis the way a great tutor would, for someone revising for a high-school exam. Give the overall word equation, then the light-dependent and light-independent stages in plain English with a memory hook for each. Use one everyday analogy, keep it under 250 words, and end with 3 exam-style questions — hold the answers until I ask so I can test myself first.

Create a 10-question quiz on the causes of World War II for 9th-grade students. Mix multiple-choice and short-answer, order them easier to harder, and make sure two questions test cause-and-effect rather than recall. Include an answer key with one-line explanations, and add a single open-ended discussion question that has no single right answer.

I'll paste a table of sales by region and month. Identify the three most important trends, call out anything that looks like an anomaly or data-quality issue worth checking before I trust it, and recommend the single chart that would make the story clearest to a non-technical exec. Keep the takeaways in plain language and don't speculate about causes you can't see in the data.

Write a job post for a mid-level backend engineer (Go, mostly remote). Lead with the impact they'll have in their first 90 days instead of a wishlist, list 5 genuine must-haves and 3 nice-to-haves, and state the salary band up front. Keep the tone human and specific to us, cut the “fast-paced environment” clichés, and end with exactly what the first interview looks like.

Summarise the vendor contract I'll paste for a non-lawyer founder. In plain English, flag the termination clauses, liability caps, indemnities, and any auto-renewal; list anything that looks unusual or one-sided; and give me the 3 questions I should ask before signing. Note where I'd genuinely need a lawyer to weigh in. (This is a summary, not legal advice.)