CRO Optimization

Purpose

Analyze a landing page and deliver a comprehensive CRO audit with specific, actionable recommendations to maximize conversions.

---

Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "cro-optimization loaded, provide your landing page URL or paste your HTML/CSS code"

Then wait for the user to provide their landing page in the next message.

If $ARGUMENTS contains content:

Proceed immediately to Task Execution (skip the "loaded" message).

---

Task Execution

When landing page is available (either from initial $ARGUMENTS or follow-up message):

1. MANDATORY: Read Reference Files FIRST

BLOCKING REQUIREMENT, DO NOT SKIP THIS STEP

Before doing ANYTHING else, you MUST use the Read tool to read ALL three reference files:

Read: ./references/cro_principles.md
Read: ./references/landing_page_patterns.md
Read: ./references/element_audit_framework.md

What you will find:

• cro_principles.md: 13 core CRO principles with detection criteria and fix patterns
• landing_page_patterns.md: Real patterns from high-converting pages (ClickUp, Notion, Stripe, Apple, etc.) organized by category
• element_audit_framework.md: Systematic framework for auditing HTML elements, CTAs, forms, and visual hierarchy

DO NOT PROCEED to Step 2 until you have read all files and have the principles, patterns, and audit framework loaded in context.

2. Check for Business Context

Check if FOUNDER_CONTEXT.md exists in the project root.

• If it exists: Read it and use the business context to personalize recommendations (industry, target audience, product type, competitors).
• If it doesn't exist: Proceed with analysis based on page content alone.

3. Fetch and Extract Landing Page

If user provided a URL:

• Use WebFetch to retrieve the landing page content
• Extract and catalog key elements (see Element Extraction below)