Communitygithub.com

SkillMedev/著陸頁文案

逐區塊撰寫著陸頁文案——英雄區、社會證明、功能即效益、異議處理、行動呼籲——以一個承諾開頭,並在頁面中逐步證明它。

著陸頁文案 是什麼?

此技能專注於為開發者、產品經理和行銷人員打造高效能的著陸頁文案。其核心方法論是:頁面只做一個承諾,並用其餘篇幅讓這個承諾變得可信。它避免了常見的「聰明但模糊」的錯誤——例如用「超級提升你的工作流程」這類詞句,結果導致訪客在了解產品前就跳出。技能支援 Claude Code、Cursor 和 Codex 等平台,並提供一個可操作的步驟式流程,從收集輸入(單一承諾、理想客戶人物誌、證據)開始,依序撰寫英雄區、社會證明、問題/解決方案、功能即效益、異議處理和行動呼籲區塊。它強調清晰度勝過巧妙,具體性勝過宏大,並包含一份品質檢查清單,以確保頁面在 5 秒內傳達產品內容、目標受眾和所需行動。此技能非常適合用於新頁面發佈、活動或文案改寫,但明確不適用於現有頁面的轉換率測試(應使用「landing-page-cro」)或高層次定位(應使用「positioning-statement」)。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/SkillMedev/skills/tree/HEAD/skills/landing-page-copy

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

著陸頁文案 是做什麼的?

一張著陸頁只做一個承諾,然後用頁面其餘部分讓這個承諾變得可信。此技能要避免的昂貴錯誤是「聰明但模糊」的頁面:付費流量進來了,看到「超級提升你的工作流程」,然後在了解產品是做什麼之前就跳離了。清晰勝過巧妙,讀者在最初五秒內決定是否要再給你三十秒。

操作流程

按照以下順序從上到下撰寫,因為每個區塊都在回答前一個區塊所引發的異議:英雄區提出主張,證明讓主張可信,效益讓主張具體,異議清除殘留疑慮,行動呼籲則收網。

步驟 1:收集輸入

  1. 一個承諾 - 頁面要銷售的單一成果。如果使用者給出三個,讓他們挑一個;其他的作為內文。如果還沒有定位,先導向 positioning-statement。
  2. 理想客戶人物誌 (ICP) 和他們自己說出的痛點(來自支援工單、銷售通話、評論——不是創辦人的轉述)。將轉述標記為猜測。
  3. 真正的替代方案(試算表、現有供應商、什麼都不做)。
  4. 可用的證據:推薦見證、客戶標誌、數字、螢幕截圖。預設:如果沒有,則使用機制的具體性作為臨時證據,並標記缺口。
  5. 頁面要求的單一動作(試用、示範、等待清單)以及點擊後會發生什麼事。
  6. 流量來源 - 頁面必須呼應將他們帶來的廣告或貼文中的承諾(訊息匹配;之後優化這個循環屬於 landing-page-cro)。

步驟 2:撰寫英雄區

  • 標題:用白話文寫出核心承諾——成果,而非功能。測試:陌生人在 5 秒內知道他們能得到什麼。少於 10 個字。
  • 副標題:用一句話說明是給誰的以及如何運作。
  • 行動呼籲 (CTA) 按鈕:一個動詞加上價值(「免費開始」、「取得範本」)——永遠不要用「提交」或「了解更多」。
  • 輔助視覺:展示成果或產品正在實現承諾,而不是抽象的插圖。

糟糕的英雄區例子:「解鎖智慧自動化的力量」/「我們由 AI 驅動的平台徹底改變現代團隊的工作方式」/ [了解更多] - 沒有成果、沒有目標受眾、三個流行詞、一個承諾要做功課的行動呼籲。

良好的英雄區例子:「5 分鐘內發送客戶報告,而不是 5 小時」/「ReportKit 自動將您機構的活動數據拉入白標報告 - 無需試算表」/ [免費開始 - 5 分鐘內取得第一份報告] - 成果附帶數字,說明了目標受眾和機制,行動呼籲重申了價值。

步驟 3:將社會證明緊接在英雄區下方

一個客戶標誌列、一個使用數字或一句有力的引述——證據屬於主張的正下方,因為此時懷疑度最高。具體性勝過數量:一個具名的客戶帶有結果(「將報告時間縮短 80% - Dana K., Brightside Agency」)勝過五個匿名的星級評分。

步驟 4:依序撰寫主體

  1. 問題 - 用讀者自己的話說出痛點;他們應該心想「就是這樣。」
  2. 解決方案 - 產品如何消除痛點,以成果為框架。
  3. 功能即效益 - 對於每個功能,完成「這意味著…」直到觸及讀者的生活:「加密備份」變成「你永遠不會丟失你的工作。」刪除任何無法完成這個句子的功能。三到五個,每個都附帶具體細節。
  4. 更深層的證明 - 帶有姓名和成果的推薦見證、螢幕截圖、數字。
  5. 異議處理 - 誠實地回答前 2-3 個最主要的猶豫點(價格、遷移工作、安全性、「這適用於我的情況嗎」),從真實的銷售對話中提取。
  6. 重複行動呼籲 (CTA) - 相同的動作、相同的措辭,如同英雄區按鈕,現在他們已經被說服了。可選擇在下方添加一條減少摩擦的文字(「無需信用卡。隨時取消。」)。

