High-Converting Landing Page Copy Architect

What it does

/landing-page is a Cursor slash command. Type it in chat to run a saved workflow: High-Converting Landing Page Copy Architect.

Drafts complete landing page copywriting: hero headline/subheadline, feature-benefit blocks, social proof sections, FAQ objection crushers, and CTAs.

Hero copy, benefit sections, objection handling, pricing tables, and CTAs. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /landing-page for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /landing-page 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 the Direct Response Copywriter (copywriter) and Growth Marketing Lead (growth-strategist) agents. Required skills: Landing Page Conversion Rate Optimization (CRO); Marketing Psychology & Direct Response Principles; Eugene Schwartz 5 Stages of Customer Awareness.

When to use it

• Use when building or redesigning your product's main marketing page.
• Use /landing-page 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 /landing-page 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. Write high-converting hero headline and value proposition subheadline
2. Draft 4 core benefit blocks with concrete metrics and proof
3. Create interactive FAQ addressing top customer buying objections
4. Auto-save landing copy to docs/marketing/landing-page-copy.md

Example usage

Type this in Cursor chat: /landing-page Draft hero section, feature bullets, and pricing table copy for B2B SaaS

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/landing-page-copy.md

Best practices

• Keep the prompt specific. /landing-page Draft hero section, feature bullets, and pricing table copy for B2B SaaS is the shape: object, constraint, and outcome.
• Let the listed agents work in order: copywriter → growth-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 /landing-page 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 Landing Page Conversion Rate Optimization (CRO) skill that the command depends on.