Update to Coder: Websites, Apps & Agents

{
  "description": "Writes and structures a pricing page: plans and tiers, a feature comparison, price anchoring, FAQs and guarantees, for services, SaaS, memberships and packages.",
  "included_files": [],
  "name": "pricing-page",
  "skill_md_contents": "---\nname: pricing-page\ndescription: \"Writes and structures a pricing page: plans and tiers, a feature comparison, price anchoring, FAQs and guarantees, for services, SaaS, memberships and packages.\"\n---\n\n# Pricing Page\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Purpose\n\nWrite and structure a pricing page that makes choosing easy and paying feel safe: clear tiers, an honest comparison, sensible anchoring, FAQs and a guarantee where one exists. Works for service packages, SaaS, memberships, courses and productized offers.\n\n## Before you start\n\n- Gather: what is sold, real prices and currency, billing (one-off, monthly, annual), who buys, what differs between levels, add-ons, and refund or guarantee terms.\n- Ask at most 2 short questions, only if the answer changes the page (usually the actual prices and what each level includes). Otherwise build the structure on stated assumptions, in one line at the top.\n- Never invent prices: mark every figure [confirm] unless the user gave it. The same goes for discounts, limits and guarantees.\n- Reply in the user's language.\n\n## Tier rules\n\n- Default to 3 tiers and highlight the middle one. Label it \"Most popular\" only if that is true; for a new business use \"Recommended\".\n- Name tiers by who they are for: Starter, Growth, Pro or Solo, Team, Business. Metal and gem names (Bronze, Gold) say nothing about fit.\n- Each tier card has: a price with its unit (per month, per project, per session), a one-line \"Best for\", 4 to 7 key inclusions with the most important differentiator first, and a CTA.\n- Higher tiers open with \"Everything in Growth, plus:\" so cards stay short.\n- Annual billing: show the monthly price and the annual option, with the saving worked out from the user's numbers and the math shown. Example: 30 a month or 300 a year is 360 vs 300, so save 60 (about 17%).\n- Custom or quote-based work: show \"Starting at [price]\" or a typical range plus a quote CTA. Never hide every number.\n- CTAs: a verb plus the result or plan (\"Start my free trial\", \"Choose Growth\"); the custom tier gets a softer one (\"Book a call\").\n- On phones the cards stack, so show the highlighted tier first or keep its label visible without long scrolling.\n\n## Anchoring and decoys, in plain terms\n\n- Anchoring: people judge a price against the first figure they see. Let a fuller tier, the cost of the alternative (hiring someone, doing it themselves) or the yearly total set that reference point, so the recommended tier feels reasonable. Use only true comparisons.\n- Decoy: when one option sits close in price to a clearly better one, people pick the better one. Use this honestly: make the step up to the recommended tier small next to what it adds. Never create a tier nobody should buy.\n- Not allowed: invented \"was\" prices, fake discounts, countdown timers on evergreen offers, and fees revealed only at checkout.\n\n## Comparison table rules\n\n- Rows are features grouped by theme; columns are tiers; mark the highlighted tier in its header.\n- Fill cells with words or values (\"Included\", \"5 users\", \"48-hour reply\"), never symbols alone: words are clearer and screen readers announce them.\n- Show the 8 to 15 differences that matter, not every feature.\n\n## Add-ons\n\nList add-ons below the table, never inside the tier cards: name, price [confirm] and one line on who needs it. Keep to 3 to 5. When most buyers take an add-on, bundle it into a higher tier instead.\n\n## Output format\n\n```text\nAssumptions: [one line]\n\nHEADLINE\n[e.g. \"Simple plans that grow with you\"]\n\nINTRO\n[1 to 2 sentences: who the plans are for and one true reassurance]\n\nBILLING TOGGLE (if annual billing)\nMonthly | Yearly (save [X]%) [confirm]\n\nTIER: [Name] [label if highlighted]\nPrice: [amount] per [unit] [confirm]\nBest for: [one line]\nIncludes:\n- [main differentiator]\n- ... (4 to 7 items)\nButton: [CTA]\n(repeat for each tier)\n\nADD-ONS\n- [Name]: [price] [confirm]. [who needs it]\n\nGUARANTEE (only if real)\n[one line]\n```\n\nThen the comparison as a Markdown table (Feature | Starter | Growth | Pro), then 5 FAQs:\n\n1. Refunds: \"Can I get a refund?\"\n2. Switching plans: \"Can I upgrade or downgrade later?\"\n3. What is included: \"What exactly do I get?\"\n4. Contracts: \"Is there a minimum term?\"\n5. Payment methods: \"How can I pay?\"\n\nAnswer each in its first sentence, with [confirm] on any policy the user has not given.\n\n## Quality checks\n\n- 3 tiers (unless the user asked otherwise), named for who they serve, with an honest label on the highlighted one.\n- Every price, saving, limit and guarantee came from the user or is marked [confirm], and the savings math is shown.\n- Each tier has a price, \"Best for\", 4 to 7 inclusions led by the differentiator, and a CTA.\n- The table uses words or values, not symbols alone.\n- No fake \"was\" prices, invented urgency or hidden fees.\n- Custom pricing shows a starting point or range.\n- The 5 FAQs cover refunds, switching, inclusions, contracts and payment methods.\n\n## Next step\n\nOffer faq-page to expand the pricing questions into a full FAQ, or landing-page to build a sales page for the recommended plan.\n"
}