growth-loop

Runs a weekly GA4-driven copy experiment on a Next.js portfolio site.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill growth-loop-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: growth-loop
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/growth-loop
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill growth-loop-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns raw Google Analytics data into one concrete, testable website copy improvement per week, removing the guesswork from deciding which words on a site to change and how to measure whether the change worked. ## Core Features & Use Cases - Analytics-driven problem finding: Pulls 28 days of GA4 data, filters bot traffic, and identifies copy-shaped problems such as weak CTAs, low-engagement landing pages, or mismatched headlines. - Falsifiable hypotheses: Forces every change to be stated as a measurable hypothesis naming its metric before any edit is made, and supports no-op runs when the data does not justify a change. - Safe implementation workflow: Makes copy edits on a separate git branch in a temporary worktree, verifies the Next.js build, and never pushes, merges, or deploys without user approval. - Use Case: A designer runs the loop every Monday; it notices a high-traffic case study with weak dwell time, rewrites its title and description on a branch, and delivers a plain-English report for approval. ## Quick Start Ask the assistant to run the growth loop to analyze last month's GA data and propose one copy change on a review branch.

Frequently Asked Questions about growth-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a GA-driven copy experiment on my website?

Invoke the growth loop, which pulls 28 days of GA4 data, filters bot traffic, forms a falsifiable hypothesis about one copy element, implements the change on a local branch, and writes a report for your approval.

What kinds of website changes does the growth loop make?

It only changes copy: headlines, body text, CTA and link labels, button text, and page metadata titles and descriptions. It never touches CSS, layout, component structure, or dependencies, and limits each run to one focused change.

Does the growth loop push or deploy changes automatically?

No. It works on a local branch in a temporary git worktree, verifies the build, and stops. You approve by merging the branch or reject by deleting it; nothing is ever pushed, merged, or deployed automatically.

What happens if the analytics data shows nothing worth changing?

The loop stops and writes a short no-op report stating nothing is worth changing that week. It does not invent a change just to have something to ship.

How does the growth loop handle previous experiments?

Each run reads the newest prior report and checks whether the previous experiment's target metric moved, recording a verdict of improved, no change, worse, or too early to tell. It avoids re-running hypotheses already tested.