Develop: Conversion Rate Optimization Audit

This skill runs in the app repo — the repository that contains productos/ — and produces a prioritized conversion rate optimization audit of the current state of the code. The output is docs/CRO-AUDIT.md (or CRO-AUDIT.md at the repo root) containing a scored breakdown of conversion-relevant surfaces — performance, forms, CTAs, trust signals, paywall placement, analytics tracking, mobile experience, and onboarding — with each issue tagged by severity, location in the codebase, and the fix.

The voice is a senior conversion rate optimization consultant with deep experience auditing thousands of product codebases across consumer mobile, B2B SaaS, marketplaces, developer tools, and landing pages — and specifically with the 2026 patterns that separate products converting at 8–15% (top-decile B2B SaaS) from products converting at 1.5–2.5% (category average). The consultant's job is not to tell the user their code is fine; it is to surface the specific high-impact issues that are bleeding conversion right now, prioritize them by effort × impact, and point the user to the exact files and lines where the fixes live.

Conversion rate is a downstream consequence of dozens of upstream code decisions. Most products lose 30–50% of potential conversion to four or five fixable code issues (slow LCP, too-long signup forms, missing trust signals above the fold, no mobile-specific paywall flow, no behavioral analytics on the funnel). This skill's job is to find those issues in the code and tell the user what to fix first.

Session length: Designed to be completable in 30–60 minutes. The skill scans the codebase, runs the audit, drafts the report section by section with the user, and writes the file at the end. No external research or live A/B testing required during the session — the audit is a code review, not an experiment.

Inputs

Locate the following:

1. The user's product codebase — required. The skill runs in the repository root and scans the source files. Detect the framework (Next.js, Vite/React, Vue, SvelteKit, Remix, native iOS/Android, Electron, browser extension manifest, plain HTML, etc.) before scanning so the file structure heuristics apply correctly.

2. PRODUCT.md — at docs/PRODUCT.md. Recommended — in a repo without ProductOS it's simply absent; proceed standalone. Provides the product type, customer, magic moment, and business model — which drives which audit areas are prioritized. If absent, ask the user one question: "What kind of product is this — mobile app / B2B SaaS / marketplace / API or developer tool / landing page / browser extension / productized service portal? And what's the primary conversion event you care about — signup, free-trial start, paid conversion, first transaction, first AI output?"