A living library of prompts, built by creators like you.

You are a direct-response copywriter with 15 years of B2B SaaS experience. Product: {PRODUCT} Audience: {ICP} Primary pain: {PAIN} Write landing page copy with: 3 headline options (max 9 words), a 2-sentence subhead, 3 benefit blocks (headline + 20 words), objection-handling FAQ (5 Q&A), and a CTA. Use concrete outcomes and numbers, avoid hype adjectives, 8th-grade reading level.

You are a senior analytics engineer. Schema: {SCHEMA} Question: {QUESTION} Return a single PostgreSQL query. Use CTEs for readability, comment each CTE in one line, avoid SELECT *, handle NULLs explicitly, and state any assumption you made about the data before the query.

Act as a staff engineer reviewing a pull request. Here is the diff: {DIFF} Return: (1) blocking issues with file/line and a fix, (2) non-blocking suggestions, (3) missing tests, (4) security or performance risks. Be terse, no praise, code snippets only where they change behavior.

Product: {PRODUCT}. Audience: {AUDIENCE}. Offer: {OFFER}. Write 15 paid social hooks under 12 words each, spread across 5 angles: pain, curiosity, contrarian, social proof, and specific-result. Then pick the 3 strongest and write a 25-word primary text for each. No emojis unless the angle needs one.

You are an SEO strategist. Target keyword: {KEYWORD}. Search intent: {INTENT}. Produce a page brief with: recommended H1, URL slug, meta title (<60 chars), meta description (<155 chars), H2/H3 outline covering entity coverage, 8 questions to answer, 5 internal link targets, and a schema.org type recommendation. No fluff, output as markdown.

Research the market for {CATEGORY}. Return: the 6 leading players, positioning of each in one sentence, pricing model, most-cited strength and weakness from real user reviews, and 3 gaps a new entrant could exploit. Cite a source URL for every factual claim. Say clearly when something is unverified.

Here is a legacy module: {CODE} Refactor it without changing behavior. Deliver: the refactored code, a list of behavior-preserving changes, any behavior you could not preserve and why, and the characterization tests you would write first. Prefer small named functions over comments.

You are a senior customer support specialist for {COMPANY}. Customer message: {MESSAGE} Write a reply that: acknowledges the specific problem in the first sentence, explains what happened in plain language, states exactly what you will do and by when, and offers one concrete next step. Under 150 words, warm but not chirpy, no apologies stacked more than once.

Stack trace: {TRACE} Context: {STACK / FRAMEWORK}. Diagnose the most likely root cause, list 3 alternative causes ranked by probability, tell me exactly what to log or inspect to distinguish them, and give the minimal fix. No speculation presented as fact.

Stack trace: {TRACE} Context: {STACK / FRAMEWORK}. Diagnose the most likely root cause, list 3 alternative causes ranked by probability, tell me exactly what to log or inspect to distinguish them, and give the minimal fix. No speculation presented as fact.

You are an SEO strategist. Target keyword: {KEYWORD}. Search intent: {INTENT}. Produce a page brief with: recommended H1, URL slug, meta title (<60 chars), meta description (<155 chars), H2/H3 outline covering entity coverage, 8 questions to answer, 5 internal link targets, and a schema.org type recommendation. No fluff, output as markdown.

Research the market for {CATEGORY}. Return: the 6 leading players, positioning of each in one sentence, pricing model, most-cited strength and weakness from real user reviews, and 3 gaps a new entrant could exploit. Cite a source URL for every factual claim. Say clearly when something is unverified.

Build a 5-email cold outreach sequence for {OFFER} targeting {TITLE} at {COMPANY TYPE}. Each email under 90 words, one idea per email, no attachments, subject lines under 5 words. Touch 1 problem, 2 proof, 3 short case study, 4 objection, 5 breakup. Output as a table with day offsets.

Product: {PRODUCT}. Audience: {AUDIENCE}. Offer: {OFFER}. Write 15 paid social hooks under 12 words each, spread across 5 angles: pain, curiosity, contrarian, social proof, and specific-result. Then pick the 3 strongest and write a 25-word primary text for each. No emojis unless the angle needs one.

Act as a staff engineer reviewing a pull request. Here is the diff: {DIFF} Return: (1) blocking issues with file/line and a fix, (2) non-blocking suggestions, (3) missing tests, (4) security or performance risks. Be terse, no praise, code snippets only where they change behavior.

You are a senior analytics engineer. Schema: {SCHEMA} Question: {QUESTION} Return a single PostgreSQL query. Use CTEs for readability, comment each CTE in one line, avoid SELECT *, handle NULLs explicitly, and state any assumption you made about the data before the query.