ph-content-recycling
Repurpose Product Hunt launch content across channels. Use this skill to maximize the value of your launch assets by adapting them for blog posts, documentation, social media, and more.
What this skill does
# Product Hunt Content Recycling ## Workspace Context Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`. ## Operating Contract This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic. This skill helps you repurpose Product Hunt launch content across multiple channels to extend your launch impact. ## When to Use This Skill - After your PH launch - Maximizing content ROI - Building your content library - Extending launch visibility - Creating evergreen materials ## The Content Recycling Framework ### What You Created for PH ``` LAUNCH ASSETS: ├── Tagline ├── Description (short + long) ├── Maker comment ├── Gallery images (4-6) ├── Video demo ├── Thumbnail/GIF ├── Email templates ├── Social posts └── Supporter materials ``` ### Where to Repurpose ``` DESTINATION CHANNELS: ├── Website (landing page, about, features) ├── Blog (launch story, learnings, how-to) ├── Documentation (README, quickstart) ├── Social media (ongoing posts) ├── Email marketing (sequences) ├── Other platforms (directories, communities) ├── Sales materials (decks, one-pagers) └── PR/Media (press releases, pitches) ``` ## Channel-by-Channel Guide ### 1. Website Updates **Landing Page:** - Tagline → Headline - Description → Value proposition section - Gallery images → Feature screenshots - Video → Hero or features section - Maker comment → About section **Features Page:** - Gallery images → Feature highlights - Demo video → Embedded walkthrough - Description points → Feature list **About Page:** - Origin story from maker comment - Mission/vision from description - Team info (if mentioned) **Homepage Badge:** ```html <!-- Product Hunt Badge --> <a href="https://www.producthunt.com/posts/your-product"> <img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=YOUR_ID" /> </a> ``` --- ### 2. Blog Content **Launch Announcement Post:** ``` Title: "Introducing [Product]: [Tagline]" Contents: - What we launched (description) - Why we built it (maker comment story) - Key features (from gallery) - Getting started (CTA) ``` **Launch Retrospective:** ``` Title: "What We Learned Launching on Product Hunt" Contents: - Our results (numbers) - What worked - What didn't - Advice for others ``` **Feature Deep-Dive (from each gallery image):** ``` Title: "How [Feature] Helps You [Benefit]" Contents: - The problem (from description) - Our solution (from demo) - How to use it (new content) - Results/examples ``` --- ### 3. Documentation **README.md:** ```markdown # [Product Name] > [Tagline] [Description - first paragraph]  ## Features - [Feature 1 from gallery] - [Feature 2 from gallery] - [Feature 3 from gallery] ## Getting Started [Adapted from demo script] ## Support [From maker comment closing] --- 🏆 Featured on Product Hunt: [Badge/Link] ``` **Quick Start Guide:** - Adapted from demo video script - Screenshots from gallery - Step-by-step from description --- ### 4. Social Media (Ongoing) **Thread Formats:** *Origin Story Thread:* ``` 1/ Just launched [Product] on Product Hunt! 🚀 Here's the story of why we built it... [Maker comment story, broken into tweets] n/ Try it here: [link] ``` *Lessons Learned Thread:* ``` 1/ We launched on Product Hunt and got [X upvotes]. Here are [X] things we learned: [List of lessons] n/ Full details: [blog link] ``` *Feature Highlight Posts:* ``` [Gallery image] [Feature name] makes [benefit] easy. Here's how: [Demo or explanation] Try it: [link] ``` --- ### 5. Email Marketing **Welcome Sequence:** - Email 1: Welcome (adapted maker comment) - Email 2: Feature 1 (gallery image 1) - Email 3: Feature 2 (gallery image 2) - Email 4: Success story - Email 5: CTA **Newsletter:** - Launch announcement - Feature highlights - User stories --- ### 6. Other Directories **Platforms to List:** - BetaList - SaaSHub - AlternativeTo - Capterra/G2 - AppSumo (if applicable) - Indie Hackers - Hacker News (Show HN) **Adapted Content:** Each platform needs slightly different format, but core content stays same: - Tagline (may need length adjustment) - Description (platform-specific) - Screenshots (gallery images) - Links --- ### 7. Sales Materials **One-Pager:** ``` [LOGO] [Tagline] THE PROBLEM [From description] THE SOLUTION [From description + demo] KEY FEATURES [From gallery] RESULTS [From launch metrics or testimonials] GET STARTED [CTA] ``` **Pitch Deck Slides:** - Slide 2: Problem (from description) - Slide 3: Solution (tagline + demo) - Slide 4-6: Features (gallery images) - Slide 7: Traction (PH results + users) --- ### 8. PR/Media **Press Release:** ``` FOR IMMEDIATE RELEASE [Tagline] — [Company] Launches [Product] [City, Date] — [First paragraph of description] [Key features and benefits] "[Quote from maker comment]" — [Founder Name], [Title] [Availability and pricing] About [Company]: [Brief company description] Contact: [Media contact info] ``` ## Content Transformation Matrix | Original Asset | Blog | Social | Email | Docs | PR | |----------------|------|--------|-------|------|-----| | Tagline | Title | Hook | Subject | Header | Headline | | Description | Body | Threads | Body | Overview | Body | | Gallery | Images | Posts | Images | Screenshots | Attachments | | Video | Embed | Clip | GIF | Tutorial | Asset | | Maker Comment | Story | Thread | Intro | About | Quote | ## Recycling Workflow ### Step 1: Inventory List all assets created for launch: - [ ] Tagline - [ ] Short description - [ ] Long description - [ ] Maker comment - [ ] Gallery image 1 - [ ] Gallery image 2 - [ ] Gallery image 3 - [ ] Gallery image 4 - [ ] Video demo - [ ] Thumbnail - [ ] Email templates - [ ] Social templates ### Step 2: Prioritize Channels Rank by impact: 1. [Channel] - [Why important] 2. [Channel] - [Why important] 3. [Channel] - [Why important] ### Step 3: Adapt For each priority channel: - Review format requirements - Adapt content to fit - Maintain core message - Optimize for platform ### Step 4: Schedule Create content calendar: | Date | Channel | Content | Asset Used | |------|---------|---------|------------| | [Date] | Blog | Launch post | All | | [Date] | Twitter | Thread | Story | | [Date] | LinkedIn | Feature post | Gallery 1 | ## Quick Win Templates ### Twitter Thread from Maker Comment 1. Take maker comment 2. Split into 5-7 logical chunks 3. Add hook as tweet 1 4. Add CTA as final tweet ### Blog Post from Description 1. Use tagline as title 2. Expand each sentence of description into paragraph 3. Add gallery images as illustrations 4. Add demo video embed ### Email from Social Posts 1. Combine 3-4 social posts 2. Add personal greeting 3. Add CTA 4. Send! ## Recycling Checklist ### Week 1 After Launch - [ ] PH badge added to website - [ ] Landing page updated with launch assets - [ ] Blog launch post published - [ ] README updated ### Week 2-4 - [ ] Feature posts scheduled - [ ] Email sequence created - [ ] Other directories submitted - [ ] Sales materials updated ### Ongoing - [ ] Social posts from old assets - [ ] Blog posts from features - [ ] Email content from results ## Output Format ``` CONTENT RECYCLING PLAN: [Product Name] ASSETS AVAILABLE: - [List all launch assets] PRIORITY CHANNELS: 1. [Channel] - [Reason] 2. [Channel] - [R
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.