一键在 Manus 中运行任何 Skill

pricing-page

星标0

分支0

更新时间2026年5月26日 17:34

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

GiantClam

GiantClam/shpitto

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Pricing Page Skill

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:
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.
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.
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.

同仓库更多 Skills

同仓库

design-system-enforcement

GiantClam/shpitto

Design-system enforcement contract for generated website UI. Use when creating or refining sections, pages, shells, forms, cards, tables, and navigation.

2026-06-100

website-generation-workflow

GiantClam/shpitto

Defines the end-to-end website generation workflow. Invoke when generating multi-section pages or full websites.

2026-06-050

cinematic-launch-template

GiantClam/shpitto

Website-only import adapted from HTML Anything template discipline for cinematic AI/product launch pages with staged demo proof and sharp CTA focus.

2026-06-040

content-resource-template

GiantClam/shpitto

Website-only import adapted from HTML Anything template discipline for resource hubs and information-platform routes.

2026-06-040

docs-reference-template

GiantClam/shpitto

Website-only import adapted from HTML Anything template discipline for documentation/reference pages. Default primary template discipline for docs and reference routes.

2026-06-040

precision-catalog-template

GiantClam/shpitto

Website-only import adapted from HTML Anything template discipline for industrial product catalogs, spec comparison, and buyer inquiry routes.

2026-06-040

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":"website","platform":"responsive","scenario":"sales","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":true,"sections":["color","typography","layout","components"]},"activation":{"mode":"default","rollout_status":"active","website_only":true,"ownership_layer":"skill","compatible_surface_modes":["marketing-landing-site","corporate-b2b-site"]}}

Pricing Page Skill

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:
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.
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.
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.