agentleFS
travisjneumantravisjneuman/.claude/skills/growth-engineering/SKILL.md

growth-engineering

Skill106 starsChanged 9 months agoMITView on GitHub

A/B testing infrastructure, feature flags (LaunchDarkly, Unleash), experimentation platforms, PLG patterns, and funnel optimization. Use when building experimentation systems, implementing feature toggles, or optimizing conversion funnels.

  • Reads credentials

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never nest feature flags (creates exponential complexity)

    line 45
  2. Distinctive:

    Don't peek: Set duration upfront, don't stop early on promising results

    line 91

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Growth Engineering Skill

Infrastructure and patterns for product-led growth, experimentation, and conversion optimization.


Feature Flag Systems

Implementation Pattern

// lib/feature-flags.ts
import { PostHog } from 'posthog-node';

const posthog = new PostHog(process.env.POSTHOG_API_KEY!);

interface FeatureFlags {
  'new-onboarding-flow': boolean;
  'pricing-experiment': 'control' | 'variant-a' | 'variant-b';
  'ai-suggestions': boolean;
}

export async function getFlag<K extends keyof FeatureFlags>(
  key: K,
  userId: string,
): Promise<FeatureFlags[K]> {
  const value = await posthog.getFeatureFlag(key, userId);
  return value as FeatureFlags[K];
}

// Usage in component
const showNewOnboarding = await getFlag('new-onboarding-flow', user.id);

Feature Flag Best Practices

  • Short-lived flags: Remove after experiment concludes (< 2 weeks)
  • Long-lived flags: Ops toggles for gradual rollouts, kill switches
  • Never nest feature flags (creates exponential complexity)
  • Clean up stale flags monthly
  • Log flag evaluations for debugging

A/B Testing Infrastructure

Experiment Design

// lib/experiments.ts
interface Experiment {
  id: string;
  name: string;
  variants: {
    id: string;
    weight: number; // 0-100, must sum to 100
  }[];
  targetAudience: {
    percentage: number; // % of users included
    filters?: Record<string, unknown>;
  };
  primaryMetric: string;
  secondaryMetrics: string[];
  minimumSampleSize: number;
  startDate: Date;
  endDate?: Date;
}

// Track experiment exposure
function trackExposure(experimentId: string, variantId: string, userId: string) {
  analytics.capture({
    event: '$experiment_started',
    distinctId: userId,
    properties: {
      $experiment_id: experimentId,
      $variant_id: variantId,
    },
  });
}

Statistical Significance

  • Minimum sample size: Calculate before starting (use Evan Miller calculator)
  • Don't peek: Set duration upfront, don't stop early on promising results
  • Sequential testing: Use if you must check early (adjusts p-values)
  • Minimum detectable effect: Define what improvement matters (e.g., 5% lift)

Product-Led Growth Patterns

Activation Metrics

StageMetricExample
Sign upRegistration completeUser creates account
SetupProfile completeFills required fields
Aha momentCore value experiencedCreates first project
HabitRepeated engagement3 sessions in first week
RevenueConversion to paidSubscribes to plan

Viral Loops

// Referral system pattern
interface Referral {
  referrerId: string;
  referredEmail: string;
  status: 'pending' | 'signed_up' | 'activated' | 'converted';
  rewardGranted: boolean;
}

// Track referral funnel
function trackReferralStep(referralId: string, step: Referral['status']) {
  analytics.capture({
    event: 'referral_step',
    properties: { referralId, step },
  });
}

Conversion Optimization

  • Reduce friction: Minimize form fields, enable social login
  • Social proof: Show user counts, testimonials, logos
  • Urgency: Trial countdown, limited-time offers (use sparingly)
  • Value demonstration: Interactive demos, free tier with clear upgrade path
  • Personalization: Onboarding flow based on use case selection

Growth Metrics

MetricFormulaTarget
Activation rateActivated / Signed up> 40%
Trial-to-paidPaid / Trial started> 15%
Net revenue retention(Start MRR + Expansion - Contraction - Churn) / Start MRR> 110%
Viral coefficientInvites sent * Conversion rate> 0.5
Time to valueMedian time from signup to aha moment< 5 min
DAU/MAU ratioDaily active / Monthly active> 20%

Experimentation Platforms

PlatformTypeBest For
PostHogSelf-hosted/cloudFull-stack, open source
LaunchDarklyCloudFeature flags at scale
StatsigCloudAuto-stats, warehouse-native
GrowthbookSelf-hosted/cloudOpen source, Bayesian stats
OptimizelyCloudEnterprise, multi-channel

Related Resources

  • ~/.claude/skills/product-analytics/SKILL.md - Analytics and tracking
  • agent-product-analytics-specialist skill - Analytics specialist
  • ~/.claude/skills/authentication-patterns/SKILL.md - Auth for PLG

Measure everything. Experiment constantly. Remove what doesn't work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.