[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AN8DEF53XTWZTEPANP8RN":3,"skill-same:01M71AN8DEF53XTWZTEPANP8RN":68},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M71AN8DEF53XTWZTEPANP8RN","solutions-page-generator",null,"When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions \"solutions\", \"solutions page\", \"by industry\" or \"industry solutions\". For sitewide page planning, use website-structure.","ariadoss\u002Fsuperskills","ariadoss","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F414341?v=4","01M71AC7383PT6JCRZSQJ4AVTM","Danilo Stern-Sapad","01M71AC73Y7NTBTJ9KQYNENRRE",12,"MIT","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fpages\u002Fmarketing\u002Fsolutions\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"generator","solutions page generator","solutions","page generator","page","user","industry","website","audit","optimize","structure","create","when","use","pages","for","planning","industry solutions","2026-11-10 10:12:30",false,"---\nname: solutions-page-generator\ndescription: When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions \"solutions\", \"solutions page\", \"by industry\" or \"industry solutions\". For sitewide page planning, use website-structure.\nmetadata:\n  version: 1.1.1\n---\n\n# Pages: Solutions\n\nGuides solutions pages focused on business outcomes. **Industry-first** is the B2B norm (Salesforce, HubSpot). Answer \"what outcome do I get for my industry\u002Fteam\u002Fsize?\" rather than \"what does it do?\" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment.\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for product, outcomes, and proof points.\n\nIdentify:\n1. **Outcomes**: Revenue growth, cost savings, efficiency, compliance\n2. **Segments**: Industry (primary), company size, team\n3. **Format**: Hub + per-solution pages, or single solutions page\n4. **Primary goal**: Demo, sign up, contact\n\n## Solutions Page Structure\n\n| Section | Purpose |\n|---------|---------|\n| **Headline** | Outcome-led; \"Achieve X with [Product]\" |\n| **Challenge** | Business problem, context |\n| **Solution** | How product delivers the outcome |\n| **Proof** | Metrics, case study, ROI |\n| **Features used** | Link to relevant features |\n| **CTA** | Book demo, start trial, see case study |\n| **Related** | Other solutions, use cases (as sub-applications) |\n\n## Best Practices\n\n### Outcome-First\n\n- **Lead with result**: \"Increase conversion by 30%\" not \"We have A\u002FB testing\"\n- **Measurable**: Time saved, revenue gained, cost reduced\n- **Specific**: Industry workflows, not generic claims\n- **Differentiate**: Each industry\u002Fsegment gets unique content\n\n### Organization (Primary → Secondary)\n\n| Dimension | Priority | Examples |\n|-----------|----------|----------|\n| **By Industry** | Primary | Healthcare, Retail, Manufacturing, Financial Services |\n| **By Company Size** | Secondary | SMB, Mid-Market, Enterprise |\n| **By Team** | Secondary | Marketing, Sales, Service, Operations |\n| **By Outcome** | Alternative | Scale support, Reduce churn, Accelerate sales |\n\n### Common Industries (Reference)\n\nAutomotive, Communications, Consumer Goods, Consumer Services, Construction & Real Estate, Education, Energy & Utilities, Financial Services, Government, Healthcare & Life Sciences, Manufacturing, Media, Nonprofit, Professional Services, Retail, Technology, Travel & Hospitality.\n\n### Company Size Segments\n\n| Size | Typical | Focus |\n|------|---------|-------|\n| Startup | \u003C50 | Speed, agility |\n| SMB | 50–500 | Ease of use, affordability |\n| Mid-Market | 500–5000 | Scalability |\n| Enterprise | 5000+ | Customization, compliance, integration |\n\n### vs. Use Cases vs. Features\n\n| Page | Answers | Primary Organization |\n|------|---------|----------------------|\n| **Features** | What does it do? | Capabilities |\n| **Use cases** | When would I use it? | By scenario, persona, business goal |\n| **Solutions** | What outcome do I get? | By industry, company size, team |\n\n**Hierarchy**: Solutions (industry\u002Fsegment) can contain Use Cases as sub-applications. Example: \u002Fsolutions\u002Fhealthcare → use cases: patient scheduling, telemedicine.\n\n### When to Use Solutions vs Use Cases\n\n| Need | Use |\n|------|-----|\n| By industry (Healthcare, Retail) | Solutions |\n| By company size (SMB, Enterprise) | Solutions |\n| By team (Marketing, Sales) | Solutions |\n| By outcome (Scale support) | Solutions |\n| By scenario (Event marketing) | Use Cases |\n| By persona (For Realtors, For CMOs) | Use Cases |\n| By business goal (Acquisition, Retention) | Use Cases |\n| Industry-specific application | Use Cases (as Solutions sub-page) |\n\n## Output Format\n\n- **Solutions list** (industries\u002Fsegments)\n- **Per-page structure** (sections, messaging)\n- **Headline** options\n- **Proof** integration (case studies, metrics)\n- **Internal linking** (features, use cases, pricing)\n- **SEO** metadata\n\n## Related Skills\n\n- **use-cases-page-generator**: Use cases as sub-applications under solutions; link between\n- **features-page-generator**: Solutions reference features; link to feature pages\n- **customer-stories-page-generator**: Case studies as proof on solutions pages\n- **pricing-page-generator**: Solutions pages link to pricing\n- **landing-page-generator**: Solutions pages apply LP principles\n","# Pages: Solutions\n\nGuides solutions pages focused on business outcomes. **Industry-first** is the B2B norm (Salesforce, HubSpot). Answer \"what outcome do I get for my industry\u002Fteam\u002Fsize?\" rather than \"what does it do?\" Distinct from features (capabilities) and use cases (scenarios); solutions emphasize measurable value by segment.\n\n**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.\n\n## Initial Assessment\n\n**Check for project context first:** If `.claude\u002Fproject-context.md` or `.cursor\u002Fproject-context.md` exists, read it for product, outcomes, and proof points.\n\nIdentify:\n1. **Outcomes**: Revenue growth, cost savings, efficiency, compliance\n2. **Segments**: Industry (primary), company size, team\n3. **Format**: Hub + per-solution pages, or single solutions page\n4. **Primary goal**: Demo, sign up, contact\n\n## Solutions Page Structure\n\n| Section | Purpose |\n|---------|---------|\n| **Headline** | Outcome-led; \"Achieve X with [Product]\" |\n| **Challenge** | Business problem, context |\n| **Solution** | How product delivers the outcome |\n| **Proof** | Metrics, case study, ROI |\n| **Features used** | Link to relevant features |\n| **CTA** | Book demo, start trial, see case study |\n| **Related** | Other solutions, use cases (as sub-applications) |\n\n## Best Practices\n\n### Outcome-First\n\n- **Lead with result**: \"Increase conversion by 30%\" not \"We have A\u002FB testing\"\n- **Measurable**: Time saved, revenue gained, cost reduced\n- **Specific**: Industry workflows, not generic claims\n- **Differentiate**: Each industry\u002Fsegment gets unique content\n\n### Organization (Primary → Secondary)\n\n| Dimension | Priority | Examples |\n|-----------|----------|----------|\n| **By Industry** | Primary | Healthcare, Retail, Manufacturing, Financial Services |\n| **By Company Size** | Secondary | SMB, Mid-Market, Enterprise |\n| **By Team** | Secondary | Marketing, Sales, Service, Operations |\n| **By Outcome** | Alternative | Scale support, Reduce churn, Accelerate sales |\n\n### Common Industries (Reference)\n\nAutomotive, Communications, Consumer Goods, Consumer Services, Construction & Real Estate, Education, Energy & Utilities, Financial Services, Government, Healthcare & Life Sciences, Manufacturing, Media, Nonprofit, Professional Services, Retail, Technology, Travel & Hospitality.\n\n### Company Size Segments\n\n| Size | Typical | Focus |\n|------|---------|-------|\n| Startup | \u003C50 | Speed, agility |\n| SMB | 50–500 | Ease of use, affordability |\n| Mid-Market | 500–5000 | Scalability |\n| Enterprise | 5000+ | Customization, compliance, integration |\n\n### vs. Use Cases vs. Features\n\n| Page | Answers | Primary Organization |\n|------|---------|----------------------|\n| **Features** | What does it do? | Capabilities |\n| **Use cases** | When would I use it? | By scenario, persona, business goal |\n| **Solutions** | What outcome do I get? | By industry, company size, team |\n\n**Hierarchy**: Solutions (industry\u002Fsegment) can contain Use Cases as sub-applications. Example: \u002Fsolutions\u002Fhealthcare → use cases: patient scheduling, telemedicine.\n\n### When to Use Solutions vs Use Cases\n\n| Need | Use |\n|------|-----|\n| By industry (Healthcare, Retail) | Solutions |\n| By company size (SMB, Enterprise) | Solutions |\n| By team (Marketing, Sales) | Solutions |\n| By outcome (Scale support) | Solutions |\n| By scenario (Event marketing) | Use Cases |\n| By persona (For Realtors, For CMOs) | Use Cases |\n| By business goal (Acquisition, Retention) | Use Cases |\n| Industry-specific application | Use Cases (as Solutions sub-page) |\n\n## Output Format\n\n- **Solutions list** (industries\u002Fsegments)\n- **Per-page structure** (sections, messaging)\n- **Headline** options\n- **Proof** integration (case studies, metrics)\n- **Internal linking** (features, use cases, pricing)\n- **SEO** metadata\n\n## Related Skills\n\n- **use-cases-page-generator**: Use cases as sub-applications under solutions; link between\n- **features-page-generator**: Solutions reference features; link to feature pages\n- **customer-stories-page-generator**: Case studies as proof on solutions pages\n- **pricing-page-generator**: Solutions pages link to pricing\n- **landing-page-generator**: Solutions pages apply LP principles\n",{"name":5,"metadata":42,"description":7},{"version":43},"1.1.1","main","c7ec8d78e5dc37484c2cfe90ab04de163d97dd41","marketing-skills\u002Fpages\u002Fmarketing\u002Fsolutions",0,"https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills","https:\u002F\u002Fhyperion360.com\u002Fblog\u002Fparallel-ai-agents-engineering-workflow\u002F","https:\u002F\u002Fgithub.com\u002Fariadoss","https:\u002F\u002Fdanilosapad.com\u002F","CEO & Founder of @Hyperion360","2026-11-13 15:29:19",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add ariadoss\u002Fsuperskills --skill solutions-page-generator",{"tool":60,"command":61},"bunx","bunx skills add ariadoss\u002Fsuperskills --skill solutions-page-generator",{"tool":63,"command":64},"pnpm","pnpm dlx skills add ariadoss\u002Fsuperskills --skill solutions-page-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fmarketing-skills\u002Fpages\u002Fmarketing\u002Fsolutions\u002FSKILL.md",true,[],[69,95,119,138,166,182],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":37},"01M71AZE3MPF891RM354EMRYA1","youtube","Download YouTube video transcripts when user provides a YouTube URL or asks to download\u002Fget\u002Ffetch a transcript from YouTube. Also use when user wants to transcribe or get captions\u002Fsubtitles from a YouTube video.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[71,24,81,82,83,84,85,86,87,31,88,89,90,91,92,32,93,94],"download","transcribe","write","transcript","video transcripts","Bash","URL","Captions","get","fetch","Video","read","subtitles","transcripts",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":37},"01M71AZAYR85PW6BJGSQXS4BN2","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY\u002FSOLID\u002FYAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs \u002Fplan-eng-review as an independent double-check before execution.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[102,103,83,104,105,106,107,108,109,31,110,111,112,113,114,34,115,116,117,118],"write plan","plan","dry","verification","review","tasks","code","you","auto","eng","coverage","complete","section","test plan","target","as","yagni",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":37},"01M71AZ8NDDP5ZMGEE6FSC4FKR","worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fworktrees\u002FSKILL.md",[],[121,126,127,128,32,129,130,131,132,133,134,105,135,31,136,137],"implementation","workspace","with","plans","feature","isolation","git","directory","work","git worktrees","selection","Safety",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":37},"01M71AZ4ZQHTNWFRZVYHKQFP08","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,149,150,151,152,153,28,154,155,31,156,157,158,159,160,161,162,163,164,165],"web","perf","web perf","resources","MCP","layout","documentation","caching","qa","knowledge","devtools","issues","render","re","performance","chrome devtools","vitals","never",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":37},"01M71AZ2KZNWYEGKKRMJH8PYG2","verify","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[168,113,173,174,134,105,175,176,31,177,32,178,179,180,181],"commands","about","claims","output","assertions","claim","prs","evidence","running",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":37},"01M71AZ0ACCK7N1QMWQK1FV2HJ","validate-idea","Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.","https:\u002F\u002Fgithub.com\u002Fariadoss\u002Fsuperskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[189,190,191,192,193,194,195,31,196,32,197],"validate","idea","validate idea","framework","it","minimalist","test","business","before building"]