[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0GRR3GHC3DK2F0ZWYZP91":3,"skill-same:01M7F0GRR3GHC3DK2F0ZWYZP91":61},{"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},"01M7F0GRR3GHC3DK2F0ZWYZP91","design-critique-case-studies",null,"Structured design critique using the Liz Lerman Critical Response Process, plus deep-dives on Stripe, Linear, Notion, Airbnb, Figma, and Arc, and post-mortems of redesign failures like Snapchat 2018 and Sonos 2024. Use when running a critique session, giving design feedback, or learning from a shipped product.","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\u002Fdesign-critique-case-studies\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: design-critique-case-studies\ndescription: Structured design critique using the Liz Lerman Critical Response Process, plus deep-dives on Stripe, Linear, Notion, Airbnb, Figma, and Arc, and post-mortems of redesign failures like Snapchat 2018 and Sonos 2024. Use when running a critique session, giving design feedback, or learning from a shipped product.\nallowed-tools: Read, Grep, Glob\n---\n\n# Design Critique & Case Studies\n\nCritique is the cheapest quality intervention in the lifecycle: a flaw caught in wireframes costs hours, the same flaw after launch costs months. It also raises the team's quality floor, builds shared vocabulary, and spreads senior judgment.\n\n## Critique Types\n\n- **Studio** — scheduled, 4-8 people, 45-60 minutes; roles: presenter, facilitator, critics, note-taker. For major milestones.\n- **Desk** — informal 1:1, frequent; still anchor feedback to a principle or user scenario.\n- **Async** — Figma comments or a 3-5 minute recorded walkthrough; tag every comment [Question], [Concern], [Suggestion], or [Praise].\n- **Self** — checklist before group critique: empty\u002Floading\u002Ferror states, hierarchy clear in 3 seconds, strongest affordance on the primary action, user language, WCAG AA contrast and target size.\n\n## Liz Lerman's Critical Response Process\n\nFour steps, in strict order:\n\n1. **Statements of Meaning** — critics name what works and why (specific, not \"looks nice\"), so the presenter knows what to protect.\n2. **Artist's Questions** — the presenter asks about what they are unsure of, steering feedback to real concerns.\n3. **Neutral Questions** — critics ask non-leading questions to surface intent (\"What was your rationale for...\", not \"Don't you think...\").\n4. **Opinion Time** — opinions only with the presenter's permission, and grounded in a principle or evidence.\n\n## Critique by Fidelity (30\u002F60\u002F90)\n\n| Stage | Focus | Out of scope |\n|---|---|---|\n| 30% concept | Right problem, information architecture, core flows, mental model | Color, type, pixels |\n| 60% mid-fi | Interaction patterns, content hierarchy, edge cases (empty, error, overflow, truncation), systematic heuristic pass | Visual polish |\n| 90% pre-handoff | Token consistency, micro-interactions, WCAG AA, responsive behavior, implementation ambiguity | Foundational architecture |\n\n## Anti-Patterns\n\n- **Design by committee** — name one decision-maker before the session; everyone is heard, one person decides.\n- **HiPPO** — the most senior person speaks last, or run an anonymous written first round.\n- **Vague feedback** (\"make it pop\") — every comment must cite a heuristic, principle, or user scenario.\n- **Preference vs. evidence** — separate them; when evidence is missing, flag the question for user testing.\n- **Bike-shedding** — time-box by decision impact; the facilitator redirects to higher-impact topics.\n\nAlways ground feedback in principles, heuristics, or evidence. When principles conflict, name the tradeoff and recommend how to resolve it: user testing, business priority, or design principle hierarchy.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Running a session: facilitator guide, formats, feedback frameworks (I Like\u002FI Wish\u002FWhat If, Rose-Thorn-Bud, Feldman, Six Thinking Hats), async protocols, the 10-dimension scoring rubric, receiving critique, critique types, full Lerman steps | `references\u002Fcritique-methodology.md` |\n| Why a product's design works: Stripe, Linear, Notion, Airbnb, Figma, Arc, Duolingo, Vercel, Apple Health, Discord, plus condensed analyses (Raycast, Supabase, Superhuman, Cal.com, Framer, Obsidian, Loom, and more) | `references\u002Fproduct-deep-dives.md` |\n| Redesign post-mortems: Snapchat, Windows 8, Digg, Twitter\u002FX, Google Plus, Sonos, Healthcare.gov, Reddit API, YouTube dislikes, Skype; redesign safety checklist | `references\u002Fredesign-failure-analysis.md` |\n\n## Cross-References\n\n- Grounding comments in a heuristic, especially at 60%: `nng-ux-heuristics`\n- Biases in the critique room (anchoring, confirmation, groupthink): `cognitive-psychology-ux`\n- Settling disagreements with a usability test: `ux-research-methods`\n- Design system component use at 90%: `component-patterns-code`\n- Quantitative evidence for feedback: `ux-metrics-measurement`\n- Dark patterns and manipulative content: `ux-ethics-content-strategy`\n","# Design Critique & Case Studies\n\nCritique is the cheapest quality intervention in the lifecycle: a flaw caught in wireframes costs hours, the same flaw after launch costs months. It also raises the team's quality floor, builds shared vocabulary, and spreads senior judgment.\n\n## Critique Types\n\n- **Studio** — scheduled, 4-8 people, 45-60 minutes; roles: presenter, facilitator, critics, note-taker. For major milestones.\n- **Desk** — informal 1:1, frequent; still anchor feedback to a principle or user scenario.\n- **Async** — Figma comments or a 3-5 minute recorded walkthrough; tag every comment [Question], [Concern], [Suggestion], or [Praise].\n- **Self** — checklist before group critique: empty\u002Floading\u002Ferror states, hierarchy clear in 3 seconds, strongest affordance on the primary action, user language, WCAG AA contrast and target size.\n\n## Liz Lerman's Critical Response Process\n\nFour steps, in strict order:\n\n1. **Statements of Meaning** — critics name what works and why (specific, not \"looks nice\"), so the presenter knows what to protect.\n2. **Artist's Questions** — the presenter asks about what they are unsure of, steering feedback to real concerns.\n3. **Neutral Questions** — critics ask non-leading questions to surface intent (\"What was your rationale for...\", not \"Don't you think...\").\n4. **Opinion Time** — opinions only with the presenter's permission, and grounded in a principle or evidence.\n\n## Critique by Fidelity (30\u002F60\u002F90)\n\n| Stage | Focus | Out of scope |\n|---|---|---|\n| 30% concept | Right problem, information architecture, core flows, mental model | Color, type, pixels |\n| 60% mid-fi | Interaction patterns, content hierarchy, edge cases (empty, error, overflow, truncation), systematic heuristic pass | Visual polish |\n| 90% pre-handoff | Token consistency, micro-interactions, WCAG AA, responsive behavior, implementation ambiguity | Foundational architecture |\n\n## Anti-Patterns\n\n- **Design by committee** — name one decision-maker before the session; everyone is heard, one person decides.\n- **HiPPO** — the most senior person speaks last, or run an anonymous written first round.\n- **Vague feedback** (\"make it pop\") — every comment must cite a heuristic, principle, or user scenario.\n- **Preference vs. evidence** — separate them; when evidence is missing, flag the question for user testing.\n- **Bike-shedding** — time-box by decision impact; the facilitator redirects to higher-impact topics.\n\nAlways ground feedback in principles, heuristics, or evidence. When principles conflict, name the tradeoff and recommend how to resolve it: user testing, business priority, or design principle hierarchy.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Running a session: facilitator guide, formats, feedback frameworks (I Like\u002FI Wish\u002FWhat If, Rose-Thorn-Bud, Feldman, Six Thinking Hats), async protocols, the 10-dimension scoring rubric, receiving critique, critique types, full Lerman steps | `references\u002Fcritique-methodology.md` |\n| Why a product's design works: Stripe, Linear, Notion, Airbnb, Figma, Arc, Duolingo, Vercel, Apple Health, Discord, plus condensed analyses (Raycast, Supabase, Superhuman, Cal.com, Framer, Obsidian, Loom, and more) | `references\u002Fproduct-deep-dives.md` |\n| Redesign post-mortems: Snapchat, Windows 8, Digg, Twitter\u002FX, Google Plus, Sonos, Healthcare.gov, Reddit API, YouTube dislikes, Skype; redesign safety checklist | `references\u002Fredesign-failure-analysis.md` |\n\n## Cross-References\n\n- Grounding comments in a heuristic, especially at 60%: `nng-ux-heuristics`\n- Biases in the critique room (anchoring, confirmation, groupthink): `cognitive-psychology-ux`\n- Settling disagreements with a usability test: `ux-research-methods`\n- Design system component use at 90%: `component-patterns-code`\n- Quantitative evidence for feedback: `ux-metrics-measurement`\n- Dark patterns and manipulative content: `ux-ethics-content-strategy`\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fdesign-critique-case-studies","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 design-critique-case-studies",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill design-critique-case-studies",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill design-critique-case-studies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-critique-case-studies\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcritique-methodology.md","REFERENCE","参考文档",43691,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-critique-case-studies\u002Freferences\u002Fcritique-methodology.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fproduct-deep-dives.md",63062,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-critique-case-studies\u002Freferences\u002Fproduct-deep-dives.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fredesign-failure-analysis.md",37391,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-critique-case-studies\u002Freferences\u002Fredesign-failure-analysis.md",[62,68,75,82,89,96],{"skillNo":63,"name":64,"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":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]