Growth & Distribution
Build growth features like landing pages, SEO, waitlists, and referral systems. Use this skill when growth or distribution features are requested.
Best use case
Growth & Distribution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build growth features like landing pages, SEO, waitlists, and referral systems. Use this skill when growth or distribution features are requested.
Teams using Growth & Distribution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/growth/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Growth & Distribution Compares
| Feature / Agent | Growth & Distribution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build growth features like landing pages, SEO, waitlists, and referral systems. Use this skill when growth or distribution features are requested.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill: Growth & Distribution ## Metadata | Field | Value | |-------|-------| | **Skill ID** | SKL-0013 | | **Version** | 1.0 | | **Owner** | builder | | **Inputs** | Task description, PRD, DECISIONS.md | | **Outputs** | Landing pages, SEO, referral/waitlist, STATE.md updated | | **Triggers** | `GROWTH_FEATURE_REQUESTED` | --- ## Purpose Build growth infrastructure — landing pages, SEO, referral mechanics, waitlists, social sharing. Growth is infrastructure that compounds, not a campaign. --- ## Procedure 1. **Extract value proposition from PRD:** - Who (target user), what problem, what product does, why now - Formula: "[Product] helps [user] [do X] so they can [outcome], without [pain]." 1.5. **Select Visual Tier:** Ask the user or infer from the PRD. This decision affects the page structure, not just styling. | Tier | When to Use | What It Produces | |------|-------------|-----------------| | **Clean** | MVP, internal tool, speed matters | Functional, readable, good defaults. Standard layout. | | **Premium** | Product launch, public-facing, brand impression matters | Everything in Clean + glassmorphism, gradients, animations, parallax, animated stats. | **Auto-detect:** If the PRD or task mentions "launch", "public", "marketing", or "brand", default to Premium. Otherwise default to Clean. 2. **Landing page structure** (high-converting order): 1. Hero — who + what + primary CTA (above fold) 2. Problem — amplify pain, make reader feel understood 3. Solution — how product solves it (show, don't tell) 4. Social proof — quotes, logos, numbers 5. Features — 3 key capabilities with user benefits 6. FAQ — top 5 objections answered 7. Final CTA — same as hero 2.5. **Premium Tier Techniques** (skip if Visual Tier = Clean): Apply these techniques during and after the page build. Premium tier defaults to dark theme (dark background, light text) unless the project has an established light brand. **Hero:** - Full-viewport hero with layered background (gradient + image at 10-20% opacity + optional particle/grid overlay) - Animated headline (word-by-word reveal or typewriter effect) - Floating accent elements (blurred gradient orbs) for depth - CTA button with glow effect on hover **Sections:** - Glassmorphism cards (backdrop-blur, semi-transparent background, subtle border) - Multi-stop gradient backgrounds flowing between sections (no hard color breaks) - Alternating dark/light sections with gradient transitions - Generous whitespace (py-24 to py-32 between sections) **Typography:** - Custom Google Fonts pairing (display font for headlines, clean sans for body) - Oversized hero headline (text-6xl to text-8xl) - Gradient text on key headlines (background-clip: text) - Animated counter/stats section (numbers count up on scroll) **Animations:** - Scroll-triggered section reveals (Framer Motion or AOS) - Staggered card entrance (50-100ms delays) - Parallax on hero background (subtle, one layer) - Floating elements with subtle CSS animation (translate + rotate keyframes) - All animations must respect `prefers-reduced-motion` **Visual Depth:** - Layered z-index composition (background, mid-ground, foreground) - Soft shadows on cards (shadow-xl with low opacity) - Noise/grain texture overlay on dark sections (2-5% opacity) - SVG decorative shapes (blurred blobs, curves) as section dividers **Social Proof (Premium):** - Logo carousel with grayscale-to-color hover effect - Testimonial cards with avatar, name, role, quote - Animated stat counters (e.g., "500+ users" counting up on scroll) **Cross-reference:** Premium tier must also pass the Design Quality Checklist (`.claude/skills/frontend-dev/CHECKLIST.md`), including the Anti-Patterns section. 3. **SEO foundations:** - SEO component on all public pages (title, description, OG tags, Twitter card, structured data) - `robots.txt` (allow public, disallow /api/ and /dashboard/) - `sitemap.xml` auto-generated from pages 4. **Waitlist / email capture:** - Validate email, check duplicates, generate referral code - Send confirmation email with position and referral link - Track `waitlist_joined` event 5. **Referral mechanics (if PRD calls for it):** - Reward both referrer and referee - Reward referrer on activation (not signup) to prevent gaming 6. **Social sharing** — native share sheet on mobile, clipboard fallback, direct platform links. 7. **Update STATE.md.** --- ## Constraints - Never writes dishonest or misleading marketing copy - Never uses dark patterns (fake urgency, hidden costs) - Never blocks signup with excessive fields — email first - Never ships landing page without SEO metadata - Always ties growth features to a PRD metric - **Friction check before shipping:** Is CTA above fold? Can a visitor understand the product in under 10 seconds? Are form fields minimized? Reference: `.claude/skills/friction-audit/CHECKLIST.md` - **Premium performance:** Premium animations must maintain 60fps. Use `will-change` sparingly. Test on mobile viewport. Prefer CSS animations over JS where possible. --- ## Primary Agent builder --- ## Definition of Done - [ ] Value proposition extracted from PRD - [ ] Landing page with hero, problem, solution, features, proof, FAQ, CTA - [ ] SEO component on all public pages - [ ] robots.txt and sitemap.xml created - [ ] Email capture / waitlist implemented - [ ] Referral mechanics (if PRD requires) - [ ] Share flow on key content/milestones - [ ] Growth events tracked - [ ] Visual Tier applied ([Clean | Premium]) - [ ] STATE.md updated ## Knowledge Enhancement (MCP mode) If Cortex MCP is available: 1. Call `search_knowledge` with query derived from task (e.g., "landing page patterns SaaS", "conversion optimization", "social proof design"), category="ux-design" 2. If relevant results found, call `get_fragment` on the top result 3. Apply as supplementary context (does not override this skill's procedure) ## Output Contract | Field | Value | |-------|-------| | **Artifacts** | Landing pages, SEO components (`robots.txt`, `sitemap.xml`), referral/waitlist logic, share flows | | **State Update** | `.claude/project/STATE.md` — mark task complete, log files modified | | **Handoff Event** | `TASK_COMPLETED` (growth infrastructure built) |
Related Skills
Supply Chain Audit
Audit the dependency supply chain for security risks beyond what `npm audit` or `pip audit` catches. Analyzes dependency health, maintainer trust signals, typosquatting risk, and transitive dependency exposure.
SEO Audit
Audit web pages for search engine optimization: meta tags, heading hierarchy, structured data, image optimization, mobile-friendliness, and content quality. Complements SKL-0013 (Growth & Distribution) by validating what was built.
Pitch Deck
Create a structured pitch deck outline for investors, stakeholders, or partners. Covers problem, solution, market, traction, team, and ask. Natural output after PRD + Problem Stress Test validation.
Launch Checklist
Pre-launch validation covering everything deployment (SKL-0021) doesn't: analytics, error tracking, social meta, legal pages, email setup, DNS, SSL, and go-live readiness. Produces a launch readiness report with pass/fail checklist. Use this skill before going live on any project.
Insecure Defaults Detection
Detect insecure default configurations, hardcoded credentials, fail-open security patterns, and dangerous default values in application code and configuration files. Complements SKL-0015 (Security Audit) by focusing on configuration-level vulnerabilities that dependency scanners miss.
Differential Security Review
Security-focused review of code changes using git diff analysis. Identifies security implications of recent modifications — new attack surfaces, removed protections, changed auth logic, and risky refactors. Complements SKL-0016 (Code Review) with a security lens on diffs.
Copywriting
Write conversion-focused copy using proven frameworks (AIDA, PAS, BAB). Produces headlines, CTAs, landing page copy, email sequences, and micro-copy. Ensures copy matches brand voice and target audience.
Competitor Analysis
Structured competitor research: features, pricing, positioning, gaps, and differentiation strategy. Feeds into PRD Writing (SKL-0004) and Problem Stress Test (SKL-0027) with better market context.
UX Design
Design user experiences including wireframes, flows, and interaction patterns. Use this skill when UX design work is requested, including onboarding flows and interface layouts.
User Acceptance Testing
Structured QA testing with four modes: diff-aware (auto-scoped to branch changes), full (systematic exploration), quick (30-second smoke test), and regression (compare against baseline). Produces health score, structured reports, and actionable bug lists. Use this skill when UAT is requested or a feature is ready for acceptance testing.
Token Audit
Audit the current project for token waste patterns. Produces a Token Health Report with scored findings and actionable fixes. Use this skill when token usage feels high, sessions are hitting limits, or before optimizing costs.
Test Writing
Write automated tests for existing or new functionality. Use this skill when tests are requested, including unit tests, integration tests, and end-to-end tests.