Menu

Individual skill

ux-pricing

0upvotes

Design or critique a pricing page. Applies the always-true core (plan ordering, CTA clarity, ethics guardrail) and gates context-dependent levers (freemium, usage sliders, live chat, PPP pricing, charm vs. round numbers) with trade-offs. Trigger when designing pricing tiers, plan tables, monetization screens, or when a pricing page isn't converting.

ux/screens/pricing/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Pricing Page Skill


## How this skill behaves (read first)

This is a **generative** skill, and pricing is the textbook case for **gating** rather than applying every best practice. The lessons offer many ways to make a pricing page stand out — badges, per-tier graphics, interactive sliders, charm pricing, anchoring, social proof. Apply them all at once and you get an overdesigned, cluttered, psychologically overwhelming page that *hurts* conversion and trust. So:

1. **Establish context** (Step 0) — pricing decisions hinge on it more than almost any other screen.
2. **Apply the always-true core** — the patterns correct for essentially every pricing page.
3. **Surface the context-dependent decisions** as a *menu* — present each with its trade-off and a recommendation, and let the user pick the few that fit. Stacking many of them is the failure mode.

Then **hand the result to the audit skills** to validate it didn't tip into clutter or dark patterns.

Scope & composition (per `docs/orchestration-policy.md` §9): this skill owns the **pricing page itself** and composes lower-scope skills rather than re-deriving them. **Core children (built as part of the page):** `ux-cards` (tier-card mechanics — shadows, padding, clickable card) and `ux-buttons` (the CTAs). **Downstream (offer, don't auto-build):** the post-click `ux-checkout-payment`. **Inherit, don't regenerate:** under an existing design system, take color/type/spacing from its tokens — only set those when designing from scratch.
Back to top