[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0G0HTMHYKA4DJHSCC4HR7":3,"skill-same:01M7F0G0HTMHYKA4DJHSCC4HR7":77},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0G0HTMHYKA4DJHSCC4HR7","business-design-templates",null,"Client-facing design deliverables: proposals, SOWs, case studies, pitch decks, pricing calculators, project briefs, and handoff documentation. Use when packaging design work for a client, an executive, or a portfolio — the artifact that leaves the team, not the interface itself.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: business-design-templates\ndescription: \"Client-facing design deliverables: proposals, SOWs, case studies, pitch decks, pricing calculators, project briefs, and handoff documentation. Use when packaging design work for a client, an executive, or a portfolio — the artifact that leaves the team, not the interface itself.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# Business Design Templates — The Business Side of Design\n\n## Mental model\n\nThese are the artifacts that leave the team. They are read by people who did not\nattend the meeting, will not read the Figma, and are deciding whether to fund,\napprove, or hire.\n\n- **Lead with the decision you want.** A proposal that opens with your process\n  makes the reader hunt for the ask. Put scope, timeline and price in the first\n  screen.\n- **Show the problem before the solution.** A case study that opens on the final\n  UI reads as a portfolio piece. One that opens on the broken funnel reads as\n  evidence.\n- **Quantify or say you cannot.** \"Improved usability\" is noise. \"Cut checkout\n  abandonment from 71% to 54% over six weeks\" is an argument. If you have no\n  number, say what you observed instead of reaching for an adjective.\n- **Scope is a fence, not a wish.** Every proposal names what is excluded. The\n  excluded list prevents more disputes than the included one.\n\n## Index\n\n| Artifact | Reference |\n|---|---|\n| Redesign, new product, design system, UX audit, retainer proposals | `proposal-templates.md` |\n| Statement of work, scope fencing, pricing structure | `proposal-templates.md` |\n| Design review deck, stakeholder direction pitch | `pitch-presentation-templates.md` |\n| E-commerce and SaaS case study narratives | `case-study-templates.md` |\n| Portfolio case study structure | `case-study-templates.md` |\n| Figma handoff practice, developer checklist | `client-handoff-templates.md` |\n| Token export, asset export | `client-handoff-templates.md` |\n| Design spec format, component docs, interaction spec | `design-documentation.md` |\n| Invoice structure, line items, payment terms | `invoice-and-billing.md` |\n\n## Reference architecture\n\n| File | Covers | Lines |\n|---|---|---|\n| `references\u002Fclient-handoff-templates.md` | handoff and export | 1054 |\n| `references\u002Fproposal-templates.md` | 5 proposal types | 1016 |\n| `references\u002Fdesign-documentation.md` | specs and component docs | 978 |\n| `references\u002Fcase-study-templates.md` | narrative + 2 templates | 920 |\n| `references\u002Fpitch-presentation-templates.md` | 2 deck templates | 851 |\n| `references\u002Finvoice-and-billing.md` | billing artifacts | 53 |\n\n## What every reference file contains\n\n1. The template as fill-in-the-blank prose, not a description of a template\n2. A worked example with realistic numbers\n3. What the reader is deciding, and what they need to decide it\n4. The section people cut that they should not\n\n## Routing\n\nFor **winning the work** — redesign, new-product, design-system, UX-audit and\nongoing-retainer proposals: read `references\u002Fproposal-templates.md`.\n\nFor **presenting** — design review decks and stakeholder decks for pitching a\ndirection: read `references\u002Fpitch-presentation-templates.md`.\n\nFor **telling the story afterwards** — the case study narrative structure plus\ne-commerce and SaaS templates: read `references\u002Fcase-study-templates.md`.\n\nFor **handing off to engineering** — Figma handoff practice, the developer\nchecklist, token export and asset export: read\n`references\u002Fclient-handoff-templates.md`.\n\nFor **documenting the system** — design spec format, component documentation and\ninteraction specification: read `references\u002Fdesign-documentation.md`.\n\nFor **odds and ends** — the patterns that had no home in the files above when this skill was converted to a router: read `references\u002Fbusiness-supplementary.md`.\n\n## Cross-References\n\n- figma-design-tool-workflows — Figma-specific handoff and dev mode workflows\n- ux-metrics-measurement — Metrics frameworks for case study results sections\n- design-systems-architecture — Design system documentation patterns\n- ux-research-methods — Research methodology details for proposals and case studies\n- design-process-methods — End-to-end process for methodology sections\n- sector-style-intelligence — Industry-specific context for proposals and case studies\n- conversion-optimization-patterns — Data for value-based pricing and case study metrics\n- micro-copy-intelligence — UX writing for documentation and component specs\n","# Business Design Templates — The Business Side of Design\n\n## Mental model\n\nThese are the artifacts that leave the team. They are read by people who did not\nattend the meeting, will not read the Figma, and are deciding whether to fund,\napprove, or hire.\n\n- **Lead with the decision you want.** A proposal that opens with your process\n  makes the reader hunt for the ask. Put scope, timeline and price in the first\n  screen.\n- **Show the problem before the solution.** A case study that opens on the final\n  UI reads as a portfolio piece. One that opens on the broken funnel reads as\n  evidence.\n- **Quantify or say you cannot.** \"Improved usability\" is noise. \"Cut checkout\n  abandonment from 71% to 54% over six weeks\" is an argument. If you have no\n  number, say what you observed instead of reaching for an adjective.\n- **Scope is a fence, not a wish.** Every proposal names what is excluded. The\n  excluded list prevents more disputes than the included one.\n\n## Index\n\n| Artifact | Reference |\n|---|---|\n| Redesign, new product, design system, UX audit, retainer proposals | `proposal-templates.md` |\n| Statement of work, scope fencing, pricing structure | `proposal-templates.md` |\n| Design review deck, stakeholder direction pitch | `pitch-presentation-templates.md` |\n| E-commerce and SaaS case study narratives | `case-study-templates.md` |\n| Portfolio case study structure | `case-study-templates.md` |\n| Figma handoff practice, developer checklist | `client-handoff-templates.md` |\n| Token export, asset export | `client-handoff-templates.md` |\n| Design spec format, component docs, interaction spec | `design-documentation.md` |\n| Invoice structure, line items, payment terms | `invoice-and-billing.md` |\n\n## Reference architecture\n\n| File | Covers | Lines |\n|---|---|---|\n| `references\u002Fclient-handoff-templates.md` | handoff and export | 1054 |\n| `references\u002Fproposal-templates.md` | 5 proposal types | 1016 |\n| `references\u002Fdesign-documentation.md` | specs and component docs | 978 |\n| `references\u002Fcase-study-templates.md` | narrative + 2 templates | 920 |\n| `references\u002Fpitch-presentation-templates.md` | 2 deck templates | 851 |\n| `references\u002Finvoice-and-billing.md` | billing artifacts | 53 |\n\n## What every reference file contains\n\n1. The template as fill-in-the-blank prose, not a description of a template\n2. A worked example with realistic numbers\n3. What the reader is deciding, and what they need to decide it\n4. The section people cut that they should not\n\n## Routing\n\nFor **winning the work** — redesign, new-product, design-system, UX-audit and\nongoing-retainer proposals: read `references\u002Fproposal-templates.md`.\n\nFor **presenting** — design review decks and stakeholder decks for pitching a\ndirection: read `references\u002Fpitch-presentation-templates.md`.\n\nFor **telling the story afterwards** — the case study narrative structure plus\ne-commerce and SaaS templates: read `references\u002Fcase-study-templates.md`.\n\nFor **handing off to engineering** — Figma handoff practice, the developer\nchecklist, token export and asset export: read\n`references\u002Fclient-handoff-templates.md`.\n\nFor **documenting the system** — design spec format, component documentation and\ninteraction specification: read `references\u002Fdesign-documentation.md`.\n\nFor **odds and ends** — the patterns that had no home in the files above when this skill was converted to a router: read `references\u002Fbusiness-supplementary.md`.\n\n## Cross-References\n\n- figma-design-tool-workflows — Figma-specific handoff and dev mode workflows\n- ux-metrics-measurement — Metrics frameworks for case study results sections\n- design-systems-architecture — Design system documentation patterns\n- ux-research-methods — Research methodology details for proposals and case studies\n- design-process-methods — End-to-end process for methodology sections\n- sector-style-intelligence — Industry-specific context for proposals and case studies\n- conversion-optimization-patterns — Data for value-based pricing and case study metrics\n- micro-copy-intelligence — UX writing for documentation and component specs\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill business-design-templates",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill business-design-templates",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill business-design-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002FSKILL.md",true,[47,53,57,61,65,69,73],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fbusiness-supplementary.md","REFERENCE","参考文档",692,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fbusiness-supplementary.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcase-study-templates.md",38589,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fcase-study-templates.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fclient-handoff-templates.md",53708,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fclient-handoff-templates.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdesign-documentation.md",50372,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fdesign-documentation.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Finvoice-and-billing.md",1224,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Finvoice-and-billing.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fpitch-presentation-templates.md",37770,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fpitch-presentation-templates.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fproposal-templates.md",44482,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fbusiness-design-templates\u002Freferences\u002Fproposal-templates.md",[78,84,91,98,105,112],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]