[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754EN6G5KSDH4QR45TJ2W14":3,"skill-same:01M754EN6G5KSDH4QR45TJ2W14":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":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M754EN6G5KSDH4QR45TJ2W14","business-operations-skills",null,"Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP\u002Frunbook authoring, procurement spend. Triggers on \"BizOps review\", \"where's the bottleneck\", \"vendor health\", \"internal SOP\", \"all-hands deck\", \"spend categorization\", \"capacity for Q3\", \"process mapping\". Forks context to route to one of six BizOps sub-skills (process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, procurement-optimizer) and returns a digest. Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational).","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\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: business-operations-skills\ndescription: Use when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP\u002Frunbook authoring, procurement spend. Triggers on \"BizOps review\", \"where's the bottleneck\", \"vendor health\", \"internal SOP\", \"all-hands deck\", \"spend categorization\", \"capacity for Q3\", \"process mapping\". Forks context to route to one of six BizOps sub-skills (process-mapper, vendor-management, capacity-planner, internal-comms, knowledge-ops, procurement-optimizer) and returns a digest. Distinct from business-growth (external sales motion) and c-level-advisor (strategic, not operational).\ncontext: fork\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [bizops, operations, process, vendor, capacity, sop, procurement, coo, orchestrator]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Business Operations — Domain Orchestrator\n\nThe BizOps surface is **internal**: how the company actually runs. This orchestrator forks its conversation context, routes your inquiry to one of six sub-skills, then returns a tight digest to the parent thread. The heavy ingestion (vendor catalogs, process interviews, multi-doc SOP intake) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill to route to |\n|---|---|\n| \"Where does the work spend most of its time waiting?\" | `process-mapper` |\n| \"Is this vendor delivering against the SLA?\" | `vendor-management` |\n| \"Do we have enough people to ship in Q3?\" | `capacity-planner` |\n| \"I need to brief the company on a re-org\" | `internal-comms` |\n| \"Write me a runbook for the incident response process\" | `knowledge-ops` |\n| \"Why is our software spend up 40% YoY?\" | `procurement-optimizer` |\n\n## Routing logic (deterministic)\n\nThe orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` |\n| **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` |\n| **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` |\n| **COMMS** | all-hands, internal newsletter, announcement, change management, FAQ, town hall | `internal-comms` |\n| **KNOWLEDGE** | SOP, runbook, knowledge base, wiki, playbook, documentation, onboarding doc | `knowledge-ops` |\n| **PROCUREMENT** | spend, procurement, purchase, supplier rationalization, software audit, SaaS sprawl | `procurement-optimizer` |\n\nIf signals are mixed (e.g., \"vendor SLA + spend audit\"), run the **highest-confidence sub-skill first**, then chain into the second one in a follow-up forked turn.\n\n### Fallback\n\nIf no signal class scores ≥ 2, ask **one** clarifying question naming the two most likely candidates. Do NOT guess silently.\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the documented canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nBefore any clarifying question, check:\n- Does the user's working directory already contain a process map, vendor catalog, SOP, or org chart we can grep?\n- Does the inquiry already disambiguate the lane (e.g., \"vendor SLA review\" — that's `vendor-management`, no question needed)?\n- Is the lane unambiguous from filenames mentioned (`procurement-Q3.csv` → procurement)?\n\nIf the codebase resolves the lane, **route silently**. Don't ask.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle questions. Never default to \"what do you think?\". Always offer your recommendation.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Cone-sentence rationale from the signal table>]\n\n(Confirm, or override?)\n```\n\nWait for the user's response. **Then** route. Never guess silently after a turn that asked a question.\n\n### Step 3 — Forking decision-tree walk (only if the inquiry crosses lanes)\n\nIf the user's inquiry legitimately crosses two lanes (e.g., \"vendor SLA + spend audit\" = VENDOR + PROCUREMENT), walk the tree **depth-first**:\n\n1. Resolve the higher-confidence lane first → run that sub-skill in forked context → return digest\n2. Ask: \"Should we now run [second lane]? My recommendation: yes, because [dependency reason].\"\n3. Only after explicit user confirmation, run the second sub-skill\n\nDo NOT chain silently. Each fork is an explicit user-confirmed step.\n\n### Step 4 — Invoke sub-skill in forked context\n\nEach sub-skill is invoked with the original prompt + a digest of any structured inputs (file paths, JSON inputs). The fork keeps heavy ingestion (vendor catalog, process transcripts, SOP source documents) out of the parent context.\n\n### Step 5 — Return digest with cited canon challenge\n\nWhen the sub-skill completes, return a **≤ 200-word digest** to the parent thread:\n\n- What was analyzed\n- Top 3 findings (each anchored in a reference doc citation — e.g., \"Goldratt's Theory of Constraints: optimize the bottleneck, not the non-constraint\")\n- Top 3 next actions (named owners if possible)\n- Path to the artifact(s) produced\n- **One grill challenge** for the user, cited: \"Your value-add ratio is 12%. Lean canon (Womack & Jones 1996) classifies \u003C15% as waste-heavy. What's blocking process redesign — political, technical, or budget?\"\n\nThe parent agent can then ask follow-ups (each triggering new forked invocations).\n\n## Forcing-question library (grill-with-docs pattern)\n\nWhen the user has provided enough context to enter a lane, the orchestrator may grill them on the **decisions inside that lane** before invoking the sub-skill. One question per turn, each with a recommended answer + canon citation. Examples:\n\n- **PROCESS lane**: \"Before mapping: do you have measured cycle times per stage, or only estimates? Recommended: insist on measured data for the top-3 longest stages. Anti-pattern (Goldratt 1984): map estimates, optimize the wrong constraint.\"\n- **VENDOR lane**: \"Before scoring: what's your tier-1 criticality threshold — by spend ($X\u002Fyear), or by operational dependency (revenue-blocking if vendor fails)? Recommended: operational dependency. Anti-pattern (Gartner TPRM): spend-only tiering misses critical low-spend vendors like the HVAC vendor in the Target breach.\"\n- **CAPACITY lane**: \"Before modeling: are you planning for utilization or throughput? Recommended: throughput (Little's Law). Anti-pattern (DORA): planning for utilization > 80% destroys throughput via queueing.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. The user is acting on behalf of an organization with ≥ 10 employees (smaller orgs don't need this surface).\n2. The user has access to the data the sub-skill needs (process docs, vendor list, spend export, etc.) — or accepts the skill's templated dummy data.\n3. The user wants **deterministic, repeatable analysis** over LLM-flavored prose. Every sub-skill ships stdlib-only Python tools.\n\n## Non-goals\n\n- Not a substitute for an ERP, vendor management platform (Vendr, Tropic), or capacity-planning SaaS (Float, Runn).\n- Does not store state across sessions — every invocation is self-contained.\n- Does not call external APIs from Python tools (stdlib only, by design).\n\n## Distinct from\n\n- **`business-growth\u002F*`** — that's the **external sales motion** (CSM, sales engineering, RevOps). BizOps is **internal**.\n- **`c-level-advisor\u002Fcoo-advisor`** — that's strategic COO judgment (\"should we restructure?\"). BizOps is tactical (\"here's the process map with bottlenecks\").\n- **`engineering\u002Fslo-architect`** — that's system reliability with SLO\u002FSLI\u002Ferror budgets. `process-mapper` is **business process** reliability, not system reliability.\n- **`engineering\u002Fllm-wiki`** — that's a **personal** PKM (Karpathy's pattern). `knowledge-ops` is **company-wide** SOP authoring.\n\n## Output artifacts\n\nEvery sub-skill produces at least one artifact (markdown, CSV, or JSON) saved to the user's working directory. The orchestrator surfaces the file path in the digest.\n\n## Anti-patterns (do not)\n\n- ❌ Run all 6 sub-skills \"to be thorough\" — pick one based on signal, return digest, let user chain\n- ❌ Auto-approve a vendor or process change — surface findings; the human decides\n- ❌ Edit production process docs without asking — write to a new file, propose the diff\n- ❌ Skip the digest step — parent context needs ≤ 200-word digest, not the full sub-skill output\n\n## References\n\n- See `c-level-advisor\u002Fcoo-advisor` for strategic COO framing\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n","# Business Operations — Domain Orchestrator\n\nThe BizOps surface is **internal**: how the company actually runs. This orchestrator forks its conversation context, routes your inquiry to one of six sub-skills, then returns a tight digest to the parent thread. The heavy ingestion (vendor catalogs, process interviews, multi-doc SOP intake) stays in the forked context.\n\n## When to invoke\n\n| Symptom | Sub-skill to route to |\n|---|---|\n| \"Where does the work spend most of its time waiting?\" | `process-mapper` |\n| \"Is this vendor delivering against the SLA?\" | `vendor-management` |\n| \"Do we have enough people to ship in Q3?\" | `capacity-planner` |\n| \"I need to brief the company on a re-org\" | `internal-comms` |\n| \"Write me a runbook for the incident response process\" | `knowledge-ops` |\n| \"Why is our software spend up 40% YoY?\" | `procurement-optimizer` |\n\n## Routing logic (deterministic)\n\nThe orchestrator classifies the inquiry by **signals** detected in the prompt. Two-signal threshold for confident routing; one-signal triggers a clarifying question.\n\n### Signal table\n\n| Signal class | Keywords | Sub-skill |\n|---|---|---|\n| **PROCESS** | bottleneck, cycle time, waiting, handoff, BPMN, process map, workflow | `process-mapper` |\n| **VENDOR** | vendor, supplier, SLA, contract, third-party, MSA, SaaS subscription, renewal | `vendor-management` |\n| **CAPACITY** | headcount, capacity, utilization, planning, hiring sequence, FTE | `capacity-planner` |\n| **COMMS** | all-hands, internal newsletter, announcement, change management, FAQ, town hall | `internal-comms` |\n| **KNOWLEDGE** | SOP, runbook, knowledge base, wiki, playbook, documentation, onboarding doc | `knowledge-ops` |\n| **PROCUREMENT** | spend, procurement, purchase, supplier rationalization, software audit, SaaS sprawl | `procurement-optimizer` |\n\nIf signals are mixed (e.g., \"vendor SLA + spend audit\"), run the **highest-confidence sub-skill first**, then chain into the second one in a follow-up forked turn.\n\n### Fallback\n\nIf no signal class scores ≥ 2, ask **one** clarifying question naming the two most likely candidates. Do NOT guess silently.\n\n## Workflow (Matt Pocock grill discipline)\n\nDerived from Matt Pocock's `grill-with-docs` pattern: **explore-then-ask, one question per turn with a recommended answer, walk the decision tree depth-first, track dependencies, anchor every challenge in the documented canon** (`references\u002F`).\n\n### Step 1 — Explore before asking\n\nBefore any clarifying question, check:\n- Does the user's working directory already contain a process map, vendor catalog, SOP, or org chart we can grep?\n- Does the inquiry already disambiguate the lane (e.g., \"vendor SLA review\" — that's `vendor-management`, no question needed)?\n- Is the lane unambiguous from filenames mentioned (`procurement-Q3.csv` → procurement)?\n\nIf the codebase resolves the lane, **route silently**. Don't ask.\n\n### Step 2 — If still ambiguous, ONE forcing question with a recommended answer\n\nMatt's rule: never bundle questions. Never default to \"what do you think?\". Always offer your recommendation.\n\nPattern:\n```\nQ1\u002F1: [precise question naming the two candidate lanes]\nRecommended: [Lane X, because \u003Cone-sentence rationale from the signal table>]\n\n(Confirm, or override?)\n```\n\nWait for the user's response. **Then** route. Never guess silently after a turn that asked a question.\n\n### Step 3 — Forking decision-tree walk (only if the inquiry crosses lanes)\n\nIf the user's inquiry legitimately crosses two lanes (e.g., \"vendor SLA + spend audit\" = VENDOR + PROCUREMENT), walk the tree **depth-first**:\n\n1. Resolve the higher-confidence lane first → run that sub-skill in forked context → return digest\n2. Ask: \"Should we now run [second lane]? My recommendation: yes, because [dependency reason].\"\n3. Only after explicit user confirmation, run the second sub-skill\n\nDo NOT chain silently. Each fork is an explicit user-confirmed step.\n\n### Step 4 — Invoke sub-skill in forked context\n\nEach sub-skill is invoked with the original prompt + a digest of any structured inputs (file paths, JSON inputs). The fork keeps heavy ingestion (vendor catalog, process transcripts, SOP source documents) out of the parent context.\n\n### Step 5 — Return digest with cited canon challenge\n\nWhen the sub-skill completes, return a **≤ 200-word digest** to the parent thread:\n\n- What was analyzed\n- Top 3 findings (each anchored in a reference doc citation — e.g., \"Goldratt's Theory of Constraints: optimize the bottleneck, not the non-constraint\")\n- Top 3 next actions (named owners if possible)\n- Path to the artifact(s) produced\n- **One grill challenge** for the user, cited: \"Your value-add ratio is 12%. Lean canon (Womack & Jones 1996) classifies \u003C15% as waste-heavy. What's blocking process redesign — political, technical, or budget?\"\n\nThe parent agent can then ask follow-ups (each triggering new forked invocations).\n\n## Forcing-question library (grill-with-docs pattern)\n\nWhen the user has provided enough context to enter a lane, the orchestrator may grill them on the **decisions inside that lane** before invoking the sub-skill. One question per turn, each with a recommended answer + canon citation. Examples:\n\n- **PROCESS lane**: \"Before mapping: do you have measured cycle times per stage, or only estimates? Recommended: insist on measured data for the top-3 longest stages. Anti-pattern (Goldratt 1984): map estimates, optimize the wrong constraint.\"\n- **VENDOR lane**: \"Before scoring: what's your tier-1 criticality threshold — by spend ($X\u002Fyear), or by operational dependency (revenue-blocking if vendor fails)? Recommended: operational dependency. Anti-pattern (Gartner TPRM): spend-only tiering misses critical low-spend vendors like the HVAC vendor in the Target breach.\"\n- **CAPACITY lane**: \"Before modeling: are you planning for utilization or throughput? Recommended: throughput (Little's Law). Anti-pattern (DORA): planning for utilization > 80% destroys throughput via queueing.\"\n\nNever run a sub-skill until the lane-defining decision is locked.\n\n## Assumptions\n\n1. The user is acting on behalf of an organization with ≥ 10 employees (smaller orgs don't need this surface).\n2. The user has access to the data the sub-skill needs (process docs, vendor list, spend export, etc.) — or accepts the skill's templated dummy data.\n3. The user wants **deterministic, repeatable analysis** over LLM-flavored prose. Every sub-skill ships stdlib-only Python tools.\n\n## Non-goals\n\n- Not a substitute for an ERP, vendor management platform (Vendr, Tropic), or capacity-planning SaaS (Float, Runn).\n- Does not store state across sessions — every invocation is self-contained.\n- Does not call external APIs from Python tools (stdlib only, by design).\n\n## Distinct from\n\n- **`business-growth\u002F*`** — that's the **external sales motion** (CSM, sales engineering, RevOps). BizOps is **internal**.\n- **`c-level-advisor\u002Fcoo-advisor`** — that's strategic COO judgment (\"should we restructure?\"). BizOps is tactical (\"here's the process map with bottlenecks\").\n- **`engineering\u002Fslo-architect`** — that's system reliability with SLO\u002FSLI\u002Ferror budgets. `process-mapper` is **business process** reliability, not system reliability.\n- **`engineering\u002Fllm-wiki`** — that's a **personal** PKM (Karpathy's pattern). `knowledge-ops` is **company-wide** SOP authoring.\n\n## Output artifacts\n\nEvery sub-skill produces at least one artifact (markdown, CSV, or JSON) saved to the user's working directory. The orchestrator surfaces the file path in the digest.\n\n## Anti-patterns (do not)\n\n- ❌ Run all 6 sub-skills \"to be thorough\" — pick one based on signal, return digest, let user chain\n- ❌ Auto-approve a vendor or process change — surface findings; the human decides\n- ❌ Edit production process docs without asking — write to a new file, propose the diff\n- ❌ Skip the digest step — parent context needs ≤ 200-word digest, not the full sub-skill output\n\n## References\n\n- See `c-level-advisor\u002Fcoo-advisor` for strategic COO framing\n- Path-B build pattern: `documentation\u002Fimplementation\u002Fbizops-commercial-expansion-plan.md`\n",{"name":5,"tags":23,"author":33,"context":34,"license":14,"version":35,"description":7,"compatible_tools":36},[24,25,26,27,28,29,30,31,32],"bizops","operations","process","vendor","capacity","sop","procurement","coo","orchestrator","claude-code-skills","fork","2.8.0",[37,38,39,40,41,42],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add ASoudy\u002FAGS --skill business-operations-skills",{"tool":55,"command":56},"bunx","bunx skills add ASoudy\u002FAGS --skill business-operations-skills",{"tool":58,"command":59},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill business-operations-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fbusiness-operations\u002Fskills\u002Fbusiness-operations-skills\u002FSKILL.md",true,[],[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",[],[]]