Pricing Page Skill
SkillMediaA skill that guides an AI agent to build a pricing page as a single HTML file. Given a brief about pricing, plans, or subscription tiers, it picks a tier structure and writes the hero, plan cards, feature comparison table, FAQ, and footer CTA, laying the page out with CSS Grid and following the project's DESIGN.md style guide.
Use Pricing Page Skill in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Pricing Page Skill and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Pricing Page Skill skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Install the pricing-page skill so the agent can load it.
What your AI can do with it
- Generates a single-file HTML pricing page from a brief
- Picks a plan tier structure based on the brief
- Writes a hero section and plan cards for each tier
- Builds a feature comparison table across plans
- Adds a pricing FAQ section and a footer CTA
- Follows the project's DESIGN.md style guide
Getting started
- Install the pricing-page skill so the agent can load it.
- Put a DESIGN.md style guide in the project, since the skill uses it for the page's look.
- Write a brief describing the page; mentioning pricing, plans, subscription tiers, or comparing plans signals this skill.
- Ask the agent to build the page, then review the HTML file it produces.
What this skill tells your AI
The instructions your AI receives, as published by nexu-io/open-design in design-templates/pricing-page/SKILL.md and read by ahel’s review.
Produce a single-screen pricing page that respects the active DESIGN.md.
Workflow
- Read the active DESIGN.md (injected above). Use only its colors, type tokens, and component patterns.
- 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".
- Sections, in order:
- Hero — page title (e.g. "Pricing"), one-line subhead, optional monthly/annual toggle.
- 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.
- Comparison table — feature rows × tier columns, ✓ / — / value cells. Group features into 2–3 logical sections (Core, Collaboration, Support, Security…). Sticky header.
- FAQ — 4–6 collapsible Q&A items. Use
<details><summary>for the collapse — no JS. - Footer CTA — single line + button, accent band sparingly.
- 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-idon each tier card and each table row.
- Money rendering: use the display font for the big number, body for the currency and "/mo" — sizes per DESIGN.md scale.
- 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.
Signals
- GitHub stars
- 99k
- Forks
- 11k
- Last commit
- Oct 2026
Questions
- When should this skill be used?
- When the brief asks for a pricing, plans, subscription tiers, or compare plans page.
- What does the agent produce?
- A single-file HTML pricing page containing a hero, plan cards for the tiers, a feature comparison table, an FAQ section, and a footer CTA.
- How does it decide how many plan tiers to show?
- It picks a tier structure based on the brief given for the page.
- Can it match an existing design system?
- It follows the project's DESIGN.md style guide when writing the page.
- What layout technique does it use?
- The page is laid out with CSS Grid.
Advanced
- Item type
- skill
- Key
pricing-page-2- Source
- github.com/nexu-io/open-design