Conversion Optimization

"Method over hacks. Evidence over assumption."

TL;DR

CRO: friction point analysis, trust signals, funnel optimization, A/B test design. All outputs follow MetodologIA brand standards and evidence tagging. [EXPLICIT]

Procedure

Step 1: Discover

• Gather requirements and context from user input
• Read existing code, docs, and configuration
• Identify current state and gaps

Step 2: Analyze

• Evaluate options against Constitution principles (XIII Think First, XIV Simple First)
• Select the approach with best evidence support
• Document trade-offs and decisions

Step 3: Execute

• Implement following established patterns
• Apply evidence tags to all claims
• Use brand template for HTML outputs (references/brand/)

Step 4: Validate

• Verify against quality criteria
• Check evidence tag coverage
• Confirm Constitution compliance

Quality Criteria

• Follows Constitution principles
• Evidence tags on all claims
• Output is actionable and specific
• No redundancy or padding

Anti-Patterns

Anti-Pattern	Why It's Bad	Do This Instead
Acting without understanding	Wastes effort on wrong solution	Think First (XIII)
Over-engineering	Complexity without value	Simple First (XIV)
Missing evidence tags	Claims without basis	Tag every assertion

Related Skills

• Related domain skills in this category

Usage

Example invocations:

• "/conversion-optimization" — Run the full conversion optimization workflow
• "conversion optimization on this project" — Apply to current context

Assumptions & Limits

• Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
• Requires English-language output unless otherwise specified [EXPLICIT]
• Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate