Save My Prompts

Search

Search prompts, tags, categories and people

Newest prompts

Every public prompt as it goes up, staff picks included. New creators' first three prompts appear here after a quick review.

Latest published 1d ago

Newest public prompts

Images & Media

Diwali catalogue flat lay

Top-down flat lay of product for a Diwali catalogue: a brass diya with a real flame, marigold petals scattered loosely, a folded handloom cotton cloth in colour, warm tungsten light from the top right, natural shadows, slight film grain, leave the left third empty for text --ar 3:2 --style raw
Lena Hoffmann380 uses
Images & Media

Lo-fi study track for a long evening

Lo-fi hip hop instrumental for late-night study, 75 BPM, dusty vinyl crackle, mellow Rhodes chords, a soft sitar phrase every 16 bars, brushed snare, no vocals, no drops, steady energy for minutes minutes, title: title
Ankit Verma410 uses
Sales

Cold email follow-up after no reply (remix)

I sent this cold email days days ago and got no reply: paste first email Write one follow-up under 50 words. Don't say "just following up" or "bumping this". Add one new, useful thing: [a resource, a number or a short idea for their team]. Same single question at the end.
Priya Nair260 uses
Education

GS Mains answer, marked by a strict examiner

Evaluate my answer to this UPSC GS Mains question as a strict examiner: question (marks marks, word limit words). Score it out of marks and explain the score. Check: · Did I address every part of the directive word (discuss, critically examine, analyse)? · Introduction and conclusion · Data, and examples from India · A diagram or flowchart where one helps Then rewrite only my weakest paragraph. My answer: paste answer
Ankit Verma902 uses
Sales

Cold email for Indian SaaS founders (remix)

Write a 90-word cold email to the founder of company, an Indian SaaS startup that just [recent milestone: raised a round, launched on Product Hunt, crossed a number]. Open with that milestone as an observation, not congratulations. Then one sentence on what we do: our offer. Mention a price in ₹ only if they sell in India. End with a single yes/no question about a 15-minute call this week. No "Hope you're doing well", no "Greetings of the day", no exclamation marks.
Rahul Bansal410 uses
Marketing

WhatsApp broadcast for a weekend sale

Write a WhatsApp broadcast for brand, a category brand. Offer: offer, valid dates Audience: past customers who bought product in the last months months Constraints: under 60 words; the first line must work as the notification preview; one link placeholder link; an opt-out line at the end ("Reply STOP to unsubscribe"). Give three versions: English, Hinglish, and Hindi in Devanagari.
Rahul Bansal1,240 uses
Productivity

Standup update from my git log

Here's my git log since yesterday's standup: [paste git log --oneline --since=yesterday] Write my standup update in three lines: Done, Doing, Blocked. Group related commits, use plain words instead of commit jargon, and leave Blocked as "Nothing" if there's nothing in the log that suggests a blocker.
Asha Rao190 uses
Coding

Unit tests for a function I paste

Write test framework tests for the function below. Cover the happy path, the boundaries, invalid input, and one property that should always hold. Use test names that read as sentences. Don't mock what you don't own. If the function is hard to test, suggest the smallest refactor that would help. paste function
Arjun Mehta720 uses
Finance

Monthly spending summary from bank SMS

Below are my bank and UPI SMS alerts for month. Put each debit in one of: rent, groceries, eating out, travel, bills, shopping, EMI, transfers to family, other. Give a table with totals per category, the top 5 merchants, and anything that looks like a subscription I may have forgotten. Use ₹ and Indian number grouping (1,23,456). Don't repeat card or account numbers. paste SMS alerts
Kavya Reddy1,490 uses
Customer Support

Reply in Hinglish without sounding like a bot

You're replying to a customer message for business name, a type of business in city. Customers write in Hindi-English code-mix, so reply the same way: Roman script, short sentences, the Hindi words people actually use on WhatsApp ("ji", "bilkul", "thoda time lagega"), English for product names and numbers. Don't turn their Hindi into formal shuddh Hindi. Under 50 words. Customer message: paste message What I want to tell them: your answer, in any language
Priya Nair1,190 uses
Human Resources

Performance review self-assessment, honest and specific

Help me write my self-assessment for the period review. My role: role. What I was expected to deliver: goals or job expectations. My rough notes are below: things I shipped, things that slipped, feedback I got. Turn them into: 1. Three wins, each as situation → what I did → result, with a number or a named person who benefited where I have one. 2. One thing that didn't go well, owned plainly, with what I changed afterwards. No "my weakness is that I care too much". 3. What I want to get better at next, and the support I'd ask for. First person, plain sentences. Don't inflate anything that isn't in my notes; if a claim needs evidence I didn't give, mark it add evidence.…
Nisha Kapoor655 uses
Personal

