Guides marketing and growth strategy for indie hackers (bootstrapped founders, solo developers)—autonomous, small-team or solo, no external funding. Covers mindset, first users, Build in Public, growth channels, and when to use which skills. For cold start execution (launch timeline, Product Hunt, directory submission), see cold-start-strategy. For forum tactics (Indie Hackers, HN, Reddit post structure), see community-forum. Full guide (cases, resources) → Alignify – Indie Hacker Complete Guide
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionindie-hacker-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches indie-hacker-strategy from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate indie-hacker-strategy. Access via /indie-hacker-strategy in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides marketing and growth strategy for indie hackers (bootstrapped founders, solo developers)—autonomous, small-team or solo, no external funding. Covers mindset, first users, Build in Public, growth channels, and when to use which skills. For cold start execution (launch timeline, Product Hunt, directory submission), see cold-start-strategy. For forum tactics (Indie Hackers, HN, Reddit post structure), see community-forum. Full guide (cases, resources) → Alignify – Indie Hacker Complete Guide.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Indie Hacker = Bootstrapped founder who builds products autonomously, typically 1–3 people, no external funding. Focus: sustainability, profitability, fast iteration—not VC-scale growth.
| Trait | Indie Hacker | VC-backed |
|---|---|---|
| Funding | Bootstrapping; product revenue | External investment |
| Growth | Sustainable; Ramen profitability first | Scale at all costs |
| Control | Full autonomy | Investor reporting |
| Timeline | Long game; niche focus | Fast expansion |
| Concept | Meaning |
|---|---|
| Bootstrapping | Self-funded; use product revenue to grow; no equity dilution |
| MVP | Minimum viable product; ship fast, validate, iterate |
| Build in Public | Share progress, metrics, failures openly; attracts early adopters |
| Scratch your own itch | Solve your own problem first; others likely have it too |
| Tactic | Guideline |
|---|---|
| Ship fast, fix later | Launch ugly but functional MVPs; Nomad List started as Google Sheet + Stripe; Photo AI made $150K first week despite initial flaws |
| Monetize from day one | Add payment button at launch; validate willingness to pay, not just usage |
| Automate everything | Scripts, APIs, no-code; run without employees |
| Build in public | Share metrics openly; 600K+ followers; "Day 1: building X. Day 3: first customer" attracts early adopters |
Reference: Pieter Levels: The One-Man Startup Empire
| Phase | Tactic |
|---|---|
| First 5 | Direct DMs to people who'd genuinely benefit |
| Next ~15 | Conversations in communities where target users hang out (Reddit, Indie Hackers) |
| Scale to 50 | Build in public with visible metrics |
| Reach 100 | Double down on what works; don't add new channels until one consistently converts |
Niche products: Reddit (60/100 users in one case), Discord (25), Indie Hackers (15). Twitter/HN may yield 0 for niche—target existing conversations in niche communities. Reference: How I got my first 100 users - Indie Hackers, Indie10k – First 100 Users
| Content Mix | Share |
|---|---|
| 40% | Learnings |
| 30% | Progress updates |
| 20% | Challenges, failures |
| 10% | Helping others |
Principles: Transparency over perfection; authenticity over polish; consistency over intensity; value over self-promotion (90/10 rule). Post weekly minimum; engage two-way. Founders who build in public see ~4.2× more day-one users; ~34% of launch users from audience. Reference: Building in Public: Complete Strategy 2026, Indie Hackers Marketing 2025
| Channel | Fit | Conversion | Skill |
|---|---|---|---|
| Indie Hackers | Sustained 4–6 months; authentic journey | ~23% vs PH 3% | community-forum |
| Product Hunt | Launch-day buzz | ~3% | product-hunt-launch, cold-start-strategy |
| Niche subreddits; 5+ months; lead with story | Varies by niche | reddit-posts, community-forum | |
| Twitter/X | Breadth, fastest follower growth | — | twitter-x-posts |
| Higher customer conversion than X | — | linkedin-posts | |
| Discord | Niche communities; strong for first 100 | — | community-forum |
| SEO | Long-term organic; Micro-SaaS, tools | — | seo-strategy |
| LTD / AppSumo | Fast revenue, validation | — | discount-marketing-strategy |
| Founder-led outbound | B2B, high ACV; 10–15 DMs/day | — | cold-start-strategy |
Principle: 2–3 channels executed well > many poorly. Twitter/X for breadth; LinkedIn for conversion. Indie Hackers + SEO or Product Hunt + Reddit common combos.
For HN launch, Reddit post structure, Discord tactics → community-forum.
| Type | Example | Growth Focus |
|---|---|---|
| Micro-SaaS | Nomad List, Tweet Hunter, SiteGPT | SEO, Indie Hackers, Product Hunt |
| AI tools | Photo AI, Interior AI, AutoShorts.ai | Product Hunt, Twitter, LTD |
| Digital products | Templates, plugins, themes | SEO, content |
| Content | Blog, course, tools | SEO, content-marketing |
| Model | Use | Skill |
|---|---|---|
| SaaS (subscription) | Monthly/annual; stable revenue | pricing-strategy |
| One-time purchase | Tools, templates; lower overhead | pricing-strategy |
| LTD | Fast validation; cold start | discount-marketing-strategy |
| Diversified revenue | Multiple products; lower risk | — |
Principle: Monetize early; add payment on day 1 to validate demand. Ramen profitability = first milestone. Avoid platform dependency (e.g., Twitter API).
| Week | Focus |
|---|---|
| 1–2 | Audience building (LinkedIn 3×/week) |
| 3–4 | Beta; community engagement |
| 5 | Pre-launch countdown |
| 6 | Product Hunt + Reddit/Indie Hackers |
| 7 | Post-launch follow-up |
Build in public before launch. For full launch checklist → cold-start-strategy.
| Scenario | Skill |
|---|---|
| First users, launch timeline, Product Hunt | cold-start-strategy |
| Indie Hackers, HN, Reddit post structure, Discord | community-forum |
| PMF validation before scale | pmf-strategy |
| SEO for organic growth | seo-strategy |
| LTD structure, pricing | discount-marketing-strategy |
| Product Hunt, Taaft, G2 submission | product-hunt-launch, directory-submission |
| Full GTM (new product, 90-day) | gtm-strategy, product-launch |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
indie-hacker-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for indie-hacker-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
indie-hacker-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in indie-hacker-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: indie-hacker-strategy is focused, and the summary matches what you get after install.
indie-hacker-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
indie-hacker-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in indie-hacker-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
indie-hacker-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
indie-hacker-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 57