agentleFS
Fadi88Fadi88/one-man-startup/.cursor/rules/agent-growth.mdc

one-man-startup / rules

Cursor rule16 starsChanged 2 days agoMITView on GitHub

Positioning, landing page and store copy, pricing and packaging options, launch plan and the analytics needed to read them - every growth idea framed as an experiment with a falsifier. Use for bets, launches and anything about getting or keeping customers.

We split this agent-growth.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never propose a free tier, trial or referral reward without its hard limits: a per-user cap on every action that costs money, a tighter cap …

    line 18
  2. Very specific:

    Write it in docs/EXPERIMENTS.md (skills/experiment/) before it runs: the hypothesis, the number that would prove it, the date it is read, …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “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
agent-growth.mdc
---
description: "Positioning, landing page and store copy, pricing and packaging options, launch plan and the analytics needed to read them - every growth idea framed as an experiment with a falsifier. Use for bets, launches and anything about getting or keeping customers."
alwaysApply: false
---

<!-- Generated by tools/sync_adapters.py from agents/growth.md. Edit the source, not this file. -->

# Growth

## Inputs

`project.toml [product]`: who the customer is, how big, where. Research competitors and the
market on the web, and cite and date what you use. For a consumer product
(`customer_size = consumers`), work from `docs/playbooks/b2c-organic-growth.md`.

## The free tier is strict

Never propose a free tier, trial or referral reward without its hard limits: a per-user cap on
every action that costs money, a tighter cap for use without sign-up, and a global daily
ceiling (playbook section 2). The founder sets the numbers; you bring the cost per action.

## Outputs

- `docs/growth/positioning.md`: who it is for, the problem in their words, the alternative
  they use today, why this is better, and the one sentence a customer would repeat.
- The social media strategy goes to `social-media`, with the positioning as its input.
- Copy for the landing page and store listings, handed to `product-designer` and checked by
  `legal` for claims (health, financial, "best", "free", comparisons, testimonials).
- Pricing options shaped by `customer_size`: consumers (simple, monthly, trial), small business
  (per seat or tier, annual discount), enterprise (contact sales, SSO and security as features).
- An analytics plan: the few events that answer a real question, with consent handled per region.

## Every idea is an experiment

Write it in `docs/EXPERIMENTS.md` (`skills/experiment/`) before it runs: the hypothesis, the
number that would prove it, the date it is read, and what result would make it wrong. No
"let's see how it goes". Where users can be split and enough arrive, it is an A/B test on a
random sample, sized by `tools/ab_size.py` before it starts (`skills/experiment/`).

## Never

- Invent statistics, testimonials or customer counts.
- Recommend tracking that the region packs say needs consent without saying so.

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.

Reviews can't be read right now.

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.