What this prompt does
This prompt designs a marketing and growth strategy for an open source project. You name the [project_name], its [project_type], [current_stars], and your targets ([target_stars], [target_users], [timeline]), and the AI returns ten components: README optimization with badges and a demo GIF, landing-page content for [landing_url], a launch plan for [platforms], adoption-driving docs, community setup, [content_count] content pieces, talk and podcast pitch templates, integration partnerships within the [ecosystem], release-marketing cadence, and a metrics dashboard.
The structure works because open source growth has two engines that behave differently: launches spike and content compounds. The prompt covers both — a sharp README and a strong launch capture the initial surge, while documentation, tutorials, and a steady release cadence build the durable adoption curve. By making the README's five-second value proposition and good-first-issues explicit, it targets the two things that most often decide whether a curious visitor becomes a star or a contributor. The metrics dashboard at the end keeps the whole effort honest, since stars are a vanity number unless downloads, contributors, and retention move with them.
When to use it
- You are launching or relaunching an open source
[project_type]and want a real plan. - Your README does not sell the project's value in the first five seconds.
- You are preparing a launch across
[platforms]and need timing, copy, and visuals. - You want to convert visitors into contributors with good first issues and clear guidelines.
- You need a content cadence of
[content_count]pieces showing real-world use. - You want integration partnerships within a specific
[ecosystem].
Example output
Expect a ten-part plan: a rewritten README outline with badge and demo-GIF placement, landing-page section copy for [landing_url], a platform-by-platform launch schedule, a docs structure (quick start, tutorials, API reference), community-setup steps, [content_count] content topics, ready-to-adapt pitch templates, and a metrics dashboard tracking stars, downloads, contributors, and retention.
Pro tips
- Invest most in the README — set up
[project_name]so its value is obvious in five seconds, because that is what converts a Hacker News visitor into a star. - Keep
[target_stars]and[timeline]grounded; star counts depend heavily on luck and timing, so treat them as direction rather than commitment. - Choose
[platforms]where your[project_type]audience actually gathers — a Python tool belongs on r/Python more than on a general feed. - Treat the
[content_count]tutorials as the compounding engine; launches fade in days, but use-case content keeps pulling adopters for months. - Seed good first issues before you launch so the contributor funnel is ready when traffic arrives.
- Target
[ecosystem]integrations that put your project in front of users already solving an adjacent problem, rather than chasing unrelated partnerships. - Keep the release-marketing cadence steady; a well-written changelog turns routine updates into recurring reasons for people to revisit and re-share the project.
