experiment-design-kit
Toolkit for structuring hypotheses, variants, guardrails, and measurement plans.
What this skill does
# Experiment Design Kit Skill ## When to Use - Translating raw ideas into testable hypotheses with clear success metrics. - Ensuring experiment briefs include guardrails, instrumentation, and rollout details. - Coaching pods on best practices for multi-variant or multi-surface tests. ## Framework 1. **Problem Framing** – define user problem, business impact, and north-star metric. 2. **Hypothesis Structure** – "If we do X for Y persona, we expect Z change" with assumptions. 3. **Measurement Plan** – primary metric, guardrails, min detectable effect, power calc. 4. **Variant Strategy** – control definition, variant catalog, targeting, and exclusion rules. 5. **Operational Plan** – owners, timeline, dependencies, QA/rollback steps. ## Templates - Experiment brief (context, hypothesis, design, metrics, launch checklist). - Guardrail register with thresholds + alerting rules. - Variant matrix for surfaces, messaging, and states. - **GTM Agents Growth Backlog Board** – capture idea → sizing → prioritization scoring (ICE/RICE) @puerto/README.md#183-212. - **Weekly Experiment Packet** – includes KPI guardrails, qualitative notes, and next bets for Marketing Director + Sales Director. - **Rollback Playbook** – pre-built checklist tied to lifecycle-mapping rip-cord procedures. ## Tips - Pressure-test hypotheses with counter-metrics to avoid local optima. - Document data constraints early to avoid rework during build. - Pair with `guardrail-scorecard` to ensure sign-off before launch. - Apply GTM Agents cadence: Monday backlog groom, Wednesday build review, Friday learnings sync. - Require KPI guardrails per stage (activation, engagement, monetization) before authorizing build. - If a test risks Sales velocity, include Sales Director in approval routing per GTM Agents governance. ## GTM Agents Experiment Operating Model 1. **Backlog Intake** – ideas flow from GTM pods; Growth Marketer tags theme, objective, expected impact. 2. **Prioritization** – score with RICE + qualitative "strategic fit" modifier; surface top 3 bets weekly. 3. **Design & Instrumentation** – reference Serena/Context7 to patch code + confirm documentation. 4. **Launch & Monitor** – use guardrail-scorecard to watch leading indicators (churn, complaints, latency). 5. **Learning Loop** – run Sequential Thinking retro; document hypothesis, result, decision, follow-up in backlog card. ## KPI Guardrails (GTM Agents Reference) - Activation rate change must stay within ±3% of baseline for Tier-1 segments. - Revenue per visitor cannot drop more than 2% for more than 48h. - Support tickets tied to experiment variant must remain <5% of total volume. ## Weekly Experiment Packet Outline ``` Week Ending: <Date> 1. Portfolio Snapshot – tests live, status, KPI trend (guardrail vs actual) 2. Key Wins – hypothesis, uplift, next action (ship, iterate, expand) 3. Guardrail Alerts – what tripped, mitigation taken (rollback? scope adjust?) 4. Pipeline Impact – SQLs, ARR influenced, notable customer anecdotes 5. Upcoming Launches – dependencies, owners, open questions ``` Share packet with Growth, Marketing Director, Sales Director, and RevOps to mirror GTM Agents's cross-functional communication rhythm. ---
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.