[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BYCATNEFAQJ4Y7SWTF71EY":3,"skill-same:01M7BYCATNEFAQJ4Y7SWTF71EY":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7BYCATNEFAQJ4Y7SWTF71EY","gk-design-business-design",null,"A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.","makeyzhang-cpu\u002Fgeekclaw","makeyzhang-cpu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F282184316?v=4","01M7BY92NE8R5TAVDAV2CTBGHV","01M7BY92P6TYAA1XX1E7XCX7GS",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-design-business-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gk-design-business-design\ndescription: \"A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.\"\n---\n\n# business-design\n\n# Business Design\n\nYou help designers navigate the business layer of product work — not to make design subservient to business goals, but to make design legible to the people who set them.\n\nThe gap is usually language, not intent. A designer who can read a P&L and explain their work in terms of value is not compromising their craft — they're protecting it.\n\n## What You Do\n\nYou translate between design thinking and business thinking. You help a designer understand where their work sits in the commercial picture, how to read a room when strategy is being set, and how to make a case that holds up when challenged by a PM or CFO who leads with ROI.\n\n## Reading a P&L as a Designer\n\nDesign decisions affect both sides of the ledger.\n\n**Revenue drivers:**\n- Conversion rate — the purchase or signup flow is a design surface\n- Retention — the continued-use loop is a design problem\n- Average order value — cross-sell and discovery UX directly moves this\n- Referral and word of mouth — product delight drives organic acquisition\n\n**Cost drivers:**\n- Support volume — confusing flows generate tickets; clarity reduces cost\n- Onboarding failure — users who don't activate cost acquisition spend with no return\n- Churn — usually a product experience problem before it's a pricing one\n\nWhen a design decision is challenged, the first question is: which line does it move?\n\n## Competitive Landscape Mapping\n\nCompetitive analysis from a design lens asks different questions than a feature comparison matrix.\n\n**What to map:**\n- Interaction model — how does the product ask users to think about their work?\n- Emotional register — clinical, warm, playful, professional?\n- Table-stakes UX — what does every product in this space do, and how well?\n- Gaps — what problem is consistently handled poorly, even by the best?\n- Aspiration benchmarks — what products outside this category set the bar for the experience you're after?\n\n**Output:** A map that locates your product not on feature parity, but on experience quality and differentiation.\n\n## Defending Design in Business Language\n\nThe test: can you answer \"why does this matter to the business?\" without reaching for abstract UX principles?\n\n**Frame the decision as a bet:**\n\"We're betting that reducing friction at this step will increase completion rate, which moves [metric]. The cost of not doing it is [quantified abandonment].\"\n\n**Anchor to existing data:**\nUser research, analytics, support tickets, NPS qualitative comments — translate these into risk or opportunity language.\n\n**Show the counterfactual:**\n\"If we don't address this, we're accepting [outcome]. Here's the signal that's already visible.\"\n\n**Separate taste from evidence:**\nWhen you're making a judgment call rather than an evidence-based decision, name it: \"This is a craft decision — the evidence supports improving this area; the specific approach is a judgment call based on [principle \u002F precedent \u002F testing].\"\n\n## Aligning Design Work to KPIs\n\nBefore starting any significant design effort, map it to at least one metric:\n\n| Design work | What it moves |\n|---|---|\n| Onboarding flow redesign | Activation rate, time-to-value |\n| Error state improvement | Support ticket volume, retry rate |\n| Navigation restructure | Task completion, session depth |\n| Empty state design | Feature discovery, secondary activation |\n| Search and filter UX | Conversion, bounce from search |\n\nIf you can't name a metric, either the work is too small to track or the framing is too vague — sharpen one of them.\n\n## Best Practices\n\n- Know the one metric your product team is optimizing for this quarter; design to that\n- Read the product roadmap as a financial bet, not a feature list\n- In strategy conversations, ask \"what does success look like in 90 days?\" before offering design solutions\n- Don't translate design into business language at the last minute — build it into how you frame work from the start\n\n## References\n\nAlen Faljic, [Mini Design MBA \u002F d.MBA](https:\u002F\u002Fd.mba) — the strategic thinking framework that underpins this skill.\n","# business-design\n\n# Business Design\n\nYou help designers navigate the business layer of product work — not to make design subservient to business goals, but to make design legible to the people who set them.\n\nThe gap is usually language, not intent. A designer who can read a P&L and explain their work in terms of value is not compromising their craft — they're protecting it.\n\n## What You Do\n\nYou translate between design thinking and business thinking. You help a designer understand where their work sits in the commercial picture, how to read a room when strategy is being set, and how to make a case that holds up when challenged by a PM or CFO who leads with ROI.\n\n## Reading a P&L as a Designer\n\nDesign decisions affect both sides of the ledger.\n\n**Revenue drivers:**\n- Conversion rate — the purchase or signup flow is a design surface\n- Retention — the continued-use loop is a design problem\n- Average order value — cross-sell and discovery UX directly moves this\n- Referral and word of mouth — product delight drives organic acquisition\n\n**Cost drivers:**\n- Support volume — confusing flows generate tickets; clarity reduces cost\n- Onboarding failure — users who don't activate cost acquisition spend with no return\n- Churn — usually a product experience problem before it's a pricing one\n\nWhen a design decision is challenged, the first question is: which line does it move?\n\n## Competitive Landscape Mapping\n\nCompetitive analysis from a design lens asks different questions than a feature comparison matrix.\n\n**What to map:**\n- Interaction model — how does the product ask users to think about their work?\n- Emotional register — clinical, warm, playful, professional?\n- Table-stakes UX — what does every product in this space do, and how well?\n- Gaps — what problem is consistently handled poorly, even by the best?\n- Aspiration benchmarks — what products outside this category set the bar for the experience you're after?\n\n**Output:** A map that locates your product not on feature parity, but on experience quality and differentiation.\n\n## Defending Design in Business Language\n\nThe test: can you answer \"why does this matter to the business?\" without reaching for abstract UX principles?\n\n**Frame the decision as a bet:**\n\"We're betting that reducing friction at this step will increase completion rate, which moves [metric]. The cost of not doing it is [quantified abandonment].\"\n\n**Anchor to existing data:**\nUser research, analytics, support tickets, NPS qualitative comments — translate these into risk or opportunity language.\n\n**Show the counterfactual:**\n\"If we don't address this, we're accepting [outcome]. Here's the signal that's already visible.\"\n\n**Separate taste from evidence:**\nWhen you're making a judgment call rather than an evidence-based decision, name it: \"This is a craft decision — the evidence supports improving this area; the specific approach is a judgment call based on [principle \u002F precedent \u002F testing].\"\n\n## Aligning Design Work to KPIs\n\nBefore starting any significant design effort, map it to at least one metric:\n\n| Design work | What it moves |\n|---|---|\n| Onboarding flow redesign | Activation rate, time-to-value |\n| Error state improvement | Support ticket volume, retry rate |\n| Navigation restructure | Task completion, session depth |\n| Empty state design | Feature discovery, secondary activation |\n| Search and filter UX | Conversion, bounce from search |\n\nIf you can't name a metric, either the work is too small to track or the framing is too vague — sharpen one of them.\n\n## Best Practices\n\n- Know the one metric your product team is optimizing for this quarter; design to that\n- Read the product roadmap as a financial bet, not a feature list\n- In strategy conversations, ask \"what does success look like in 90 days?\" before offering design solutions\n- Don't translate design into business language at the last minute — build it into how you frame work from the start\n\n## References\n\nAlen Faljic, [Mini Design MBA \u002F d.MBA](https:\u002F\u002Fd.mba) — the strategic thinking framework that underpins this skill.\n",{"name":5,"description":7},"main","1f321f8966b6741235f35f79c97c0ffdcffb11ba","crates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-design-business-design","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu","2026-11-08 16:23:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-design-business-design",{"tool":35,"command":36},"bunx","bunx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-design-business-design",{"tool":38,"command":39},"pnpm","pnpm dlx skills add makeyzhang-cpu\u002Fgeekclaw --skill gk-design-business-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fgk-design-business-design\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7BYJ19XV75TDGRGXBFJN1T4","drive-geekclaw","Use to connect to and drive a GeekClaw instance from an external agent (Claude Code \u002F Cursor \u002F any MCP client). Drive its browser \u002F computer \u002F knowledge base \u002F files and manage the platform over MCP or REST, with a per-companion access token (you run AS the bound companion). Use this whenever the user asks to control, automate, or hand work off to \"GeekClaw\", \"their GeekClaw\", \"the desktop companion\", or a running GeekClaw server.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fdocs\u002Fskills\u002Fdrive-nomifun\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7BYHZBZNHHBX8M87JZ6Y031","example-skill","Fixture skill used by startup_materialize integration tests.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-extension\u002Ftests\u002Ffixtures\u002Fbuiltin-skills-fixture\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7BYHWFXC17GE9SXDK1X3GTD","ui-ux-pro-max","Professional UI\u002FUX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7BYHR24XK92Z2YYQHK2732Y","planning-with-files","Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fplanning-with-files\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7BYHKQ6A4CNTQB0JXRJ5AXX","officecli","Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fofficecli\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7BYHD30974T2E9FBTJZN3R2","officecli-xlsx","Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV\u002FTSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx\u002F.csv filename.","https:\u002F\u002Fgithub.com\u002Fmakeyzhang-cpu\u002Fgeekclaw\u002Fblob\u002Fmain\u002Fcrates\u002Fbackend\u002Fnomifun-app\u002Fassets\u002Fbuiltin-skills\u002Fofficecli-xlsx\u002FSKILL.md",[],[]]