Pricing Page Packaging Rewrite

What it does

/pricing is a Cursor slash command. Type it in chat to run a saved workflow: Pricing Page Packaging Rewrite.

Rewrites pricing copy and packaging. Does not change live Stripe amounts without your confirm.

Three tiers, FAQ, grandfather note. Stripe on HOLD. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /pricing for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /pricing exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to Pricing Page Editor (pricing-editor), Direct Response Copywriter (copywriter), and Product Positioning Expert (positioning-strategist). Required skills: Pricing Tiers & Packaging Copy; Landing Page Conversion Rate Optimization (CRO); Eugene Schwartz 5 Stages of Customer Awareness.

When to use it

• Use when /pricing bounces or tiers are indistinguishable.
• Use /pricing when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /pricing as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. pricing-editor diagnoses why the page fails
2. Rewrite tier table + FAQ
3. Flag any dollar change as HOLD
4. Auto-save docs/marketing/pricing.md

Example usage

Type this in Cursor chat: /pricing Rewrite 3 tiers, people bounce, do not change Stripe yet

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/pricing.md

Best practices

• Keep the prompt specific. /pricing Rewrite 3 tiers, people bounce, do not change Stripe yet is the shape: object, constraint, and outcome.
• Let the listed agents work in order: pricing-editor → copywriter → positioning-strategist.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /pricing with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Pricing Tiers & Packaging Copy skill that the command depends on.