菜单
When the user wants help with pricing, packaging, or monetization — 'pricing tiers,' 'freemium,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'how much should I charge,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan.' For in-app upgrade screens, see paywall-upgrade-cro.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When the user wants to write, rewrite, or improve marketing copy for any page — homepage, landing, pricing, feature, about, or product pages; "headline help," "CTA copy," "value proposition," "tagline," "hero section," "make this more compelling," "conversion copy," or complete Figma-ready full-page copy (see Full-Page Mode below). For email copy, see email-sequence. For popups, see popup-cro. For editing existing copy, see copy-editing.
When the user wants to increase conversions on any marketing page — homepage, landing, pricing, feature, or blog; "CRO," "this page isn't converting," "low conversion rate," "bounce rate," "my landing page sucks" — or just shares a URL asking for feedback. For signup flows, see signup-flow-cro; post-signup activation, onboarding-cro; forms, form-cro; popups, popup-cro.
When the user wants to audit or diagnose SEO issues — "technical SEO," "why am I not ranking," "meta tags review," "my traffic dropped," "Google update hit me," "core web vitals," "crawl errors," "indexing issues," or even a vague "my SEO is bad." For pages at scale, see programmatic-seo. For structured data, see schema-markup. For AI search, see ai-seo.
Coder<->reviewer handoff loop (Claude<->Codex, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
| name | pricing-strategy |
| description | When the user wants help with pricing, packaging, or monetization — 'pricing tiers,' 'freemium,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'how much should I charge,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan.' For in-app upgrade screens, see paywall-upgrade-cro. |
| category | marketing |
| tier | on-demand |
Design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Gather (ask if not provided):
Price on value delivered, not cost to serve: customer's perceived value is the ceiling; next best alternative is the floor for differentiation; your cost to serve is only a baseline, not the basis.
Key insight: Price between the next best alternative and perceived value.
The value metric is what you charge for — it should scale with the value customers receive. Good value metrics align price with value delivered, are easy to understand, scale as the customer grows, and are hard to game.
| Metric | Best For | Example |
|---|---|---|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
Ask: "As a customer uses more of [metric], do they get more value?" Yes → good value metric; no → price doesn't align with value.
Good (Entry): core features, limited usage, low price. Better (Recommended): full features, reasonable limits, anchor price. Best (Premium): everything, advanced features, 2-3x Better price.
Tier differentiation: feature gating (basic vs. advanced), usage limits (same features, different limits), support level (Email → Priority → Dedicated), access (API, SSO, custom branding).
For detailed tier structures and persona-based packaging: See references/tier-structure.md
Four questions that identify the acceptable price range:
Analyze intersections to find the optimal pricing zone.
Show sets of features; ask which is most/least important; results inform tier packaging.
For detailed research methods: See references/research-methods.md
Above the fold: clear tier comparison table, recommended tier highlighted, monthly/annual toggle, primary CTA per tier.
Common elements: feature comparison table, who each tier is for, FAQ, annual discount callout (17-20%), money-back guarantee, customer logos/trust signals.
Psychology: anchoring (show higher-priced option first); decoy effect (middle tier = best value); charm pricing ($49 vs. $50, for value-focused); round pricing ($50 vs. $49, for premium).
