[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E23PJKG7MHFPDT3SC74QXX":3,"skill-same:01M6E23PJKG7MHFPDT3SC74QXX":72},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6E23PJKG7MHFPDT3SC74QXX","pm-product-strategy",null,"Product strategy frameworks for startup and product teams. Covers vision, competitive analysis (Porter, PESTLE), market sizing, SWOT, personas, BMC, Lean Canvas, pricing, PRD, and user stories.","ByeongminLee\u002Fnextjs-claude-code","ByeongminLee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71276006?v=4","01M6E1S467E7GC0NE144SWHC0V","Byeongmin Lee","01M6E1S4AV3W0B08Z2YBK26VG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fpm-product-strategy\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 strategy","pm product strategy","product","pm","strategy","competitive analysis","swot","frameworks","lean canvas","personas","Market","vision","canvas","lean","analysis","startup","prd","teams","market sizing","pricing","2026-11-10 10:12:30",false,"---\nname: pm-product-strategy\ndescription: Product strategy frameworks for startup and product teams. Covers vision, competitive analysis (Porter, PESTLE), market sizing, SWOT, personas, BMC, Lean Canvas, pricing, PRD, and user stories.\n---\n\n# Product Strategy Skill\n\nConsolidated product management frameworks from phuryn\u002Fpm-skills. Use this skill when developing product strategy, analyzing markets, building business models, or defining product vision.\n\n## Product Vision\n\nA compelling product vision answers: \"How can we inspire people? What are we aspiring to achieve? What values do we uphold?\"\n\n### Characteristics of Effective Visions\n- **Inspiring** — motivates teams toward genuine commitment\n- **Achievable** — grounded in realistic resources and market conditions\n- **Emotional** — creates meaningful connection with stakeholders\n- **Memorable** — communicable in a single sentence\n\n### Development Process\n1. Review company mission, product information, and market landscape\n2. Identify core problems being solved and for whom\n3. Envision the ideal future state for customers and the organization\n4. Draft 3-5 vision variations with different angles\n5. Select the strongest option with clear rationale\n6. Validate alignment with company values and market opportunities\n\nVision is a living statement that evolves with strategy. It is distinct from strategy, objectives, and roadmaps.\n\n## Product Strategy Canvas\n\nDevelop strategy across nine dimensions:\n\n1. **Vision** — inspiration, aspirational goals, core values\n2. **Market Segments** — customer problems via Jobs to Be Done; identify initial target segments strategically\n3. **Relative Costs** — position between cost optimization (Southwest model) and premium value (Starbucks model)\n4. **Value Proposition** — \"What before \u002F How \u002F What after\" structure examining customer situations, solutions, outcomes, and competitive alternatives\n5. **Trade-offs** — what the product explicitly will NOT pursue, creating strategic focus\n6. **Key Metrics** — North Star Metric and quarterly One Metric That Matters (OMTM)\n7. **Growth** — acquisition strategy, scaling approach, unit economics\n8. **Capabilities** — required competencies, build vs. partner decisions\n9. **Defensibility** — network effects, switching costs, IP, market entry barriers\n\nValidate strategy through hypothesis identification and low-effort experiments. Revise quarterly.\n\n## Market Sizing (TAM \u002F SAM \u002F SOM)\n\n### Seven-Step Framework\n1. **Market Definition** — establish boundaries, customer segments, geography\n2. **Top-Down Estimation** — narrow from total industry size using available data\n3. **Bottom-Up Estimation** — build from unit economics to cross-validate\n4. **SAM Scoping** — identify realistically serviceable portion of TAM\n5. **SOM Estimation** — achievable share over 1-3 years based on competitive position\n6. **Growth Projection** — forecast market evolution with drivers and trends\n7. **Assumption Mapping** — surface and validate underlying assumptions\n\n### Required Output\n- Market definition with problem space and constraints\n- TAM with top-down and bottom-up estimates, reconciliation, annual revenue opportunity\n- SAM with serviceable portion percentage and reasoning\n- SOM with competitive position basis and achievement timeline\n- Summary table comparing current and 2-3 year projections\n- Key assumptions with confidence levels and validation methods\n\nAlways use dual estimation approaches for triangulation. Cite data sources explicitly.\n\n## SWOT Analysis\n\n### Framework Structure\n\n**Internal Factors:**\n- **Strengths** — unique capabilities, brand recognition, customer loyalty, technology advantages, operational efficiencies\n- **Weaknesses** — resource constraints, infrastructure gaps, limited market presence, cost challenges, outdated systems\n\n**External Factors:**\n- **Opportunities** — growing market segments, technological advances, regulatory shifts, expansion into adjacent markets\n- **Threats** — emerging competitors, shifting preferences, technological disruption, regulatory risks, supply chain vulnerabilities\n\n### Process\n1. Identify 5-7 items per category with specific evidence\n2. Cross-reference: how strengths address opportunities, how weaknesses create vulnerability to threats\n3. Determine strategic direction:\n   - **Build** — leverage strengths + opportunities\n   - **Defend** — address weaknesses + threats\n   - **Pivot** — use opportunities to reshape competitive dynamics\n   - **Exit** — if competitive position deteriorates significantly\n\nUpdate SWOT quarterly aligned with market conditions.\n\n## User Personas\n\n### Building Effective Personas\n1. **Research** — interview 5-10 users per segment; analyze behavioral data\n2. **Identify Patterns** — cluster by goals, pain points, and behaviors (not demographics alone)\n3. **Define Each Persona:**\n   - Name, role, and context\n   - Primary goals and motivations\n   - Key pain points and frustrations\n   - Current workarounds and tools\n   - Decision-making criteria\n   - Success metrics from their perspective\n4. **Validate** — test personas against real user behavior; update with new data\n\n### Jobs to Be Done (JTBD)\nFrame personas around jobs: \"When [situation], I want to [motivation], so I can [expected outcome].\"\n\n## Business Model Canvas\n\nNine building blocks for how the business creates, delivers, and captures value:\n\n### Creating Value (Left)\n1. **Key Partners** — strategic partners, suppliers, joint ventures\n2. **Key Activities** — critical processes (production, problem-solving, platform)\n3. **Key Resources** — physical, intellectual, human, financial assets\n\n### The Value Proposition (Center)\n4. **Value Propositions** — problems solved, needs satisfied, quantitative vs. qualitative value\n\n### Delivering Value (Right)\n5. **Customer Relationships** — personal assistance, self-service, automated, community\n6. **Channels** — awareness, purchase, delivery, after-sales (direct vs. indirect)\n7. **Customer Segments** — mass market, niche, segmented, multi-sided platform\n\n### Financial Viability (Bottom)\n8. **Cost Structure** — fixed vs. variable, cost drivers, cost-driven vs. value-driven\n9. **Revenue Streams** — pricing mechanisms, LTV, unit economics\n\n**Viability test:** LTV > 3x CAC.\n\n### When to Use\n- **BMC** — established businesses, corporate strategy, investor materials\n- **Lean Canvas** — startups, hypothesis testing, faster iteration\n- **Startup Canvas** — new products needing strategic clarity alongside business model\n\n## Porter's Five Forces\n\nAssess competitive intensity and industry attractiveness:\n\n1. **Threat of New Entrants** — barriers to entry (capital, regulation, brand loyalty, economies of scale)\n2. **Bargaining Power of Suppliers** — few suppliers = high power; many substitutes = low power\n3. **Bargaining Power of Buyers** — low switching costs or many alternatives = high buyer power\n4. **Threat of Substitutes** — alternative solutions that fulfill the same need differently\n5. **Industry Rivalry** — number of competitors, growth rate, differentiation, exit barriers\n\nScore each force (Low\u002FMedium\u002FHigh). High total = less attractive industry. Identify which force to address first.\n\n## PESTLE Analysis\n\nSix macro-environmental factors that affect strategy:\n\n- **Political** — government stability, trade policy, tax regulations, labor law\n- **Economic** — GDP growth, inflation, interest rates, exchange rates, consumer spending\n- **Social** — demographics, cultural trends, lifestyle changes, education levels\n- **Technological** — R&D activity, automation, tech maturity, disruption potential\n- **Legal** — consumer protection, employment law, data privacy (GDPR, CCPA), IP\n- **Environmental** — sustainability regulations, climate impact, resource availability\n\n## Lean Canvas\n\nOne-page business model for startups (Ash Maurya adaptation):\n\n| Block | Question |\n|-------|----------|\n| Problem (top 3) | What are the top 3 problems? |\n| Customer Segments | Who has this problem? Early adopters? |\n| Unique Value Proposition | Single clear message: why different and worth attention |\n| Solution | Top 3 features for each problem |\n| Channels | How do you reach customers? |\n| Revenue Streams | How do you make money? Pricing model? |\n| Cost Structure | Fixed + variable costs, burn rate |\n| Key Metrics | One metric that matters right now |\n| Unfair Advantage | Something that cannot be easily copied or bought |\n\n## Pricing Strategy\n\n- **Cost-Plus** — cost + markup %. Simple but ignores value perception.\n- **Value-Based** — price reflects perceived value to customer. Requires user research.\n- **Competitive** — match or undercut competitors. Risk: race to bottom.\n- **Penetration** — low initial price to gain share, raise later. Risk: hard to raise.\n- **Freemium** — free base + paid premium. Key metric: free-to-paid conversion rate (2-5% typical).\n- **Usage-Based** — pay per use. Aligns cost with value. Risk: unpredictable revenue.\n\nRule of 100: for prices under $100, show % discount; over $100, show $ amount off.\n\n## PRD Structure (Product Requirements Document)\n\n1. **Problem Statement** — what problem, who has it, evidence of demand\n2. **Goals & Success Metrics** — measurable outcomes, north star metric\n3. **User Stories** — \"As a [user], I want [action], so that [outcome]\"\n4. **Requirements** — functional (what it does) + non-functional (performance, security)\n5. **Out of Scope** — explicitly what this does NOT include\n6. **Design & UX** — wireframes, user flows, interaction patterns\n7. **Technical Considerations** — architecture impact, dependencies, migration\n8. **Timeline & Milestones** — phases, MVP scope, future iterations\n\n## Usage\n\nStart with vision + market sizing → SWOT for position → personas for user grounding → Strategy Canvas → BMC\u002FLean Canvas for viability. Revisit quarterly.\n\n*Sourced from [phuryn\u002Fpm-skills](https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills) (MIT License)*\n","# Product Strategy Skill\n\nConsolidated product management frameworks from phuryn\u002Fpm-skills. Use this skill when developing product strategy, analyzing markets, building business models, or defining product vision.\n\n## Product Vision\n\nA compelling product vision answers: \"How can we inspire people? What are we aspiring to achieve? What values do we uphold?\"\n\n### Characteristics of Effective Visions\n- **Inspiring** — motivates teams toward genuine commitment\n- **Achievable** — grounded in realistic resources and market conditions\n- **Emotional** — creates meaningful connection with stakeholders\n- **Memorable** — communicable in a single sentence\n\n### Development Process\n1. Review company mission, product information, and market landscape\n2. Identify core problems being solved and for whom\n3. Envision the ideal future state for customers and the organization\n4. Draft 3-5 vision variations with different angles\n5. Select the strongest option with clear rationale\n6. Validate alignment with company values and market opportunities\n\nVision is a living statement that evolves with strategy. It is distinct from strategy, objectives, and roadmaps.\n\n## Product Strategy Canvas\n\nDevelop strategy across nine dimensions:\n\n1. **Vision** — inspiration, aspirational goals, core values\n2. **Market Segments** — customer problems via Jobs to Be Done; identify initial target segments strategically\n3. **Relative Costs** — position between cost optimization (Southwest model) and premium value (Starbucks model)\n4. **Value Proposition** — \"What before \u002F How \u002F What after\" structure examining customer situations, solutions, outcomes, and competitive alternatives\n5. **Trade-offs** — what the product explicitly will NOT pursue, creating strategic focus\n6. **Key Metrics** — North Star Metric and quarterly One Metric That Matters (OMTM)\n7. **Growth** — acquisition strategy, scaling approach, unit economics\n8. **Capabilities** — required competencies, build vs. partner decisions\n9. **Defensibility** — network effects, switching costs, IP, market entry barriers\n\nValidate strategy through hypothesis identification and low-effort experiments. Revise quarterly.\n\n## Market Sizing (TAM \u002F SAM \u002F SOM)\n\n### Seven-Step Framework\n1. **Market Definition** — establish boundaries, customer segments, geography\n2. **Top-Down Estimation** — narrow from total industry size using available data\n3. **Bottom-Up Estimation** — build from unit economics to cross-validate\n4. **SAM Scoping** — identify realistically serviceable portion of TAM\n5. **SOM Estimation** — achievable share over 1-3 years based on competitive position\n6. **Growth Projection** — forecast market evolution with drivers and trends\n7. **Assumption Mapping** — surface and validate underlying assumptions\n\n### Required Output\n- Market definition with problem space and constraints\n- TAM with top-down and bottom-up estimates, reconciliation, annual revenue opportunity\n- SAM with serviceable portion percentage and reasoning\n- SOM with competitive position basis and achievement timeline\n- Summary table comparing current and 2-3 year projections\n- Key assumptions with confidence levels and validation methods\n\nAlways use dual estimation approaches for triangulation. Cite data sources explicitly.\n\n## SWOT Analysis\n\n### Framework Structure\n\n**Internal Factors:**\n- **Strengths** — unique capabilities, brand recognition, customer loyalty, technology advantages, operational efficiencies\n- **Weaknesses** — resource constraints, infrastructure gaps, limited market presence, cost challenges, outdated systems\n\n**External Factors:**\n- **Opportunities** — growing market segments, technological advances, regulatory shifts, expansion into adjacent markets\n- **Threats** — emerging competitors, shifting preferences, technological disruption, regulatory risks, supply chain vulnerabilities\n\n### Process\n1. Identify 5-7 items per category with specific evidence\n2. Cross-reference: how strengths address opportunities, how weaknesses create vulnerability to threats\n3. Determine strategic direction:\n   - **Build** — leverage strengths + opportunities\n   - **Defend** — address weaknesses + threats\n   - **Pivot** — use opportunities to reshape competitive dynamics\n   - **Exit** — if competitive position deteriorates significantly\n\nUpdate SWOT quarterly aligned with market conditions.\n\n## User Personas\n\n### Building Effective Personas\n1. **Research** — interview 5-10 users per segment; analyze behavioral data\n2. **Identify Patterns** — cluster by goals, pain points, and behaviors (not demographics alone)\n3. **Define Each Persona:**\n   - Name, role, and context\n   - Primary goals and motivations\n   - Key pain points and frustrations\n   - Current workarounds and tools\n   - Decision-making criteria\n   - Success metrics from their perspective\n4. **Validate** — test personas against real user behavior; update with new data\n\n### Jobs to Be Done (JTBD)\nFrame personas around jobs: \"When [situation], I want to [motivation], so I can [expected outcome].\"\n\n## Business Model Canvas\n\nNine building blocks for how the business creates, delivers, and captures value:\n\n### Creating Value (Left)\n1. **Key Partners** — strategic partners, suppliers, joint ventures\n2. **Key Activities** — critical processes (production, problem-solving, platform)\n3. **Key Resources** — physical, intellectual, human, financial assets\n\n### The Value Proposition (Center)\n4. **Value Propositions** — problems solved, needs satisfied, quantitative vs. qualitative value\n\n### Delivering Value (Right)\n5. **Customer Relationships** — personal assistance, self-service, automated, community\n6. **Channels** — awareness, purchase, delivery, after-sales (direct vs. indirect)\n7. **Customer Segments** — mass market, niche, segmented, multi-sided platform\n\n### Financial Viability (Bottom)\n8. **Cost Structure** — fixed vs. variable, cost drivers, cost-driven vs. value-driven\n9. **Revenue Streams** — pricing mechanisms, LTV, unit economics\n\n**Viability test:** LTV > 3x CAC.\n\n### When to Use\n- **BMC** — established businesses, corporate strategy, investor materials\n- **Lean Canvas** — startups, hypothesis testing, faster iteration\n- **Startup Canvas** — new products needing strategic clarity alongside business model\n\n## Porter's Five Forces\n\nAssess competitive intensity and industry attractiveness:\n\n1. **Threat of New Entrants** — barriers to entry (capital, regulation, brand loyalty, economies of scale)\n2. **Bargaining Power of Suppliers** — few suppliers = high power; many substitutes = low power\n3. **Bargaining Power of Buyers** — low switching costs or many alternatives = high buyer power\n4. **Threat of Substitutes** — alternative solutions that fulfill the same need differently\n5. **Industry Rivalry** — number of competitors, growth rate, differentiation, exit barriers\n\nScore each force (Low\u002FMedium\u002FHigh). High total = less attractive industry. Identify which force to address first.\n\n## PESTLE Analysis\n\nSix macro-environmental factors that affect strategy:\n\n- **Political** — government stability, trade policy, tax regulations, labor law\n- **Economic** — GDP growth, inflation, interest rates, exchange rates, consumer spending\n- **Social** — demographics, cultural trends, lifestyle changes, education levels\n- **Technological** — R&D activity, automation, tech maturity, disruption potential\n- **Legal** — consumer protection, employment law, data privacy (GDPR, CCPA), IP\n- **Environmental** — sustainability regulations, climate impact, resource availability\n\n## Lean Canvas\n\nOne-page business model for startups (Ash Maurya adaptation):\n\n| Block | Question |\n|-------|----------|\n| Problem (top 3) | What are the top 3 problems? |\n| Customer Segments | Who has this problem? Early adopters? |\n| Unique Value Proposition | Single clear message: why different and worth attention |\n| Solution | Top 3 features for each problem |\n| Channels | How do you reach customers? |\n| Revenue Streams | How do you make money? Pricing model? |\n| Cost Structure | Fixed + variable costs, burn rate |\n| Key Metrics | One metric that matters right now |\n| Unfair Advantage | Something that cannot be easily copied or bought |\n\n## Pricing Strategy\n\n- **Cost-Plus** — cost + markup %. Simple but ignores value perception.\n- **Value-Based** — price reflects perceived value to customer. Requires user research.\n- **Competitive** — match or undercut competitors. Risk: race to bottom.\n- **Penetration** — low initial price to gain share, raise later. Risk: hard to raise.\n- **Freemium** — free base + paid premium. Key metric: free-to-paid conversion rate (2-5% typical).\n- **Usage-Based** — pay per use. Aligns cost with value. Risk: unpredictable revenue.\n\nRule of 100: for prices under $100, show % discount; over $100, show $ amount off.\n\n## PRD Structure (Product Requirements Document)\n\n1. **Problem Statement** — what problem, who has it, evidence of demand\n2. **Goals & Success Metrics** — measurable outcomes, north star metric\n3. **User Stories** — \"As a [user], I want [action], so that [outcome]\"\n4. **Requirements** — functional (what it does) + non-functional (performance, security)\n5. **Out of Scope** — explicitly what this does NOT include\n6. **Design & UX** — wireframes, user flows, interaction patterns\n7. **Technical Considerations** — architecture impact, dependencies, migration\n8. **Timeline & Milestones** — phases, MVP scope, future iterations\n\n## Usage\n\nStart with vision + market sizing → SWOT for position → personas for user grounding → Strategy Canvas → BMC\u002FLean Canvas for viability. Revisit quarterly.\n\n*Sourced from [phuryn\u002Fpm-skills](https:\u002F\u002Fgithub.com\u002Fphuryn\u002Fpm-skills) (MIT License)*\n",{"name":5,"description":7},"main","330a71e3d12264515ce3477e446d29fd34a88a9d","template\u002Fskills-archive\u002Fpm-product-strategy",1,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code","https:\u002F\u002Fbyeongminlee.github.io\u002Fnextjs-claude-code\u002F","https:\u002F\u002Fgithub.com\u002FByeongminLee","byeongmin.dev","2026-03-27 12:45:44",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add ByeongminLee\u002Fnextjs-claude-code --skill pm-product-strategy",{"tool":64,"command":65},"bunx","bunx skills add ByeongminLee\u002Fnextjs-claude-code --skill pm-product-strategy",{"tool":67,"command":68},"pnpm","pnpm dlx skills add ByeongminLee\u002Fnextjs-claude-code --skill pm-product-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fpm-product-strategy\u002FSKILL.md",true,[],[73,92,100,132,159,198],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":44},"01M6E263DRDCZ5AX01N6MDYC6Z","zustand","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fzustand\u002FSKILL.md",[],[75,80,81,82,83,84,85,86,87,88,89,90,91],"triggers","state management","zustand state","implementation","use","guide","management","src","actions","state","code","development",{"skillNo":93,"name":94,"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":95,"categories":96,"keywords":97,"publishedAt":44},"01M6E260QFP3ZMXY2Y6KTGZYXS","web-vitals","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fweb-vitals\u002FSKILL.md",[],[98,99],"web vitals","web",{"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":111,"publishedAt":44},"01M6E25QEKXHH092S5RB0GKM0K","vercel-storage","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-storage\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131],"vercel","vercel storage","storage","supabase","api","mongodb","SET","nextjs","database","auth","migrate","click","app","neon","prisma","postgres","expert","up","auto","configure",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":142,"publishedAt":44},"01M6E25EC9YM4QM0KBQ2W5R1SC","vercel-functions","Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",[138,139],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[143,112,144,145,146,147,148,149,124,125,150,151,152,153,154,155,156,157,158,128],"functions","vercel functions","local","shared","project","time","apps","express","vercel ai sdk","router","loop","server","logs","streaming","delete","create",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":180,"publishedAt":44},"01M6E25873YRYP96MSQK7E2D9X","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fui-ux-pro-max\u002FSKILL.md",[165,168,171,174,177],{"categoryNo":166,"categoryName":167,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":169,"categoryName":170,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":172,"categoryName":173,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[181,182,183,184,185,186,187,188,124,189,190,191,192,193,194,195,196,88,197,158],"ui ux pro max","ui","ux","max","css","MCP","design","react","card","chart","fix","projects","plan","improve","Tailwind","Animation","search",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":44},"01M6E251G3FJSRB9019V20QK9X","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturborepo\u002FSKILL.md",[],[200,205,84,206,207,149,80,208,209,129,210,211,212,213,214,215,90,216,217,218],"cli","filter","environment variables","caching","structure","environment","monorepo","system","canary","Optimization","ci","packages","tasks","workflows"]