步驟 5:編輯校對

  • 對一個人說話,使用第二人稱(「你」);不使用第一人稱。
  • 具體勝過宏大:「3 分鐘內設定完成」勝過「極度簡單。」
  • 刪除形容詞;讓證據自己說話。刪除每一個「強大」、「無縫」、「革命性」。
  • 每個區塊一個承諾;每個區塊讓讀者離行動呼籲更近一步——刪除任何做不到這一點的區塊。
  • 大聲讀出標題和行動呼籲;任何聽起來像行銷話術而不是像一個人在說話的內容,都要重寫。

頁面骨架範本

英雄區
  標題:[填寫:成果承諾,<10 字]
  副標題:[填寫:給誰的 + 如何運作,1 句話]
  行動呼籲:[填寫:動詞 + 價值]

證明列:[填寫:客戶標誌 / 使用數字 / 1 句具名引述]

問題:[填寫:用客戶自己的話說出的痛點,2-3 句話]
解決方案:[填寫:如何消除,以成果為框架,2-3 句話]

效益(3-5 個):
  - [填寫:功能] - 這意味著 [填寫:對讀者的成果]

深層證明:[填寫:1-2 個帶結果的具名推薦見證 / 螢幕截圖]

異議處理(2-3 個):
  - "[填寫:猶豫點]" - [填寫:誠實的回答]

最終行動呼籲:[填寫:與英雄區相同的動詞 + 價值] [填寫:減少摩擦的文字]

交付成果

按照骨架順序產出完整的頁面草稿——英雄區(標題、副標題、行動呼籲)、證明列、問題、解決方案、3-5 個功能即效益、深層證明、異議回答和重複的行動呼籲——並附上一行關於最薄弱證據點的說明,以便在擴大流量前加強。

禁止事項

  • 不要以公司或類別開頭(「Acme 是一個提供…的平台」)——要以讀者的成果開頭。
  • 不要在英雄區做出兩個承諾;必須選擇的訪客會選擇離開。
  • 不要使用沒有附加價值的「提交」、「了解更多」或「開始使用」——按鈕文案是決策前最後讀到的東西。
  • 不要編造推薦見證或數字;如果缺少證據,請標記出來——偽造的證據是信任和法律責任。
  • 不要將證據埋在摺頁下方,而主張卻沒有任何支撐地放在頂部。
  • 不要在此處對現有頁面進行 A/B 測試或重構——這種以診斷為先的循環屬於 landing-page-cro。

品質標準

  • 陌生人在看到英雄區後的 5 秒內,能說出產品是做什麼的、給誰用、以及要點擊哪裡。
  • 每個功能行都完成了一個「這意味著…」並且觸及讀者。
  • 至少有一項證據是具體的(姓名、數字或螢幕截圖)。
  • 零個不當的形容詞;每一個主張要不是已證明,就是很具體。
  • 頁面的承諾與引導流量的廣告或貼文相符。

升級處理

將現有頁面的轉換率測試導向 landing-page-cro,將單行主張導向 positioning-statement,將承諾/支柱/證據階梯導向 messaging-hierarchy,將頁面的發佈排程導向 launch-plan-sequencer。

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

SkillMedev/skills

Designs REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.

SkillMedev/skills

Produce an accurate, properly timed caption track (SRT or WebVTT) from a video's audio - transcribing or aligning to the voiceover script, timing cues to speech, and enforcing line-length and reading-speed rules so captions are readable and in sync. Use when someone says "generate captions", "make subtitles from the audio", "transcribe and caption this", "export an SRT or VTT", "the captions are out of sync", or "the subtitles flash by too fast to read". Do NOT use to burn-in, style, reframe, or position an existing caption track for a platform (9:16, brand styling, safe areas) - that is social-video-formatter; do NOT use to animate text word-by-word as a motion graphic - that is kinetic-typography; do NOT use to write the spoken script in the first place - that is narration-script.

SkillMedev/skills

Turns data and charts into a decision-driving narrative structured as headline finding, trend, implication, and recommended action - with finding-led chart titles, context for every number, annotation guidance, and honest flags on any conclusion the data cannot support. Use when someone says "turn these numbers into a story", "what's the takeaway from this data", "help me present these results to leadership", or has charts but no narrative. Do NOT use for compressing a long document into a one-pager - use executive-summary instead - or for running the analysis that produces the findings - use eda-playbook instead.

SkillMedev/skills

