agentleFS
botirkhaltaevbotirkhaltaev/botir-skills/skills/conversion-growth-design/SKILL.md

conversion-growth-design

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Apply behavioral psychology to design for action. Covers landing page design, CRO principles, behavioral psychology frameworks, A/B testing strategy, friction reduction, and the persuasion toolkit. Use when optimizing for conversions, designing landing pages, or building growth features. Triggers on: "conversion optimization", "CRO", "landing page", "growth design", "behavioral psychology", "persuasion design", "funnel optimization", "A/B testing design".

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    All three must converge:

    line 22
  2. Distinctive:

    Design implication: If motivation is low, increase ability (make it effortless).

    line 27
  3. Distinctive:

    Run for complete business cycles (full weeks)

    line 127
  4. Distinctive:

    Check guardrail metrics (don't improve conversion at expense of retention)

    line 129
  5. Distinctive:

    If the honest answer to any of these is no, don't do it.

    line 141

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill 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
SKILL.md

Conversion & Growth Design

Apply behavioral psychology to design for action. Conversion is not manipulation — it's removing friction between user intent and the outcome they want.

Core Frameworks

Fogg Behavior Model

Behavior = Motivation × Ability × Prompt

All three must converge:

  • Motivation — does the user want this? (emotion, anticipation, belonging)
  • Ability — is it easy to do? (time, money, effort, skill)
  • Prompt — is there a clear call to action? (trigger, nudge, reminder)

Design implication: If motivation is low, increase ability (make it effortless). If ability is low, increase motivation (show value). Always provide a clear prompt.

Hick's Law

More choices = longer decision time = more abandonment.

Apply: One primary action per screen. Highlight the recommended option. Collapse advanced options.

Cognitive Load Theory

Working memory is limited. Reduce mental effort.

Source of LoadFix
Too much informationProgressive disclosure
Unfamiliar termsPlain language
Too many decisionsSmart defaults, recommended option
Visual clutterWhite space, clear hierarchy
Task switchingLinear flow, one thing at a time

Landing Page Design

The 5-Second Rule

A visitor decides whether to stay or leave in 5 seconds. Above the fold must communicate:

  1. What this is
  2. Why it matters to them
  3. What to do next

Above-the-Fold Structure

┌─────────────────────────────────────┐
│  Logo          Nav          [CTA]   │  ← Navigation minimal
│                                     │
│  Headline: The value proposition    │  ← One clear benefit
│  Subhead: How it works (brief)      │  ← Clarify, not sell
│                                     │
│  [Primary CTA]  [Secondary CTA]     │  ← One primary action
│                                     │
│  [Visual: product/demo/social proof]│  ← Show, don't tell
└─────────────────────────────────────┘

Headline Formula

[Outcome user wants] + [How you deliver it] + [Timeframe if impressive]

Examples:

  • "Ship your SaaS in weeks, not months"
  • "Automatic backups that never slow you down"
  • "The project management tool that actually gets used"

CTA Design

  • Use first-person — "Start my free trial" outperforms "Start your free trial"
  • Lead with a verb — "Get", "Start", "Create", "Download"
  • Include the benefit — "Get the guide" not "Submit"
  • One primary CTA per section — multiple CTAs compete and confuse

Persuasion Elements

ElementWhen to UseExample
Social proofAbove the fold, near CTAs"Join 10,000+ teams" / logos
TestimonialsAfter feature descriptionsQuote + photo + title + company
Risk reversalNear purchase/signup"30-day money back", "Cancel anytime"
SpecificityInstead of vague claims"Save 5 hours per week" not "Save time"
ScarcityOnly if genuine"Only 3 seats left at this price"
AuthorityB2B, professional toolsCertifications, industry awards

Friction Reduction

Form Optimization

TechniqueImpact
Reduce fieldsEach field reduces completion ~10%
Inline validationValidate on blur, not submit
Show password toggleAlways
Autofill enabledautocomplete attributes on all fields
Progress indicatorFor multi-step forms
Address lookupAuto-complete from postal code

Checkout Optimization

  • Guest checkout option (don't force account creation)
  • Summary visible throughout (what, how much, when)
  • Security signals near payment (SSL badge, encryption note)
  • Multiple payment options
  • Clear error messages with inline correction

A/B Testing for Conversion

Hypothesis Structure

"If we change [element] for [audience], we expect [result] because [behavioral reason]."

What to Test (Priority Order)

  1. Headline and value proposition
  2. CTA text and placement
  3. Social proof placement and format
  4. Form length and fields
  5. Page length (short vs. long)
  6. Visual hierarchy
  7. Color (last — usually smallest impact)

Statistical Rigor

  • Run for complete business cycles (full weeks)
  • Reach 95% statistical significance
  • Check guardrail metrics (don't improve conversion at expense of retention)
  • Segment results (what works for mobile may not for desktop)

Dark Side Warning

Many growth tactics are dark patterns in disguise. Before implementing any persuasion technique, run it through the ethical filter:

  • Is this genuinely helping the user?
  • Would I be comfortable explaining this to a frustrated user?
  • Am I creating real value or manufactured urgency?
  • Can users easily undo this action?

If the honest answer to any of these is no, don't do it.

Reference Map

  • references/fogg-hicks-checklist.md — Fogg B=MAP, Hick’s Law, 5-second fold checklist
  • references/ab-test-priority.md — hypothesis template, test priority order, rigor gate

Related Skills

  • For onboarding and activation → use onboarding-ux
  • For landing page UX writing → use ux-writing-content-design
  • For ethical boundaries → use ethical-design-patterns
  • For A/B testing methods → use user-research-methods

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.