[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PYY2EGHVT17CANDQJKS522":3,"skill-same:01M6PYY2EGHVT17CANDQJKS522":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6PYY2EGHVT17CANDQJKS522","gtm-developer-ecosystem",null,"Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.","ibragimov-oasis\u002Fvibe-coder","ibragimov-oasis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F240665573?v=4","01M6DF78Y45R8228FHAZ7G6JXM","IBRAGIMOV MUKHAMMADJON","01M6K5ZYR8TDPAFG4R6693E2A6",3,"MIT","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-copilot\u002Fgtm-developer-ecosystem\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"developer","gtm developer ecosystem","ecosystem","gtm","artifact","student","source","source\u002Fskills-copilot","domain\u002Fagents","platform","scaling","ecosystems","copilot","domain","use","technical","linkedin","open","adoption","product","2026-11-10 10:12:30",false,"---\nname: gtm-developer-ecosystem\ndescription: Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.\nlicense: MIT\nmetadata:\n  author: Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)\n  source: https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm\ntags:\n  - domain\u002Fagents\n  - artifact\u002Fskill\n  - source\u002Fskills-copilot\n---\n\n# Developer Ecosystem\n\nBuild and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.\n\n## When to Use\n\n**Triggers:**\n- \"How do we build a developer ecosystem?\"\n- \"Should we curate quality or go open?\"\n- \"Developer community isn't growing\"\n- \"Nobody's building on our API\"\n- \"How do we compete with larger platforms?\"\n\n**Context:**\n- API platforms and developer tools\n- Products with extensibility (plugins, integrations)\n- Developer-first GTM motion\n- Platform business models\n\n---\n\n## Core Frameworks\n\n### 1. Open vs Curated Ecosystem (The Marketplace Decision)\n\n**The Pattern:**\n\nRunning ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality?\n\n**Quality control camp:** \"We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage.\"\n\n**Open camp:** \"Developers route around gatekeepers. Network effects matter more than quality control.\"\n\n**The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping.\n\n**What We Built Instead of Gatekeeping:**\n\n1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation\n2. **Trust signals** — Verified badges, usage stats, health scores\n3. **Community curation** — User ratings, collections, recommendations\n4. **Moderation** — Remove spam after publication, not block before\n\n**Result:** Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.\n\n**Decision Framework:**\n- **Curated** works when: Brand risk high, dozens of partners, can scale human review\n- **Open** works when: Hundreds\u002Fthousands of potential partners, network effects matter more than quality control\n\n**Common Mistake:**\n\nDefaulting to curated because \"we need quality control.\" This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead.\n\n---\n\n### 2. The Three-Year Student Program Arc\n\n**The Pattern:**\n\nMost developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.\n\n**Year 1: University Partnerships**\n- Partner with CS departments\n- Curriculum integration (hackathons, coursework)\n- Student licenses (free or heavily discounted)\n- Metrics: # universities, # students activated\n\n**Year 2: Student Community & Certification**\n- Student expert certification program\n- Student-led workshops and events\n- Campus ambassadors\n- Metrics: # certified, # student-led events\n\n**Year 3: Career Bridge**\n- Job board connecting students → companies\n- Enterprise partnerships (hire certified students)\n- Alumni network\n- Metrics: # hired, company partnerships\n\n**Why This Works:**\n\nStudents become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.\n\n**Common Mistake:**\n\nTreating students as immediate revenue. They're not. They're future enterprise decision-makers.\n\n---\n\n### 3. Developer Journey (Awareness → Integration → Advocacy)\n\n**Stage 1: Awareness**\n- How do they discover you?\n- Content, search, word-of-mouth, events\n\n**Stage 2: Onboarding**\n- First API call in \u003C10 minutes\n- Quick-start guides\n- Sample code in popular languages\n\n**Stage 3: Integration**\n- Building real use cases\n- Integration guides\n- Support when stuck\n\n**Stage 4: Production**\n- Deployed and generating value\n- Monitoring usage\n- Enterprise upgrade path\n\n**Stage 5: Advocacy**\n- Sharing publicly\n- Recommending to others\n- Contributing back (docs, code, community)\n\n**Metrics That Matter:**\n- Time to first API call (onboarding)\n- % reaching production (integration success)\n- Monthly active developers (engagement)\n- Developer NPS (advocacy)\n\n**Common Mistake:**\n\nMeasuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).\n\n---\n\n### 4. Documentation Hierarchy\n\n**Tier 1: Quick Starts (Get to Value Fast)**\n- \"Hello World\" in 5 minutes\n- Common use case examples\n- Copy-paste code that works\n\n**Tier 2: Guides (Solve Real Problems)**\n- Use case-specific tutorials\n- Integration patterns\n- Best practices\n\n**Tier 3: Reference (Complete API Docs)**\n- Every endpoint documented\n- Request\u002Fresponse examples\n- Error codes and handling\n\n**Tier 4: Conceptual (Understand the System)**\n- Architecture overviews\n- Design philosophy\n- Advanced patterns\n\n**Most developers need:** Tier 1 first, then Tier 2. Very few read Tier 4.\n\n**Common Mistake:**\n\nStarting with Tier 3 (comprehensive API reference). Developers want quick wins first.\n\n---\n\n### 5. Community vs Support (When to Use Which)\n\n**Community (Async, Scalable):**\n- Slack\u002FDiscord for real-time help\n- Forum for searchable Q&A\n- GitHub discussions for feature requests\n- Best for: Common questions, peer-to-peer help\n\n**Support (Sync, Expensive):**\n- Email support for enterprise\n- Dedicated Slack channels for partners\n- Video calls for complex integrations\n- Best for: Paying customers, strategic partners\n\n**How to Route:**\n\n**Community first:**\n- Developer asks question\n- Community member answers\n- You validate and upvote\n- Searchable for future developers\n\n**Escalate to support when:**\n- No community answer in 24 hours\n- Enterprise\u002Fpaying customer\n- Security or compliance issue\n- Complex integration requiring custom work\n\n**Common Mistake:**\n\nProviding white-glove support to everyone. Doesn't scale. Build community that helps itself.\n\n---\n\n### 6. Partner Tiering for Developer Ecosystems\n\n**Tier 1: Integration Partners (Self-Serve)**\n- Build with public API\n- You provide: docs, Slack channel, office hours\n- They drive their own marketing\n- Best for: Ambitious partners with resources\n\n**Tier 2: Strategic Partners (Co-Development)**\n- Co-developed integration\n- You provide: dedicated channel, co-marketing\n- Joint case studies\n- Best for: High-impact integrations\n\n**Don't over-tier.** 2 tiers is enough. More creates confusion.\n\n---\n\n## Decision Trees\n\n### Open or Curated Ecosystem?\n\n```\nIs brand damage risk high if low-quality partners join?\n├─ Yes (regulated, security) → Curated\n└─ No → Continue...\n    │\n    Can you scale human review?\n    ├─ No (hundreds\u002Fthousands) → Open + discovery systems\n    └─ Yes (dozens) → Curated\n```\n\n### Community or Support?\n\n```\nIs this a common question?\n├─ Yes → Community (forum, Slack, docs)\n└─ No → Continue...\n    │\n    Is requester paying customer?\n    ├─ Yes → Support (email, dedicated)\n    └─ No → Community (with escalation path)\n```\n\n---\n\n## Common Mistakes\n\n**1. Building ecosystem before product-market fit**\n   - Fix core product first, then build ecosystem\n\n**2. No developer success team**\n   - Developers need help to succeed beyond docs\n\n**3. Poor documentation**\n   - Foundation of ecosystem, non-negotiable\n\n**4. Treating all developers equally**\n   - Tier support by strategic value (paying > free, partners > hobbyists)\n\n**5. No integration quality standards**\n   - Low-quality integrations hurt your brand\n\n**6. Measuring only vanity metrics**\n   - Track activation and production usage, not just sign-ups\n\n**7. Developer advocates with no technical depth**\n   - Hire developers who can code and teach\n\n---\n\n## Quick Reference\n\n**Open ecosystem checklist:**\n- [ ] Search and discovery (surface quality algorithmically)\n- [ ] Trust signals (verified badges, usage stats, ratings)\n- [ ] Community curation (user recommendations, collections)\n- [ ] Moderation (remove spam after publication)\n\n**Developer journey metrics:**\n- Awareness: Traffic, sign-ups\n- Onboarding: Time to first API call (\u003C10 min target)\n- Integration: % reaching production deployment\n- Advocacy: Developer NPS, public sharing\n\n**Documentation hierarchy:**\n1. Quick starts (5-min \"Hello World\")\n2. Use case guides (solve real problems)\n3. API reference (complete documentation)\n4. Conceptual (architecture, philosophy)\n\n**Partner tiers:**\n- Tier 1: Self-serve (public API, docs, community)\n- Tier 2: Strategic (co-development, co-marketing)\n\n**Student program timeline:**\n- Year 1: University partnerships, activation\n- Year 2: Certification, student community\n- Year 3: Job board, enterprise hiring bridge\n\n---\n\n## Related Skills\n\n- **partnership-architecture**: Partner deal structures and co-marketing\n- **product-led-growth**: Self-serve activation funnels for developer products\n- **0-to-1-launch**: Launching developer products\n\n---\n\n*Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.*\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-copilot]] — Category: skills-copilot\n- [[MOC - Agents]] — Copilot agents\n\n","# Developer Ecosystem\n\nBuild and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.\n\n## When to Use\n\n**Triggers:**\n- \"How do we build a developer ecosystem?\"\n- \"Should we curate quality or go open?\"\n- \"Developer community isn't growing\"\n- \"Nobody's building on our API\"\n- \"How do we compete with larger platforms?\"\n\n**Context:**\n- API platforms and developer tools\n- Products with extensibility (plugins, integrations)\n- Developer-first GTM motion\n- Platform business models\n\n---\n\n## Core Frameworks\n\n### 1. Open vs Curated Ecosystem (The Marketplace Decision)\n\n**The Pattern:**\n\nRunning ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality?\n\n**Quality control camp:** \"We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage.\"\n\n**Open camp:** \"Developers route around gatekeepers. Network effects matter more than quality control.\"\n\n**The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping.\n\n**What We Built Instead of Gatekeeping:**\n\n1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation\n2. **Trust signals** — Verified badges, usage stats, health scores\n3. **Community curation** — User ratings, collections, recommendations\n4. **Moderation** — Remove spam after publication, not block before\n\n**Result:** Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.\n\n**Decision Framework:**\n- **Curated** works when: Brand risk high, dozens of partners, can scale human review\n- **Open** works when: Hundreds\u002Fthousands of potential partners, network effects matter more than quality control\n\n**Common Mistake:**\n\nDefaulting to curated because \"we need quality control.\" This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead.\n\n---\n\n### 2. The Three-Year Student Program Arc\n\n**The Pattern:**\n\nMost developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.\n\n**Year 1: University Partnerships**\n- Partner with CS departments\n- Curriculum integration (hackathons, coursework)\n- Student licenses (free or heavily discounted)\n- Metrics: # universities, # students activated\n\n**Year 2: Student Community & Certification**\n- Student expert certification program\n- Student-led workshops and events\n- Campus ambassadors\n- Metrics: # certified, # student-led events\n\n**Year 3: Career Bridge**\n- Job board connecting students → companies\n- Enterprise partnerships (hire certified students)\n- Alumni network\n- Metrics: # hired, company partnerships\n\n**Why This Works:**\n\nStudents become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.\n\n**Common Mistake:**\n\nTreating students as immediate revenue. They're not. They're future enterprise decision-makers.\n\n---\n\n### 3. Developer Journey (Awareness → Integration → Advocacy)\n\n**Stage 1: Awareness**\n- How do they discover you?\n- Content, search, word-of-mouth, events\n\n**Stage 2: Onboarding**\n- First API call in \u003C10 minutes\n- Quick-start guides\n- Sample code in popular languages\n\n**Stage 3: Integration**\n- Building real use cases\n- Integration guides\n- Support when stuck\n\n**Stage 4: Production**\n- Deployed and generating value\n- Monitoring usage\n- Enterprise upgrade path\n\n**Stage 5: Advocacy**\n- Sharing publicly\n- Recommending to others\n- Contributing back (docs, code, community)\n\n**Metrics That Matter:**\n- Time to first API call (onboarding)\n- % reaching production (integration success)\n- Monthly active developers (engagement)\n- Developer NPS (advocacy)\n\n**Common Mistake:**\n\nMeasuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).\n\n---\n\n### 4. Documentation Hierarchy\n\n**Tier 1: Quick Starts (Get to Value Fast)**\n- \"Hello World\" in 5 minutes\n- Common use case examples\n- Copy-paste code that works\n\n**Tier 2: Guides (Solve Real Problems)**\n- Use case-specific tutorials\n- Integration patterns\n- Best practices\n\n**Tier 3: Reference (Complete API Docs)**\n- Every endpoint documented\n- Request\u002Fresponse examples\n- Error codes and handling\n\n**Tier 4: Conceptual (Understand the System)**\n- Architecture overviews\n- Design philosophy\n- Advanced patterns\n\n**Most developers need:** Tier 1 first, then Tier 2. Very few read Tier 4.\n\n**Common Mistake:**\n\nStarting with Tier 3 (comprehensive API reference). Developers want quick wins first.\n\n---\n\n### 5. Community vs Support (When to Use Which)\n\n**Community (Async, Scalable):**\n- Slack\u002FDiscord for real-time help\n- Forum for searchable Q&A\n- GitHub discussions for feature requests\n- Best for: Common questions, peer-to-peer help\n\n**Support (Sync, Expensive):**\n- Email support for enterprise\n- Dedicated Slack channels for partners\n- Video calls for complex integrations\n- Best for: Paying customers, strategic partners\n\n**How to Route:**\n\n**Community first:**\n- Developer asks question\n- Community member answers\n- You validate and upvote\n- Searchable for future developers\n\n**Escalate to support when:**\n- No community answer in 24 hours\n- Enterprise\u002Fpaying customer\n- Security or compliance issue\n- Complex integration requiring custom work\n\n**Common Mistake:**\n\nProviding white-glove support to everyone. Doesn't scale. Build community that helps itself.\n\n---\n\n### 6. Partner Tiering for Developer Ecosystems\n\n**Tier 1: Integration Partners (Self-Serve)**\n- Build with public API\n- You provide: docs, Slack channel, office hours\n- They drive their own marketing\n- Best for: Ambitious partners with resources\n\n**Tier 2: Strategic Partners (Co-Development)**\n- Co-developed integration\n- You provide: dedicated channel, co-marketing\n- Joint case studies\n- Best for: High-impact integrations\n\n**Don't over-tier.** 2 tiers is enough. More creates confusion.\n\n---\n\n## Decision Trees\n\n### Open or Curated Ecosystem?\n\n```\nIs brand damage risk high if low-quality partners join?\n├─ Yes (regulated, security) → Curated\n└─ No → Continue...\n    │\n    Can you scale human review?\n    ├─ No (hundreds\u002Fthousands) → Open + discovery systems\n    └─ Yes (dozens) → Curated\n```\n\n### Community or Support?\n\n```\nIs this a common question?\n├─ Yes → Community (forum, Slack, docs)\n└─ No → Continue...\n    │\n    Is requester paying customer?\n    ├─ Yes → Support (email, dedicated)\n    └─ No → Community (with escalation path)\n```\n\n---\n\n## Common Mistakes\n\n**1. Building ecosystem before product-market fit**\n   - Fix core product first, then build ecosystem\n\n**2. No developer success team**\n   - Developers need help to succeed beyond docs\n\n**3. Poor documentation**\n   - Foundation of ecosystem, non-negotiable\n\n**4. Treating all developers equally**\n   - Tier support by strategic value (paying > free, partners > hobbyists)\n\n**5. No integration quality standards**\n   - Low-quality integrations hurt your brand\n\n**6. Measuring only vanity metrics**\n   - Track activation and production usage, not just sign-ups\n\n**7. Developer advocates with no technical depth**\n   - Hire developers who can code and teach\n\n---\n\n## Quick Reference\n\n**Open ecosystem checklist:**\n- [ ] Search and discovery (surface quality algorithmically)\n- [ ] Trust signals (verified badges, usage stats, ratings)\n- [ ] Community curation (user recommendations, collections)\n- [ ] Moderation (remove spam after publication)\n\n**Developer journey metrics:**\n- Awareness: Traffic, sign-ups\n- Onboarding: Time to first API call (\u003C10 min target)\n- Integration: % reaching production deployment\n- Advocacy: Developer NPS, public sharing\n\n**Documentation hierarchy:**\n1. Quick starts (5-min \"Hello World\")\n2. Use case guides (solve real problems)\n3. API reference (complete documentation)\n4. Conceptual (architecture, philosophy)\n\n**Partner tiers:**\n- Tier 1: Self-serve (public API, docs, community)\n- Tier 2: Strategic (co-development, co-marketing)\n\n**Student program timeline:**\n- Year 1: University partnerships, activation\n- Year 2: Certification, student community\n- Year 3: Job board, enterprise hiring bridge\n\n---\n\n## Related Skills\n\n- **partnership-architecture**: Partner deal structures and co-marketing\n- **product-led-growth**: Self-serve activation funnels for developer products\n- **0-to-1-launch**: Launching developer products\n\n---\n\n*Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.*\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-copilot]] — Category: skills-copilot\n- [[MOC - Agents]] — Copilot agents\n\n",{"name":5,"tags":49,"license":15,"metadata":51,"description":7},[32,50,31],"artifact\u002Fskill",{"author":52,"source":53},"Smit Patel (https:\u002F\u002Flinkedin.com\u002Fin\u002Fsmitkpatel)","https:\u002F\u002Fgithub.com\u002Fbeingsmit\u002Ftechnical-product-gtm","main","bdd9f958d7bb1a0f19b8ad8da020b0bab0f53eb1","vc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-copilot\u002Fgtm-developer-ecosystem",1,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis","2026-06-24 16:31:18",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add ibragimov-oasis\u002Fvibe-coder --skill gtm-developer-ecosystem",{"tool":67,"command":68},"bunx","bunx skills add ibragimov-oasis\u002Fvibe-coder --skill gtm-developer-ecosystem",{"tool":70,"command":71},"pnpm","pnpm dlx skills add ibragimov-oasis\u002Fvibe-coder --skill gtm-developer-ecosystem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-copilot\u002Fgtm-developer-ecosystem\u002FSKILL.md",true,[],[76,111,137,157,183,214],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":90,"publishedAt":44},"01M6Q4Q22KKKVMJJYA411DQ4ER","ckm:ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fui-styling\u002FSKILL.md",[82,87],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110],"ui styling","ui","styling","ckm:ui styling","ckm","design","css","canvas","components","component","create","design systems","Tailwind","across","themes","utility","mode","implementing","artifact\u002Fui-component","source\u002Fui-design",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":125,"publishedAt":44},"01M6Q4PQ2NX4NDVWTEHA3MQ2R0","ckm:design","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign\u002FSKILL.md",[117,120,121,124],{"categoryNo":118,"categoryName":119,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":122,"categoryName":123,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[96,113,95,126,100,91,127,101,128,129,130,131,132,133,134,135,28,136,109,110],"google","presentations","generate","screenshot","actions","Media","logo","ads","youtube","tiktok","chart",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":44},"01M6Q4PJE27GEA3M0CECEBCZKS","ckm:design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fdesign-system\u002FSKILL.md",[143,144],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[96,146,147,148,113,95,97,100,149,127,28,150,151,152,153,154,155,156,109,110],"design system","system","ckm:design system","architecture","token","creation","systematic","css variables","Variables","spacing","layer",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":168,"publishedAt":44},"01M6Q4P90JXFYMH2S634QM6SQJ","ckm:banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fui-design\u002Fui-rules\u002Fui-ux-pro-max\u002Fclaude\u002Fskills\u002Fbanner-design\u002FSKILL.md",[163,166,167],{"categoryNo":164,"categoryName":165,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[96,169,170,171,95,172,130,131,173,174,175,176,177,178,179,180,109,110,181,182],"banner design","ckm:banner design","banner","frontend","3D","generated","Art","social","dimensions","neon","direction","display","frontend-design","hero",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":44},"01M6Q2RZXBJ9TBE413GXCYQNDB","seo","Comprehensive SEO analysis for any website or business type. Performs full site audits, single-page deep analysis, technical SEO checks (crawlability, indexability, Core Web Vitals with INP), schema markup detection\u002Fvalidation\u002Fgeneration, content quality assessment (E-E-A-T framework per Dec 2025 update extending to all competitive queries), image optimization, sitemap analysis, and Generative Engine Optimization (GEO) for AI Overviews, ChatGPT, and Perplexity citations. Analyzes AI crawler accessibility (GPTBot, ClaudeBot, PerplexityBot), llms.txt compliance, brand mention signals, and passage-level citability. Industry detection for SaaS, e-commerce, local business, publishers, agencies. Triggers on: \"SEO\", \"audit\", \"schema\", \"Core Web Vitals\", \"sitemap\", \"E-E-A-T\", \"AI Overviews\", \"GEO\", \"technical SEO\", \"content quality\", \"page speed\", \"structured data\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000035","市场营销",[185,196,197,198,199,200,201,28,202,203,204,205,206,207,208,209,210,211,212,213],"image","llms","assessment","deep analysis","Citations","analysis","local","deep","crawlability","seo analysis","2025","commerce","URL","domain\u002Fseo","source\u002Fskills-seo","vitals","generative","publishers",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":222,"publishedAt":44},"01M6Q2RVE7VGFCFQKBK468NHVY","seo-technical","Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says \"technical SEO\", \"crawl issues\", \"robots.txt\", \"Core Web Vitals\", \"site speed\", or \"security headers\".","https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-seo\u002Fseo\u002Fclaude-seo\u002Fskills\u002Fseo-technical\u002FSKILL.md",[220,221],{"categoryNo":190,"categoryName":191,"taxonomyType":85,"taxonomyTypeDesc":86},{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},[185,39,223,224,225,226,227,228,229,28,104,204,230,231,208,232,233,209,210,211],"seo technical","issues","audit","data","mobile","crawl","structure","rendering","technical seo audit","headers","categories"]