القائمة
Use when reviewing a landing page, homepage, signup page, pricing page, checkout, form, onboarding screen, popup, or paywall for conversion blockers.
التثبيت باستخدام 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 | cro-audit |
| description | Use when reviewing a landing page, homepage, signup page, pricing page, checkout, form, onboarding screen, popup, or paywall for conversion blockers. |
Find the points on a page or flow where visitors lose clarity, trust, interest, or momentum.
Use the provided URL, screenshot, copy, or code. If the surface is live, inspect desktop and mobile when possible.
Capture:
Classify each issue:
Map the page as a decision path:
For each fix, note whether it is reversible. Prefer reversible copy, layout, and proof changes before deep product or pricing changes unless the evidence is strong.
Prioritize by likely impact and effort. Include concrete replacement copy or layout changes when useful.
Avoid pretending all pages need the same pattern. A pricing page, waitlist, checkout, and enterprise demo page have different jobs.
Page friction read:
[one paragraph]
Conversion path:
Visitor intent -> Page promise -> Proof -> Action
Hesitation sequence:
Seeing -> Believing -> Trusting -> Acting
Friction log:
| Step | Problem | Evidence | Fix | Reversible | Impact | Effort |
Highest-leverage changes:
1. [change]
2. [change]
3. [change]
Copy replacements:
- Current: [text]
Replace with: [text]
Test next:
- [experiment or measurement]