ph-tagline-writer

Product Hunt Tagline Writer

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ph-tagline-writer" with this command: npx skills add yoanbernabeu/producthunt-skills/yoanbernabeu-producthunt-skills-ph-tagline-writer

Product Hunt Tagline Writer

This skill helps you craft perfect taglines for Product Hunt - the single most important piece of copy that determines whether users click on your product.

When to Use This Skill

  • Writing your Product Hunt tagline

  • Testing multiple tagline variations

  • Refining existing taglines for clarity

  • Adapting taglines for different audiences

  • Checking tagline against best practices

The Golden Rules

Rule 1: Under 60 Characters

  • Product Hunt truncates longer taglines

  • Optimal length: 40-55 characters

  • Every character must earn its place

Rule 2: Instant Clarity

  • Reader should understand what product does in 3 seconds

  • No jargon, no buzzwords, no fluff

  • Assume zero context

Rule 3: Value First

  • Lead with the benefit, not the feature

  • Answer "Why should I care?"

  • Focus on the outcome

Proven Tagline Formulas

Formula 1: "X for Y"

Compare to known product for instant understanding.

Structure: [Known Product] for [Target Audience/Use Case]

Examples:

  • "Notion for personal finance"

  • "Figma for video editing"

  • "Stripe for marketplace payments"

When to Use: When your product is similar to something well-known

Formula 2: Action + Outcome

State what user does and what they get.

Structure: [Action] [Object] [Positive Outcome]

Examples:

  • "Turn feedback into product improvements"

  • "Write emails that get replies"

  • "Build apps without code"

When to Use: When the action-result relationship is clear

Formula 3: Problem Killer

Directly address the pain point.

Structure: [Eliminate/Stop/End] [Pain Point] [How]

Examples:

  • "Never lose a customer email again"

  • "Stop wasting time on manual reports"

  • "End meeting chaos forever"

When to Use: When your audience has a clear, urgent pain

Formula 4: Speed/Ease Promise

Emphasize how fast or easy something becomes.

Structure: [Action] in [Timeframe/Ease]

Examples:

  • "Create landing pages in 60 seconds"

  • "Deploy APIs without configuration"

  • "Design logos with one click"

When to Use: When speed or simplicity is your key differentiator

Formula 5: Transformation

Show the before/after state.

Structure: Turn [Current State] into [Desired State]

Examples:

  • "Turn ideas into shipped products"

  • "Turn strangers into loyal customers"

  • "Turn chaos into organized workflows"

When to Use: When the transformation is dramatic and desirable

Formula 6: The "But Better"

Position against existing behavior.

Structure: [What they already do], but [improvement]

Examples:

  • "Spreadsheets, but for product teams"

  • "Email, but without the noise"

  • "Notes, but with AI superpowers"

When to Use: When improving on something people already use

Formula 7: Specific Number

Add credibility with specifics.

Structure: [Number]x [Improvement] for [Activity]

Examples:

  • "10x faster database queries"

  • "3x more replies from cold emails"

  • "50% less time on code reviews"

When to Use: When you have impressive metrics to share

Tagline Testing Checklist

Clarity Test

  • Can someone outside your industry understand it?

  • Does it pass the "explain to mom" test?

  • Would a 10-year-old get the gist?

Specificity Test

  • Could this tagline only describe YOUR product?

  • Is it different from competitors' messaging?

  • Does it avoid generic terms?

Value Test

  • Is the benefit immediately clear?

  • Does it answer "What's in it for me?"

  • Would you click based on this tagline alone?

Character Count Test

  • Under 60 characters? (Required)

  • Under 50 characters? (Better)

  • Every word necessary? (Best)

What to AVOID

Red Flags

  • ❌ "World's first..." (Unprovable, distracting)

  • ❌ "Revolutionary..." (Empty buzzword)

  • ❌ "AI-powered..." (Overused, meaningless alone)

  • ❌ "All-in-one..." (Vague, unfocused)

  • ❌ "Best..." (Subjective, unbelievable)

  • ❌ "Next-gen..." (Meaningless)

Common Mistakes

  • ❌ Being clever over being clear

  • ❌ Using internal jargon

  • ❌ Focusing on features over benefits

  • ❌ Trying to say too much

  • ❌ Being vague to sound inclusive

Tagline Workshop Process

Step 1: Brain Dump (5 min)

Write 10+ tagline variations without judgment

Step 2: Categorize (3 min)

Group by formula type (X for Y, Problem Killer, etc.)

Step 3: Test Clarity (5 min)

Share top 5 with someone unfamiliar with your product

Step 4: Character Count (2 min)

Trim all options to under 60 characters

Step 5: Final Selection (5 min)

Pick top 3, sleep on it, choose winner

Examples from Top Launches

Product Tagline Characters Formula

Notion "All-in-one workspace" 21 Category

Linear "The issue tracker you'll enjoy using" 38 Experience

Raycast "Supercharged productivity" 26 Benefit

Loom "Video messaging for work" 26 X for Y

Figma "Design, prototype, collaborate" 30 Actions

Output Format

When generating taglines, provide:

TAGLINE OPTIONS FOR: [Product Name]

TOP RECOMMENDATION: "[Tagline]" (X characters)

  • Formula: [Formula type]
  • Why it works: [Brief explanation]

ALTERNATIVES:

  1. "[Tagline]" (X chars) - [Formula]
  2. "[Tagline]" (X chars) - [Formula]
  3. "[Tagline]" (X chars) - [Formula]

TESTING SUGGESTION: Share these 3 with [target audience] and ask: "Based only on this tagline, what do you think this product does?"

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

ph-community-outreach

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-social-media-launch

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-launch-strategy

No summary provided by upstream source.

Repository SourceNeeds Review
General

ph-launch-day-checklist

No summary provided by upstream source.

Repository SourceNeeds Review