Five dinners from what's in my fridge

I have: ingredients. I cook for number of people: [diet, e.g. vegetarian, no onion or garlic on Tuesdays]. Make a five-day dinner plan using mostly what I have, each under minutes minutes. Give a short shopping list for what's missing, grouped by aisle. Reuse ingredients across days so nothing goes to waste.
Tom Linden880 uses
Advertisement
Ad slot (preview)In-feed band · responsive (728×90 desktop, 300×250 phone)Shown only after AdSense approval and consent
Coding

Stack trace to root cause in three sentences

Read this stack trace from service name (language / framework). In three sentences: what failed, the most likely root cause, and the first thing I should check. Then list up to three other possible causes, ranked, each with the log line or metric that would confirm it. If the trace is cut off or ambiguous, say what extra information you need instead of guessing. paste stack trace
Arjun Mehta2,240 uses
Productivity

Decision log with a RACI table (remix)

Here are my raw notes from meeting. Turn them into: 1. A decision log: decision, owner, deadline. Write "unassigned" when no owner was named. 2. A RACI table for each decision (Responsible, Accountable, Consulted, Informed), using only names that appear in the notes. 3. A list of open questions. Flag any decision that has two Accountable people. Notes: paste notes
Meera Iyer380 uses
Sales

Reply to “it's too expensive” without discounting

A prospect just wrote back: "their message" We sell product at price. The deal is worth deal size and they're comparing us with alternative, or "doing nothing". Write a reply I can send today: · Acknowledge the concern once, in their words, without apologising for the price. · Ask one question that finds out what "expensive" is being measured against. · Give one concrete number from [proof: a customer result, hours saved, the cost of how they do it now], and nothing else. · Offer a smaller first step instead of a discount, if there is one: smaller option. Under 120 words. No "I totally understand", no "just checking in". Then, separately, tell me in two lines what I should not…
Vikram Shetty712 uses
Design

Light and dark colour tokens from one brand colour

Generate light and dark colour tokens from the brand colour hex. Output CSS custom properties for: page background, raised surface, sunken surface, primary text, secondary text, muted text, hairline, control border, focus ring and the primary button. Rules: · Body text must reach 4.5:1 against its background in both themes. Show the ratio next to each pair. · Don't put the brand colour on large surfaces. · Dark mode is designed, not inverted: lift surfaces with lightness, not shadows. :root { /* light */ } data-theme="dark" { /* dark */ }
Sofia Marquez640 uses
Coding

Blameless postmortem from an incident timeline

Turn this incident timeline into a blameless postmortem. 1. Summary: what users saw, for how long, how many were affected 2. Timeline: in time zone, one line per event 3. Root cause: technical, never "human error" 4. What went well, what didn't 5. Action items: owner, due date, and whether each one prevents or detects If the timeline has gaps longer than 15 minutes, point them out. Timeline: paste timeline
Daniel Okafor690 uses
Personal

A trip plan that isn't a tourist checklist

Plan number days in place for who's travelling in month. We like interests and dislike dislikes. Budget: budget per day, not counting where we stay. For each day: one anchor thing in the morning, a lunch place locals actually go to, a slow afternoon, and where to be at sunset. Group things by neighbourhood so we never cross the city twice. Flag anything that needs booking ahead.
Priya Nair1,150 uses
Design

UX critique of one screen

Critique this screen as a senior product designer: [describe the screen, or attach a screenshot]. The user's goal here is goal. Go through: · hierarchy: what do eyes hit first? · copy: is every label specific? · states: empty, loading, error · accessibility: contrast, focus order, touch targets · one thing to remove Rank findings by impact. Don't redesign the whole thing.
Sofia Marquez960 uses
Customer Support

Public reply to a one-star review

A customer left this review on Google, Amazon or our site: "review text" What actually happened, from our side: [order details, what went wrong, what we've already done]. Write a public reply that: · thanks them for the specifics, not for "the feedback" · says what went wrong in one sentence, without blaming the courier or the customer · says what we've done or will do, with a date if there is one · asks them to write to support email or WhatsApp number so we can finish fixing it Under 80 words. Future customers will read it as much as this one, so stay calm and specific. No "we value your business".
Rahul Bansal598 uses
Customer Support

Customer support reply for a refund

Write a customer support reply for a refund request. Order: order_id Reason they gave: reason Our policy: policy summary Decision: approve / partial / decline Acknowledge the specific problem first, explain the decision in one sentence, then give the exact next step and timeline. Under 90 words. Never write "we apologise for any inconvenience".
Rahul Bansal870 uses