[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754Q5KTBS7S2WEJ6RYPHDTM":3,"skill-same:01M754Q5KTBS7S2WEJ6RYPHDTM":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":13,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M754Q5KTBS7S2WEJ6RYPHDTM","competitive-intel",null,"Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win\u002Floss, or market positioning.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fcompetitive-intel\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"competitive-intel\"\ndescription: \"Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win\u002Floss, or market positioning.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: competitive-strategy\n  updated: 2026-03-05\n  frameworks: ci-playbook, battlecard-template\n---\n\n# Competitive Intelligence\n\nSystematic competitor tracking. Not obsession — intelligence that drives real decisions.\n\n## Keywords\ncompetitive intelligence, competitor analysis, battlecard, win\u002Floss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy\n\n## Quick Start\n\n```\n\u002Fci:landscape         — Map your competitive space (direct, indirect, future)\n\u002Fci:battlecard [name] — Build a sales battlecard for a specific competitor\n\u002Fci:winloss           — Analyze recent wins and losses by reason\n\u002Fci:update [name]     — Track what a competitor did recently\n\u002Fci:map               — Build competitive positioning map\n```\n\n## Framework: 5-Layer Intelligence System\n\n### Layer 1: Competitor Identification\n\n**Direct competitors:** Same ICP, same problem, comparable solution, similar price point.\n**Indirect competitors:** Same budget, different solution (including \"do nothing\" and \"build in-house\").\n**Future competitors:** Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.\n\n**The 2x2 Threat Matrix:**\n\n| | Same ICP | Different ICP |\n|---|---|---|\n| **Same problem** | Direct threat | Adjacent (watch) |\n| **Different problem** | Displacement risk | Ignore for now |\n\nUpdate this quarterly. Who's moved quadrants?\n\n### Layer 2: Tracking Dimensions\n\nTrack these 8 dimensions per competitor:\n\n| Dimension | Sources | Cadence |\n|-----------|---------|---------|\n| **Product moves** | Changelog, G2\u002FCapterra reviews, Twitter\u002FLinkedIn | Monthly |\n| **Pricing changes** | Pricing page, sales call intel, customer feedback | Triggered |\n| **Funding** | Crunchbase, TechCrunch, LinkedIn | Triggered |\n| **Hiring signals** | LinkedIn job postings, Indeed | Monthly |\n| **Partnerships** | Press releases, co-marketing | Triggered |\n| **Customer wins** | Case studies, review sites, LinkedIn | Monthly |\n| **Customer losses** | Win\u002Floss interviews, churned accounts | Ongoing |\n| **Messaging shifts** | Homepage, ads (Facebook\u002FGoogle Ad Library) | Quarterly |\n\n### Layer 3: Analysis Frameworks\n\n**SWOT per Competitor:**\n- Strengths: What do they do well? Where do they win?\n- Weaknesses: Where do they lose? What do customers complain about?\n- Opportunities: What could they do that would threaten you?\n- Threats: What's their existential risk?\n\n**Competitive Positioning Map (2 axis):**\nChoose axes that matter for your buyers:\n- Common: Price vs Feature Depth; Enterprise-ready vs SMB-ready; Easy to implement vs Configurable\n- Pick axes that show YOUR differentiation clearly\n\n**Feature Gap Analysis:**\n| Feature | You | Competitor A | Competitor B | Gap status |\n|---------|-----|-------------|-------------|------------|\n| [Feature] | ✅ | ✅ | ❌ | Your advantage |\n| [Feature] | ❌ | ✅ | ✅ | Gap — roadmap? |\n| [Feature] | ✅ | ❌ | ❌ | Moat |\n| [Feature] | ❌ | ❌ | ✅ | Competitor B only |\n\n### Layer 4: Output Formats\n\n**For Sales (CRO):** Battlecards — one page per competitor, designed for pre-call prep.\nSee `templates\u002Fbattlecard-template.md`\n\n**For Marketing (CMO):** Positioning update — message shifts, new differentiators, claims to stop or start making.\n\n**For Product (CPO):** Feature gap summary — what customers ask for that we don't have, what competitors ship, what to reprioritize.\n\n**For CEO\u002FBoard:** Monthly competitive summary — 1-page: who moved, what it means, recommended responses.\n\n### Layer 5: Intelligence Cadence\n\n**Monthly (scheduled):**\n- Review all tier-1 competitors (direct threats, top 3)\n- Update battlecards with new intel\n- Publish 1-page summary to leadership\n\n**Triggered (event-based):**\n- Competitor raises funding → assess implications within 48 hours\n- Competitor launches major feature → product + sales response within 1 week\n- Competitor poaches key customer → win\u002Floss interview within 2 weeks\n- Competitor changes pricing → analyze and respond within 1 week\n\n**Quarterly:**\n- Full competitive landscape review\n- Update positioning map\n- Refresh ICP competitive threat assessment\n- Add\u002Fremove companies from tracking list\n\n---\n\n## Win\u002FLoss Analysis\n\nThis is the highest-signal competitive data you have. Most companies do it too rarely.\n\n**When to interview:**\n- Every lost deal >$50K ACV\n- Every churn >6 months tenure\n- Every competitive win (learn why — it may not be what you think)\n\n**Who conducts it:**\n- NOT the AE who worked the deal (too close, prospect won't be candid)\n- Customer success, product team, or external researcher\n\n**Question structure:**\n1. \"Walk me through your evaluation process\"\n2. \"Who else were you considering?\"\n3. \"What were the top 3 criteria in your decision?\"\n4. \"Where did [our product] fall short?\"\n5. \"What was the deciding factor?\"\n6. \"What would have changed your decision?\"\n\n**Aggregate findings monthly:**\n- Win reasons (rank by frequency)\n- Loss reasons (rank by frequency)\n- Competitor win rates (by competitor, by segment)\n- Patterns over time\n\n---\n\n## The Balance: Intelligence Without Obsession\n\n**Signs you're over-tracking competitors:**\n- Roadmap decisions are primarily driven by \"they just shipped X\"\n- Team morale drops when competitors fundraise\n- You're shipping features you don't believe in to match their checklist\n- Pricing discussions always start with \"well, they charge X\"\n\n**Signs you're under-tracking:**\n- Your AEs get blindsided on calls\n- Prospects know more about competitors than your team does\n- You missed a major product launch until customers told you\n- Your positioning hasn't changed in 12+ months despite market moves\n\n**The right posture:**\n- Know competitors well enough to win against them\n- Don't let them set your agenda\n- Your roadmap is led by customer problems, informed by competitive gaps\n\n---\n\n## Distributing Intelligence\n\n| Audience | Format | Cadence | Owner |\n|----------|--------|---------|-------|\n| AEs + SDRs | Updated battlecards in CRM | Monthly + triggered | CRO |\n| Product | Feature gap analysis | Quarterly | CPO |\n| Marketing | Positioning brief | Quarterly | CMO |\n| Leadership | 1-page competitive summary | Monthly | CEO\u002FCOO |\n| Board | Competitive landscape slide | Quarterly | CEO |\n\n**One source of truth:** All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.\n\n---\n\n## Red Flags in Competitive Intelligence\n\n| Signal | What it means |\n|--------|---------------|\n| Competitor's win rate >50% in your core segment | Fundamental positioning problem, not sales problem |\n| Same objection from 5+ deals: \"competitor has X\" | Feature gap that's real, not just optics |\n| Competitor hired 10 engineers in your domain | Major product investment incoming |\n| Competitor raised >$20M and targets your ICP | 12-month runway for them to compete hard |\n| Prospects evaluate you to justify competitor decision | You're the \"check box\" — fix perception or segment |\n\n## Integration with C-Suite Roles\n\n| Intelligence Type | Feeds To | Output Format |\n|------------------|----------|---------------|\n| Product moves | CPO | Roadmap input, feature gap analysis |\n| Pricing changes | CRO, CFO | Pricing response recommendations |\n| Funding rounds | CEO, CFO | Strategic positioning update |\n| Hiring signals | CHRO, CTO | Talent market intelligence |\n| Customer wins\u002Flosses | CRO, CMO | Battlecard updates, positioning shifts |\n| Marketing campaigns | CMO | Counter-positioning, channel intelligence |\n\n## References\n- `references\u002Fci-playbook.md` — OSINT sources, win\u002Floss framework, positioning map construction\n- `templates\u002Fbattlecard-template.md` — sales battlecard template\n","# Competitive Intelligence\n\nSystematic competitor tracking. Not obsession — intelligence that drives real decisions.\n\n## Keywords\ncompetitive intelligence, competitor analysis, battlecard, win\u002Floss analysis, competitive positioning, competitive tracking, market intelligence, competitor research, SWOT, competitive map, feature gap analysis, competitive strategy\n\n## Quick Start\n\n```\n\u002Fci:landscape         — Map your competitive space (direct, indirect, future)\n\u002Fci:battlecard [name] — Build a sales battlecard for a specific competitor\n\u002Fci:winloss           — Analyze recent wins and losses by reason\n\u002Fci:update [name]     — Track what a competitor did recently\n\u002Fci:map               — Build competitive positioning map\n```\n\n## Framework: 5-Layer Intelligence System\n\n### Layer 1: Competitor Identification\n\n**Direct competitors:** Same ICP, same problem, comparable solution, similar price point.\n**Indirect competitors:** Same budget, different solution (including \"do nothing\" and \"build in-house\").\n**Future competitors:** Well-funded startups in adjacent space; large incumbents with stated roadmap overlap.\n\n**The 2x2 Threat Matrix:**\n\n| | Same ICP | Different ICP |\n|---|---|---|\n| **Same problem** | Direct threat | Adjacent (watch) |\n| **Different problem** | Displacement risk | Ignore for now |\n\nUpdate this quarterly. Who's moved quadrants?\n\n### Layer 2: Tracking Dimensions\n\nTrack these 8 dimensions per competitor:\n\n| Dimension | Sources | Cadence |\n|-----------|---------|---------|\n| **Product moves** | Changelog, G2\u002FCapterra reviews, Twitter\u002FLinkedIn | Monthly |\n| **Pricing changes** | Pricing page, sales call intel, customer feedback | Triggered |\n| **Funding** | Crunchbase, TechCrunch, LinkedIn | Triggered |\n| **Hiring signals** | LinkedIn job postings, Indeed | Monthly |\n| **Partnerships** | Press releases, co-marketing | Triggered |\n| **Customer wins** | Case studies, review sites, LinkedIn | Monthly |\n| **Customer losses** | Win\u002Floss interviews, churned accounts | Ongoing |\n| **Messaging shifts** | Homepage, ads (Facebook\u002FGoogle Ad Library) | Quarterly |\n\n### Layer 3: Analysis Frameworks\n\n**SWOT per Competitor:**\n- Strengths: What do they do well? Where do they win?\n- Weaknesses: Where do they lose? What do customers complain about?\n- Opportunities: What could they do that would threaten you?\n- Threats: What's their existential risk?\n\n**Competitive Positioning Map (2 axis):**\nChoose axes that matter for your buyers:\n- Common: Price vs Feature Depth; Enterprise-ready vs SMB-ready; Easy to implement vs Configurable\n- Pick axes that show YOUR differentiation clearly\n\n**Feature Gap Analysis:**\n| Feature | You | Competitor A | Competitor B | Gap status |\n|---------|-----|-------------|-------------|------------|\n| [Feature] | ✅ | ✅ | ❌ | Your advantage |\n| [Feature] | ❌ | ✅ | ✅ | Gap — roadmap? |\n| [Feature] | ✅ | ❌ | ❌ | Moat |\n| [Feature] | ❌ | ❌ | ✅ | Competitor B only |\n\n### Layer 4: Output Formats\n\n**For Sales (CRO):** Battlecards — one page per competitor, designed for pre-call prep.\nSee `templates\u002Fbattlecard-template.md`\n\n**For Marketing (CMO):** Positioning update — message shifts, new differentiators, claims to stop or start making.\n\n**For Product (CPO):** Feature gap summary — what customers ask for that we don't have, what competitors ship, what to reprioritize.\n\n**For CEO\u002FBoard:** Monthly competitive summary — 1-page: who moved, what it means, recommended responses.\n\n### Layer 5: Intelligence Cadence\n\n**Monthly (scheduled):**\n- Review all tier-1 competitors (direct threats, top 3)\n- Update battlecards with new intel\n- Publish 1-page summary to leadership\n\n**Triggered (event-based):**\n- Competitor raises funding → assess implications within 48 hours\n- Competitor launches major feature → product + sales response within 1 week\n- Competitor poaches key customer → win\u002Floss interview within 2 weeks\n- Competitor changes pricing → analyze and respond within 1 week\n\n**Quarterly:**\n- Full competitive landscape review\n- Update positioning map\n- Refresh ICP competitive threat assessment\n- Add\u002Fremove companies from tracking list\n\n---\n\n## Win\u002FLoss Analysis\n\nThis is the highest-signal competitive data you have. Most companies do it too rarely.\n\n**When to interview:**\n- Every lost deal >$50K ACV\n- Every churn >6 months tenure\n- Every competitive win (learn why — it may not be what you think)\n\n**Who conducts it:**\n- NOT the AE who worked the deal (too close, prospect won't be candid)\n- Customer success, product team, or external researcher\n\n**Question structure:**\n1. \"Walk me through your evaluation process\"\n2. \"Who else were you considering?\"\n3. \"What were the top 3 criteria in your decision?\"\n4. \"Where did [our product] fall short?\"\n5. \"What was the deciding factor?\"\n6. \"What would have changed your decision?\"\n\n**Aggregate findings monthly:**\n- Win reasons (rank by frequency)\n- Loss reasons (rank by frequency)\n- Competitor win rates (by competitor, by segment)\n- Patterns over time\n\n---\n\n## The Balance: Intelligence Without Obsession\n\n**Signs you're over-tracking competitors:**\n- Roadmap decisions are primarily driven by \"they just shipped X\"\n- Team morale drops when competitors fundraise\n- You're shipping features you don't believe in to match their checklist\n- Pricing discussions always start with \"well, they charge X\"\n\n**Signs you're under-tracking:**\n- Your AEs get blindsided on calls\n- Prospects know more about competitors than your team does\n- You missed a major product launch until customers told you\n- Your positioning hasn't changed in 12+ months despite market moves\n\n**The right posture:**\n- Know competitors well enough to win against them\n- Don't let them set your agenda\n- Your roadmap is led by customer problems, informed by competitive gaps\n\n---\n\n## Distributing Intelligence\n\n| Audience | Format | Cadence | Owner |\n|----------|--------|---------|-------|\n| AEs + SDRs | Updated battlecards in CRM | Monthly + triggered | CRO |\n| Product | Feature gap analysis | Quarterly | CPO |\n| Marketing | Positioning brief | Quarterly | CMO |\n| Leadership | 1-page competitive summary | Monthly | CEO\u002FCOO |\n| Board | Competitive landscape slide | Quarterly | CEO |\n\n**One source of truth:** All competitive intel lives in one place (Notion, Confluence, Salesforce). Avoid Slack-only distribution — it disappears.\n\n---\n\n## Red Flags in Competitive Intelligence\n\n| Signal | What it means |\n|--------|---------------|\n| Competitor's win rate >50% in your core segment | Fundamental positioning problem, not sales problem |\n| Same objection from 5+ deals: \"competitor has X\" | Feature gap that's real, not just optics |\n| Competitor hired 10 engineers in your domain | Major product investment incoming |\n| Competitor raised >$20M and targets your ICP | 12-month runway for them to compete hard |\n| Prospects evaluate you to justify competitor decision | You're the \"check box\" — fix perception or segment |\n\n## Integration with C-Suite Roles\n\n| Intelligence Type | Feeds To | Output Format |\n|------------------|----------|---------------|\n| Product moves | CPO | Roadmap input, feature gap analysis |\n| Pricing changes | CRO, CFO | Pricing response recommendations |\n| Funding rounds | CEO, CFO | Strategic positioning update |\n| Hiring signals | CHRO, CTO | Talent market intelligence |\n| Customer wins\u002Flosses | CRO, CMO | Battlecard updates, positioning shifts |\n| Marketing campaigns | CMO | Counter-positioning, channel intelligence |\n\n## References\n- `references\u002Fci-playbook.md` — OSINT sources, win\u002Floss framework, positioning map construction\n- `templates\u002Fbattlecard-template.md` — sales battlecard template\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29},"Alireza Rezvani","competitive-strategy",1772668800000,"1.0.0","c-level","ci-playbook, battlecard-template","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fcompetitive-intel","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ASoudy\u002FAGS --skill competitive-intel",{"tool":42,"command":43},"bunx","bunx skills add ASoudy\u002FAGS --skill competitive-intel",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill competitive-intel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fcompetitive-intel\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fci-playbook.md","REFERENCE","参考文档",9978,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fcompetitive-intel\u002Freferences\u002Fci-playbook.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"templates\u002Fbattlecard-template.md",3589,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fcompetitive-intel\u002Ftemplates\u002Fbattlecard-template.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]