shadcn-lar

• Headline 4-U Formula: Useful, Unique, Urgent, Ultra-specific (80% won't read past this) • Above-Fold Value Proposition: Customer problem focus, no company story, zero scroll required • CTA First-Person Psychology: "Get MY Guide" vs "Get YOUR Guide" (90% more clicks) • 5-Field Form Maximum: Every field kills conversions, progressive profiling for the rest • Message Match Precision: Ad copy, landing page headline, broken promises = bounce • Social Proof Near CTAs: Testimonials with faces/names, results, placed at decision points • Cognitive Bias Stack: Loss aversion (fear), social proof (FOMO), anchoring (pricing) • PAS Copy Framework: Problem > Agitate > Solve, emotion before logic • Genuine Urgency Only: Real deadlines, actual limits, fake timers destroy trust forever • Price Anchoring Display: Show expensive option first, make real price feel like relief • Trust Signal Clustering: Security badges, guarantees, policies all visible together • Visual Hierarchy F-Pattern: Eyes scan F-shape, put conversions in the path • Lead Magnet Hierarchy: Templates > Checklists > Guides (instant > delayed gratification) • Objection Preemption: Address top 3 concerns before they think them, FAQ near CTA • Mobile Thumb Zone: CTAs where thumbs naturally rest, not stretching required • One-Variable Testing: Change one thing, measure impact, compound wins over time • Post-Conversion Momentum: Thank you page sells next step while excitement peaks • Cart Recovery Sequence: Email in 1 hour, retarget in 4 hours, incentive at 24 hours • Reading Level Grade 6: Smart people prefer simple, 11-word sentences, short paragraphs • TOFU/MOFU/BOFU Logic: Awareness content ≠ decision content, match intent precisely • White Space = Focus: Empty space makes CTAs impossible to miss, crowded = confused • Benefit-First Language: Features tell, benefits sell, transformations compel • Micro-Commitment Ladder: Small yes leads to big yes, start with email only • Performance Tracking Stack: Heatmaps show problems, recordings show why, events show what • Weekly Optimization Ritual: Review metrics Monday, test Tuesday, iterate or scale

• If the user provides a screenshots or videos, use ai-multimodal skill to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description. • If the user provides a URL, use web_fetch tool to fetch the content of the URL and analyze the current issues. • You can use screenshot capture tools along with ai-multimodal skill to capture screenshots of the exact parent container and analyze the current issues with the appropriate Gemini analysis skills (ai-multimodal, gemini-video-understanding, or gemini-document-processing). • Use /scout:ext (preferred) or /scout (fallback) slash command to search the codebase for files needed to complete the task • Use planner agent to create a comprehensive CRO plan following the progressive disclosure structure: • Create a directory plans/{date}-plan-name (date format from $CK_PLAN_DATE_FORMAT). • Save the overview access point at plan.md, keep it generic, under 80 lines, and list each phase with status/progress and links. • For each phase, add phase-XX-phase-name.md files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps). • Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations. • Do not start implementing the CRO plan yet, wait for the user to approve the plan first. IMPORTANT: Sacrifice grammar for the sake of concision when writing reports. IMPORTANT: In reports, list any unresolved questions at the end, if any.