[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754SDXQVQ4JYWZ6DDJ3EVRE":3,"skill-same:01M754SDXQVQ4JYWZ6DDJ3EVRE":63},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M754SDXQVQ4JYWZ6DDJ3EVRE","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?'","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\u002Fscenario-war-room\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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\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","# 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",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","strategic-planning",1772668800000,"1.0.0","c-level","scenario-planning","scenario_modeler.py","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add ASoudy\u002FAGS --skill scenario-war-room",{"tool":43,"command":44},"bunx","bunx skills add ASoudy\u002FAGS --skill scenario-war-room",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill scenario-war-room","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fscenario-planning.md","REFERENCE","参考文档",8011,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002Freferences\u002Fscenario-planning.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fscenario_modeler.py","SCRIPT","脚本",17706,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fscenario-war-room\u002Fscripts\u002Fscenario_modeler.py",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]