Use when a task needs live or historical money data - "convert USD to EUR", "current/past exchange rate", "FX rate on this date / over this range", or "current price of Bitcoin/Ethereum, market cap, 24h change". Frankfurter (ECB reference rates, no key) is the FX default; CoinGecko's free keyless tier covers crypto. Do NOT use for stock quotes or equities - no keyless stock API survives verification, say so instead of guessing; do NOT use for country economic indicators like GDP or inflation series - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Builds a driver-based FP&A operating model linking business inputs to P&L, balance sheet, and cash flow outputs. Use when building an annual plan, preparing investor materials, running scenario analysis, or stress-testing the business.

SkillMedev/skills

Use when a task needs live geographic lookups - "geocode this address", "what's at these coordinates" (reverse geocoding), "lat/lon for this city", "which country/state is this ZIP or postal code in", or "country facts: capital, currency, population, flag". Nominatim (OpenStreetMap) is the geocoding default; Zippopotam for postal codes; APICountries for country facts. All keyless. Do NOT use for weather at a location - use weather-climate instead; do NOT use for country-level statistics over time (GDP, population trends) - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Runs the full Getting Things Done loop - capture, clarify, organize, reflect, engage - building a trusted system of context lists, a projects list with defined next actions, and a weekly review habit. Use when someone says "I'm overwhelmed and things are slipping through the cracks", "set up GTD for me", "help me do a brain dump and organize it", or "my to-do list is a mess". Do NOT use for just running the weekly review ritual itself - use weekly-review instead - or for clearing an email backlog - use inbox-zero.

SkillMedev/skills

Processes any email backlog to zero using the 4Ds - Delete, Delegate, Defer, Do - with a mass-archive strategy for the obvious, a touch-each-email-once discipline, and a keep-it-clear system of batched processing windows, ruthless unsubscribing, filters, and a minimal folder setup. Use when someone says "I have 5,000 unread emails", "help me get to inbox zero", "email is eating my whole day", or treats their inbox as a to-do list. Do NOT use for drafting the reply emails themselves or prioritization rules for an ongoing support queue - use email-triage instead - or for protecting focus time around the email windows - use deep-work-planner instead.

SkillMedev/skills

Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.

SkillMedev/skills

Runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

SkillMedev/skills

Adapts English content for a target language and region - swapping idioms, setting the right formality register, replacing cultural references, converting dates, units, and currency - and delivers the localized text with a notes column explaining each adaptation and flagging what needs a native reviewer. Use when someone asks "localize this copy for the Japanese market", "adapt our marketing copy for the Mexican market", "make this translation sound native instead of literal", or a literal translation reads foreign, stiff, or risky. Do NOT use for auditing in-product UI text quality - use ux-writing-audit instead.

SkillMedev/skills

Turns a natural-language video brief into a complete, ready-to-preview Remotion composition - extracts duration, scenes, brand colors, aspect ratio, and real copy; plans the frame budget; and writes data-driven React/TypeScript using useCurrentFrame, interpolate, spring, AbsoluteFill, and Sequence, registered in Root.tsx. Use when someone says "build a 20-second product demo video", "animate a feature walkthrough", "write the Remotion code for this marketing clip", or wants a scene-by-scene composition they can scrub in Studio. Do NOT use for rendering, iterating, or batching the finished MP4 - use remotion-render instead - or for installing and scaffolding the project - use remotion-setup instead.

SkillMedev/skills

Scaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just "make product videos with Claude.

SkillMedev/skills

Classifies incident severity (SEV1-4) using impact, scope, and urgency signals and decides who to page. Use when an alert fires or a report comes in and a severity call must be made quickly.

SkillMedev/skills

Use the Skill Me catalog from inside any conversation - discover, install, and manage Claude skills through the Skill Me MCP, and load installed skills automatically each session.

SkillMedev/skills

Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a dedicated standalone LinkedIn post - use linkedin-post-writer instead; or a multi-post X thread - use tweet-thread-builder instead; or to adapt one existing piece of content into versions for several channels - use cross-platform-reformatter instead.

SkillMedev/skills

Reframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compo...

SkillMedev/skills

Writes and tunes PySpark jobs - join strategy and broadcast size limits, shuffle-partition sizing, skew diagnosis and salting, UDF avoidance, caching, and output file layout - with concrete size and skew thresholds. Use when someone asks "why is my Spark job slow", "should I broadcast this join", "one task takes forever while the rest finish", "my job OOMs during a join", or is writing a new PySpark ETL job. Do NOT use for Kafka topic, consumer-group, or streaming-pipeline design - use kafka-pipelines instead; do NOT use for single-machine dataframe work that fits in memory - use pandas-expert instead.

SkillMedev/skills

Builds clean, performant, accessible SwiftUI views with correct state ownership, scoped invalidation, and smooth list scrolling, and reviews existing SwiftUI code against a concrete frame-time and re-render budget. Use when someone asks "why does my SwiftUI list stutter", "should this be @State or @Observable", "my whole screen re-renders when one row changes", "how do I animate this transition", or wants a SwiftUI view built or refactored. Do NOT use for cross-platform React Native apps - use react-native-pro instead; do NOT use for Flutter widget trees - use flutter-widget-architect instead; do NOT use for Android Compose UIs - use jetpack-compose-builder instead.

相關技能