mcpField
P
pricing-page

pricing-page

github.com/nexu-ioDesign & UI105.0k245 installsUpdated 1d ago
Repository

About pricing-page

pricing-page is a design skill for producing single-screen pricing pages that follow an active DESIGN.md. It specifies the page structure and outputs a self-contained HTML document.

Key features

  1. 01Uses active DESIGN.md tokens
  2. 02Selects tiers from the brief
  3. 03Builds plan cards and comparison tables
  4. 04Adds collapsible FAQ items
  5. 05Outputs standalone HTML with inline CSS

Use cases

  1. 01Create a single-screen product pricing page
  2. 02Present subscription tiers within a design system
  3. 03Build a page with plan comparisons and FAQs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nexu-io/open-design --skill pricing-page

After installing, type/pricing-pagein Claude Code to confirm it loaded.

Bundled filesexample.html

Details

From the project README

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.

Comments

Markdown supported