Skills

Grow App

Guided journey from an app people sign up for and then quietly abandon to a sealed...

Install

npx skills add wondelai/skills --skill grow-app -g -a claude-code -y
Repository
wondelai/skills2.6k
Category
Design
Updated
2mo ago
License
MIT
Context cost
Mediumabout 3,000 tokens
Runs scripts
No, instructions only

What it does

Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says ''users sign up then disappear''. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.

Grow an App

Your app has users who sign up and then quietly disappear, cohorts decay, daily actives are flat, the activation funnel leaks where it always has, and nothing looks obviously broken. This journey seals the bucket: it turns first-time users into activated, then habitual, then would-miss-it users across eight interactive phases. The agent asks before every decision and records the outcome in docs/, so the work resumes across sessions instead of restarting. Growth here is an engineering and design problem, not a bigger ad budget.

Core Principle

Fix the leaky bucket before pouring in acquisition: habit, activation, and retention come before any growth spend. This skill sequences the eight phases, asks every decision question, and records each choice in docs/. The constituent skills carry the method, invoke them rather than improvising their frameworks.

Journey Map

PhaseSkillQuestion it answersArtifact
1hooked-uxWhy do users come back without us paying?Extends docs/PRODUCT.md
2improve-retentionWhy don't new users reach the loop?Extends docs/PRODUCT.md
3continuous-discoveryWhat do our own users actually need?Extends docs/PRODUCT.md + docs/CUSTOMER.md
4lean-uxWhich bet is worth building?Extends docs/EXPERIMENTS.md
5inspired-productIs the team building the right things?Extends docs/PRODUCT.md
6lean-analyticsWhich single number tells the truth?Creates docs/METRICS.md, sets the Rule 8 bar
7microinteractionsDoes it feel alive in the hand?Extends docs/DESIGN.md
8drive-motivationWill engagement last, or curdle?Extends docs/PRODUCT.md
Read the whole SKILL.md on GitHub

More in Design