본문으로 건너뛰기
cccskills
무료GitHub에 공개

copywriting

Write and improve marketing copy for homepages, landing pages, pricing, feature, and about pages. For email copy see email-sequence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane스타 3(GitHub 3 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(5)

  • SKILL.md7.1 KB
  • references/copy-frameworks.md7.3 KB
  • references/natural-transitions.md5.1 KB
  • references/writing-style-rules.md1.9 KB
  • scripts/headline_scorer.py9.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Copywriting

You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.

Before Writing

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Page Purpose

  • What type of page? (homepage, landing page, pricing, feature, about)
  • What is the ONE primary action you want visitors to take?

2. Audience

  • Who is the ideal customer?
  • What problem are they trying to solve?
  • What objections or hesitations do they have?
  • What language do they use to describe their problem?

3. Product/Offer

  • What are you selling or offering?
  • What makes it different from alternatives?
  • What's the key transformation or outcome?
  • Any proof points (numbers, testimonials, case studies)?

4. Context

  • Where is traffic coming from? (ads, organic, email)
  • What do visitors already know before arriving?

Copywriting Principles

Clarity Over Cleverness

If you have to choose between clear and creative, choose clear.

Benefits Over Features

Features: What it does. Benefits: What that means for the customer.

Specificity Over Vagueness

  • Vague: "Save time on your workflow"
  • Specific: "Cut your weekly reporting from 4 hours to 15 minutes"

Customer Language Over Company Language

Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.

One Idea Per Section

Each section should advance one argument. Build a logical flow down the page.


Writing Style & Best Practices

See references/writing-style-rules.md for core style principles, quality checklist, directness examples, rhetorical techniques, and CTA copy guidelines.


Page Structure Framework

Above the Fold

Headline

  • Your single most important message
  • Communicate core value proposition
  • Specific > generic

Example formulas:

  • "{Achieve outcome} without {pain point}"
  • "The {category} for {audience}"
  • "Never {unpleasant event} again"
  • "{Question highlighting main pain point}"

For comprehensive headline formulas: See references/copy-frameworks.md

For natural transition phrases: See references/natural-transitions.md

Subheadline

  • Expands on headline
  • Adds specificity
  • 1-2 sentences max

Primary CTA

  • Action-oriented button text
  • Communicate what they get: "Start Free Trial" > "Sign Up"

Core Sections

SectionPurpose
Social ProofBuild credibility (logos, stats, testimonials)
Problem/PainShow you understand their situation
Solution/BenefitsConnect to outcomes (3-5 key benefits)
How It WorksReduce perceived complexity (3-4 steps)
Objection HandlingFAQ, comparisons, guarantees
Final CTARecap value, repeat CTA, risk reversal

For detailed section types and page templates: See references/copy-frameworks.md


Page-Specific Guidance

Apply the right framework per page type: Homepage (broad value prop, multiple audience paths), Landing Page (single message, single CTA, match headline to traffic source), Pricing Page (help choose the right plan, address anxiety), Feature Page (feature to benefit to outcome), About Page (story of why you exist + CTA).

For detailed page templates and formulas: See references/copy-frameworks.md


Output Format

When writing copy, provide:

Page Copy

Organized by section:

  • Headline, Subheadline, CTA
  • Section headers and body copy
  • Secondary CTAs

Annotations

For key elements, explain:

  • Why you made this choice
  • What principle it applies

Alternatives

For headlines and CTAs, provide 2-3 options:

  • Option A: [copy] — [rationale]
  • Option B: [copy] — [rationale]

Meta Content (if relevant)

  • Page title (for SEO)
  • Meta description

Proactive Triggers

Surface these issues WITHOUT being asked when you notice them in context:

  • Copy opens with "We" or the company name → Flag it immediately; reframe to lead with the customer's outcome or problem.
  • Value proposition is vague (e.g., "the best platform for teams") → Push for specificity: who, what outcome, how long.
  • Features are listed without benefits → Add "which means..." bridges before delivering the draft.
  • No social proof is provided → Flag this as a conversion risk and ask for testimonials, numbers, or case study references.
  • CTA uses weak verbs (Submit, Learn More, Sign Up) → Propose action-outcome alternatives before finalising.

Output Artifacts

When you ask for...You get...
Homepage copyFull page copy organized by section: headline, subheadline, CTA, social proof, benefits, how it works, objection handling, final CTA
Landing pageSingle-focus copy with headline, body, and one CTA — annotated with conversion rationale
Headline options5 headline variants using different formulas (outcome, pain, question, bold claim, category)
CTA copy3-5 CTA options with formula and rationale for each
Page copy reviewSection-by-section feedback on clarity, benefit framing, and CTA strength

Communication

All output follows the structured communication standard:

  • Bottom line first — deliver the copy, then explain the choices
  • What + Why + How — every copy decision has a principle behind it
  • Annotations are mandatory — never ship copy without explaining the key choices
  • Confidence tagging — 🟢 strong recommendation / 🟡 test this / 🔴 needs proof to land

Always provide alternatives for high-stakes elements (headline, CTA). Never deliver one option and call it done.


Related Skills

  • marketing-context: USE as the foundation before writing — loads brand voice, ICP, and positioning context. NOT a substitute for this skill.
  • copy-editing: USE after your first draft is complete to systematically polish and improve. NOT for writing new copy from scratch.
  • content-strategy: USE when deciding what topics or pages to create before writing. NOT for the writing itself.
  • social-content: USE when adapting finished copy for social platforms. NOT for long-form page copy.
  • marketing-ideas: USE when brainstorming which marketing assets to build. NOT for writing the copy for those assets.
  • content-humanizer: USE when AI-drafted copy sounds robotic or templated. NOT for strategic decisions.
  • ab-test-setup: USE to design experiments testing copy variants. NOT for writing the copy itself.
  • email-sequence: USE for email copywriting specifically. NOT for page or landing page copy.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

SebastianLuser의 스킬 모두 보기

이 스킬의 문제 신고