[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETC6KQQJSSHN7B6H7NFMTN":3,"skill-same:01M7ETC6KQQJSSHN7B6H7NFMTN":75},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M7ETC6KQQJSSHN7B6H7NFMTN","define-problem-statement",null,"Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: define-problem-statement\ndescription: Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.\nlicense: Apache-2.0\nmetadata:\n  phase: define\n  version: \"2.1.0\"\n  updated: 2026-06-10\n  category: problem-framing\n  frameworks: [triple-diamond, lean-startup, design-thinking]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Problem Statement\n\nA problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on *what* problem to solve before jumping to *how* to solve it.\n\n## When to Use\n\n- Starting a new initiative or project to establish shared understanding\n- Realigning a drifted project back to its original intent\n- Communicating up to leadership or stakeholders about priorities\n- Evaluating whether a proposed solution actually addresses the core problem\n- Onboarding new team members to provide context\n\n## When NOT to Use\n\n- The problem is already agreed and engineering needs the spec -> use `deliver-prd`\n- You want to propose and compare solution approaches -> use `develop-solution-brief`\n- You are capturing customer motivation rather than a business problem -> use `define-jtbd-canvas`\n- The \"problem\" is really an unvalidated assumption -> frame it with `define-hypothesis` and test it before committing a team to it\n\n## Instructions\n\nWhen asked to create a problem statement, follow these steps:\n\n1. **Identify the User Segment**\n   Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like \"users\" - instead target \"mobile shoppers completing checkout\" or \"enterprise admins managing 50+ users.\"\n\n2. **Understand the Pain Points**\n   Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.\n\n3. **Establish Business Context**\n   Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?\n\n4. **Define Success Metrics**\n   Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.\n\n5. **Surface Constraints and Considerations**\n   Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.\n\n6. **Capture Open Questions**\n   Document what you don't know yet. What assumptions need validation? What additional research is needed?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete problem statement fills every template section: Problem Summary; User Impact; Business Context; Success Criteria; Constraints & Considerations; and Open Questions.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Problem is specific to a defined user segment (not \"all users\")\n- [ ] Impact is quantified with data or reasonable estimates\n- [ ] Success metrics have baselines and targets\n- [ ] Problem describes the \"what\" without prescribing the \"how\"\n- [ ] Business context explains why this matters now\n- [ ] Open questions are captured for follow-up\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Problem Statement\n\nA problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on *what* problem to solve before jumping to *how* to solve it.\n\n## When to Use\n\n- Starting a new initiative or project to establish shared understanding\n- Realigning a drifted project back to its original intent\n- Communicating up to leadership or stakeholders about priorities\n- Evaluating whether a proposed solution actually addresses the core problem\n- Onboarding new team members to provide context\n\n## When NOT to Use\n\n- The problem is already agreed and engineering needs the spec -> use `deliver-prd`\n- You want to propose and compare solution approaches -> use `develop-solution-brief`\n- You are capturing customer motivation rather than a business problem -> use `define-jtbd-canvas`\n- The \"problem\" is really an unvalidated assumption -> frame it with `define-hypothesis` and test it before committing a team to it\n\n## Instructions\n\nWhen asked to create a problem statement, follow these steps:\n\n1. **Identify the User Segment**\n   Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like \"users\" - instead target \"mobile shoppers completing checkout\" or \"enterprise admins managing 50+ users.\"\n\n2. **Understand the Pain Points**\n   Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.\n\n3. **Establish Business Context**\n   Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?\n\n4. **Define Success Metrics**\n   Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.\n\n5. **Surface Constraints and Considerations**\n   Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.\n\n6. **Capture Open Questions**\n   Document what you don't know yet. What assumptions need validation? What additional research is needed?\n\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete problem statement fills every template section: Problem Summary; User Impact; Business Context; Success Criteria; Constraints & Considerations; and Open Questions.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] Problem is specific to a defined user segment (not \"all users\")\n- [ ] Impact is quantified with data or reasonable estimates\n- [ ] Success metrics have baselines and targets\n- [ ] Problem describes the \"what\" without prescribing the \"how\"\n- [ ] Business context explains why this matters now\n- [ ] Open questions are captured for follow-up\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n",{"name":5,"license":14,"metadata":23,"description":7},{"phase":24,"author":25,"updated":26,"version":27,"category":28,"frameworks":29},"define","product-on-purpose",1781049600000,"2.1.0","problem-framing",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill define-problem-statement",{"tool":45,"command":46},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill define-problem-statement",{"tool":48,"command":49},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill define-problem-statement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Foutput-scenarios\u002Fcheckout-abandonment.md","REFERENCE","参考文档",1992,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002Fevals\u002Foutput-scenarios\u002Fcheckout-abandonment.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"evals\u002Ftrigger-fixtures.json",4396,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002Fevals\u002Ftrigger-fixtures.json",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"HISTORY.md",731,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002FHISTORY.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002FEXAMPLE.md",4095,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002Freferences\u002FEXAMPLE.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002FTEMPLATE.md",1727,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fproduct-on-purpose\u002Fpm-skills\u002Fdefine-problem-statement\u002Freferences\u002FTEMPLATE.md",[76,85,93,101,108,115],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]