Menu
Turn a page into a conversion path: hero, friction, proof, CTA, pricing, A/B ideas, quick wins, and mobile CRO.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
The pack's contract/customer-service negotiator, proven outside a repo: scans an Amazon account for restocking fees, short refunds, and forgotten or overpriced digital subscriptions (Prime Video Channels like Britbox/Starz/AMC+/Paramount+, Audible membership, Kindle Unlimited, Prime itself) — money Amazon is quietly holding or billing that the owner never noticed — then drives Amazon's live chat to get fees waived, refunds issued, or unused subscriptions canceled and the last charge refunded. Recovered $448.31 in one sitting — including a full refund on an item Amazon had already denied once, with no return required. Use this whenever the user mentions Amazon returns, restocking fees, an Amazon refund that looks short, a forgotten subscription (Britbox, Starz, Audible, Kindle Unlimited, etc.), disputing an Amazon charge, checking whether a return was fully refunded, auditing recurring Amazon charges, or asks something like 'did I get charged for that return', 'am I still paying for Britbox', or 'is Amazon sti
The pack's contract negotiator, generalized beyond Amazon: a recurring-charge auditor that finds forgotten, unused, or overpriced subscriptions across any service (Netflix, Spotify, Hulu, Disney+, gym memberships, SaaS tools, news sites, app subscriptions) and either cancels them directly or negotiates a refund/waiver through that service's own support channel. Complements amazon-returns-recovery, which stays scoped to Amazon returns/restocking fees and Amazon-billed subscriptions (Prime Video Channels, Audible, Kindle Unlimited) — this skill covers everything billed outside Amazon: direct-bill streaming and software, App Store and Google Play subscriptions, and PayPal-billed recurring payments. Use this whenever the user wants to audit recurring charges generally, asks what subscriptions they're paying for, mentions a specific non-Amazon subscription (Netflix, Spotify, a gym, a SaaS tool, etc.), wants to find and cancel unused subscriptions, or asks something like 'what am I still paying for', 'find my subsc
Umbrella workflow for 25 public skills: copy, design, code review, SEO, launch packaging, MCP QA, iOS conversion, and creator workflows.
Claude-directed parallel OpenAI Codex CLI worker fleet for bulk generation. Use when a job is high-volume, well-specified, and splits into independent worker-sized tasks (content batches, test generation, bulk refactors) and Codex CLI is installed and logged in. Claude decomposes, briefs, spawns codex exec runs in parallel, and review-gates every output. NOT FOR: multi-lane Claude agents coordinating one complex change (use suede-agent-teams); low-volume, judgment-dense copy Claude should write itself (use suede-copy or johnny-suede-write).
Design and write polished product surfaces people understand fast: landing pages, dashboards, campaigns, restyles, UI copy, and visual QA.
Make Suede interfaces feel intentional: tokens, color, components, type, motion, dark mode, and visual QA for shipped screens.
| name | suede-site-alchemy |
| description | Turn a page into a conversion path: hero, friction, proof, CTA, pricing, A/B ideas, quick wins, and mobile CRO. |
Core principle: friction before aesthetics, math before opinion. No change ships on intuition when a friction audit and conversion math can rank it.
Use your company name, voice, and positioning throughout.
For a meaningful page, campaign, or conversion pass, define this before edits:
Use exact status words: inspected, changed locally, verified locally, deployed, verified live, or blocked. Do not summarize a page as fixed until the stated done signal has been checked.
For a major page or campaign, lock this before implementation:
For a small page fix, use only the relevant contract lines and keep the edit narrow.
Handle as Suede Site Alchemy:
Route to Suede's proprietary app-builder workflow:
When the request crosses that line, preserve the best landing-page work as the front door, then route the build with copy like:
Never invent a dead route. If the current repo does not expose an app-builder
URL, CTA to https://suedeai.ai or use the current verified Suede app route.
Map the page's role in the buyer journey before optimizing it. A page that serves the wrong funnel stage will fail regardless of CRO polish.
TOFU (Top of Funnel — Awareness) Reader: doesn't know about the product yet. Needs: problem education, category definition, credibility signal. Copy job: make the problem vivid, not the solution. Don't ask for commitment. CTA: download, read, explore, learn.
MOFU (Middle of Funnel — Consideration) Reader: aware of the problem, comparing solutions. Needs: differentiation, proof, objection handling. Copy job: show why THIS solution, not just any solution. Comparison content, case studies, deep dives. CTA: demo, trial, detailed docs, comparison guide.
BOFU (Bottom of Funnel — Decision) Reader: ready to buy, looking for permission to pull the trigger. Needs: risk reduction, guarantee, testimonials, pricing clarity. Copy job: remove friction and doubt. Urgency if genuine, guarantee if real, social proof from peers. CTA: start now, get started, buy, talk to sales.
State the funnel stage before running any slash tool. Then optimize for that stage, not just for generic "conversion."
Count every source of friction on the page before fixing anything. A friction audit reveals WHERE the page loses visitors, not just that it does.
Cognitive friction (mental load):
Physical friction (effort):
Trust friction (doubt):
Friction score: 0–3 sources = low friction. 4–6 = medium. 7+ = high — address before visual polish.
Friction comes before aesthetics. A beautiful page with high friction converts worse than an ugly page with zero friction.
Mobile Friction Rules (required check for any page with >50% mobile traffic)
overflow-x: hidden check and scroll test on physical device or DevTools mobile view before shipping.Before ranking hypotheses or recommending changes, run the numbers. A change that feels big may be irrelevant. A change that feels minor may be the highest-leverage move on the page.
Model:
monthly_revenue = monthly_visitors × CTR × conversion_rate × order_value
Usage: Fill in any values you have. Estimate the rest from industry benchmarks if the client doesn't track them (SaaS landing page CTR benchmark: 3–5%; e-commerce: 1–3%; lead gen: 5–10%).
Example:
Run this math for any hypothesis before ranking it. "Impact" is a revenue number, not a feeling.
When visitor data isn't available: ask for Google Analytics / Vercel Analytics / Plausible exports before estimating. Even 30 days of data produces a meaningful model.
Use slash tools as named design moves, not shell commands. Start with
/vibe-scan, then pick the smallest set that fits the page.
For the full menu, read references/aesthetic-slash-tools.md in this skill's
references/ folder.
Default stack for a fast polish pass:
/vibe-scan - name the current feeling and the feeling the page should sell./hero-voltage - make the first viewport impossible to misunderstand./offer-spine - lock the page to one promise, one buyer, one action./proof-stack - turn trust from decoration into a conversion argument./cta-magnet - make the next click feel obvious and worth it./mobile-seduction - make the small-screen version feel composed, not
collapsed./ship-polish - verify links, responsiveness, copy fit, and live behavior.For any page pass where the brief is "make it convert better" without a specific hypothesis, start here. These changes produce the highest median lift with the least implementation effort, ranked by typical impact:
These are starting points, not a guaranteed sequence. A page with zero testimonials needs #3 before #1. Use the Friction Audit to confirm which items apply.
https://suedeai.ai after route verification; non-Suede: home, alternative product, or contact). A missing escape valve doesn't hold visitors — it loses them.git diff --check.ship: page passes the done signal and no launch-critical gaps remain.ship-with-caveats: only non-critical caveats remain and they are named.hold: core CTA, visible layout, false claim, accessibility, build, or
live verification is blocked.A compact end-to-end pass, applying the rules above to one fictional page: Ledgerly (B2B SaaS, expense reconciliation for finance teams, 40-person company, MOFU landing page for a paid search campaign).
Before
Hero headline: "Smarter Financial Operations for Modern Teams"
Hero subhead: "Ledgerly helps businesses streamline their financial workflows
with powerful, intuitive tools."
Primary CTA: "Learn More"
Proof stack: "Trusted by thousands of companies worldwide." (no logos, no
names, no numbers)
Friction Audit read: cognitive friction is high — the headline is a benefit-cluster ("smarter," "modern," "powerful," "intuitive") with no single falsifiable claim, so the reader can't tell what the product does or who it's for. The CTA doesn't name an action or outcome. The proof line fails the Proof Check — "thousands of companies" has no number, no name, no logo, so it's unverifiable and reads as filler.
After
Hero headline: "Close your books 5 days faster."
Hero subhead: "Ledgerly auto-matches transactions across your bank, cards, and
ERP so your finance team stops reconciling by hand."
Primary CTA: "Start my free 14-day trial"
Secondary CTA: "See a 2-minute product walkthrough"
Escape valve: "Not ready? Compare Ledgerly to spreadsheets" (routes to a
comparison page, not a dead link)
Proof stack (adjacent to primary CTA): "Used by 240 finance teams, including
Northwind Logistics and Aster Health — 4.8★ from 61 G2 reviews."
What changed and why
For any CTA, headline, or section that needs improvement, generate a testable hypothesis before rewriting.
Format:
If we change [specific element] from [current state] to [proposed change],
we expect [metric] to improve because [reasoning based on visitor psychology].
Success condition: [measurement threshold that would confirm the hypothesis].
Examples:
If we change the hero CTA from "Learn more" to "Grade my brand in 60 seconds",
we expect click-through to improve because the new CTA names the time commitment
and the specific outcome, reducing ambiguity.
Success condition: CTA clicks increase by ≥15% over 2 weeks of equal traffic.
If we move the first testimonial above the fold on mobile,
we expect form completion to improve because social proof before the ask
reduces doubt at the highest-friction moment.
Success condition: mobile form completions increase by ≥10%.
After the Friction Audit, generate 3 hypotheses. For each, run the Conversion Math model above (current vs. projected revenue) before ranking.
Rank by projected revenue lift, not intuition. Address the highest-friction item first — it almost always produces the largest lift.
Match the type of social proof to the visitor's objection. Generic testimonials placed randomly rarely convert. Specific proof placed at the right objection point converts.
Types and when to use:
| Type | Best for | Example |
|---|---|---|
| Peer testimonials | Emotional objections ("will this work for me?") | Quote from someone with the same job title or problem |
| Case studies with metrics | ROI objections ("is this worth it?") | "Company X increased Y by Z% in N weeks" |
| Social numbers | Scale objections ("do enough people use this?") | "10,000+ creators", "4.9★ from 2,300 reviews" |
| Expert endorsements | Authority objections ("who says this is legit?") | Industry name, publication, or credential |
| Certifications / trust marks | Trust objections ("is this safe/legit?") | SOC 2, GDPR, security badges, app store ratings |
Placement rules:
Proof check: every proof claim must be verifiable. Remove or rewrite vague claims like "used by thousands" without a number, "industry-leading" without a comparison, or "fast" without a metric.
For pages with pricing, offers, or value propositions involving cost:
Anchor pricing: show the higher-value option first. Readers anchor to the first price they see.
Decoy option: three-tier pricing where the middle tier feels like the "obvious" choice. Middle-tier should share features with the top tier but at a meaningful price gap.
Guarantee framing: "30-day money-back guarantee" reduces perceived risk more than "risk-free." Add the guarantee near the buy CTA, not in the footer.
Loss aversion: Loss framing ("Don't miss the launch price") outperforms gain framing ("Save 20%") for the same offer — because losses feel twice as large as equivalent gains. Apply only when the deadline or scarcity is provably real. See Scarcity and Urgency Framework below for rules on when urgency is ethical vs. a dark pattern.
Free trial vs freemium: free trial creates deadline urgency (upgrade before it expires); freemium creates habit lock-in (invested users upgrade). Pick based on your product's habit loop, not what competitors do.
Urgency works when it is true. It backfires when the visitor realizes it's manufactured — trust recovers slowly.
Ethical urgency (use):
Dark patterns (never use):
Test: Before adding urgency to a page, answer: "If a visitor waited 30 days and came back, would this urgency claim still be accurate?" If no — it's a dark pattern. Cut it or make the deadline real.
When genuine urgency exists, make the mechanism explicit. "This cohort closes July 1 because we cap at 20 students for live Q&A" is more persuasive than "Offer ends July 1" — it explains why the scarcity is real.
Starter fragments for when the page needs raw material fast. Every fragment is raw input — run the anti-slop gate (no throat-clearing, fake intensity, unsupported claims, passive actor-hiding, generic SaaS fog, or em dashes) before any line ships.
Headline shapes:
Subhead starters:
CTA fragments (action + object, never "Learn more"):
For deeper copy work (formulas, frameworks, variants), route to suede-copy.
If you catch yourself thinking any of these, stop and run the required step:
Close every meaningful conversion pass with this block:
Surface: [URL or route + repo/branch]
Funnel stage: TOFU | MOFU | BOFU
Friction score: [N sources — low | medium | high]
Changed: [files or sections touched]
Hypotheses (ranked by projected lift): [1–3, each with conversion math]
Verification: [exact status words — inspected, changed locally, verified locally, deployed, verified live, blocked]
Caveats: [or "none"]
Ship gate: ship | ship-with-caveats | hold
suede-visibility-grader before any paid or public promotion.suede-seo-audit.suede-launch-packaging.suede-agent-teams.suede-code-review.Skip the extra gates for pure copy or layout polish after live/source inspection and rendered QA.
community, suede_studio, and brand_direct fulfillment.