40 prompts that save time

Review this {{language|TypeScript}} code. Context: {{what the code does}}. Check in this order: 1. Bugs and edge cases (null, empty lists, races, overflow). 2. Security: injections, leaked secrets, unsafe input. 3. Performance: extra passes, N+1 queries, memory leaks. 4. Readability: naming, function length, duplication. For each issue give the line or snippet, why it is a problem and a fixed version. Mark severity: critical / should fix / nit. End with the top three changes. ``` {{code}} ```

Explain what this SQL query ({{database|PostgreSQL}}) does, step by step: the order in which parts run, what it returns and why. Then: - point out possible bugs (duplicates from JOINs, NULLs in conditions, wrong grouping); - suggest indexes that would speed it up and how to verify that with EXPLAIN ANALYZE; - if it can be written simpler or faster, show the rewrite. ```sql {{query}} ```

Refactor this code. Goal: {{goal|make it easier to read and test}}. Rules: - behavior and public interface stay the same; - no new dependencies; - small steps, each one could be a separate commit. Show: the list of steps with reasons, the final code in full, and which tests to write first so the refactor is safe. ```{{language|ts}} {{code}} ```

Write unit tests with {{framework|Vitest}} for the code below. Cover: - normal cases; - edge values (empty input, zero, very large values, unicode); - errors and exceptions; - whatever is easy to break with future changes. Name each test as "does X when Y". Do not mock what can be checked directly. Finish with cases you deliberately left out and why. ``` {{code}} ```

Write a Conventional Commits message in {{message language|English}} for this diff. - First line: type(scope): what changed, up to 72 characters, imperative mood. - Blank line, then 2–5 bullets: why the change was made and what a reviewer should know. - Add a BREAKING CHANGE block if anything breaks. - If the diff mixes unrelated changes, suggest how to split it into separate commits. ```diff {{diff}} ```

Write a regular expression for {{engine|JavaScript}} that matches: {{what to match}}. Should match: {{matching examples}} Should not match: {{non-matching examples|invent 5 similar but invalid strings}} Explain the pattern piece by piece, show a check table against every example, and warn about catastrophic backtracking (ReDoS) if it is possible.

Help me find the cause of this error. Environment: {{environment|Node.js 22, macOS}} What I did: {{steps}} What I expected: {{expected}} Message and stack trace: ``` {{error}} ``` Code near the failure: ``` {{code}} ``` Give the 3 most likely causes, most likely first. For each: how to check it quickly (command, log line, breakpoint) and how to fix it. Do not rewrite the whole code, only the parts that matter.

Design a REST API for: {{task}}. Constraints: {{constraints|up to 1,000 requests per minute, token auth}}. Include: - resources and endpoints (method, path, purpose); - example requests and responses in JSON; - error codes and one error format; - pagination, filters, idempotency for POST; - API versioning and how to evolve it without breaking clients. End with 3 decisions you are unsure about and their alternatives.

I am a {{my level|mid-level developer}} and see this code for the first time. Explain: 1. What it does, in two sentences. 2. How it works, block by block, with line numbers. 3. The non-obvious parts: language tricks, side effects, hidden dependencies. 4. What breaks if I change {{what I want to change|the input data}}. ``` {{code}} ```

Write a Dockerfile and docker-compose.yml for this stack: {{stack|Node.js 22 + PostgreSQL 16 + Redis}}. Requirements: - multi-stage build, smallest possible final image; - run as non-root; - a healthcheck for every service; - environment variables via .env, no secrets baked into the image; - volumes for database data. After the files, give the commands to start, follow logs and clean up fully, plus a short list of what to change for production.

Help me reply to this email. Email: """ {{email}} """ What I want to say: {{main point}} Tone: {{tone|polite and businesslike}} Recipient: {{recipient|a colleague at another company}} Write a reply under 120 words: no corporate filler, with a clear next step and deadline if needed. Give two versions: a shorter one and a softer one.

Rewrite this text as a post for {{platform|LinkedIn}}. Audience: {{audience|founders and marketers}} Goal: {{goal|get people to read to the end and click the link}} Rules: the first line hooks with something concrete, not "Did you know…"; short paragraphs; no jargon or stacked exclamation marks; up to {{length|800}} characters; one call to action at the end. Source text: """ {{text}} """ Give 2 versions with different opening lines.

Edit this text: make it simpler and about {{how much|30%}} shorter while keeping the meaning and facts. Remove: jargon, nominalizations, needless passive voice and filler phrases ("in order to", "it is important to note", "leverage"). Show the final text, then a "before → after" table for the 5 most noticeable edits with the reason. """ {{text}} """

