Communitygithub.com

Mr-Q526/TeamCC-Platform

Use when the task is to design a campaign page, 营销落地页, launch page, feature promotion page, webinar signup page, or lead generation page. Focus on one conversion goal, persuasive sequencing, proof, CTA rhythm, and low-friction form design.

TeamCC-Platform とは?

TeamCC-Platform is a Claude Code agent skill that use when the task is to design a campaign page, 营销落地页, launch page, feature promotion page, webinar signup page, or lead generation page. Focus on one conversion goal, persuasive sequencing, proof, CTA rhythm, and low-friction form design.

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Mr-Q526/TeamCC-Platform/tree/HEAD/skill-graph/skills-flat/marketing-landing-page

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

Marketing Landing Page

Use this skill when the page exists to convert a specific campaign intent: signup, download, demo request, waitlist, registration, or lead capture.

Goal: keep the page single-minded. Every section should remove one objection or strengthen one reason to convert.

Conversion model

Before building, define:

  • one audience
  • one offer
  • one primary CTA
  • one strongest proof source

If the page has multiple goals, split the page or downgrade secondary actions.

Default sequence

  1. Hero: promise, audience fit, CTA, proof teaser
  2. Why now: pain, change, or opportunity
  3. Offer detail: what the visitor gets and how it works
  4. Proof: results, logos, testimonials, or product evidence
  5. Friction removal: FAQ, pricing cue, timeline, or requirements
  6. Final CTA: repeat the action with reduced hesitation

Hero rules

  • State the benefit fast.
  • Keep the CTA visible without scrolling.
  • Show one dominant visual or one product demonstration, not both competing equally.
  • Use supporting proof near the CTA if trust is the main blocker.
  • Minimize top navigation unless the campaign requires exploration.

CTA rules

  • Use one label consistently across the page.
  • Repeat the CTA after each major proof or explanation block.
  • Match the CTA to effort: "Book demo" and "Start free" are not interchangeable.
  • If a form is above the fold, keep it short and explain what happens next.

Content rules

  • Write to a specific problem, not to "everyone".
  • Replace abstract claims with concrete outcomes.
  • Use sections to handle objections one at a time.
  • Put technical detail below value and proof unless the audience is highly technical.

Reject these failures

  • Website-style nav with too many exits
  • Multiple competing CTAs
  • Long feature grids with no proof
  • Testimonial quotes with no role, company, or context
  • Forms that ask for more than the offer justifies

Final checks

  • Can the visitor understand the offer in under five seconds?
  • Is the primary CTA obvious in every major section?
  • Does each section either explain, prove, or reduce friction?

関連スキル