[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0H4HHSR2CTMXC32RDNSXB":3,"skill-same:01M7F0H4HHSR2CTMXC32RDNSXB":65},{"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},"01M7F0H4HHSR2CTMXC32RDNSXB","design-process-methods",null,"Design process methodology: NNG's six phases, Double Diamond, Google Design Sprint, IDEO, Lean UX, and the bridge from AI-assisted building to evidence-based UX. Use when framing how the work should run, planning a sprint, or grounding a build in Empathize, Define, Ideate, Prototype, Test.","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-process-methods\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: design-process-methods\ndescription: \"Design process methodology: NNG's six phases, Double Diamond, Google Design Sprint, IDEO, Lean UX, and the bridge from AI-assisted building to evidence-based UX. Use when framing how the work should run, planning a sprint, or grounding a build in Empathize, Define, Ideate, Prototype, Test.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# UX Process Workflow — From Process to Product\n\n## Purpose\n\nGround every AI-assisted build in established UX process. Prompting can produce polished UI quickly; process decides whether it solves the right problem. The vibe-coding shortcut is:\n\n```\nTraditional:  Empathize → Define → Ideate → Prototype → Test → Implement\nVibe coding:  Prompt → Ship → Hope\n```\n\nThe result is UI that solves the wrong problem, looks like every other AI-generated interface, and erodes the builder's own design judgment (arXiv:2509.10652).\n\n## The process in three lines\n\n```\nBEFORE you prompt: \"Who is this for, and what problem does it solve?\"\nWHILE it generates:  \"Does this match the user's reality, or the AI's patterns?\"\nAFTER it generates:  Run \u002Faudit + \u002Fa11y. Fix severity 3-4. Ship.\n```\n\n## Core rules\n\n- **Use NNG's six phases in three stages.** Understand (Empathize, Define) → Explore (Ideate, Prototype) → Materialize (Test, Implement). Design Ops is iterative, so loop back as needed. NNG provides the thinking; Design Ops commands provide the doing.\n- **Empathize before prompting.** Name a specific user, the task (verb + noun), their current workaround, what frustrates them, and their environment (device, context, accessibility needs).\n- **Define in one sentence:** \"Users who [X] need [Y] because [Z].\" If you can't fill it in, go back to Empathize. Add measurable success criteria.\n- **Diverge before converging.** List three approaches before generating one. The first idea is rarely the best.\n- **Prototypes are questions.** Generate 2-3 variations and evaluate them; don't treat the first output as production code.\n- **Testing is learning, not validation.** Heuristic review, cognitive walkthrough, accessibility audit, and 5-user think-aloud tests find problems; they don't prove the design works.\n- **Watch for the three risks** of skipping process: pseudo-productivity (more screens, fewer solved problems), homogenization (every AI UI looks the same), and skill erosion (losing the ability to critique).\n- **Check every generated screen** for the persona, the information hierarchy, and all seven states: empty, loading, populated, error, partial, offline, updating.\n\n## Choosing a methodology\n\n| Context | Methodology |\n| --- | --- |\n| Solo developer, vibe coding | Lean UX + Vercel\u002FFigma design-engineer workflow |\n| Small team (2-5) | Google Design Sprint (compressed) or Double Diamond |\n| Large organization | IBM Enterprise Design Thinking |\n| Accessibility-first | Microsoft Inclusive Design |\n| Complex, ambiguous problem | IDEO Human-Centered Design |\n| Continuous iteration | Spotify squad model + Lean UX |\n\n## The Builder's Cheat Sheet\n\n### I have 2 minutes\n\nRun `\u002Fbrief` on whatever you're about to build. Just the problem statement. That's it.\n\n### I have 10 minutes\n\n`\u002Fdesign-ops` → `\u002Fbrief` → then build with the constraint stack pasted into your prompt.\n\n### I have 30 minutes\n\n`\u002Fbrief` → `\u002Fstyle` → `\u002Ftokens` → then build. You now have a defined problem, visual direction, and token system.\n\n### I have 2 hours\n\nFull Phase 0→5 journey. `\u002Fdesign-ops` → `\u002Fbrief` → `\u002Fstyle` → `\u002Fstyle` → `\u002Ftokens` → `\u002Fscreen` → `\u002Fcomponent` → `\u002Faudit` → `\u002Fa11y` → `\u002Froast`. This is what real design teams do.\n\n### I have a real product to ship\n\nFollow the full 22-step journey via `\u002Fdesign-ops`. Run every audit. Loop `\u002Froast` → `\u002Fremix` → `\u002Froast` until all scores are 7+. This is how Stripe, Linear, and Notion work.\n\n### The one non-negotiable\n\nWhatever your time budget: **run `\u002Faudit` + `\u002Fa11y` before shipping**. 5 minutes. Zero excuses.\n\n## Routing\n\n| Question | Read |\n| --- | --- |\n| Each NNG phase: goals, methods, terminal workflow, command mapping; full process-to-command map | `references\u002Fnng-six-phases.md` |\n| IDEO, Double Diamond, Design Sprint, IBM, Lean UX, Spotify, Microsoft, Vercel\u002FFigma in depth; summary table; decision matrix | `references\u002Fcompany-ux-methodologies.md` |\n| Before\u002Fwhile\u002Fafter checklists, 15-minute UX check, anti-patterns, process recipes, maturity, constraint stack | `references\u002Fvibe-coder-ux-bridge.md` |\n| ISO 9241-210, Norman's seven principles, cognitive laws | `references\u002Facademic-foundations.md` |\n\n## Cross-References\n\n- `nng-ux-heuristics` — The 10 heuristics used in the Test phase\n- `ux-research-methods` — Research methodologies for the Empathize phase\n- `cognitive-psychology-ux` — Cognitive laws that justify process rigor\n- `agentic-ai-generative-ux` — AI-assisted design patterns and risks\n- `ux-ethics-content-strategy` — Ethical frameworks for the Define phase\n- `ux-metrics-measurement` — Measurement frameworks for success criteria\n- `design-systems-architecture` — System thinking for the Implement phase\n- `design-critique-case-studies` — Case studies showing process impact (Stripe, Linear: process-heavy; Sonos 2024, Healthcare.gov: process-light failures)\n","# UX Process Workflow — From Process to Product\n\n## Purpose\n\nGround every AI-assisted build in established UX process. Prompting can produce polished UI quickly; process decides whether it solves the right problem. The vibe-coding shortcut is:\n\n```\nTraditional:  Empathize → Define → Ideate → Prototype → Test → Implement\nVibe coding:  Prompt → Ship → Hope\n```\n\nThe result is UI that solves the wrong problem, looks like every other AI-generated interface, and erodes the builder's own design judgment (arXiv:2509.10652).\n\n## The process in three lines\n\n```\nBEFORE you prompt: \"Who is this for, and what problem does it solve?\"\nWHILE it generates:  \"Does this match the user's reality, or the AI's patterns?\"\nAFTER it generates:  Run \u002Faudit + \u002Fa11y. Fix severity 3-4. Ship.\n```\n\n## Core rules\n\n- **Use NNG's six phases in three stages.** Understand (Empathize, Define) → Explore (Ideate, Prototype) → Materialize (Test, Implement). Design Ops is iterative, so loop back as needed. NNG provides the thinking; Design Ops commands provide the doing.\n- **Empathize before prompting.** Name a specific user, the task (verb + noun), their current workaround, what frustrates them, and their environment (device, context, accessibility needs).\n- **Define in one sentence:** \"Users who [X] need [Y] because [Z].\" If you can't fill it in, go back to Empathize. Add measurable success criteria.\n- **Diverge before converging.** List three approaches before generating one. The first idea is rarely the best.\n- **Prototypes are questions.** Generate 2-3 variations and evaluate them; don't treat the first output as production code.\n- **Testing is learning, not validation.** Heuristic review, cognitive walkthrough, accessibility audit, and 5-user think-aloud tests find problems; they don't prove the design works.\n- **Watch for the three risks** of skipping process: pseudo-productivity (more screens, fewer solved problems), homogenization (every AI UI looks the same), and skill erosion (losing the ability to critique).\n- **Check every generated screen** for the persona, the information hierarchy, and all seven states: empty, loading, populated, error, partial, offline, updating.\n\n## Choosing a methodology\n\n| Context | Methodology |\n| --- | --- |\n| Solo developer, vibe coding | Lean UX + Vercel\u002FFigma design-engineer workflow |\n| Small team (2-5) | Google Design Sprint (compressed) or Double Diamond |\n| Large organization | IBM Enterprise Design Thinking |\n| Accessibility-first | Microsoft Inclusive Design |\n| Complex, ambiguous problem | IDEO Human-Centered Design |\n| Continuous iteration | Spotify squad model + Lean UX |\n\n## The Builder's Cheat Sheet\n\n### I have 2 minutes\n\nRun `\u002Fbrief` on whatever you're about to build. Just the problem statement. That's it.\n\n### I have 10 minutes\n\n`\u002Fdesign-ops` → `\u002Fbrief` → then build with the constraint stack pasted into your prompt.\n\n### I have 30 minutes\n\n`\u002Fbrief` → `\u002Fstyle` → `\u002Ftokens` → then build. You now have a defined problem, visual direction, and token system.\n\n### I have 2 hours\n\nFull Phase 0→5 journey. `\u002Fdesign-ops` → `\u002Fbrief` → `\u002Fstyle` → `\u002Fstyle` → `\u002Ftokens` → `\u002Fscreen` → `\u002Fcomponent` → `\u002Faudit` → `\u002Fa11y` → `\u002Froast`. This is what real design teams do.\n\n### I have a real product to ship\n\nFollow the full 22-step journey via `\u002Fdesign-ops`. Run every audit. Loop `\u002Froast` → `\u002Fremix` → `\u002Froast` until all scores are 7+. This is how Stripe, Linear, and Notion work.\n\n### The one non-negotiable\n\nWhatever your time budget: **run `\u002Faudit` + `\u002Fa11y` before shipping**. 5 minutes. Zero excuses.\n\n## Routing\n\n| Question | Read |\n| --- | --- |\n| Each NNG phase: goals, methods, terminal workflow, command mapping; full process-to-command map | `references\u002Fnng-six-phases.md` |\n| IDEO, Double Diamond, Design Sprint, IBM, Lean UX, Spotify, Microsoft, Vercel\u002FFigma in depth; summary table; decision matrix | `references\u002Fcompany-ux-methodologies.md` |\n| Before\u002Fwhile\u002Fafter checklists, 15-minute UX check, anti-patterns, process recipes, maturity, constraint stack | `references\u002Fvibe-coder-ux-bridge.md` |\n| ISO 9241-210, Norman's seven principles, cognitive laws | `references\u002Facademic-foundations.md` |\n\n## Cross-References\n\n- `nng-ux-heuristics` — The 10 heuristics used in the Test phase\n- `ux-research-methods` — Research methodologies for the Empathize phase\n- `cognitive-psychology-ux` — Cognitive laws that justify process rigor\n- `agentic-ai-generative-ux` — AI-assisted design patterns and risks\n- `ux-ethics-content-strategy` — Ethical frameworks for the Define phase\n- `ux-metrics-measurement` — Measurement frameworks for success criteria\n- `design-systems-architecture` — System thinking for the Implement phase\n- `design-critique-case-studies` — Case studies showing process impact (Stripe, Linear: process-heavy; Sonos 2024, Healthcare.gov: process-light failures)\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods","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-process-methods",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill design-process-methods",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill design-process-methods","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Facademic-foundations.md","REFERENCE","参考文档",3838,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods\u002Freferences\u002Facademic-foundations.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcompany-ux-methodologies.md",40683,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods\u002Freferences\u002Fcompany-ux-methodologies.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fnng-six-phases.md",12086,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods\u002Freferences\u002Fnng-six-phases.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fvibe-coder-ux-bridge.md",32724,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-process-methods\u002Freferences\u002Fvibe-coder-ux-bridge.md",[66,72,79,86,93,100],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":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":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[]]