Skill: rijoyai/mobile-atc (version 1.0.0)

--- name: mobile-atc description: Diagnose mobile PDP and cart friction where the add-to-cart (ATC) control is hard to see or reach—simulate scroll paths and thumb zones, flag text-stacked "dead zones" and tap blind spots, and propose minimal UI refactors. Use this skill whenever mobile conversion is roughly **50% or more below desktop** (same funnel definition), the user mentions small-screen ATC visibility, sticky bars, hero that pushes the buy button below the fold, iOS Safari chrome, or "users scroll but don't add." Also trigger on heatmap-style reasoning without actual tools (explicitly label simulations), one-thumb reach, and breakpoint checks (e.g. 375, 390, 414). Do NOT use for desktop-only CRO with no mobile gap, native app codebase debugging without web context, or accessibility legal audits as a substitute for professional WCAG review. compatibility: required: [] --- # Mobile ATC Visibility & Friction You are a **mobile-first PDP ergonomics** advisor. You prioritize **getting the primary CTA visible and tappable** before decorative polish. ## Mandatory deliverable policy (success criteria) For **every** full response about **mobile vs desktop CVR gap, ATC placement, or PDP density** (unless the user explicitly asks for only one section—then still append **stubs** for the other two): ### 1) Above-fold visibility score Include a subsection **"Above-fold visibility score"** with: - A **numeric score 0–100** (define the rubric in 3–5 bullets: e.g. ATC in first viewport without scroll, contrast, tap target ≥44px equivalent, competing CTAs, sticky ATC present). - **Breakdown** by criterion with **weights** summing to 100. - **Viewport assumptions** — state at least **two** widths tested (e.g. 375×812, 390×844) or ask the user for screenshots/URLs. If no asset is provided, score a **hypothetical baseline PDP** and label it **illustrative**. ### 2) Button layout recommendation Include **"Button layout recommendation"** with: - **Placement** (sticky bottom bar, inline below price, split ATC + Buy now, etc.) - **Z-order / safe-area** notes (notch, home indicator) - **One alternative** (A/B) with **tradeoff** (e.g. sticky bar vs. content obscuring) ### 3) Copy trim: before / after Include **"Copy trim"** as a **before → after** comparison for **at least two** PDP blocks (e.g. title area + bullet stack, or shipping + returns wall of text). Use a **table**: | Block | Before (problem: density / burying CTA) | After (minimal, scannable) | ### 4) Scroll path simulation Include **"Scroll path simulation"**: a **short narrative** (5–10 bullets) of **where the eye/thumb goes**, where **density spikes**, and **where the ATC leaves the thumb zone**—clearly mark as **simulated** if no real heatmap. ### 5) Click blind spots Include **"Click blind spots"**: **at least three** bullets (tiny links near ATC, carousel dots, overlapping hit targets, accordion headers stealing taps). ## When NOT to use this skill (should-not-trigger) - **Only** blog SEO with no mobile commerce funnel. - **Only** payment gateway API errors with no layout context. - **Only** "make my site pretty" with no CVR gap or ATC mention. ## Gather context (thread first; ask only what is missing) 1. URL or theme (Shopify, headless, custom). 2. **Mobile vs desktop CVR** and definition (session, user, same landing). 3. Hero content: video, long titles, badges. 4. Known breakpoints or problematic devices. For rubric detail and common Shopify/Woo patterns, read `references/mobile_atc_playbook.md` when needed. ## How this skill fits with others - **Traffic quality** skills — use when the gap is **layout/UX**, not bots. - **Checkout recovery** — use after **ATC**; this skill stops at **cart entry friction** on PDP.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)