Write a meeting summary from these notes or transcript. Meeting: {{meeting topic}}, attendees: {{attendees|from the text}}. Format: **Decisions** — a list. **Action items** — table: what / who / due date. If the owner or date is missing, write "not assigned". **Open questions** — what was left unanswered. **TL;DR for people who missed it** — 3 sentences. Do not invent anything: use only what is in the text. """ {{notes}} """

Write a cover letter for this job. Job posting: """ {{job posting}} """ My experience: {{experience}} Why this company: {{motivation|suggest questions I should ask myself}} Up to 200 words. Do not open with "My name is"; open with how I can help with their needs. Link 2–3 job requirements to concrete results from my experience, with numbers. No clichés like "team player" or "works well under pressure".

Suggest 10 headlines for an article about {{topic}}. Audience: {{audience|general readers}}. Where it will run: {{venue|company blog}}. Mix approaches: benefit with a number, question, how-to, common mistake, surprising fact. Up to 70 characters, no clickbait or promises the article does not keep. Mark the top 3 and explain each pick in one sentence.

Translate this text into {{language|Russian}} the way a native speaker would write it, not word for word. Context: {{where it appears|app interface}}. Tone: {{tone|friendly, formal "вы"}}. Keep formatting, placeholders in braces, and these terms untranslated: {{terms|none}}. After the translation, list the places where you departed from the original and why (idioms, cultural references, string length). """ {{text}} """

I need to tell {{whom|my manager}} something unpleasant: {{situation}}. What I want to achieve: {{goal|keep the relationship and agree on a solution}}. Suggest: 1. An opening line: calm, no excuses, no blame. 2. A 3–4 step structure for the conversation. 3. Three likely objections and how to answer them. 4. Phrases to avoid and what to say instead.

Write a description for {{what we sell}}. Specs and facts: {{facts}} Buyer: {{buyer|someone comparing 3–4 similar options}} Where it appears: {{venue|marketplace listing}} Structure: headline with the main benefit → 3–5 "what you get" bullets (benefits, not specs) → answer to the buyer's main doubt → short call to action. Use only the facts provided; do not invent any.

Outline a {{slide count|10}}-slide presentation. Topic: {{topic}} Audience: {{audience|company leadership}} What they should decide or remember: {{goal}} Talk length: {{minutes|15}} minutes. For each slide: an action title (a full sentence, not "Summary"), 2–3 points, what to show visually (chart, diagram, photo) and rough timing. The first slide states the problem; the last one makes a concrete ask.

Do a SWOT analysis for: {{company or project}}. Market: {{market|EU small businesses}} What is known: {{facts|public information only}} 4–6 points per quadrant, concrete, no vague items like "strong team". Flag where you rely on assumptions. Then give 3 strategies from the intersections: S+O (exploit), W+O (improve), S+T (defend), and what to do in the next 90 days.

Analyze this data and answer: {{question}}. Source: {{source|CRM export}} ``` {{data}} ``` I need: 1. Key observations with numbers (5 at most). 2. What looks like an anomaly or a data error. 3. Which conclusions cannot be drawn and why (small sample, correlation ≠ causation, seasonality). 4. What extra data would make the answer more certain. 5. Which chart would show this best.

Compare {{our product}} with competitors: {{competitors}}. Criteria: {{criteria|price, key features, ease of use, support, best fit}}. Use a table. Where you are unsure of a fact, mark it "verify" and do not invent numbers. Below the table: - where competitors are genuinely stronger; - 2–3 unclaimed niches; - one positioning line competitors cannot say about themselves.

Help me choose between: {{options}}. What matters to me: {{criteria}} Constraints: {{constraints|budget and timeline}} Build a weighted matrix: propose criteria weights (summing to 100%) and explain them, score each option 1–5 with a short reason, compute totals. Then test robustness: which weight would have to change for another option to win. Finish with questions I should ask myself before deciding.

Calculate unit economics for {{business}}. Inputs: - average order value: {{average order value}} - cost of goods or variable cost per order: {{costs}} - customer acquisition cost (CAC): {{CAC|unknown, estimate from the market and flag it}} - repeat purchases: {{repeat purchases|unknown}} Show the math step by step: margin per order, LTV, LTV/CAC, payback period. Then name the 2 parameters with the biggest effect and what happens if each moves ±20%.

Problem: {{problem}}. When it started and what changed right before: {{context|unknown}}. Use the "5 whys" method, but keep several branches if there may be more than one cause. For each branch, name the fact that would confirm or rule out the hypothesis and how to get it quickly. Finish with the most likely root cause, a stopgap for today, and a systemic fix so it does not happen again.

