Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nexu-io avatar

Pricing Page

  • 249 installs
  • 83.7k repo stars
  • Updated August 5, 2026
  • nexu-io/open-design

pricing-page is a design agent skill that builds conversion-oriented pricing pages with tier comparison, feature matrices, FAQs, and CTAs for developers testing SaaS packaging and willingness to pay.

About

pricing-page is a nexu-io/open-design skill for drafting high-conversion pricing pages before or during packaging experiments. The skill structures tier comparison tables, feature matrices, FAQ sections, and primary CTAs so developers can test how plans are presented and understood. It emphasizes clarity between free, pro, and enterprise tiers and surfaces common objection-handling copy developers often postpone. Reach for pricing-page when you have defined plans but need a polished page layout and comparison copy for a landing site or in-app upgrade screen. Outputs include section outlines, tier labels, feature checklists, and FAQ drafts ready for implementation in React, Next.js, or static site generators.

  • tier comparison
  • feature matrices
  • pricing CTAs
  • plan framing
  • conversion layout

Pricing Page by the numbers

  • 249 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #875 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nexu-io/open-design --skill pricing-page

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs249
repo stars83.7k
Last updatedAugust 5, 2026
Repositorynexu-io/open-design

How do you design a SaaS pricing comparison page?

Design conversion-oriented pricing pages with tier comparison, feature matrices, FAQs, and CTAs to test packaging and willingness to pay.

Who is it for?

Developers validating SaaS packaging who need a structured pricing page with tier comparison and FAQ copy before frontend implementation.

Skip if: Teams still defining unit economics or payment backend integration without settled plan tiers or feature boundaries.

When should I use this skill?

The user asks to design a pricing page, tier comparison table, feature matrix, pricing FAQ, or packaging layout to test willingness to pay.

What you get

Pricing page layout, tier comparison matrix, feature checklist, FAQ section, and CTA copy

  • pricing page outline
  • tier comparison matrix
  • FAQ copy draft

Files

SKILL.mdMarkdownGitHub ↗

Pricing Page Skill

Produce a single-screen pricing page that respects the active DESIGN.md.

Workflow

1. Read the active DESIGN.md (injected above). Use only its colors, type tokens, and component patterns. 2. Classify the product from the brief and pick a tier shape:

  • 3-tier (most common): Free / Pro / Team or Starter / Growth / Enterprise.
  • 4-tier when the brief says "scale" or "enterprise plus".
  • 2-tier when it says "individual / business" or "personal / pro".

3. Sections, in order: 1. Hero — page title (e.g. "Pricing"), one-line subhead, optional monthly/annual toggle. 2. Plan cards — one card per tier. Each card: tier name, price (use the display font + larger scale for the number), 1-line positioning, 4–6 bullet features, primary CTA. Mark the recommended tier with the DS accent border or a small badge. 3. Comparison table — feature rows × tier columns, ✓ / — / value cells. Group features into 2–3 logical sections (Core, Collaboration, Support, Security…). Sticky header. 4. FAQ — 4–6 collapsible Q&A items. Use <details><summary> for the collapse — no JS. 5. Footer CTA — single line + button, accent band sparingly. 4. Write one self-contained HTML document:

  • <!doctype html> through </html>, CSS in one inline <style>.
  • CSS Grid for the plan-card row; CSS Grid for the comparison table.
  • data-od-id on each tier card and each table row.

5. Money rendering: use the display font for the big number, body for the currency and "/mo" — sizes per DESIGN.md scale. 6. Self-check:

  • Prices are plausible for the product (not "$X / month").
  • Accent is on the recommended tier and one CTA only.
  • Comparison table renders cleanly at 1024px and stacks readably below

768px (rotate column headers or scroll-x).

  • No fake feature names — every row reads as something a real product

would actually offer.

Output contract

Emit between <artifact> tags:

<artifact identifier="pricing-slug" type="text/html" title="Pricing — Product Name">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.

Related skills

FAQ

What sections does pricing-page include?

pricing-page designs tier comparison tables, feature matrices, FAQ blocks, and CTAs for conversion-focused pricing screens. The skill targets SaaS packaging tests before full implementation.

When should developers use pricing-page?

pricing-page fits validate-stage packaging work when plan tiers exist but the pricing screen needs structured comparison copy and layout guidance before frontend coding begins.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.