JasonColapietro/suede-creator-skills / skills/suede-site-alchemy
suede-site-alchemy
VerifiedTurn landing, launch, campaign, and product pages into measured conversion paths: funnel stage, friction, hero, proof, CTAs, pricing, mobile QA, and pre-registered experiments. Use when asked to "fix this page that gets no signups" or improve demos and sales from existing traffic. Implements and verifies changes within scope. NOT FOR: SEO scores (use suede-seo-audit), AI citations (use suede-ai-seo), promotion grades (use suede-visibility-grader), or copy alone (use suede-copy).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 20.4 KB |
| agents/openai.yaml | config | 655 B |
| assets/cro-hypothesis-ledger.csv | other | 528 B |
| references/aesthetic-slash-tools.md | markdown | 3.2 KB |
| references/cro-frameworks.md | markdown | 1.2 KB |
| references/evidence-boundary-worked-example.md | markdown | 1.9 KB |
| references/experiment-design.md | markdown | 7.8 KB |
| references/hypothesis-recipes.md | markdown | 1.6 KB |
| references/pricing-and-urgency.md | markdown | 2.5 KB |
| references/worked-handoff.md | markdown | 1.8 KB |
references/pricing-and-urgency.md
View on GitHub# Suede Site Alchemy Skills: Pricing and Urgency
## Pricing Psychology
For pages with pricing, optimize comprehension and informed choice before
persuasion. Verify currency, billing interval, taxes/fees, renewal, usage limits,
cancellation, refund terms, eligibility, and feature truth.
- **Order and emphasis**: anchoring can affect judgments, but it does not prove
a particular plan order will improve qualified conversion or retention. Test
order with revenue quality and cancellation/refund guardrails.
- **Plan architecture**: do not add a decoy or manufacture an "obvious" tier.
Each plan must serve a real segment and remain understandable on its own.
- **Guarantee framing**: display only an approved guarantee and its material
terms. Test placement; do not imply it is universally superior.
- **Gain/loss framing**: treat framing as a hypothesis. Never manufacture loss,
scarcity, or a deadline, and monitor trust and post-purchase outcomes.
- **Trial/freemium**: choose from activation path, marginal cost, abuse risk,
support load, retention evidence, and billing constraints. Measure downstream
activation and retention, not signup rate alone.
## Scarcity and Urgency Framework
Urgency works when it is true. It backfires when the visitor realizes it's manufactured: trust recovers slowly.
**Ethical urgency (use):**
- Real deadlines: event date, price increase date, enrollment close date. State the date explicitly: "Price increases July 1" not "Offer ends soon."
- Real inventory: "4 spots remaining in the June cohort" when the cohort has a verified seat cap.
- Real time-sensitivity: early-access pricing that provably expires, seasonal promotions tied to actual calendar events.
- Behavioral triggers: "You've been looking at this for a while: here's the case study that usually answers the last question."
**Dark patterns (never use):**
- Countdown timers that reset on page refresh.
- "Only 3 left in stock" for digital products.
- "Offer expires tonight" when the offer is permanent.
- Implied scarcity with no mechanism: "limited slots" without a seat cap.
- Urgency language in automated email sequences with no actual deadline.
**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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |