メニュー
Use when improving ecommerce product pages, collection pages, carts, checkout, subscriptions, app store listings, screenshots, reviews, or mobile conversion surfaces.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.
Use when planning a product launch, feature release, waitlist, beta, public announcement, relaunch, Product Hunt-style push, repeated feature launch system, launch-week checklist, or multi-channel GTM rollout.
Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or landing page copy.
Use when turning a marketing, growth, CRO, pricing, onboarding, email, ad, or acquisition idea into a useful experiment or test plan.
Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.
Use when auditing, planning, or debugging marketing measurement, conversion tracking, GA4, GTM, UTMs, pixels, CRM attribution, funnel reporting, or dashboard trust.
| name | ecommerce-app-cro |
| description | Use when improving ecommerce product pages, collection pages, carts, checkout, subscriptions, app store listings, screenshots, reviews, or mobile conversion surfaces. |
Improve product pages, carts, app listings, screenshots, paywalls, and checkout surfaces where users are close to buying or installing.
Classify the request:
Gather the URL, screenshots, product details, traffic source, current conversion rate if known, price, reviews, and return or cancellation concerns.
Each surface must answer a different question:
Classify the blocker:
Look for gaps in proof, comparison, sizing, benefit clarity, social proof, risk reversal, visual explanation, shipping or billing transparency, and mobile usability.
Use channel-native fixes:
Conversion surface:
[surface and goal]
Buyer question:
[what must be answered]
Friction points:
| Blocker | Problem | Evidence | Fix |
Asset changes:
- Image/screenshot:
- Copy:
- Proof:
- Offer:
- UX:
Priority fixes:
1. [fix]
2. [fix]
3. [fix]
Test idea:
[what to test and how to judge it]