[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N5V554SC5R5X0MSWSEJWM7":3,"skill-same:01M6N5V554SC5R5X0MSWSEJWM7":89},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6N5V554SC5R5X0MSWSEJWM7","scenario-war-room",null,"Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'","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-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fscenario-war-room\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"war room","scenario war room","scenario","artifact","source","for","strategic","functional","stress","modeling","across","testing","domain","functions","use","business","decisions","risk","planning","stress testing","2026-11-10 10:12:30",false,"---\nname: \"scenario-war-room\"\ndescription: \"Cross-functional what-if modeling for cascading multi-variable scenarios. Unlike single-assumption stress testing, this models compound adversity across all business functions simultaneously. Use when facing complex risk scenarios, strategic decisions with major downside, or when the user asks 'what if X AND Y both happen?'\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: strategic-planning\n  updated: 2026-03-05\n  python-tools: scenario_modeler.py\n  frameworks: scenario-planning\ntags:\n  - domain\u002Fagents\n  - artifact\u002Fskill\n  - source\u002Fskills-claude\n---\n\n# Scenario War Room\n\nModel cascading what-if scenarios across all business functions. Not single-assumption stress tests — compound adversity that shows how one problem creates the next.\n\n## Keywords\nscenario planning, war room, what-if analysis, risk modeling, cascading effects, compound risk, adversity planning, contingency planning, stress test, crisis planning, multi-variable scenario, pre-mortem\n\n## Quick Start\n\n```bash\npython scripts\u002Fscenario_modeler.py   # Interactive scenario builder with cascade modeling\n```\n\nOr describe the scenario:\n```\n\u002Fwar-room \"What if we lose our top customer AND miss the Q3 fundraise?\"\n\u002Fwar-room \"What if 3 engineers quit AND we need to ship by Q3?\"\n\u002Fwar-room \"What if our market shrinks 30% AND a competitor raises $50M?\"\n```\n\n## What This Is Not\n\n- **Not** a single-assumption stress test (that's `\u002Fem:stress-test`)\n- **Not** financial modeling only — every function gets modeled\n- **Not** worst-case-only — models 3 severity levels\n- **Not** paralysis by analysis — outputs concrete hedges and triggers\n\n## Framework: 6-Step Cascade Model\n\n### Step 1: Define Scenario Variables (max 3)\nState each variable with:\n- **What changes** — specific, quantified if possible\n- **Probability** — your best estimate\n- **Timeline** — when it hits\n\n```\nVariable A: Top customer (28% ARR) gives 60-day termination notice\n  Probability: 15% | Timeline: Within 90 days\n\nVariable B: Series A fundraise delayed 6 months beyond target close\n  Probability: 25% | Timeline: Q3\n\nVariable C: Lead engineer resigns\n  Probability: 20% | Timeline: Unknown\n```\n\n### Step 2: Domain Impact Mapping\n\nFor each variable, each relevant role models impact:\n\n| Domain | Owner | Models |\n|--------|-------|--------|\n| Cash & runway | CFO | Burn impact, runway change, bridge options |\n| Revenue | CRO | ARR gap, churn cascade risk, pipeline |\n| Product | CPO | Roadmap impact, PMF risk |\n| Engineering | CTO | Velocity impact, key person risk |\n| People | CHRO | Attrition cascade, hiring freeze implications |\n| Operations | COO | Capacity, OKR impact, process risk |\n| Security | CISO | Compliance timeline risk |\n| Market | CMO | CAC impact, competitive exposure |\n\n### Step 3: Cascade Effect Mapping\n\nThis is the core. Show how Variable A triggers consequences in domains that trigger Variable B's effects:\n\n```\nTRIGGER: Customer churn ($560K ARR)\n  ↓\nCFO: Runway drops 14 → 8 months\n  ↓\nCHRO: Hiring freeze; retention risk increases (morale hit)\n  ↓\nCTO: 3 open engineering reqs frozen; roadmap slips\n  ↓\nCPO: Q4 feature launch delayed → customer retention risk\n  ↓\nCRO: NRR drops; existing accounts see reduced velocity → more churn risk\n  ↓\nCFO: [Secondary cascade — potential death spiral if not interrupted]\n```\n\nName the cascade explicitly. Show where it can be interrupted.\n\n### Step 4: Severity Matrix\n\nModel three scenarios:\n\n| Scenario | Definition | Recovery |\n|----------|------------|---------|\n| **Base** | One variable hits; others don't | Manageable with plan |\n| **Stress** | Two variables hit simultaneously | Requires significant response |\n| **Severe** | All variables hit; full cascade | Existential; requires board intervention |\n\nFor each severity level:\n- Runway impact\n- ARR impact\n- Headcount impact\n- Timeline to unacceptable state (trigger point)\n\n### Step 5: Trigger Points (Early Warning Signals)\n\nDefine the measurable signal that tells you a scenario is unfolding **before** it's confirmed:\n\n```\nTrigger for Customer Churn Risk:\n  - Sponsor goes dark for >3 weeks\n  - Usage drops >25% MoM\n  - No Q1 QBR confirmed by Dec 1\n\nTrigger for Fundraise Delay:\n  - \u003C3 term sheets after 60 days of process\n  - Lead investor requests >30-day extension on DD\n  - Competitor raises at lower valuation (market signal)\n\nTrigger for Engineering Attrition:\n  - Glassdoor activity from engineering team\n  - 2+ referral interview requests from engineers\n  - Above-market offer counter-required in last 3 months\n```\n\n### Step 6: Hedging Strategies\n\nFor each scenario: actions to take **now** (before the scenario materializes) that reduce impact if it does.\n\n| Hedge | Cost | Impact | Owner | Deadline |\n|-------|------|--------|-------|---------|\n| Establish $500K credit line | $5K\u002Fyear | Buys 3 months if churn hits | CFO | 60 days |\n| 12-month retention bonus for 3 key engineers | $90K | Locks team through fundraise | CHRO | 30 days |\n| Diversify to \u003C20% revenue concentration per customer | Sales effort | Reduces single-customer risk | CRO | 2 quarters |\n| Compress fundraise timeline, start parallel process | CEO time | Closes before runways merge | CEO | Immediate |\n\n---\n\n## Output Format\n\nEvery war room session produces:\n\n```\nSCENARIO: [Name]\nVariables: [A, B, C]\nMost likely path: [which combination actually plays out, with probability]\n\nSEVERITY LEVELS\nBase (A only): [runway\u002FARR impact] — recovery: [X actions]\nStress (A+B): [runway\u002FARR impact] — recovery: [X actions]\nSevere (A+B+C): [runway\u002FARR impact] — existential risk: [yes\u002Fno]\n\nCASCADE MAP\n[A → domain impact → B trigger → domain impact → end state]\n\nEARLY WARNING SIGNALS\n- [Signal 1 → which scenario it indicates]\n- [Signal 2 → which scenario it indicates]\n- [Signal 3 → which scenario it indicates]\n\nHEDGES (take these actions now)\n1. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n2. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n3. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n\nRECOMMENDED DECISION\n[One paragraph. What to do, in what order, and why.]\n```\n\n---\n\n## Rules for Good War Room Sessions\n\n**Max 3 variables per scenario.** More than 3 is noise — you can't meaningfully prepare for 5-variable collapse. Model the 3 that actually worry you.\n\n**Quantify or estimate.** \"Revenue drops\" is not useful. \"$420K ARR at risk over 60 days\" is. Use ranges if uncertain.\n\n**Don't stop at first-order effects.** The damage is always in the cascade, not the initial hit.\n\n**Model recovery, not just impact.** Every scenario should have a \"what we do\" path.\n\n**Separate base case from sensitivity.** Don't conflate \"what probably happens\" with \"what could happen.\"\n\n**Don't over-model.** 3-4 scenarios per planning cycle is the right number. More creates analysis paralysis.\n\n---\n\n## Common Scenarios by Stage\n\n**Seed:**\n- Co-founder leaves + product misses launch\n- Funding runs out + bridge terms unfavorable\n\n**Series A:**\n- Miss ARR target + fundraise delayed\n- Key customer churns + competitor raises\n\n**Series B:**\n- Market contraction + burn multiple spikes\n- Lead investor wants pivot + team resists\n\n## Integration with C-Suite Roles\n\n| Scenario Type | Primary Roles | Cascade To |\n|--------------|---------------|------------|\n| Revenue miss | CRO, CFO | CMO (pipeline), COO (cuts), CHRO (layoffs) |\n| Key person departure | CHRO, COO | CTO (if eng), CRO (if sales) |\n| Fundraise failure | CFO, CEO | COO (runway extension), CHRO (hiring freeze) |\n| Security breach | CISO, CTO | CEO (comms), CFO (cost), CRO (customer impact) |\n| Market shift | CEO, CPO | CMO (repositioning), CRO (new segments) |\n| Competitor move | CMO, CRO | CPO (roadmap response), CEO (strategy) |\n\n## References\n- `references\u002Fscenario-planning.md` — Shell methodology, pre-mortem, Monte Carlo, cascade frameworks\n- `scripts\u002Fscenario_modeler.py` — CLI tool for structured scenario modeling\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-claude]] — Category: skills-claude\n- [[MOC - Agents]] — Claude agents\n\n","# Scenario War Room\n\nModel cascading what-if scenarios across all business functions. Not single-assumption stress tests — compound adversity that shows how one problem creates the next.\n\n## Keywords\nscenario planning, war room, what-if analysis, risk modeling, cascading effects, compound risk, adversity planning, contingency planning, stress test, crisis planning, multi-variable scenario, pre-mortem\n\n## Quick Start\n\n```bash\npython scripts\u002Fscenario_modeler.py   # Interactive scenario builder with cascade modeling\n```\n\nOr describe the scenario:\n```\n\u002Fwar-room \"What if we lose our top customer AND miss the Q3 fundraise?\"\n\u002Fwar-room \"What if 3 engineers quit AND we need to ship by Q3?\"\n\u002Fwar-room \"What if our market shrinks 30% AND a competitor raises $50M?\"\n```\n\n## What This Is Not\n\n- **Not** a single-assumption stress test (that's `\u002Fem:stress-test`)\n- **Not** financial modeling only — every function gets modeled\n- **Not** worst-case-only — models 3 severity levels\n- **Not** paralysis by analysis — outputs concrete hedges and triggers\n\n## Framework: 6-Step Cascade Model\n\n### Step 1: Define Scenario Variables (max 3)\nState each variable with:\n- **What changes** — specific, quantified if possible\n- **Probability** — your best estimate\n- **Timeline** — when it hits\n\n```\nVariable A: Top customer (28% ARR) gives 60-day termination notice\n  Probability: 15% | Timeline: Within 90 days\n\nVariable B: Series A fundraise delayed 6 months beyond target close\n  Probability: 25% | Timeline: Q3\n\nVariable C: Lead engineer resigns\n  Probability: 20% | Timeline: Unknown\n```\n\n### Step 2: Domain Impact Mapping\n\nFor each variable, each relevant role models impact:\n\n| Domain | Owner | Models |\n|--------|-------|--------|\n| Cash & runway | CFO | Burn impact, runway change, bridge options |\n| Revenue | CRO | ARR gap, churn cascade risk, pipeline |\n| Product | CPO | Roadmap impact, PMF risk |\n| Engineering | CTO | Velocity impact, key person risk |\n| People | CHRO | Attrition cascade, hiring freeze implications |\n| Operations | COO | Capacity, OKR impact, process risk |\n| Security | CISO | Compliance timeline risk |\n| Market | CMO | CAC impact, competitive exposure |\n\n### Step 3: Cascade Effect Mapping\n\nThis is the core. Show how Variable A triggers consequences in domains that trigger Variable B's effects:\n\n```\nTRIGGER: Customer churn ($560K ARR)\n  ↓\nCFO: Runway drops 14 → 8 months\n  ↓\nCHRO: Hiring freeze; retention risk increases (morale hit)\n  ↓\nCTO: 3 open engineering reqs frozen; roadmap slips\n  ↓\nCPO: Q4 feature launch delayed → customer retention risk\n  ↓\nCRO: NRR drops; existing accounts see reduced velocity → more churn risk\n  ↓\nCFO: [Secondary cascade — potential death spiral if not interrupted]\n```\n\nName the cascade explicitly. Show where it can be interrupted.\n\n### Step 4: Severity Matrix\n\nModel three scenarios:\n\n| Scenario | Definition | Recovery |\n|----------|------------|---------|\n| **Base** | One variable hits; others don't | Manageable with plan |\n| **Stress** | Two variables hit simultaneously | Requires significant response |\n| **Severe** | All variables hit; full cascade | Existential; requires board intervention |\n\nFor each severity level:\n- Runway impact\n- ARR impact\n- Headcount impact\n- Timeline to unacceptable state (trigger point)\n\n### Step 5: Trigger Points (Early Warning Signals)\n\nDefine the measurable signal that tells you a scenario is unfolding **before** it's confirmed:\n\n```\nTrigger for Customer Churn Risk:\n  - Sponsor goes dark for >3 weeks\n  - Usage drops >25% MoM\n  - No Q1 QBR confirmed by Dec 1\n\nTrigger for Fundraise Delay:\n  - \u003C3 term sheets after 60 days of process\n  - Lead investor requests >30-day extension on DD\n  - Competitor raises at lower valuation (market signal)\n\nTrigger for Engineering Attrition:\n  - Glassdoor activity from engineering team\n  - 2+ referral interview requests from engineers\n  - Above-market offer counter-required in last 3 months\n```\n\n### Step 6: Hedging Strategies\n\nFor each scenario: actions to take **now** (before the scenario materializes) that reduce impact if it does.\n\n| Hedge | Cost | Impact | Owner | Deadline |\n|-------|------|--------|-------|---------|\n| Establish $500K credit line | $5K\u002Fyear | Buys 3 months if churn hits | CFO | 60 days |\n| 12-month retention bonus for 3 key engineers | $90K | Locks team through fundraise | CHRO | 30 days |\n| Diversify to \u003C20% revenue concentration per customer | Sales effort | Reduces single-customer risk | CRO | 2 quarters |\n| Compress fundraise timeline, start parallel process | CEO time | Closes before runways merge | CEO | Immediate |\n\n---\n\n## Output Format\n\nEvery war room session produces:\n\n```\nSCENARIO: [Name]\nVariables: [A, B, C]\nMost likely path: [which combination actually plays out, with probability]\n\nSEVERITY LEVELS\nBase (A only): [runway\u002FARR impact] — recovery: [X actions]\nStress (A+B): [runway\u002FARR impact] — recovery: [X actions]\nSevere (A+B+C): [runway\u002FARR impact] — existential risk: [yes\u002Fno]\n\nCASCADE MAP\n[A → domain impact → B trigger → domain impact → end state]\n\nEARLY WARNING SIGNALS\n- [Signal 1 → which scenario it indicates]\n- [Signal 2 → which scenario it indicates]\n- [Signal 3 → which scenario it indicates]\n\nHEDGES (take these actions now)\n1. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n2. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n3. [Action] — cost: $X — impact: [what it buys] — owner: [role] — deadline: [date]\n\nRECOMMENDED DECISION\n[One paragraph. What to do, in what order, and why.]\n```\n\n---\n\n## Rules for Good War Room Sessions\n\n**Max 3 variables per scenario.** More than 3 is noise — you can't meaningfully prepare for 5-variable collapse. Model the 3 that actually worry you.\n\n**Quantify or estimate.** \"Revenue drops\" is not useful. \"$420K ARR at risk over 60 days\" is. Use ranges if uncertain.\n\n**Don't stop at first-order effects.** The damage is always in the cascade, not the initial hit.\n\n**Model recovery, not just impact.** Every scenario should have a \"what we do\" path.\n\n**Separate base case from sensitivity.** Don't conflate \"what probably happens\" with \"what could happen.\"\n\n**Don't over-model.** 3-4 scenarios per planning cycle is the right number. More creates analysis paralysis.\n\n---\n\n## Common Scenarios by Stage\n\n**Seed:**\n- Co-founder leaves + product misses launch\n- Funding runs out + bridge terms unfavorable\n\n**Series A:**\n- Miss ARR target + fundraise delayed\n- Key customer churns + competitor raises\n\n**Series B:**\n- Market contraction + burn multiple spikes\n- Lead investor wants pivot + team resists\n\n## Integration with C-Suite Roles\n\n| Scenario Type | Primary Roles | Cascade To |\n|--------------|---------------|------------|\n| Revenue miss | CRO, CFO | CMO (pipeline), COO (cuts), CHRO (layoffs) |\n| Key person departure | CHRO, COO | CTO (if eng), CRO (if sales) |\n| Fundraise failure | CFO, CEO | COO (runway extension), CHRO (hiring freeze) |\n| Security breach | CISO, CTO | CEO (comms), CFO (cost), CRO (customer impact) |\n| Market shift | CEO, CPO | CMO (repositioning), CRO (new segments) |\n| Competitor move | CMO, CRO | CPO (roadmap response), CEO (strategy) |\n\n## References\n- `references\u002Fscenario-planning.md` — Shell methodology, pre-mortem, Monte Carlo, cascade frameworks\n- `scripts\u002Fscenario_modeler.py` — CLI tool for structured scenario modeling\n\n## ? Связи\n\n- [[MOC - Skills]] — Skills library\n- [[skills\u002Fskills-claude]] — Category: skills-claude\n- [[MOC - Agents]] — Claude agents\n\n",{"name":5,"tags":44,"license":15,"metadata":48,"description":7},[45,46,47],"domain\u002Fagents","artifact\u002Fskill","source\u002Fskills-claude",{"author":49,"domain":50,"updated":51,"version":52,"category":53,"frameworks":54,"python-tools":55},"Alireza Rezvani","strategic-planning",1772668800000,"1.0.0","c-level","scenario-planning","scenario_modeler.py","main","bdd9f958d7bb1a0f19b8ad8da020b0bab0f53eb1","vc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fscenario-war-room",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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add ibragimov-oasis\u002Fvibe-coder --skill scenario-war-room",{"tool":69,"command":70},"bunx","bunx skills add ibragimov-oasis\u002Fvibe-coder --skill scenario-war-room",{"tool":72,"command":73},"pnpm","pnpm dlx skills add ibragimov-oasis\u002Fvibe-coder --skill scenario-war-room","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fscenario-war-room\u002FSKILL.md",true,[77,83],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fscenario-planning.md","REFERENCE","参考文档",8201,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fscenario-war-room\u002Freferences\u002Fscenario-planning.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fscenario_modeler.py","SCRIPT","脚本",17706,"https:\u002F\u002Fgithub.com\u002Fibragimov-oasis\u002Fvibe-coder\u002Fblob\u002Fmain\u002Fvc-kit\u002Fcontent\u002FCOMBINED\u002FCOMBINED\u002Fskills\u002Fskills-claude\u002Fclaude-skills\u002Fc-level-advisor\u002Fscenario-war-room\u002Fscripts\u002Fscenario_modeler.py",[90,126,152,172,198,229],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":106,"publishedAt":39},"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",[96,101],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[107,108,109,110,111,112,113,114,115,116,117,118,119,29,120,121,122,123,124,125],"ui styling","ui","styling","ckm:ui styling","ckm","design","css","canvas","components","component","create","design systems","Tailwind","themes","utility","mode","implementing","artifact\u002Fui-component","source\u002Fui-design",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":140,"publishedAt":39},"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",[132,135,136,139],{"categoryNo":133,"categoryName":134,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":137,"categoryName":138,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[112,128,111,141,116,107,142,117,143,144,145,146,147,148,149,150,22,151,124,125],"google","presentations","generate","screenshot","actions","Media","logo","ads","youtube","tiktok","chart",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":160,"publishedAt":39},"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",[158,159],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[112,161,162,163,128,111,113,116,164,142,22,165,166,167,168,169,170,171,124,125],"design system","system","ckm:design system","architecture","token","creation","systematic","css variables","Variables","spacing","layer",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":39},"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",[178,181,182],{"categoryNo":179,"categoryName":180,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[112,184,185,186,111,187,145,146,188,189,190,191,192,193,194,195,124,125,196,197],"banner design","ckm:banner design","banner","frontend","3D","generated","Art","social","dimensions","neon","direction","display","frontend-design","hero",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":210,"publishedAt":39},"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",[204,207],{"categoryNo":205,"categoryName":206,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":208,"categoryName":209,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000035","市场营销",[200,211,212,213,214,215,216,22,217,218,219,220,221,222,223,224,225,226,227,228],"image","llms","assessment","deep analysis","Citations","analysis","local","deep","crawlability","seo analysis","2025","commerce","URL","domain\u002Fseo","source\u002Fskills-seo","vitals","generative","publishers",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":237,"publishedAt":39},"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",[235,236],{"categoryNo":205,"categoryName":206,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":208,"categoryName":209,"taxonomyType":104,"taxonomyTypeDesc":105},[200,238,239,240,241,242,243,244,245,22,29,219,246,247,223,248,249,224,225,226],"technical","seo technical","issues","audit","data","mobile","crawl","structure","rendering","technical seo audit","headers","categories"]