[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74YHB5R8F4MWAHS4Y4RGAEW":3,"skill-same:01M74YHB5R8F4MWAHS4Y4RGAEW":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M74YHB5R8F4MWAHS4Y4RGAEW","landing-page",null,"When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.","shawnpang\u002Fstartup-founder-skills","shawnpang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22985112?v=4","01M74YFD4GVKV76K78PEE9TNNW","Shawn Pang","01M74YFD562PQ7839XQB42P2GS",386,"MIT","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Flanding-page\u002FSKILL.md",[],[],"2026-11-11 17:31:55",false,"---\nname: landing-page\ndescription: When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.\nrelated: [content-strategy, seo-technical, cold-outreach]\nreads: [startup-context]\n---\n\n# Landing Page\n\n## When to Use\n- Creating a new landing page from scratch (product launch, feature page, waitlist).\n- Auditing an existing page for conversion rate optimization (CRO).\n- Rewriting headlines, CTAs, or hero sections.\n- Structuring page sections for a specific audience and traffic source.\n- Generating A\u002FB test variants for copy or layout changes.\n\n## Context Required\n- **From startup-context:** product description, ICP (ideal customer profile), value proposition, competitive positioning, stage, tone of voice.\n- **From the user:** page URL or current copy (if auditing), page type (homepage, landing page, pricing, feature, blog), primary conversion goal (signup, demo, purchase, subscribe, download), traffic source (organic, paid, email, social), any existing conversion data or user research.\n\n## Workflow\n1. **Identify page type and conversion goal** -- Every page gets one primary conversion action. Determine whether this is a homepage, landing page, pricing page, feature page, or blog post -- each has a different CRO framework.\n2. **Assess value proposition clarity** -- Can a visitor understand what this is and why they should care within 5 seconds? Check whether copy is benefit-focused (good) or feature-focused (common problem). Ensure it is written in the customer's language, not company jargon.\n3. **Evaluate headline effectiveness** -- Does the headline communicate the core value proposition? Is it specific enough to be meaningful? Does it match the traffic source's messaging? Apply headline patterns:\n   - **Outcome-focused:** \"Get [desired outcome] without [pain point]\"\n   - **Specificity:** Include numbers, timeframes, or concrete results\n   - **Social proof:** \"Join [N] teams who [achieve outcome]\"\n   - **Direct address:** \"You [do painful thing]. There's a better way.\"\n4. **Audit CTA placement, copy, and hierarchy** -- Is there one clear primary action visible without scrolling? Does button copy communicate value, not just action? (\"Start my free trial\" beats \"Submit\"). Check CTA hierarchy: primary vs. secondary, repeated at key decision points.\n5. **Check visual hierarchy and scannability** -- Can someone scanning the page get the main message? Are the most important elements visually prominent? Is there sufficient whitespace? Do images support or distract from the message?\n6. **Evaluate trust signals and social proof** -- Look for: customer logos (especially recognizable ones), testimonials with specifics and attribution, case study snippets with real numbers, review scores, security badges. Place trust signals near CTAs and after benefit claims.\n7. **Identify objection handling** -- Are common objections addressed? Price\u002Fvalue concerns, \"will this work for me?\", implementation difficulty, \"what if it doesn't work?\" Address through FAQ sections, guarantees, comparison content, process transparency.\n8. **Find friction points** -- Too many form fields, unclear next steps, confusing navigation, required fields that should not be required, poor mobile experience, slow load times.\n\n## Output Format\n- **If auditing:** Recommendations structured as: (1) Quick Wins -- easy changes with immediate impact, (2) High-Impact Changes -- bigger efforts with significant conversion improvement, (3) Test Ideas -- hypotheses worth A\u002FB testing. For key elements, provide 2-3 copy alternatives with rationale.\n- **If drafting:** Full page copy organized by section with 2-3 headline variants and CTA text options. Include layout and visual recommendations.\n\n## Frameworks & Best Practices\n\n### Page-Specific CRO\n- **Homepage:** Clear positioning for cold visitors, quick path to primary conversion, handle both \"ready to buy\" and \"still researching\" visitors.\n- **Landing page:** Message-match with traffic source, single CTA (remove navigation if possible), complete argument on one page.\n- **Pricing page:** Clear plan comparison, recommended plan indication, address \"which plan is right for me?\" anxiety.\n- **Feature page:** Connect feature to benefit, include use cases and examples, clear path to try\u002Fbuy.\n- **Blog post:** Contextual CTAs matching content topic, inline CTAs at natural stopping points.\n\n### Copy Principles\n- **The headline is the most important element on the page.** If the headline does not stop the scroll, nothing else matters. Test headlines before anything else.\n- **Specificity beats cleverness.** \"Save 12 hours per week on reporting\" outperforms \"Work smarter, not harder\" every time.\n- **The subheadline does the heavy lifting.** The headline earns attention; the subheadline explains the value. Use it to clarify who the product is for, what it does, and why it matters.\n- **Awareness-level matching.** Match copy depth to visitor awareness. Paid search visitors are typically solution-aware (want pricing and CTAs). Social ad visitors are typically problem-aware or unaware (need problem education first). Traffic source reveals awareness level.\n\n### Conversion Principles\n- **One page, one goal.** Never give the visitor two equal choices. Every element should push toward the primary CTA.\n- **Above-the-fold rule.** Visitor should understand what you do, who it is for, and what to do next within 5 seconds.\n- **Risk reversal near final CTA.** Address \"what if it doesn't work?\" -- free trial, money-back guarantee, or no-commitment language.\n- **Social proof placement.** Small proof element in hero section (\"Trusted by 500+ teams\"), dedicated proof section below the fold.\n- **Testimonial specificity.** \"This product is great\" is worthless. \"We reduced onboarding time from 3 weeks to 2 days\" is persuasive. Seek specific, outcome-driven testimonials with numbers.\n- **Reduce cognitive load.** Every additional choice, link, or piece of information adds friction. Cut anything that does not directly support the primary conversion.\n- **Mobile-first.** Over 60% of traffic is mobile. Design for thumb zones. Ensure CTAs are tappable without zooming.\n\n## Related Skills\n- `content-strategy` -- when the landing page needs supporting content to drive traffic\n- `seo-technical` -- when the landing page needs to rank organically\n- `cold-outreach` -- when the landing page is the destination for outbound campaigns and copy must align with email messaging\n\n## Examples\n\n**Example 1: Page audit**\n> \"Here's our landing page copy. We're getting 15k visitors\u002Fmonth but only 1.2% conversion. What's wrong?\"\n\nGood output: Quick wins (e.g., rewrite feature-focused headline to outcome-focused), high-impact changes (restructure page sections, add social proof to hero), and test ideas (3 headline variants, 2 CTA copy options). Each recommendation includes the specific issue, the fix, and expected impact.\n\n**Example 2: New page draft**\n> \"We're launching a waitlist page for our developer tool. Target audience is backend engineers frustrated with deployment complexity.\"\n\nGood output: Full section-by-section copy. Hero headline: \"Deploy to production in 3 commands, not 30 steps.\" Problem agitation naming the specific pain. 3-step \"how it works\" section. Social proof placeholder guidance. CTA: \"Join 2,400 engineers on the waitlist.\" Two alternative headline options and layout notes.\n\n**Example 3: A\u002FB test recommendations**\n> \"Our signup page converts at 3.5%. What should we test first?\"\n\nGood output: Priority-ordered test plan. (1) Headline -- 3 variants reframing value prop from feature-first to outcome-first. (2) CTA copy -- \"Start free trial\" vs. \"See it in action\" vs. \"Get started in 2 minutes.\" (3) Hero trust element -- customer count or logo bar. Each test includes control, variant, hypothesis, and minimum sample size guidance.\n","# Landing Page\n\n## When to Use\n- Creating a new landing page from scratch (product launch, feature page, waitlist).\n- Auditing an existing page for conversion rate optimization (CRO).\n- Rewriting headlines, CTAs, or hero sections.\n- Structuring page sections for a specific audience and traffic source.\n- Generating A\u002FB test variants for copy or layout changes.\n\n## Context Required\n- **From startup-context:** product description, ICP (ideal customer profile), value proposition, competitive positioning, stage, tone of voice.\n- **From the user:** page URL or current copy (if auditing), page type (homepage, landing page, pricing, feature, blog), primary conversion goal (signup, demo, purchase, subscribe, download), traffic source (organic, paid, email, social), any existing conversion data or user research.\n\n## Workflow\n1. **Identify page type and conversion goal** -- Every page gets one primary conversion action. Determine whether this is a homepage, landing page, pricing page, feature page, or blog post -- each has a different CRO framework.\n2. **Assess value proposition clarity** -- Can a visitor understand what this is and why they should care within 5 seconds? Check whether copy is benefit-focused (good) or feature-focused (common problem). Ensure it is written in the customer's language, not company jargon.\n3. **Evaluate headline effectiveness** -- Does the headline communicate the core value proposition? Is it specific enough to be meaningful? Does it match the traffic source's messaging? Apply headline patterns:\n   - **Outcome-focused:** \"Get [desired outcome] without [pain point]\"\n   - **Specificity:** Include numbers, timeframes, or concrete results\n   - **Social proof:** \"Join [N] teams who [achieve outcome]\"\n   - **Direct address:** \"You [do painful thing]. There's a better way.\"\n4. **Audit CTA placement, copy, and hierarchy** -- Is there one clear primary action visible without scrolling? Does button copy communicate value, not just action? (\"Start my free trial\" beats \"Submit\"). Check CTA hierarchy: primary vs. secondary, repeated at key decision points.\n5. **Check visual hierarchy and scannability** -- Can someone scanning the page get the main message? Are the most important elements visually prominent? Is there sufficient whitespace? Do images support or distract from the message?\n6. **Evaluate trust signals and social proof** -- Look for: customer logos (especially recognizable ones), testimonials with specifics and attribution, case study snippets with real numbers, review scores, security badges. Place trust signals near CTAs and after benefit claims.\n7. **Identify objection handling** -- Are common objections addressed? Price\u002Fvalue concerns, \"will this work for me?\", implementation difficulty, \"what if it doesn't work?\" Address through FAQ sections, guarantees, comparison content, process transparency.\n8. **Find friction points** -- Too many form fields, unclear next steps, confusing navigation, required fields that should not be required, poor mobile experience, slow load times.\n\n## Output Format\n- **If auditing:** Recommendations structured as: (1) Quick Wins -- easy changes with immediate impact, (2) High-Impact Changes -- bigger efforts with significant conversion improvement, (3) Test Ideas -- hypotheses worth A\u002FB testing. For key elements, provide 2-3 copy alternatives with rationale.\n- **If drafting:** Full page copy organized by section with 2-3 headline variants and CTA text options. Include layout and visual recommendations.\n\n## Frameworks & Best Practices\n\n### Page-Specific CRO\n- **Homepage:** Clear positioning for cold visitors, quick path to primary conversion, handle both \"ready to buy\" and \"still researching\" visitors.\n- **Landing page:** Message-match with traffic source, single CTA (remove navigation if possible), complete argument on one page.\n- **Pricing page:** Clear plan comparison, recommended plan indication, address \"which plan is right for me?\" anxiety.\n- **Feature page:** Connect feature to benefit, include use cases and examples, clear path to try\u002Fbuy.\n- **Blog post:** Contextual CTAs matching content topic, inline CTAs at natural stopping points.\n\n### Copy Principles\n- **The headline is the most important element on the page.** If the headline does not stop the scroll, nothing else matters. Test headlines before anything else.\n- **Specificity beats cleverness.** \"Save 12 hours per week on reporting\" outperforms \"Work smarter, not harder\" every time.\n- **The subheadline does the heavy lifting.** The headline earns attention; the subheadline explains the value. Use it to clarify who the product is for, what it does, and why it matters.\n- **Awareness-level matching.** Match copy depth to visitor awareness. Paid search visitors are typically solution-aware (want pricing and CTAs). Social ad visitors are typically problem-aware or unaware (need problem education first). Traffic source reveals awareness level.\n\n### Conversion Principles\n- **One page, one goal.** Never give the visitor two equal choices. Every element should push toward the primary CTA.\n- **Above-the-fold rule.** Visitor should understand what you do, who it is for, and what to do next within 5 seconds.\n- **Risk reversal near final CTA.** Address \"what if it doesn't work?\" -- free trial, money-back guarantee, or no-commitment language.\n- **Social proof placement.** Small proof element in hero section (\"Trusted by 500+ teams\"), dedicated proof section below the fold.\n- **Testimonial specificity.** \"This product is great\" is worthless. \"We reduced onboarding time from 3 weeks to 2 days\" is persuasive. Seek specific, outcome-driven testimonials with numbers.\n- **Reduce cognitive load.** Every additional choice, link, or piece of information adds friction. Cut anything that does not directly support the primary conversion.\n- **Mobile-first.** Over 60% of traffic is mobile. Design for thumb zones. Ensure CTAs are tappable without zooming.\n\n## Related Skills\n- `content-strategy` -- when the landing page needs supporting content to drive traffic\n- `seo-technical` -- when the landing page needs to rank organically\n- `cold-outreach` -- when the landing page is the destination for outbound campaigns and copy must align with email messaging\n\n## Examples\n\n**Example 1: Page audit**\n> \"Here's our landing page copy. We're getting 15k visitors\u002Fmonth but only 1.2% conversion. What's wrong?\"\n\nGood output: Quick wins (e.g., rewrite feature-focused headline to outcome-focused), high-impact changes (restructure page sections, add social proof to hero), and test ideas (3 headline variants, 2 CTA copy options). Each recommendation includes the specific issue, the fix, and expected impact.\n\n**Example 2: New page draft**\n> \"We're launching a waitlist page for our developer tool. Target audience is backend engineers frustrated with deployment complexity.\"\n\nGood output: Full section-by-section copy. Hero headline: \"Deploy to production in 3 commands, not 30 steps.\" Problem agitation naming the specific pain. 3-step \"how it works\" section. Social proof placeholder guidance. CTA: \"Join 2,400 engineers on the waitlist.\" Two alternative headline options and layout notes.\n\n**Example 3: A\u002FB test recommendations**\n> \"Our signup page converts at 3.5%. What should we test first?\"\n\nGood output: Priority-ordered test plan. (1) Headline -- 3 variants reframing value prop from feature-first to outcome-first. (2) CTA copy -- \"Start free trial\" vs. \"See it in action\" vs. \"Get started in 2 minutes.\" (3) Hero trust element -- customer count or logo bar. Each test includes control, variant, hypothesis, and minimum sample size guidance.\n",{"name":5,"reads":24,"related":26,"description":7},[25],"startup-context",[27,28,29],"content-strategy","seo-technical","cold-outreach","main","4ad31b43eef3ae3755cc57ec7e435dab4699ab44","skills\u002Flanding-page",44,"https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills","https:\u002F\u002Fgithub.com\u002Fshawnpang","allscale.io","Building @allscale-io \r\nAlum @RichardIveyBusinessSchool \r\nExited from HashMatrix\r\nEx-Backend Dev @ByteDance\r\nEx-Product @CapitalOne @TikTok","2026-03-17 00:47:55",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add shawnpang\u002Fstartup-founder-skills --skill landing-page",{"tool":45,"command":46},"bunx","bunx skills add shawnpang\u002Fstartup-founder-skills --skill landing-page",{"tool":48,"command":49},"pnpm","pnpm dlx skills add shawnpang\u002Fstartup-founder-skills --skill landing-page","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Flanding-page\u002FSKILL.md",true,[],[54,61,68,75,82,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74YKFJBG7D7CVZHZQX9QB6X","user-research-synthesis","When the user has raw customer interview transcripts, survey responses, support tickets, or other qualitative data and needs to extract actionable insights.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fuser-research-synthesis\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74YKDA0DMZGMKN0ZXWQ83RS","terms-of-service","When the user needs to draft, review, or update terms of service for their SaaS product or web application.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fterms-of-service\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74YKA5EDTSDCJ3M60GGWK42","tech-stack-eval","When the user needs to choose between technologies, frameworks, or tools — or says \"which framework should I use\", \"compare X vs Y\", \"should we migrate from X to Y\", \"what database should I use\", \"calculate TCO\".","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftech-stack-eval\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74YK6WBXMTA6QDMKWAC4EDV","support-docs","When the user needs to create help center articles, FAQs, troubleshooting guides, API documentation, or getting-started guides for customers.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsupport-docs\u002FSKILL.md",[],[],{"skillNo":83,"name":25,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M74YK4RRS1AST1VVX3HP24ZZ","When the user wants to create or update their startup context document. Also use when the user mentions \"set up context\", \"tell you about my startup\", or any other skill needs context that doesn't exist yet.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstartup-context\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74YK26W3TXVY4MSC185QHY3","sourcing-outreach","When the user needs to write recruiting outreach messages to attract passive candidates or request referrals.","https:\u002F\u002Fgithub.com\u002Fshawnpang\u002Fstartup-founder-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsourcing-outreach\u002FSKILL.md",[],[]]