Copywriting

1️⃣ Page Purpose

• Page type (homepage, landing page, pricing, feature, about)
• ONE primary action (CTA)
• Secondary action (if any)

2️⃣ Audience

• Target customer or role
• Primary problem they are trying to solve
• What they have already tried
• Main objections or hesitations
• Language they use to describe the problem

3️⃣ Product / Offer

• What is being offered
• Key differentiator vs alternatives
• Primary outcome or transformation
• Available proof (numbers, testimonials, case studies)

4️⃣ Context

• Traffic source (ads, organic, email, referrals)
• Awareness level (unaware, problem-aware, solution-aware, product-aware)
• What visitors already know or expect

Phase 2 — Copy Brief Lock (Hard Gate)

Before writing any copy, you MUST present a Copy Brief Summary and pause.

Copy Brief Summary

Summarize in 4–6 bullets:

• Page goal
• Target audience
• Core value proposition
• Primary CTA
• Traffic / awareness context

Assumptions

List any assumptions explicitly (e.g. awareness level, urgency, sophistication).

Then ask:

“Does this copy brief accurately reflect what we’re trying to achieve? Please confirm or correct anything before I write copy.”

Do NOT proceed until confirmation is given.

Phase 3 — Copywriting Principles

Core Principles (Non-Negotiable)

• Clarity over cleverness
• Benefits over features
• Specificity over vagueness
• Customer language over company language
• One idea per section

Always connect:

Feature → Benefit → Outcome

Writing Style Rules

Style Guidelines

• Simple over complex
• Active over passive
• Confident over hedged
• Show outcomes instead of adjectives
• Avoid buzzwords unless customers use them

Claim Discipline

• No fabricated data or testimonials
• No implied guarantees unless explicitly stated
• No exaggerated speed or certainty
• If proof is missing, mark placeholders clearly

Phase 4 — Page Structure Framework

Above the Fold

Headline

• Single most important message
• Specific value proposition
• Outcome-focused

Subheadline

• Adds clarity or context
• 1–2 sentences max

Primary CTA

• Action-oriented
• Describes what the user gets

Core Sections (Use as Appropriate)

• Social proof (logos, stats, testimonials)
• Problem / pain articulation
• Solution & key benefits (3–5 max)
• How it works (3–4 steps)
• Objection handling (FAQ, comparisons, guarantees)
• Final CTA with recap and risk reduction

Avoid stacking features without narrative flow.

Phase 5 — Writing the Copy

When writing copy, provide:

Page Copy

Organized by section with clear labels:

• Headline
• Subheadline
• CTAs
• Section headers
• Body copy

Alternatives

Provide 2–3 options for:

• Headlines
• Primary CTAs

Each option must include a brief rationale.

Annotations

For key sections, explain:

• Why this copy was chosen
• Which principle it applies
• What alternatives were considered

Testability Guidance

Write copy with testing in mind:

• Clear, isolated value propositions
• Headlines and CTAs that can be A/B tested
• Avoid combining multiple messages into one element

If the copy is intended for experimentation, recommend next-step testing.

Completion Criteria (Hard Stop)

This skill is complete ONLY when:

• Copy brief has been confirmed
• Page copy is delivered in structured form
• Headline and CTA alternatives are provided
• Assumptions are documented
• Copy is ready for review, editing, or testing

Key Principles (Summary)

• Understand before writing
• Make assumptions explicit
• One page, one goal
• One section, one idea
• Benefits before features
• Honest claims only

Final Reminder

Good copy does not persuade everyone. It persuades the right person to take the right action.

If the copy feels clever but unclear,
rewrite it until it feels obvious.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.