Pricing Page Editor

What it does

Pricing Page Editor is a Cursor agent playbook named pricing-editor. AgenticKit installs it so a session can adopt this role instead of acting as a generic coding assistant.

The pricing-editor agent fixes packaging and copy. positioning-strategist sets category. This role rewrites good/better/best, grandfather notes, and objections. It will not edit Stripe products unless you confirm the numbers.

Rewrites three tiers. Does not silently change Stripe. Diagnoses a bouncing pricing page and rewrites names, limits, FAQs. Dollar amounts stay on HOLD until you confirm.

Why it exists

A pile of agent files is not a team. pricing-editor exists so one job, pricing page editor, has a written brief, required skills, and a stop condition.

It ships in the Marketing Kit. Skills it must read: Pricing Tiers & Packaging Copy; Eugene Schwartz 5 Stages of Customer Awareness; Landing Page Conversion Rate Optimization (CRO). Commands that adopt this role: /pricing: Pricing Page Packaging Rewrite; /landing-page: High-Converting Landing Page Copy Architect; /landing-fix: Landing Page CRO Audit & Copy Optimizer.

When to use it

• People bounce on /pricing
• Tiers nobody can tell apart
• Need packaging copy before touching Stripe

When not to use it

• Do not ask pricing-editor to do a different role's job. If you need a migration, switch agents.
• Do not keep the same chat after this agent has finished its artifact. Start a reviewer in a new thread.
• Do not invoke every agent in the kit for a small change.

Example workflow

1. Install the Marketing Kit so .cursor/agents/pricing-editor is on disk.
2. Run /pricing: Pricing Page Packaging Rewrite, or start a chat and tell Cursor to adopt the pricing-editor role.
3. The agent should read: Pricing Tiers & Packaging Copy; Eugene Schwartz 5 Stages of Customer Awareness; Landing Page Conversion Rate Optimization (CRO).
4. It produces the artifact for this role only, then stops.
5. A different agent or you review. Same-chat self-review is not a review.

Example usage

Example: "You are pricing-editor. People bounce on /pricing. Read pricing-packaging before you edit."

Or let the pipeline invoke it: /pricing: Pricing Page Packaging Rewrite.

Capabilities you should actually see: Tier table: who it's for, limits, CTA

Example output

• pricing-editor should leave files or a written verdict, not a vibe check. Tier table: who it's for, limits, CTA Pricing FAQ and objection answers
• Marketing agents write markdown under docs/marketing/ so later commands can reuse positioning and voice.

Best practices

• Tier table: who it's for, limits, CTA
• Pricing FAQ and objection answers
• Grandfathering notes for existing customers
• HOLD on live price changes
• One role per chat unless a command is explicitly orchestrating a sequence.

Common mistakes

• Using pricing-editor as a synonym for 'the Cursor agent'. It is a brief, not the product.
• Skipping the required skills and hoping the role name is enough.
• Publishing the first draft of launch copy without a human edit.
• Invoking this agent and three unrelated ones in the same prompt.