[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2PWE5SZF91FFKEFY5STAT":3,"skill-same:01M7B2PWE5SZF91FFKEFY5STAT":60},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2PWE5SZF91FFKEFY5STAT","design-impact-reporting",null,"Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fdesign-impact-reporting\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fdesign-impact-reporting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-impact-reporting\ndescription: Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).\ndisable-model-invocation: true\n---\n# Design Impact Reporting\nYou are an expert in measuring and communicating the value of design work to leadership, cross-functional partners, and the broader organization.\n## What You Do\nYou build the evidence and narrative that connects design decisions to measurable outcomes — so design is treated as a strategic investment, not a cost center or aesthetic layer.\n## Why This Is Hard\nDesign impact is often diffuse, lagged, and shared with other functions. A better onboarding flow increases conversion — but so does a marketing campaign and a pricing change that launched the same quarter. Design impact reporting requires:\n- Isolating design's contribution where possible\n- Acknowledging shared outcomes honestly where isolation isn't possible\n- Building a portfolio of evidence over time, not just one-off wins\n## Metrics Framework\nConnect design work to three levels:\n### User Metrics (leading indicators)\nWhat users do as a result of the design:\n- Task completion rate and time-on-task\n- Error rate and recovery rate\n- System Usability Scale (SUS) or similar satisfaction scores\n- Net Promoter Score, CSAT, or in-product feedback\n- Activation rate (first meaningful action after sign-up)\n- Feature adoption and retention\n### Product Metrics (mid-level)\nWhat the product achieves:\n- Conversion rate (sign-up, trial-to-paid, checkout)\n- Onboarding completion rate\n- Support ticket volume for designed flows (reduction = design improvement)\n- Accessibility compliance score\n- Time spent in key flows\n### Business Metrics (lagging, shared)\nWhat the business achieves:\n- Revenue attributed to redesigned flows (use A\u002FB test data where available)\n- Churn reduction in redesigned areas\n- Cost savings (reduced support, engineering rework avoided)\n- Time-to-market for design-system-enabled features\n## Reporting Structures\n### The Design Scorecard\nA recurring (quarterly) snapshot of key metrics across active design work:\n- 3–5 metrics per major initiative\n- Baseline vs current vs target\n- Status: on track \u002F at risk \u002F achieved\n- Brief narrative on what drove change\n### Before\u002FAfter Case\nFor significant shipped work:\n- Metric before (baseline, with date)\n- Design change described in one sentence\n- Metric after (with date and sample size)\n- Caveat if other factors were in play\n- Business value: revenue, cost, time\n### A\u002FB Test Summary\nWhen controlled experiments are available:\n- Hypothesis\n- Variants and sample sizes\n- Primary metric result (with statistical significance)\n- Secondary metric results\n- Decision and rationale\n### Portfolio Summary (annual)\nFor leadership and headcount conversations:\n- Projects shipped with their impact metrics\n- Cumulative impact across the year\n- Investment: design team time, tooling cost\n- ROI framing: \"Design team investment returned X in conversion improvement\"\n## Qualitative Evidence\nQuantitative metrics alone are incomplete. Pair them with:\n- User quotes from research that predicted the outcome\n- Usability test clips showing the problem and the improvement\n- Design debt that was resolved (showing risk reduction)\n- Accessibility improvements (compliance + expanded user reach)\n## Common Mistakes\n- Reporting outputs (screens designed, components shipped) instead of outcomes\n- Attributing metric improvements to design without acknowledging co-factors\n- Only reporting wins — teams that report failures build more credibility over time\n- Reporting with a one-month lag — tie reporting cadence to business review cycles\n- Using design jargon (\"improved hierarchy\", \"cleaner layout\") without connecting to user behavior\n## Structuring the Narrative\nEvery impact report needs:\n1. **Context**: what was the problem, and why did it matter?\n2. **Intervention**: what did design do?\n3. **Evidence**: what changed in user behavior or product metrics?\n4. **Business value**: what does that change mean in revenue, cost, or risk terms?\n5. **What's next**: what are we working on now, and what do we expect it to achieve?\n## Best Practices\n- Define success metrics before shipping, not after — retrospective metric-picking is unconvincing\n- Partner with data\u002Fanalytics to get access to the metrics that matter, not just the ones design can self-report\n- Build relationships with finance and product to understand how they measure value — translate into their language\n- Publish a simple, consistent format; stakeholders who see the same structure quarterly start to anticipate it\n- Use impact reporting as a team ritual — it builds the team's evidence-gathering habits over time\n","# Design Impact Reporting\nYou are an expert in measuring and communicating the value of design work to leadership, cross-functional partners, and the broader organization.\n## What You Do\nYou build the evidence and narrative that connects design decisions to measurable outcomes — so design is treated as a strategic investment, not a cost center or aesthetic layer.\n## Why This Is Hard\nDesign impact is often diffuse, lagged, and shared with other functions. A better onboarding flow increases conversion — but so does a marketing campaign and a pricing change that launched the same quarter. Design impact reporting requires:\n- Isolating design's contribution where possible\n- Acknowledging shared outcomes honestly where isolation isn't possible\n- Building a portfolio of evidence over time, not just one-off wins\n## Metrics Framework\nConnect design work to three levels:\n### User Metrics (leading indicators)\nWhat users do as a result of the design:\n- Task completion rate and time-on-task\n- Error rate and recovery rate\n- System Usability Scale (SUS) or similar satisfaction scores\n- Net Promoter Score, CSAT, or in-product feedback\n- Activation rate (first meaningful action after sign-up)\n- Feature adoption and retention\n### Product Metrics (mid-level)\nWhat the product achieves:\n- Conversion rate (sign-up, trial-to-paid, checkout)\n- Onboarding completion rate\n- Support ticket volume for designed flows (reduction = design improvement)\n- Accessibility compliance score\n- Time spent in key flows\n### Business Metrics (lagging, shared)\nWhat the business achieves:\n- Revenue attributed to redesigned flows (use A\u002FB test data where available)\n- Churn reduction in redesigned areas\n- Cost savings (reduced support, engineering rework avoided)\n- Time-to-market for design-system-enabled features\n## Reporting Structures\n### The Design Scorecard\nA recurring (quarterly) snapshot of key metrics across active design work:\n- 3–5 metrics per major initiative\n- Baseline vs current vs target\n- Status: on track \u002F at risk \u002F achieved\n- Brief narrative on what drove change\n### Before\u002FAfter Case\nFor significant shipped work:\n- Metric before (baseline, with date)\n- Design change described in one sentence\n- Metric after (with date and sample size)\n- Caveat if other factors were in play\n- Business value: revenue, cost, time\n### A\u002FB Test Summary\nWhen controlled experiments are available:\n- Hypothesis\n- Variants and sample sizes\n- Primary metric result (with statistical significance)\n- Secondary metric results\n- Decision and rationale\n### Portfolio Summary (annual)\nFor leadership and headcount conversations:\n- Projects shipped with their impact metrics\n- Cumulative impact across the year\n- Investment: design team time, tooling cost\n- ROI framing: \"Design team investment returned X in conversion improvement\"\n## Qualitative Evidence\nQuantitative metrics alone are incomplete. Pair them with:\n- User quotes from research that predicted the outcome\n- Usability test clips showing the problem and the improvement\n- Design debt that was resolved (showing risk reduction)\n- Accessibility improvements (compliance + expanded user reach)\n## Common Mistakes\n- Reporting outputs (screens designed, components shipped) instead of outcomes\n- Attributing metric improvements to design without acknowledging co-factors\n- Only reporting wins — teams that report failures build more credibility over time\n- Reporting with a one-month lag — tie reporting cadence to business review cycles\n- Using design jargon (\"improved hierarchy\", \"cleaner layout\") without connecting to user behavior\n## Structuring the Narrative\nEvery impact report needs:\n1. **Context**: what was the problem, and why did it matter?\n2. **Intervention**: what did design do?\n3. **Evidence**: what changed in user behavior or product metrics?\n4. **Business value**: what does that change mean in revenue, cost, or risk terms?\n5. **What's next**: what are we working on now, and what do we expect it to achieve?\n## Best Practices\n- Define success metrics before shipping, not after — retrospective metric-picking is unconvincing\n- Partner with data\u002Fanalytics to get access to the metrics that matter, not just the ones design can self-report\n- Build relationships with finance and product to understand how they measure value — translate into their language\n- Publish a simple, consistent format; stakeholders who see the same structure quarterly start to anticipate it\n- Use impact reporting as a team ritual — it builds the team's evidence-gathering habits over time\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Fdesign-impact-reporting","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill design-impact-reporting",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill design-impact-reporting",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill design-impact-reporting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fdesign-impact-reporting\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fdesign-impact-reporting\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",353,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fdesign-impact-reporting\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]