page-cro
Page Conversion Optimization (CRO)
Initial Assessment
Before optimizing, understand:
- Page type - Homepage, landing, pricing, feature, blog?
- Conversion goal - Signup, purchase, contact, download?
- Traffic source - Ads, organic, referral, direct?
- Current metrics - Conversion rate, bounce rate, time on page?
Core Analysis Framework
1. Value Proposition (Above the Fold)
- Can visitors understand what you offer in 5 seconds?
- Is the benefit clear, not just features?
- Does it match the ad/link that brought them?
Test: Show page for 5 seconds, ask "What does this company do?"
More from jamelna-apps/claude-dash
cost-tracking
When user mentions "spending", "usage", "tokens", "API cost", "budget", "expensive", or wants to understand Claude API costs. Provides cost awareness and optimization guidance.
11session-handoff
When user says "continue", "pick up where we left off", "last time", "previous session", "what were we doing", or wants explicit session continuity. Provides structured context handoff between sessions.
4error-diagnosis
When user encounters "error", "exception", "failed", "stack trace", "crashed", or needs error categorization. Provides structured root cause analysis and prevention strategies.
4code-review
When the user mentions "review", "PR", "pull request", "code review", "check my code", "feedback on", or asks for code quality assessment.
3smart-routing
When deciding which Claude model (Opus/Sonnet/Haiku) to use, or when "route", "which model", "complex task", "multi-file", "architectural", or "deep debugging" is mentioned. Guides quality-first model selection.
3rag-enhancement
When user asks "explain", "how does", "understand", "background on", "context for", or needs deep explanations with retrieved history. Auto-enhances answers with decision history and patterns.
3