/growth
Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems.
$ npx -y skills add whawkinsiv/claude-code-superpowers --skill growth --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/growth
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems.
SKILL.md
growth.SKILL.mdname: growth
description: "Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems."
Growth & Product-Led Growth
In PLG, the product is your best salesperson. This skill helps you design growth into your product — with concrete tactics and prompts you can hand to Claude Code.
Core Principles
- Growth is a system, not a hack. Build loops, not one-time campaigns.
- Activation is the most important metric. A user who never experiences value is already lost.
- Virality is engineered, not accidental. Design sharing into the product.
- Retention is the foundation. Growing on top of a leaky bucket is a losing game.
- For a solo founder: pick ONE growth lever, make it work, then add the next.
---
The PLG Funnel
Acquisition → Activation → Retention → Revenue → Referral
**The most common mistake:** Founders focus on Acquisition first. Focus on Activation and Retention first — there's no point driving signups into a leaky bucket.
---
Activation (Start Here)
Define Your Aha Moment
The specific action where users first experience core value:
| Product Type | Example Aha Moment | |-------------|-------------------| | Project management | Created first project + added a task | | Email tool | Sent first campaign | | Analytics | Saw first dashboard with real data | | Design tool | Exported first design | | Scheduling | Booked first meeting through the tool |
**Your aha moment:** [Action that makes users say "I get it, this is useful"]
Drive Users to Aha Fast
Every screen between signup and the aha moment is a drop-off risk.
**Tell AI:**
Design the onboarding flow to get users to [your aha moment] in under 3 minutes:
1. After signup, skip the "check your email" screen — go directly to the product
2. Show a setup wizard (3-5 steps max) that collects only what's needed to deliver value
3. Pre-populate with sample data or templates so the product looks useful immediately
4. Add a progress checklist: "Complete your setup: ☑ Create [X] ☐ [Next step] ☐ [Final step]"
5. Show an empty state with a clear CTA on every empty page ("Create your first [X]")Activation Emails
Pair your in-product onboarding with a 5-email welcome sequence that nudges unactivated users. See the **email** skill for the full welcome sequence template with ready-to-paste copy for each email.
---
Acquisition Strategies
Pick ONE that matches your product. Don't spread across all of them.
| Strategy | Best For | Effort | Time to Results | |----------|----------|--------|-----------------| | Free tool / calculator | Products that solve measurable problems | Medium | 1-3 months | | Template gallery | Products with customizable outputs | Medium | 2-4 months | | Content-as-product | Products in information-heavy spaces | High | 3-6 months | | Community-driven | Products with passionate niche users | High | 3-6 months | | Integrations | Products that connect to other tools | Medium | 1-2 months per integration | | Freemium | Products where free use drives word-of-mouth | Low | Immediate (but slow growth) |
**Tell AI:**
Build a [free tool / template gallery / calculator] that:
- Solves a specific problem our ICP has (related to our product)
- Requires no signup to use
- Shows a teaser of our full product's value
- Includes a CTA: "Want more? [Product name] does this automatically."
- Is SEO-optimized so it attracts organic traffic
---
Viral Loop Design
A viral loop has 4 parts: User gets value → Has reason to share → New user sees value → Converts → Loop repeats.
Viral Mechanics for SaaS
| Mechanic | How It Works | Example | |----------|-------------|---------| | Collaboration invites | Product requires multiple users | "Invite your team to edit this" | | Shared outputs | User creates something shareable | Reports, links, dashboards with "Made with [Product]" | | Referral rewards | Incentivized invitations | "Give $20, get $20" | | Public pages | User content is SEO-indexable | Public profiles, portfolios, pages | | Embeds | Widget on user's site links back | Badges, chat widgets, forms |
**Tell AI:**
Add a sharing/invite mechanic to our product:
- After a user completes [key action], prompt: "Share this with your team" or "Invite a collaborator"
- Make shared links show a preview of the output (not just a signup page)
- Add "Made with [Product]" branding on shared/public outputs with a link to our homepage
- Track invite sends, invite accepts, and invite-to-signup conversion
---
Retention Mechanics
Build Habit Loops
| Component | What It Is | Example | |-----------|-----------|---------| | Trigger | What brings them back | Email digest, notification, calendar event | | Action | What they do in the product | Check dashboard, respond to comment, update status | | Reward | Value they get | New insight, progress indicator, completed task | | Investment | What makes leaving harder | More data, more connections, more history |
**Tell AI:**
Build retention mechanics into the product:
1. Weekly email digest: summarize what happened this week + one insight or action item
2. Activity notifications: "[Name] commented on your [item]" — not time-based ("It's been 3 days")
3. Progress indicators: Show users their cumulative value ("You've saved 14 hours this month")
4. Data investment: The more they use it, the more valuable their data becomes (history, reports, trends)Feature Drips
Don't show everything on day 1. Reveal features as users are ready:
**Tell AI:**
Implement progressive feature disclosure:
- Week 1: Show only core features (the ones needed for the aha moment)
- Week 2: Surface advanced feature with a tooltip: "Now that you've [done X], try [advanced feature]"
- Week 3+: Unlock remaining features with brief explanations
- Gate premium features w
Read more
name: growth description: "Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems."
Growth & Product-Led Growth
In PLG, the product is your best salesperson. This skill helps you design growth into your product — with concrete tactics and prompts you can hand to Claude Code.
Core Principles
- Growth is a system, not a hack. Build loops, not one-time campaigns.
- Activation is the most important metric. A user who never experiences value is already lost.
- Virality is engineered, not accidental. Design sharing into the product.
- Retention is the foundation. Growing on top of a leaky bucket is a losing game.
- For a solo founder: pick ONE growth lever, make it work, then add the next.
---
The PLG Funnel
Acquisition → Activation → Retention → Revenue → Referral
**The most common mistake:** Founders focus on Acquisition first. Focus on Activation and Retention first — there's no point driving signups into a leaky bucket.
---
Activation (Start Here)
Define Your Aha Moment
The specific action where users first experience core value:
| Product Type | Example Aha Moment | |-------------|-------------------| | Project management | Created first project + added a task | | Email tool | Sent first campaign | | Analytics | Saw first dashboard with real data | | Design tool | Exported first design | | Scheduling | Booked first meeting through the tool |
**Your aha moment:** [Action that makes users say "I get it, this is useful"]
Drive Users to Aha Fast
Every screen between signup and the aha moment is a drop-off risk.
**Tell AI:**
Design the onboarding flow to get users to [your aha moment] in under 3 minutes:
1. After signup, skip the "check your email" screen — go directly to the product
2. Show a setup wizard (3-5 steps max) that collects only what's needed to deliver value
3. Pre-populate with sample data or templates so the product looks useful immediately
4. Add a progress checklist: "Complete your setup: ☑ Create [X] ☐ [Next step] ☐ [Final step]"
5. Show an empty state with a clear CTA on every empty page ("Create your first [X]")Activation Emails
Pair your in-product onboarding with a 5-email welcome sequence that nudges unactivated users. See the **email** skill for the full welcome sequence template with ready-to-paste copy for each email.
---
Acquisition Strategies
Pick ONE that matches your product. Don't spread across all of them.
| Strategy | Best For | Effort | Time to Results | |----------|----------|--------|-----------------| | Free tool / calculator | Products that solve measurable problems | Medium | 1-3 months | | Template gallery | Products with customizable outputs | Medium | 2-4 months | | Content-as-product | Products in information-heavy spaces | High | 3-6 months | | Community-driven | Products with passionate niche users | High | 3-6 months | | Integrations | Products that connect to other tools | Medium | 1-2 months per integration | | Freemium | Products where free use drives word-of-mouth | Low | Immediate (but slow growth) |
**Tell AI:**
Build a [free tool / template gallery / calculator] that: - Solves a specific problem our ICP has (related to our product) - Requires no signup to use - Shows a teaser of our full product's value - Includes a CTA: "Want more? [Product name] does this automatically." - Is SEO-optimized so it attracts organic traffic
---
Viral Loop Design
A viral loop has 4 parts: User gets value → Has reason to share → New user sees value → Converts → Loop repeats.
Viral Mechanics for SaaS
| Mechanic | How It Works | Example | |----------|-------------|---------| | Collaboration invites | Product requires multiple users | "Invite your team to edit this" | | Shared outputs | User creates something shareable | Reports, links, dashboards with "Made with [Product]" | | Referral rewards | Incentivized invitations | "Give $20, get $20" | | Public pages | User content is SEO-indexable | Public profiles, portfolios, pages | | Embeds | Widget on user's site links back | Badges, chat widgets, forms |
**Tell AI:**
Add a sharing/invite mechanic to our product: - After a user completes [key action], prompt: "Share this with your team" or "Invite a collaborator" - Make shared links show a preview of the output (not just a signup page) - Add "Made with [Product]" branding on shared/public outputs with a link to our homepage - Track invite sends, invite accepts, and invite-to-signup conversion
---
Retention Mechanics
Build Habit Loops
| Component | What It Is | Example | |-----------|-----------|---------| | Trigger | What brings them back | Email digest, notification, calendar event | | Action | What they do in the product | Check dashboard, respond to comment, update status | | Reward | Value they get | New insight, progress indicator, completed task | | Investment | What makes leaving harder | More data, more connections, more history |
**Tell AI:**
Build retention mechanics into the product:
1. Weekly email digest: summarize what happened this week + one insight or action item
2. Activity notifications: "[Name] commented on your [item]" — not time-based ("It's been 3 days")
3. Progress indicators: Show users their cumulative value ("You've saved 14 hours this month")
4. Data investment: The more they use it, the more valuable their data becomes (history, reports, trends)Feature Drips
Don't show everything on day 1. Reveal features as users are ready:
**Tell AI:**
Implement progressive feature disclosure: - Week 1: Show only core features (the ones needed for the aha moment) - Week 2: Surface advanced feature with a tooltip: "Now that you've [done X], try [advanced feature]" - Week 3+: Unlock remaining features with brief explanations - Gate premium features w
43 expert skills for non-technical founders building SaaS with AI tools (Claude Code, Lovable, Replit, Cursor). Covers the full lifecycle of planning, building, launching, and growing a software business — actionable guides, checklists, and copy-paste prompts.
Other skills on solo-founder-superpowers.
- /about-me
Use this skill when the user wants to create a founder profile, establish their personal voice for content, or set up context so other skills produce personalized output instead of generic AI copy. Also use when the user says 'set up my voice,' 'create my profile,' 'who am I,'
Open skill - /accounting
Use this skill when the user needs to set up bookkeeping, track revenue and expenses, prepare for taxes, choose accounting software, understand SaaS revenue recognition, or manage the financial operations of their bootstrapped business. Covers bookkeeping setup, tax preparation,
Open skill - /ads
Use this skill when the user needs to run Google Ads, write ad copy, select keywords, optimize CAC/LTV, or manage a small paid acquisition budget. Covers Google Ads strategy, keyword selection, ad copywriting, and conversion tracking for bootstrapped SaaS.
Open skill - /ai-features
Use this skill when the user needs to add AI-powered features to their SaaS product, integrate LLM APIs, build AI assistants, implement RAG, or use AI to differentiate their product. Covers API selection, prompt engineering for product features, cost management, and building AI
Open skill - /analytics
Use this skill when the user needs to set up analytics, design event tracking, define key metrics, build funnels, or instrument their SaaS product for data-driven decisions. Covers event naming conventions, tracking strategy, funnel analytics, and data quality.
Open skill - /beautify
Use this skill when the user wants to make their app look better, says it looks like a template, asks how to achieve Stripe/Linear quality, or says something looks off. Covers visual hierarchy, whitespace, composition, color application, and typography in practice.
Open skill

