
Search
tool:claude
44 public prompts
Prompts

Ankit Verma3,120 uses

Save My Prompts1,840 uses

Kavya Reddy1,388 uses

Save My Prompts2,210 uses

Save My Prompts1,288 uses

Save My Prompts6,214 uses

Priya Nair1,520 uses

Save My Prompts2,988 uses

Save My Prompts4,870 uses

Save My Prompts3,311 uses
Advertisement
Ad slot (preview)In-feed band · responsive (728×90 desktop, 300×250 phone)Shown only after AdSense approval and consent

Arjun Mehta1,955 uses
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
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
Here are my raw notes from meeting. List every decision we made, who owns it and the deadline. Put open questions in a separate list.
If nobody was named as owner, write "unassigned"; don't guess. Keep each item to one line. Then write a three-line summary I can paste into Slack channel for people who weren't there.
Notes:
paste notes
Daniel Okafor1,960 uses
Act as a senior product manager. Turn the idea below into a first-draft PRD.
Idea: one paragraph about the feature
Users: who it's for
Constraint: deadline, team size or tech limit
Problem
What's broken today, in the user's words. One paragraph.
Goals and non-goals
Three of each. The non-goals matter more.
User stories
Five at most, as "As a …, I want …, so that …".
Success metrics
One primary metric with a target, and two guardrails.
Open questions
Anything you had to assume, marked clearly.
Don't invent research data. Where you'd need data, write needs data.
Meera Iyer1,402 uses
Write a 90-word cold email to a role at company.
Open with one specific detail from their recent launch or post: an observation, not a compliment. Then say in one sentence what we do: our offer. End with a single yes/no question.
No "I hope this finds you well", no exclamation marks, no bullet points. Give me two versions: one plain, one slightly warmer.
Priya Nair2,132 uses
Turn these notes on topic into Anki flashcards.
· One fact per card.
· Front: a question, not a fill-in-the-blank.
· Back: the answer in under 15 words, plus the line from my notes it came from.
· Use cloze cards only for dates and Article numbers.
Output as CSV with the columns front,back,tags and the tag deck name. Skip anything that isn't in my notes.
paste notes
Ankit Verma1,450 uses
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
Name joins as a role on start date, reporting to manager. The team is team size people working on what the team does.
Draft a 30-60-90 day plan we can share with them in week one:
Days 1–30: learn. Who to meet (by role, and why), which docs and tools they need access to, and one small task they can finish in the first two weeks.
Days 31–60: contribute. One piece of real work they own, and how we'll both know it went well.
Days 61–90: own. What they should be running without help by day 90.
For each phase, add one question the manager should ask in their 1:1. Keep it realistic for full-time or part-time, and don't fill gaps with generic "build relationships" items…
Nisha Kapoor1,020 uses
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
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
I received a GST notice under section section number (form form, e.g. ASMT-10 or DRC-01) for the period period. Here's the text, with the GSTIN and names removed:
paste notice text
Explain in plain English: what they're asking for, the deadline, which documents I'd usually need, and whether this typically needs a CA. This isn't legal advice; tell me what to ask my CA.
Kavya Reddy1,080 uses
Advertisement
Ad slot (preview)In-feed band · responsive (728×90 desktop, 300×250 phone)Shown only after AdSense approval and consent
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
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
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
I have a discovery call with name, their role at company, on date. We sell what we sell to type of team.
From what I paste below (their website copy, a recent post, our CRM notes), build a one-page prep brief:
1. Three things worth knowing about the company right now, each with where it came from.
2. What I think their problem is, as a guess I could be wrong about, in one sentence.
3. Five questions that get them talking about the process we replace: open, specific, nothing they can answer with yes or no. Put the one about budget last.
4. What would make this a bad fit, so I can say so early instead of in week six.
5. The next step I'll ask for if the call…
Vikram Shetty964 uses
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
Plan a 50-minute lesson on topic for year group students. Most of them already prior knowledge.
· Starter (5 min): a question they can answer on a mini whiteboard
· Teach (15 min): the one idea that matters most, with a worked example
· Practice (20 min): three tasks that get harder; the last one is a stretch
· Exit ticket (5 min): two questions that show who got it
· Spare (5 min): what to cut if we run late
List the misconceptions students usually have about topic, and where in the lesson I deal with each one.
Tom Linden780 uses
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
Explain concept to someone who knows field they already know well but nothing about new field.
Use one analogy from their field, then drop the analogy and explain it properly. Then give me 3 questions to check I understood, with the answers below a line of dashes. Max 250 words before the questions.
Tom Linden1,366 uses
I got an offer for role at company: current offer details.
I want target, because [reason: competing offer, market data or bigger scope].
Write a reply that thanks them, states the number once, gives one reason and keeps the door open. Under 120 words. No apologising. Then tell me what to say if they call instead of replying.
Meera Iyer1,012 uses
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
Rewrite the job description below so a good candidate from outside our industry would understand it and want to apply.
· Replace jargon and internal team names with what the person will actually do in a normal week.
· Turn "rockstar", "ninja", "fast-paced" and the like into specific facts, or cut them.
· Split requirements into Must have (five at most) and Nice to have. Anything that's really a preference goes in the second list.
· Keep the salary range, location and working pattern exactly as they are: salary range, location, remote or hybrid.
· Use "you" for the candidate and "we" for us. No gendered words.
After the rewrite, list every requirement you moved or removed and why,…
Nisha Kapoor841 uses
Explain this language module to a new teammate who knows the language but not our codebase.
Start with what it's for in one sentence, then the main flow, then the two things most likely to trip them up. Point to functions by name. Finish with a Mermaid sequence diagram of the call flow.
paste code
Daniel Okafor510 uses
Advertisement
Ad slot (preview)In-feed band · responsive (728×90 desktop, 300×250 phone)Shown only after AdSense approval and consent
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
I have a 1:1 with name, a role, about issue. They've been observed behaviour for how long.
Help me plan 30 minutes:
· an opening line that isn't a compliment sandwich
· two open questions
· the one specific example I'll share
· what I need from them, by when
· how I'll close
Also list two things I should not say. Keep my tone direct but kind.
Daniel Okafor760 uses
Write alt text for this image: describe the image or attach it. It appears on page next to surrounding text.
Describe what the image adds that the text doesn't. One or two sentences, no "image of", no keyword stuffing. If the image is decorative, say so and return an empty alt.
Asha Rao330 uses
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
I'm hiring a role at seniority level. Write 8 behavioural interview questions that separate people who have actually done key skill from people who've read about it.
For each: the question, what a strong answer includes, and a follow-up that exposes a rehearsed answer. No brain-teasers, nothing about personal life.
Meera Iyer880 uses
Help me write a two-minute toast for friend's wedding to partner. I've known friend since how you met.
Three stories I could use:
1. story 1
2. story 2
3. story 3
Pick the best one, build the toast around it, and end with a line about the couple, not just my friend. No inside jokes that need explaining. Mark where to pause with (pause).
Priya Nair640 uses
Here's a student's type of writing answering: task. Their level: level.
Give feedback in this format: one thing they did well (quote it), the single most important thing to fix (with an example of how the sentence could look), and one question that makes them think.
Write it to the student, in the second person, in under 80 words, with no grade.
paste student writing
Tom Linden530 uses
Summarise this paper for a 10-minute journal club slot. Audience: audience.
Give: the question, the method in three lines, the main result with the actual numbers, the biggest limitation the authors admit and one they don't, and two discussion questions. Quote the paper for any claim you're unsure about.
paste abstract and key sections
Meera Iyer470 uses

