Landing page hero copy
Marketing · copywriting · landing
You are a direct-response copywriter for {{product}} aimed at {{audience}}.
Write 5 hero-section options. Each: a headline (max 8 words) naming the specific outcome, a subheadline (max 20 words) naming the mechanism, and one supporting proof point.
Rules: no superlatives without evidence, no "revolutionary", benefit before feature. Number each option.Open the Playground →
Cold email (short)
Marketing · email · outreach
Write a cold email to {{prospect_role}} at a {{company_type}} about {{offer}}.
Constraints: under 90 words, one specific observation about their business in line one, one sentence on the mechanism, one low-friction ask (not a meeting). Plain language, no flattery, no "I hope this finds you well".Open the Playground →
Ad variant generator
Marketing · ads · ppc
Generate 10 search-ad variants for {{keyword}} targeting {{audience}}.
For each: 2 headlines (max 30 chars) and 1 description (max 90 chars). Vary the angle across: price, speed, risk-reversal, social proof, and specific outcome. Mark the strongest variant and say why in one line.Open the Playground →
Feature announcement
Marketing · launch · blog
Write a 250-word release note for {{feature}}.
Open with the user-visible change in the first sentence. Then: what it does (1 paragraph), why it matters (1 paragraph), what changes for existing users (bullets), one call to action. No jargon the user has not met before.Open the Playground →
Keyword cluster map
SEO · keywords · planning
Cluster these keywords into topic groups for a content plan about {{topic}}: {{keywords}}
Return a table: cluster name | primary keyword | secondary keywords | search intent (informational/commercial/transactional) | suggested page type. Flag any keyword that belongs to two clusters.Open the Playground →
SERP gap analysis brief
SEO · content · brief
You are an SEO content strategist. Write a brief for an article targeting "{{keyword}}".
Include: the search intent in one sentence, 5 H2 sections the article needs (based on what would fully answer the query), 3 questions for an FAQ section, suggested internal link anchor texts, and one angle competitors typically miss.Open the Playground →
Meta description set
SEO · meta · on-page
Write 5 meta descriptions for a page about {{page_topic}} targeting {{keyword}}.
Each under 155 characters, each with: the primary benefit, a specific detail, and an implicit reason to click. No clickbait, no exclamation marks. Number them and mark the one you would ship.Open the Playground →
Internal link audit
SEO · links · audit
Here is a list of my pages with their topics:
{{page_list}}
Suggest 15 internal links as: source page → target page → suggested anchor text. Prioritize links from high-authority pages to pages I want to rank. Flag any orphan pages with no incoming suggestions.Open the Playground →
Discovery call questions
Sales · discovery · b2b
I sell {{product}} to {{icp}}. Design a 20-minute discovery call.
Give me 8 questions ordered from context to pain to impact, each with: the question, what a good answer sounds like, and what a red flag sounds like. End with one question that quantifies the cost of doing nothing.Open the Playground →
Objection handling
Sales · objections · b2b
Write responses to the 5 most common objections for {{product}}: price, timing, "we already have a solution", "send me info", and "I need to ask my boss".
Each response: acknowledge in one clause, reframe with a question, then a 2-sentence answer grounded in {{proof_point}}. No pressure tactics.Open the Playground →
Proposal summary
Sales · proposal
Summarize this call transcript into a proposal-ready brief: {{transcript}}
Return: their problem in their words (2 sentences), the outcome they want, measurable success criteria, constraints (budget/timeline/technical), decision process, and 3 risks. Quote them directly where possible.Open the Playground →
Follow-up cadence
Sales · followup · email
Write a 5-touch follow-up cadence for a prospect who went quiet after {{stage}}.
Each touch: channel (email/LinkedIn), subject line, body under 70 words, and the value it adds (not "just checking in"). Space them over 3 weeks; touch 5 is the polite close.Open the Playground →
Ruthless editor
Writing · editing
Edit the text below for clarity and force. Keep the author's voice and meaning.
Rules: cut every word that does no work; prefer concrete nouns and active verbs; break sentences over 25 words; one idea per paragraph. Return the edited text, then a 3-bullet list of the biggest changes.
Text:
{{text}}Open the Playground →
Story structure coach
Writing · storytelling
Here is my story draft: {{draft}}
Diagnose it against classic story structure: is the stakes moment clear by 20% in? What does the protagonist want, and what is in the way? Where does tension sag? Give me 3 specific, surgical edits — not a rewrite.Open the Playground →
Style transfer
Writing · style
Rewrite the text below in the style of {{style_reference}} (e.g. "a New Yorker science writer", "Paul Graham").
Match sentence rhythm, vocabulary register, and how examples are introduced — not topic. Keep it the same length ±10%. Then list the 3 stylistic devices you used most.
Text:
{{text}}Open the Playground →
Outline from chaos
Writing · outline
Here are my unstructured notes: {{notes}}
Produce an outline: a one-sentence thesis, 3-5 sections in the order a reader needs them, 2-3 bullets of content per section, and a note on what to research next. Do not invent facts my notes do not contain — mark gaps explicitly.Open the Playground →
Code reviewer
Development · review
You are a senior {{language}} reviewer. Review the code below for correctness first, then security, then readability.
Report findings as a numbered list ordered by severity, each with the exact line reference and a one-line fix. No praise, no summary of what the code does.
Code:
{{code}}Open the Playground →
Bug reproduction plan
Development · debugging
I have this bug: {{bug_description}}
Environment: {{environment}}
Build me a systematic reproduction plan: 5 hypotheses ordered by likelihood, the cheapest experiment to test each, and what evidence would rule it out. Stop and tell me what data to collect if reproduction fails.Open the Playground →
Test case generator
Development · testing
Write test cases for this function/spec: {{code_or_spec}}
Cover: happy path, boundary values, nulls/empties, invalid types, and the two nastiest edge cases you can think of. Output as a table: name | input | expected | why it matters. Language: {{language}}.Open the Playground →
Regex from English
Development · regex
Write a regex that matches {{description}}.
Return: the pattern, a breakdown of each part in one line each, 3 strings that match, 3 near-miss strings that must NOT match, and the flavor assumptions (lookahead support etc.). If the requirement is ambiguous, state the assumption you made first.Open the Playground →
SQL from a question
Data · sql
Schema:
{{schema}}
Question: {{question}}
Write the SQL. Rules: explain each CTE in one comment line; prefer explicit JOINs; no SELECT *; note any assumption about grain or nulls. Then give a sanity-check query that would catch a wrong answer.Open the Playground →
Chart chooser
Data · visualization
I have this data and message: {{data_description}}. The point I need to make: {{message}}.
Recommend the best chart type and defend it: why this encoding, what it makes visible, what it hides, and the one alternative worth considering. Then specify axis labels, bin sizes, and any annotations.Open the Playground →
Metric definition
Data · metrics
Define the metric "{{metric_name}}" for a {{product_type}} product like a data engineer would own it.
Return: precise definition (numerator, denominator, window), 3 ways it can be gamed, the guardrail metric to watch alongside it, and the SQL sketch for computing it weekly.Open the Playground →
Survey design
Data · survey · research
Design a {{length}}-question survey to learn {{objective}} from {{audience}}.
Rules: no leading questions, no double-barreled questions, scales must be labeled at every point, include one attention check, and order from easy to personal. For each question: the question, type, options/scale, and what decision the answer informs.Open the Playground →
Feynman tutor
Education · learning
Teach me {{concept}} at the level of a {{level}}.
Rules: one plain-language explanation paragraph, then one concrete analogy from everyday life, then the most common misconception and why it is wrong, then 3 questions to check my understanding (easy/medium/hard). Wait for my answers before explaining them.Open the Playground →
Practice problem generator
Education · practice
Generate 5 practice problems about {{topic}} at {{difficulty}} difficulty, ordered from easiest to hardest.
Each problem: the question, why it tests the skill, the full worked solution, and the trap a student typically falls into. Make problem 4 require combining two ideas.Open the Playground →
Rubric builder
Education · grading · rubric
Build a 4-point rubric for grading {{assignment}} by {{grade_level}} students.
For each point value on each dimension: one observable, checkable criterion — not vague adjectives. Dimensions: content accuracy, reasoning, communication, and effort/completeness. Add the one-line feedback you would give a 2/4 on reasoning.Open the Playground →
Lesson plan scaffold
Education · lesson
Create a {{duration}} lesson plan for {{topic}} teaching {{audience}}.
Structure: hook (2 min, concrete), direct instruction (the 3 things they must leave knowing), guided practice with the exact exercises, independent practice, and a 3-question exit ticket. Time-box each section.Open the Playground →
User story splitter
Product · agile
Split this epic into stories a team can finish in a sprint: {{epic}}
Each story: "As a {{who}}, I want {{what}}, so that {{why}}" plus acceptance criteria as Given/When/Then, and a complexity guess (S/M/L). Order by dependency. Flag anything that is really two stories.Open the Playground →
Feature prioritizer
Product · prioritization
Score these features for a {{product}} at {{stage}} stage: {{features}}
Score each 1-5 on: user pain it removes, usage frequency, strategic fit, and effort (inverted). Show the table, then the top 3 with one-line rationales, then the one you would deliberately NOT build and why.Open the Playground →
Churn interview script
Product · retention · research
Write a 15-minute exit interview script for a customer who cancelled {{product}}.
10 questions, open-ended, ordered from facts to feelings, no "why did you leave us" before question 6. Include follow-up probes for vague answers. End with the one question whose answer would change our roadmap most.Open the Playground →
Release note writer
Product · changelog
Turn these merged changes into user-facing release notes: {{changes}}
Group under Added/Changed/Fixed. Each entry one sentence, verb-first, user benefit visible. Cut anything a user cannot perceive. Keep the whole thing under 150 words.Open the Playground →
STAR story builder
Career · interview
Turn my raw notes into a STAR interview story: {{notes}}
Situation and Task: 2 sentences total, with a number in each. Action: 3 bullets starting with verbs I personally did. Result: 1 sentence with a measurable outcome and a comparison. Flag anywhere I claim credit without evidence.Open the Playground →
Resume bullet rewriter
Career · resume
Rewrite these resume bullets with strong verbs and quantified outcomes: {{bullets}}
Rules: verb-first, past tense, one accomplishment per bullet, numbers wherever honest (add a [NUMBER?] placeholder where I should quantify). Never invent an achievement. Max 2 lines each.Open the Playground →
Salary negotiation script
Career · negotiation
I received an offer: {{offer_details}}. My situation: {{situation}}.
Write a negotiation script: the exact opening sentence to anchor, two fallback positions, answers to the 3 most likely counters, and the one thing I should get in writing. Respectful, factual, no ultimatums. Mark my BATNA clearly.Open the Playground →
Weekly update template
Career · communication
Turn my rough week notes into a status update for {{audience}}: {{notes}}
Format: 3 headline outcomes (one line each), progress detail only where it changes decisions, risks/asks with owners and dates, and next week in 3 bullets. Honest about slips — propose a recovery, do not hide it.Open the Playground →
Angry customer reply
Support · email · de-escalation
Draft a reply to this angry customer: {{message}}
Their issue in facts: {{facts}}
Structure: acknowledge the specific frustration (1 sentence), what we found (2 sentences, plain language), what we are doing now with a time estimate, and what we will do so it does not recur. No corporate apologies-as-nouns ("we apologize for any inconvenience" is banned).Open the Playground →
Help article writer
Support · help · docs
Write a help article for: "{{how_to_question}}"
Structure: one-sentence answer first, then numbered steps (each starting with a verb, one action each), then common problems as a Q/A, and a "still stuck?" line. Reading level: beginner. No marketing voice.Open the Playground →
FAQ from tickets
Support · faq
Here are support tickets on the same theme: {{tickets}}
Extract the 5 questions customers are actually asking (in their words), and write an answer for each: direct answer first sentence, then detail, then the workaround if the fix is not available yet. Flag anything that looks like a product bug rather than a docs gap.Open the Playground →
Rewrite this reply at a {{tone}} register without losing any information or commitments: {{draft}}
Keep every factual claim identical. Then list the 3 tone devices you changed. Do not add apologies that were not in the original.Open the Playground →
Idea multiplier
Brainstorm · ideation
Here are my ideas for {{challenge}}: {{ideas}}
First: combine two of them into something better than either. Then: generate 5 new ideas constrained by {{constraint}}. Then: the deliberately weird one — an idea that violates an assumption everyone in {{domain}} holds. One line each, no evaluation.Open the Playground →
Pre-mortem
Brainstorm · risk · planning
Run a pre-mortem on this plan: {{plan}}
It is 12 months from now and the project failed completely. Write: the 5 most probable causes of death, ranked; the earliest observable warning sign for each; and the cheapest pre-emptive move for the top two. Be specific to THIS plan, not generic risk language.Open the Playground →
Assumption crusher
Brainstorm · strategy
My plan relies on these assumptions: {{assumptions}}
For each: rate confidence (high/medium/low), name the cheapest test that would falsify it within a week, and state what I would do differently if it is false. End with the single assumption whose failure breaks everything.Open the Playground →
SCAMPER prompt
Brainstorm · ideation · framework
Apply SCAMPER to {{subject}}: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse.
Two concrete ideas per letter, each one sentence. Then pick the two ideas with the best effort-to-unexpectedness ratio and expand each to a 3-sentence pitch.Open the Playground →
Product photo prompt
Image · midjourney · product
studio product photo of {{product}} on a matte {{color}} pedestal, soft window light from the left, subtle shadow, shallow depth of field, 85mm lens, editorial minimalism --ar 1:1 --stylize 200Open the Playground →
Character portrait prompt
Image · midjourney · character
portrait of a {{character_description}}, {{expression}}, cinematic still, dramatic rim lighting against deep shadow, 85mm lens, film grain, muted earth tones --ar 4:5 --stylize 400Open the Playground →
Isometric illustration prompt
Image · isometric · illustration
isometric illustration of {{scene}}, clean vector shapes, soft gradients, pastel palette with one accent color, tiny details rewarding zoom, white background --ar 1:1Open the Playground →
Website hero background prompt
Image · web · background
abstract background for a {{industry}} website hero, soft geometric forms, generous negative space on the left for text, {{palette}} palette, subtle grain, no text, no faces --ar 16:9 --stylize 150Open the Playground →