[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NKQX2KXGT59BEPW8FBZPW":3,"skill-same:01M71NKQX2KXGT59BEPW8FBZPW":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71NKQX2KXGT59BEPW8FBZPW","product-lens",null,"Use when pressure-testing whether a feature or product is worth building: YC-style diagnostic, founder review or user-journey audit with a go\u002Fno-go brief. For turning an approved idea into an implementation contract, use product-capability.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-lens\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-lens\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"product","lens","product lens","journey","when","capability","user-journey","for","feature","contract","yc","testing","idea","strategy","brief","audit","ux","planning","go","review","2026-11-10 10:56:23",false,"---\nname: product-lens\ndescription: \"Use when pressure-testing whether a feature or product is worth building: YC-style diagnostic, founder review or user-journey audit with a go\u002Fno-go brief. For turning an approved idea into an implementation contract, use product-capability.\"\ntags: [\"product\",\"strategy\",\"ux\",\"planning\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC\nsource_path: \"skills\u002Fproduct-lens\"\nsource_commit: bf70150eb2df8070024e5bdf08e4aa08959e2735\n---\n# Product Lens — Think Before You Build\n\nThis lane owns product diagnosis, not implementation-ready specification writing.\n\nIf the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to `product-capability`.\n\n## When to Use\n\n- Before starting any feature — validate the \"why\"\n- Weekly product review — are we building the right thing?\n- When stuck choosing between features\n- Before a launch — sanity check the user journey\n- When converting a vague idea into a product brief before engineering planning starts\n\n## How It Works\n\n### Mode 1: Product Diagnostic\n\nLike YC office hours but automated. Asks the hard questions:\n\n```\n1. Who is this for? (specific person, not \"developers\")\n2. What's the pain? (quantify: how often, how bad, what do they do today?)\n3. Why now? (what changed that makes this possible\u002Fnecessary?)\n4. What's the 10-star version? (if money\u002Ftime were unlimited)\n5. What's the MVP? (smallest thing that proves the thesis)\n6. What's the anti-goal? (what are you explicitly NOT building?)\n7. How do you know it's working? (metric, not vibes)\n```\n\nOutput: a `PRODUCT-BRIEF.md` with answers, risks, and a go\u002Fno-go recommendation.\n\nIf the result is \"yes, build this,\" the next lane is `product-capability`, not more founder-theater.\n\n### Mode 2: Founder Review\n\nReviews your current project through a founder lens:\n\n```\n1. Read README, CLAUDE.md, package.json, recent commits\n2. Infer: what is this trying to be?\n3. Score: product-market fit signals (0-10)\n   - Usage growth trajectory\n   - Retention indicators (repeat contributors, return users)\n   - Revenue signals (pricing page, billing code, Stripe integration)\n   - Competitive moat (what's hard to copy?)\n4. Identify: the one thing that would 10x this\n5. Flag: things you're building that don't matter\n```\n\n### Mode 3: User Journey Audit\n\nMaps the actual user experience:\n\n```\n1. Clone\u002Finstall the product as a new user\n2. Document every friction point (confusing steps, errors, missing docs)\n3. Time each step\n4. Compare to competitor onboarding\n5. Score: time-to-value (how long until the user gets their first win?)\n6. Recommend: top 3 fixes for onboarding\n```\n\n### Mode 4: Feature Prioritization\n\nWhen you have 10 ideas and need to pick 2:\n\n```\n1. List all candidate features\n2. Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)\n3. Rank by ICE score\n4. Apply constraints: runway, team size, dependencies\n5. Output: prioritized roadmap with rationale\n```\n\n## Output\n\nAll modes output actionable docs, not essays. Every recommendation has a specific next step.\n\n## Integration\n\nPair with:\n- `\u002Fbrowser-qa` to verify the user journey audit findings\n- `\u002Fdesign-system audit` for visual polish assessment\n- `\u002Fcanary-watch` for post-launch monitoring\n- `product-capability` when the product brief needs to become an implementation-ready capability plan\n","# Product Lens — Think Before You Build\n\nThis lane owns product diagnosis, not implementation-ready specification writing.\n\nIf the user needs a durable PRD-to-SRS or capability-contract artifact, hand off to `product-capability`.\n\n## When to Use\n\n- Before starting any feature — validate the \"why\"\n- Weekly product review — are we building the right thing?\n- When stuck choosing between features\n- Before a launch — sanity check the user journey\n- When converting a vague idea into a product brief before engineering planning starts\n\n## How It Works\n\n### Mode 1: Product Diagnostic\n\nLike YC office hours but automated. Asks the hard questions:\n\n```\n1. Who is this for? (specific person, not \"developers\")\n2. What's the pain? (quantify: how often, how bad, what do they do today?)\n3. Why now? (what changed that makes this possible\u002Fnecessary?)\n4. What's the 10-star version? (if money\u002Ftime were unlimited)\n5. What's the MVP? (smallest thing that proves the thesis)\n6. What's the anti-goal? (what are you explicitly NOT building?)\n7. How do you know it's working? (metric, not vibes)\n```\n\nOutput: a `PRODUCT-BRIEF.md` with answers, risks, and a go\u002Fno-go recommendation.\n\nIf the result is \"yes, build this,\" the next lane is `product-capability`, not more founder-theater.\n\n### Mode 2: Founder Review\n\nReviews your current project through a founder lens:\n\n```\n1. Read README, CLAUDE.md, package.json, recent commits\n2. Infer: what is this trying to be?\n3. Score: product-market fit signals (0-10)\n   - Usage growth trajectory\n   - Retention indicators (repeat contributors, return users)\n   - Revenue signals (pricing page, billing code, Stripe integration)\n   - Competitive moat (what's hard to copy?)\n4. Identify: the one thing that would 10x this\n5. Flag: things you're building that don't matter\n```\n\n### Mode 3: User Journey Audit\n\nMaps the actual user experience:\n\n```\n1. Clone\u002Finstall the product as a new user\n2. Document every friction point (confusing steps, errors, missing docs)\n3. Time each step\n4. Compare to competitor onboarding\n5. Score: time-to-value (how long until the user gets their first win?)\n6. Recommend: top 3 fixes for onboarding\n```\n\n### Mode 4: Feature Prioritization\n\nWhen you have 10 ideas and need to pick 2:\n\n```\n1. List all candidate features\n2. Score each on: impact (1-5) × confidence (1-5) ÷ effort (1-5)\n3. Rank by ICE score\n4. Apply constraints: runway, team size, dependencies\n5. Output: prioritized roadmap with rationale\n```\n\n## Output\n\nAll modes output actionable docs, not essays. Every recommendation has a specific next step.\n\n## Integration\n\nPair with:\n- `\u002Fbrowser-qa` to verify the user journey audit findings\n- `\u002Fdesign-system audit` for visual polish assessment\n- `\u002Fcanary-watch` for post-launch monitoring\n- `product-capability` when the product brief needs to become an implementation-ready capability plan\n",{"name":5,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[24,37,40,41],[],"https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC","skills\u002Fproduct-lens","bf70150eb2df8070024e5bdf08e4aa08959e2735","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-lens",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill product-lens",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill product-lens",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill product-lens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-lens\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1071,[83,111,143,166,190,217],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":110},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[91,92,93,94,95,96,97,98,99,100,101,43,102,103,104,105,106,107,108,109],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":126,"publishedAt":110},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[118,123],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[127,128,129,95,130,131,28,132,100,133,134,135,24,136,137,138,139,140,141,142],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":110},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[150],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,152,153,154,155,98,156,28,157,158,159,24,160,161,36,162,32,163,164,165],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","metrics","problem statement","use","document",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":110},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[100,136,177,178,31,179,98,164,28,180,181,182,183,159,184,185,186,187,188,189],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":202,"publishedAt":110},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":200,"categoryName":201,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000023","Skill与智能体开发",[203,204,205,206,31,207,208,209,210,99,211,212,213,100,102,184,214,215,216,186],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":224,"publishedAt":110},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[223],{"categoryNo":200,"categoryName":201,"taxonomyType":121,"taxonomyTypeDesc":122},[205,225,226,227,228,229,41,31,230,231,133,232,233,234,102,184,235,236,186,237],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]