AI Prompts That Work, Ranked

Code Refactoring Architect

Ask an AI to mercilessly review your code for scalability, security, and edge cases.

Review this code like a senior architect. Do not rewrite it yet. Instead, point out 3 security flaws, 2 performance bottlenecks, and 1 edge case it fails to handle. Then ask me which one to fix first.

SaaS Product Name & Branding Strategist

Generate 10 available-style brand names, visual identity concepts, and value propositions.

Act as a branding director. I am building [PRODUCT]. Give me: 1) 10 short punchy brand names, 2) 2-color aesthetic palette recommendations, 3) 3 tagline variations, and 4) a 1-sentence value proposition for ProductHunt.

Learn Prompting

A free, structured course on prompting written by researchers rather than course sellers.

Prompt Engineering Guide

The open reference on techniques, with the papers each one came from.

PromptHero

Search millions of images by the exact prompt that produced them.

PromptBase

A marketplace for prompts that reliably work — useful to study even if you never buy one.

FlowGPT

A large community library of prompts, sorted by what people actually use.

Turn an idea into a 48-hour test

Break any idea into customers, pain, revenue, risks, and a free first experiment.

My idea is [IDEA]. Identify: 1) three customer groups most likely to pay, 2) their sharpest problem, 3) a free 48-hour validation test, 4) three paths to first revenue, and 5) clear failure conditions. Put it in a table and challenge the riskiest assumption first.

Design a viral 30-second Short

Turn one topic into a hook, fast story, payoff, and natural call to action.

Turn [TOPIC] into a 30-second vertical video. Write: 0–2s pattern-interrupt hook, 3–15s rapid setup, 16–25s surprising payoff, and 26–30s natural CTA. Include on-screen text and cut notes. Do not invent facts or make unverifiable promises.

The universal beginner teacher

Explain a hard idea with a definition, analogy, example, misconceptions, and quiz.

Teach [CONCEPT] to a complete beginner. Give a two-sentence definition, an everyday analogy, the smallest useful example, three common misconceptions, and three quiz questions with answers and explanations.

Image prompt director

Expand a rough visual idea into a production-ready image prompt.

Expand [SCENE] into a concise image-generation prompt. Specify subject, action, environment, composition, lens, lighting, palette, texture, era, and aspect ratio. Remove empty adjectives and finish with a separate negative-prompt list.

Honest buying comparison

Compare products using real constraints instead of advertising copy.

Compare [PRODUCTS] using total price, core features, data requirements, returns, warranty limits, and best-fit user. Mark anything unverified as unknown. End with recommendations by use case, not one universal winner.

Explain code I did not write

What it does, why it is shaped that way, and where the surprises are.

Explain this code: [CODE]. Tell me what it does in two sentences, why it is structured this way (what problem the structure solves), which parts would surprise someone reading it quickly, and what would break if I changed each of the non-obvious decisions.

Validate an idea in 48 hours

Who pays, what hurts, and the free test that could kill it this week.

My idea is [IDEA]. Identify: the three groups most likely to pay and why; their sharpest current pain; a validation test I can run in 48 hours for no money; three paths to first revenue; and the conditions under which I should abandon it. Put it in a table and attack the riskiest assumption first.

Read a contract for the traps

The clauses that matter and the ones written to be skimmed past.

Here is a contract or terms document: [TEXT]. List the clauses that create real obligation or risk for me, in plain language, worst first. Flag anything unusual for this kind of agreement, anything that survives termination, and anything vague enough to be argued either way. This is not legal advice — mark what I should take to a lawyer.

Plan a trip around what I actually enjoy

Fewer things, better placed, with the travel time counted honestly.

I am going to [PLACE] for [DAYS]. I enjoy [WHAT] and dislike [WHAT]. Build a plan with no more than two fixed things per day, real travel time between them, and one unplanned block daily. For each suggestion say why it fits what I said. Skip anything that is only famous.

Research without invented sources

Separates what is verifiable from what the model is guessing.

Research [TOPIC]. Build the answer only from things you can state with a verifiable source, and put anything uncertain in a separate section labelled as unverified. Do not produce citations you are not confident exist. End by telling me what the strongest counter-position is and who holds it.

Compare products honestly

Real constraints, not marketing copy, and no universal winner.

Compare [PRODUCTS] on: total cost including what is not advertised, the features that actually differ, data and lock-in requirements, return and warranty limits, and who each one genuinely suits. Mark anything you cannot verify as unknown. End with recommendations by use case, not a single winner.

Cut a draft in half without losing anything

Finds the sentences that repeat, hedge or decorate, and shows what each cut costs.

Here is a draft: [TEXT]. Cut it to half the length. Rules: keep every claim and every number; remove hedging, repetition and throat-clearing; do not add anything new. Output the shortened version, then a short list of what you removed and why each removal was safe.

Make writing sound like a person, not a model

Strips the tells — the triads, the "moreover", the summary that repeats the intro.

Rewrite this so it reads as if a competent human wrote it in one pass: [TEXT]. Remove lists of three, transitional filler ("moreover", "furthermore", "in conclusion"), and any closing paragraph that repeats the opening. Vary sentence length. Keep the meaning and the facts exactly. Do not make it more formal.

Write the email you are avoiding

Bad news, a refusal or a chase, written so the relationship survives it.

Write an email to [WHO] about [SITUATION]. It has to say [THE HARD PART] plainly in the first two sentences. Then one sentence of context, then what happens next. No apology padding, no "I hope this finds you well", under 120 words. Give me two versions: one warmer, one more direct.

Turn a mess of notes into structure

Groups scattered notes by the argument they support and shows what is missing.

Here are raw notes: [NOTES]. Group them by the underlying point each one supports. Name each group in five words or fewer. Then tell me: which groups are thin on evidence, what a reader would ask that these notes cannot answer, and what order the groups should go in.

Argue against my own idea

The strongest case for why this fails, made by someone who wants it to.

My plan is: [PLAN]. Argue against it as the smartest person in the room who wants it to succeed. Give the three most likely reasons it fails, in order of probability, each with the earliest signal I would see. Then say which single assumption, if wrong, kills the whole thing. Do not soften anything.

Decide when both options look fine

Forces out the criteria you are actually deciding on but have not named.

I am choosing between [A] and [B]. First infer what I appear to care about from how I described them, and say it back to me. Then build a comparison table on those criteria only. Then tell me which one I should pick if I am wrong about my main assumption, and which if I am right.