pricing-page · nexu-io — Claude Code skill: generates pricing tiers page
pricing-page — a skill for Claude Code, Codex, Cursor and other AI code editors that generates a single-page pricing layout with tiers, feature comparison table, and FAQ. Triggers on requests like “pricing”, “plans”, or “compare plans”.
Apache-2.0 246 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill pricing-page -a claude-codeWhat pricing-page does
Produces a ready-to-use HTML file with hero, tier cards, feature matrix, and collapsible questions. Supports Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
The skill reads your brief and chooses tier structure: two-tier (personal / pro), three-tier (most common: Starter / Growth / Enterprise), or four-tier for scale. It applies colors, typefaces, and components from your DESIGN.md and layouts the table with CSS Grid so it scrolls cleanly below 768px. Output is one HTML file: inline styles in <style>, collapsible Q&As use native <details> elements, no dependencies.
Prices and feature names must be realistic for the product — the skill validates this during generation.
What it helps with
- Build a pricing page with tier cards and feature comparison
- Match pricing design to an existing design system
- Generate self-contained HTML pricing without frameworks
- Add interactive plan switching with monthly / annual billing
Example prompts for the agent
- Generate a pricing page with three tiers: Starter, Professional, and Enterprise
- Create a pricing layout with monthly and annual toggles, highlight the Pro plan
- Build a feature comparison table for a SaaS with three subscription tiers
How to install pricing-page
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pricing-page -a claude-code2Manually: put the files in place
~/.claude/skills/pricing-page/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pricing-page/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pricing-page -a codex2Manually: put the files in place
.agents/skills/pricing-page/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pricing-page -a cursor2Manually: put the files in place
.cursor/skills/pricing-page/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/pricing-page/SKILL.md2Manually: put the files in place
.github/skills/pricing-page/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pricing-page -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/pricing-pageManually: put the files in place
.devin/skills/pricing-page/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pricing-page -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pricing-page
How do I install pricing-page in Claude Code?
Run npx skills add nexu-io/open-design --skill pricing-page -a claude-code, then read ~/.claude/skills/pricing-page/SKILL.md.
What does the pricing-page skill output?
A single HTML document with hero, pricing tiers, comparison matrix, and FAQ. Styles are inline, no external dependencies.
Can it use my design system?
Yes. The skill reads DESIGN.md and applies your colors, typography, and components. Your design system must define color, type tokens, layout rules, and component patterns.
Source text
SKILL.md · Apache-2.0
---
name: pricing-page
description: |
A standalone pricing page — header, plan tiers, feature comparison table,
and an FAQ. Use when the brief asks for "pricing", "plans",
"subscription tiers", or a "compare plans" page.
triggers:
- "pricing"
- "pricing page"
- "plans"
- "subscription"
- "compare plans"
- "定价"
- "套餐"
od:
mode: prototype
platform: desktop
scenario: sales
preview:
type: html
entry: index.html
design_system:
requires: true
sections: [color, typography, layout, components]
craft:
requires: [laws-of-ux]
---
# 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.
© nexu-io · Apache-2.0 · nexu-io/open-design
Similar skills
All skills for Frontend and UI →pricing-page by other authors comes first.