Here are {{what this is|customer reviews}}, one per line: """ {{reviews}} """ Group them by theme. For each theme: name, number of mentions, sentiment (positive / neutral / negative) and 1–2 verbatim quotes. Sort themes by frequency. Then list the 3 main problems to fix first and 1–2 strengths customers mention on their own.

Build a risk register for: {{project}}. Timeline: {{timeline|3 months}}. Team: {{team|5 people}}. Budget: {{budget|limited}}. Table: risk / likelihood (low, medium, high) / impact / early warning sign / mitigation / owner. 10–12 risks, including non-obvious ones: key-person dependency, vendors, legal issues, data. Sort by likelihood × impact.

Here is a text or position: """ {{text}} """ Act as a strict but fair opponent: 1. List the claims and what each one rests on. 2. Find logical fallacies, shifting definitions and unproven assumptions. 3. Which facts need checking and where to look. 4. The strongest counterargument. 5. How to strengthen the original position if it is broadly right.

Help me with an A/B test. What we change: {{change}} Primary metric: {{metric|purchase conversion}} Current metric value: {{baseline}} Traffic: {{traffic|1,000 visitors a day}} 1. State the hypothesis as "if…, then…, because…". 2. Compute sample size and test duration for a minimum effect of {{minimum effect|10% relative}} at α = 0.05 and 80% power. Show the formula. 3. Which guardrail metrics to watch so we do no harm. 4. Common mistakes: peeking, novelty effect, weekday traffic differences. If the test already ran, here are the results: {{results|no test yet}} — assess significance and say whether we can decide.

Explain {{concept}} so that {{who|a five-year-old}} would understand. Use one everyday analogy and carry it all the way through. No jargon; if a term is unavoidable, explain it at once. Under 150 words. Then explain the same thing again for {{second level|a high-school student}} and show where the first analogy stops working.

Make {{how many|20}} spaced-repetition (Anki) flashcards from the material below. Rules: - one fact per card; - unambiguous question, short answer (15 words max); - besides definitions, include "why" and "how is X different from Y" cards; - no yes/no cards. Output: CSV with ";" as the separator — question;answer;tag. Tag: {{tag|topic}}. Material: """ {{material}} """

Write {{how many|10}} self-check questions on "{{topic}}" at {{level|first-year university}} level. Mix the types: 4 multiple choice (one correct, three plausible wrong answers), 3 open questions that test understanding, 3 application problems. Show the questions first. Put answers with short explanations in a separate block at the end under "Answers", so I can try on my own first.

Build a study plan for: {{topic}}. Current level: {{current level|almost nothing}} Goal: {{goal|use it confidently at work}} Time: {{hours per week|5}} hours a week for {{weeks|8}} weeks. Week by week: what to study, a hands-on task, and how to check the topic has stuck. Include review of earlier weeks. Mark topics that can be skipped if time runs short. Suggest only sources you are sure exist.

Be my tutor on "{{topic}}". Do not give me ready answers. Ask one question at a time, from simple to hard. If I am wrong, do not correct me at once; ask a guiding question. If I am stuck twice, give a hint. Every 5 questions, briefly sum up what I have understood and what I have not. My level: {{level|beginner}}. Start with a question that reveals what I already know.

Summarize this text for {{purpose|seminar prep}}. Structure: 1. The main idea in one sentence. 2. Key claims with their arguments, 5–7 points. 3. Terms and definitions. 4. What is debatable or weakly supported. 5. Three discussion questions. Length: up to {{length|300}} words. Use only what is in the text; if something is missing, say so. """ {{text}} """

Let's practice {{language|Spanish}} at {{level|B1}} level. Situation: {{situation|checking into a hotel and there is a problem with the room}}. You play the other person. Keep your lines short, like real speech. After each of my replies, on a separate line in brackets, correct my mistakes and suggest a more natural way to say it. Put useful new words in bold. After 10 exchanges, give a review: 3 recurring mistakes and what to practice.

Solve this {{subject|math}} problem and explain every step: which rule or formula applies and why that one. Problem: """ {{problem}} """ At the end, check the answer another way or by substitution. Then make up a similar problem with different numbers for me to solve, and give only its answer.

Build a concept map for "{{topic}}" at {{level|high-school}} level. 1. 10–15 key concepts, from basic to advanced. 2. Links between them as "A → (how related) → B". 3. Diagram code in Mermaid (graph TD) so it can be rendered. 4. Three common misconceptions about the topic and why they are wrong.

Run a mock interview with me for {{position}} at {{company|a product tech company}}. Ask one question at a time: first about my experience, then technical, then behavioral (STAR method). After each answer, give a short 1–5 score, what worked and how to strengthen the answer. {{number of questions|8}} questions in total. Finish with an overall review and 3 questions I should ask the employer.