From solo
Sets up PostHog metrics tracking plans for iOS/web projects with event funnels, KPI benchmarks, North Star metrics, and kill/iterate/scale decision rules.
npx claudepluginhub fortunto2/solo-factory --plugin soloThis skill is limited to using the following tools:
Set up a metrics tracking plan for a project. Defines PostHog event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds based on lean startup principles.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Set up a metrics tracking plan for a project. Defines PostHog event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds based on lean startup principles.
kb_search(query) — find PostHog methodology, analytics patternsIf MCP tools are not available, fall back to Grep + Read.
This skill implements metrics tracking based on lean startup principles:
Parse project from $ARGUMENTS.
Detect platform:
Load PostHog methodology:
kb_search("PostHog analytics events funnel identity")Define event funnel based on PRD features:
Standard funnel: Awareness → Acquisition → Activation → Revenue → Retention → Referral
See references/kpi-benchmarks.md for the full event table, KPI thresholds, PostHog code snippets, and A/B test template. Adapt events to the specific product.
Forced reasoning — metrics selection: Before defining KPIs, write out:
Set KPI benchmarks per stage:
Use thresholds from references/kpi-benchmarks.md as starting point. Adjust for product type (B2B has lower volume/higher conversion, B2C mobile has higher volume/lower retention).
Define decision rules — use kill/iterate/scale framework from references/kpi-benchmarks.md. Adapt thresholds to project-specific values from step 6.
Generate PostHog implementation snippets — use platform-specific examples from references/kpi-benchmarks.md. Adapt event names and properties to the funnel defined in step 4.
A/B Test Analysis Template — copy template from references/kpi-benchmarks.md into the metrics plan. Include decision rules (SHIP / KEEP / EXTEND / INCONCLUSIVE).
Write metrics plan to docs/metrics-plan.md:
# Metrics Plan: {Project Name}
**Generated:** {YYYY-MM-DD}
**Platform:** {iOS / Web / Both}
**North Star:** {north star metric}
## Event Funnel
| Stage | Event | Properties |
|-------|-------|------------|
{event table from step 4}
## KPIs & Thresholds
| KPI | Target | Kill | Scale |
|-----|--------|------|-------|
{benchmark table from step 6}
## Decision Rules
{framework from step 7}
## Implementation
### PostHog Setup
- Project: {project name} (EU region)
- SDK: {posthog-ios / posthog-js}
- Identity: {anonymous → identified on signup}
### Code Snippets
{snippets from step 8}
## A/B Test Template
{template from step 9}
## Dashboard Template
- Funnel: {stage1} → {stage2} → ... → {stageN}
- Retention: D1 / D7 / D30 cohort chart
- Revenue: MRR trend + trial conversion
---
*Generated by /metrics-track. Implement events, then review weekly.*
$set for user properties, capture for eventsidentify() on signup with user IDCause: Project has both web and iOS indicators. Fix: Skill checks package manifests. If both exist, it generates cross-platform identity setup. Verify the detected platform in the output.
Cause: Default thresholds are industry averages.
Fix: Adjust thresholds in docs/metrics-plan.md based on your niche. B2B typically has lower volume but higher conversion.
Cause: Metrics plan generated but SDK not installed.
Fix: This skill generates the PLAN only. Install PostHog SDK separately: pnpm add posthog-js (web) or add posthog-ios via SPM (iOS).