[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HFPWHPSHNEYDM18KA988F":3,"skill-same:01M71HFPWHPSHNEYDM18KA988F":112},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M71HFPWHPSHNEYDM18KA988F","cpo-advisor",null,"Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"advisor","cpo advisor","vision","org","playbook","reporting","at","2026","organization","product","portfolio","product vision","org design","leadership","prioritization","when","org-design","roadmap","design","scaling","2026-11-10 10:12:30",false,"---\nname: \"cpo-advisor\"\ndescription: \"Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: cpo-leadership\n  updated: 2026-03-05\n  python-tools: pmf_scorer.py, portfolio_analyzer.py\n  frameworks: pmf-playbook, product-strategy, product-org-design\n---\n\n# CPO Advisor\n\nStrategic product leadership. Vision, portfolio, PMF, org design. Not for feature-level work — for the decisions that determine what gets built, why, and by whom.\n\n## Keywords\nCPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, Jobs to be Done, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects\n\n## Quick Start\n\n### Score Your Product-Market Fit\n```bash\npython scripts\u002Fpmf_scorer.py\n```\nMulti-dimensional PMF score across retention, engagement, satisfaction, and growth.\n\n### Analyze Your Product Portfolio\n```bash\npython scripts\u002Fportfolio_analyzer.py\n```\nBCG matrix classification, investment recommendations, portfolio health score.\n\n## The CPO's Core Responsibilities\n\nThe CPO owns three things. Everything else is delegation.\n\n| Responsibility | What It Means | Reference |\n|---------------|--------------|-----------|\n| **Portfolio** | Which products exist, which get investment, which get killed | `references\u002Fproduct_strategy.md` |\n| **Vision** | Where the product is going in 3-5 years and why customers care | `references\u002Fproduct_strategy.md` |\n| **Org** | The team structure that can actually execute the vision | `references\u002Fproduct_org_design.md` |\n| **PMF** | Measuring, achieving, and not losing product-market fit | `references\u002Fpmf_playbook.md` |\n| **Metrics** | North star → leading → lagging hierarchy, board reporting | This file |\n\n## Diagnostic Questions\n\nThese questions expose whether you have a strategy or a list.\n\n**Portfolio:**\n- Which product is the dog? Are you killing it or lying to yourself?\n- If you had to cut 30% of your portfolio tomorrow, what stays?\n- What's your portfolio's combined D30 retention? Is it trending up?\n\n**PMF:**\n- What's your retention curve for your best cohort?\n- What % of users would be \"very disappointed\" if your product disappeared?\n- Is organic growth happening without you pushing it?\n\n**Org:**\n- Can every PM articulate your north star and how their work connects to it?\n- When did your last product trio do user interviews together?\n- What's blocking your slowest team — the people or the structure?\n\n**Strategy:**\n- If you could only ship one thing this quarter, what is it and why?\n- What's your moat in 12 months? In 3 years?\n- What's the riskiest assumption in your current product strategy?\n\n## Product Metrics Hierarchy\n\n```\nNorth Star Metric (1, owned by CPO)\n  ↓ explains changes in\nLeading Indicators (3-5, owned by PMs)\n  ↓ eventually become\nLagging Indicators (revenue, churn, NPS)\n```\n\n**North Star rules:** One number. Measures customer value delivered, not revenue. Every team can influence it.\n\n**Good North Stars by business model:**\n\n| Model | North Star Example |\n|-------|------------------|\n| B2B SaaS | Weekly active accounts using core feature |\n| Consumer | D30 retained users |\n| Marketplace | Successful transactions per week |\n| PLG | Accounts reaching \"aha moment\" within 14 days |\n| Data product | Queries run per active user per week |\n\n### The CPO Dashboard\n\n| Category | Metric | Frequency |\n|----------|--------|-----------|\n| Growth | North star metric | Weekly |\n| Growth | D30 \u002F D90 retention by cohort | Weekly |\n| Acquisition | New activations | Weekly |\n| Activation | Time to \"aha moment\" | Weekly |\n| Engagement | DAU\u002FMAU ratio | Weekly |\n| Satisfaction | NPS trend | Monthly |\n| Portfolio | Revenue per product | Monthly |\n| Portfolio | Engineering investment % per product | Monthly |\n| Moat | Feature adoption depth | Monthly |\n\n## Investment Postures\n\nEvery product gets one: **Invest \u002F Maintain \u002F Kill**. \"Wait and see\" is not a posture — it's a decision to lose share.\n\n| Posture | Signal | Action |\n|---------|--------|--------|\n| **Invest** | High growth, strong or growing retention | Full team. Aggressive roadmap. |\n| **Maintain** | Stable revenue, slow growth, good margins | Bug fixes only. Milk it. |\n| **Kill** | Declining, negative or flat margins, no recovery path | Set a sunset date. Write a migration plan. |\n\n## Red Flags\n\n**Portfolio:**\n- Products that have been \"question marks\" for 2+ quarters without a decision\n- Engineering capacity allocated to your highest-revenue product but your highest-growth product is understaffed\n- More than 30% of team time on products with declining revenue\n\n**PMF:**\n- You have to convince users to keep using the product\n- Support requests are mostly \"how do I do X\" rather than \"I want X to also do Y\"\n- D30 retention is below 20% (consumer) or 40% (B2B) and not improving\n\n**Org:**\n- PMs writing specs and handing to design, who hands to engineering (waterfall in agile clothing)\n- Platform team has a 6-week queue for stream-aligned team requests\n- CPO has not talked to a real customer in 30+ days\n\n**Metrics:**\n- North star going up while retention is going down (metric is wrong)\n- Teams optimizing their own metrics at the expense of company metrics\n- Roadmap built from sales requests, not user behavior data\n\n## Integration with Other C-Suite Roles\n\n| When... | CPO works with... | To... |\n|---------|-------------------|-------|\n| Setting company direction | CEO | Translate vision into product bets |\n| Roadmap funding | CFO | Justify investment allocation per product |\n| Scaling product org | COO | Align hiring and process with product growth |\n| Technical feasibility | CTO | Co-own the features vs. platform trade-off |\n| Launch timing | CMO | Align releases with demand gen capacity |\n| Sales-requested features | CRO | Distinguish revenue-critical from noise |\n| Data and ML product strategy | CTO + CDO | Where data is a product feature vs. infrastructure |\n| Compliance deadlines | CISO \u002F RA | Tier-0 roadmap items that are non-negotiable |\n\n## Resources\n\n| Resource | When to load |\n|----------|-------------|\n| `references\u002Fproduct_strategy.md` | Vision, JTBD, moats, positioning, BCG, board reporting |\n| `references\u002Fproduct_org_design.md` | Team topologies, PM ratios, hiring, product trio, remote |\n| `references\u002Fpmf_playbook.md` | Finding PMF, retention analysis, Sean Ellis, post-PMF traps |\n| `scripts\u002Fpmf_scorer.py` | Score PMF across 4 dimensions with real data |\n| `scripts\u002Fportfolio_analyzer.py` | BCG classify and score your product portfolio |\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Retention curve not flattening → PMF at risk, raise before building more\n- Feature requests piling up without prioritization framework → propose RICE\u002FICE\n- No user research in 90+ days → product team is guessing\n- NPS declining quarter over quarter → dig into detractor feedback\n- Portfolio has a \"dog\" everyone avoids discussing → force the kill\u002Finvest decision\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Do we have PMF?\" | PMF scorecard (retention, engagement, satisfaction, growth) |\n| \"Prioritize our roadmap\" | Prioritized backlog with scoring framework |\n| \"Evaluate our product portfolio\" | Portfolio map with invest\u002Fmaintain\u002Fkill recommendations |\n| \"Design our product org\" | Org proposal with team topology and PM ratios |\n| \"Prep product for the board\" | Product board section with metrics + roadmap + risks |\n\n## Reasoning Technique: First Principles\n\nDecompose to fundamental user needs. Question every assumption about what customers want. Rebuild from validated evidence, not inherited roadmaps.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n","# CPO Advisor\n\nStrategic product leadership. Vision, portfolio, PMF, org design. Not for feature-level work — for the decisions that determine what gets built, why, and by whom.\n\n## Keywords\nCPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, Jobs to be Done, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects\n\n## Quick Start\n\n### Score Your Product-Market Fit\n```bash\npython scripts\u002Fpmf_scorer.py\n```\nMulti-dimensional PMF score across retention, engagement, satisfaction, and growth.\n\n### Analyze Your Product Portfolio\n```bash\npython scripts\u002Fportfolio_analyzer.py\n```\nBCG matrix classification, investment recommendations, portfolio health score.\n\n## The CPO's Core Responsibilities\n\nThe CPO owns three things. Everything else is delegation.\n\n| Responsibility | What It Means | Reference |\n|---------------|--------------|-----------|\n| **Portfolio** | Which products exist, which get investment, which get killed | `references\u002Fproduct_strategy.md` |\n| **Vision** | Where the product is going in 3-5 years and why customers care | `references\u002Fproduct_strategy.md` |\n| **Org** | The team structure that can actually execute the vision | `references\u002Fproduct_org_design.md` |\n| **PMF** | Measuring, achieving, and not losing product-market fit | `references\u002Fpmf_playbook.md` |\n| **Metrics** | North star → leading → lagging hierarchy, board reporting | This file |\n\n## Diagnostic Questions\n\nThese questions expose whether you have a strategy or a list.\n\n**Portfolio:**\n- Which product is the dog? Are you killing it or lying to yourself?\n- If you had to cut 30% of your portfolio tomorrow, what stays?\n- What's your portfolio's combined D30 retention? Is it trending up?\n\n**PMF:**\n- What's your retention curve for your best cohort?\n- What % of users would be \"very disappointed\" if your product disappeared?\n- Is organic growth happening without you pushing it?\n\n**Org:**\n- Can every PM articulate your north star and how their work connects to it?\n- When did your last product trio do user interviews together?\n- What's blocking your slowest team — the people or the structure?\n\n**Strategy:**\n- If you could only ship one thing this quarter, what is it and why?\n- What's your moat in 12 months? In 3 years?\n- What's the riskiest assumption in your current product strategy?\n\n## Product Metrics Hierarchy\n\n```\nNorth Star Metric (1, owned by CPO)\n  ↓ explains changes in\nLeading Indicators (3-5, owned by PMs)\n  ↓ eventually become\nLagging Indicators (revenue, churn, NPS)\n```\n\n**North Star rules:** One number. Measures customer value delivered, not revenue. Every team can influence it.\n\n**Good North Stars by business model:**\n\n| Model | North Star Example |\n|-------|------------------|\n| B2B SaaS | Weekly active accounts using core feature |\n| Consumer | D30 retained users |\n| Marketplace | Successful transactions per week |\n| PLG | Accounts reaching \"aha moment\" within 14 days |\n| Data product | Queries run per active user per week |\n\n### The CPO Dashboard\n\n| Category | Metric | Frequency |\n|----------|--------|-----------|\n| Growth | North star metric | Weekly |\n| Growth | D30 \u002F D90 retention by cohort | Weekly |\n| Acquisition | New activations | Weekly |\n| Activation | Time to \"aha moment\" | Weekly |\n| Engagement | DAU\u002FMAU ratio | Weekly |\n| Satisfaction | NPS trend | Monthly |\n| Portfolio | Revenue per product | Monthly |\n| Portfolio | Engineering investment % per product | Monthly |\n| Moat | Feature adoption depth | Monthly |\n\n## Investment Postures\n\nEvery product gets one: **Invest \u002F Maintain \u002F Kill**. \"Wait and see\" is not a posture — it's a decision to lose share.\n\n| Posture | Signal | Action |\n|---------|--------|--------|\n| **Invest** | High growth, strong or growing retention | Full team. Aggressive roadmap. |\n| **Maintain** | Stable revenue, slow growth, good margins | Bug fixes only. Milk it. |\n| **Kill** | Declining, negative or flat margins, no recovery path | Set a sunset date. Write a migration plan. |\n\n## Red Flags\n\n**Portfolio:**\n- Products that have been \"question marks\" for 2+ quarters without a decision\n- Engineering capacity allocated to your highest-revenue product but your highest-growth product is understaffed\n- More than 30% of team time on products with declining revenue\n\n**PMF:**\n- You have to convince users to keep using the product\n- Support requests are mostly \"how do I do X\" rather than \"I want X to also do Y\"\n- D30 retention is below 20% (consumer) or 40% (B2B) and not improving\n\n**Org:**\n- PMs writing specs and handing to design, who hands to engineering (waterfall in agile clothing)\n- Platform team has a 6-week queue for stream-aligned team requests\n- CPO has not talked to a real customer in 30+ days\n\n**Metrics:**\n- North star going up while retention is going down (metric is wrong)\n- Teams optimizing their own metrics at the expense of company metrics\n- Roadmap built from sales requests, not user behavior data\n\n## Integration with Other C-Suite Roles\n\n| When... | CPO works with... | To... |\n|---------|-------------------|-------|\n| Setting company direction | CEO | Translate vision into product bets |\n| Roadmap funding | CFO | Justify investment allocation per product |\n| Scaling product org | COO | Align hiring and process with product growth |\n| Technical feasibility | CTO | Co-own the features vs. platform trade-off |\n| Launch timing | CMO | Align releases with demand gen capacity |\n| Sales-requested features | CRO | Distinguish revenue-critical from noise |\n| Data and ML product strategy | CTO + CDO | Where data is a product feature vs. infrastructure |\n| Compliance deadlines | CISO \u002F RA | Tier-0 roadmap items that are non-negotiable |\n\n## Resources\n\n| Resource | When to load |\n|----------|-------------|\n| `references\u002Fproduct_strategy.md` | Vision, JTBD, moats, positioning, BCG, board reporting |\n| `references\u002Fproduct_org_design.md` | Team topologies, PM ratios, hiring, product trio, remote |\n| `references\u002Fpmf_playbook.md` | Finding PMF, retention analysis, Sean Ellis, post-PMF traps |\n| `scripts\u002Fpmf_scorer.py` | Score PMF across 4 dimensions with real data |\n| `scripts\u002Fportfolio_analyzer.py` | BCG classify and score your product portfolio |\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Retention curve not flattening → PMF at risk, raise before building more\n- Feature requests piling up without prioritization framework → propose RICE\u002FICE\n- No user research in 90+ days → product team is guessing\n- NPS declining quarter over quarter → dig into detractor feedback\n- Portfolio has a \"dog\" everyone avoids discussing → force the kill\u002Finvest decision\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Do we have PMF?\" | PMF scorecard (retention, engagement, satisfaction, growth) |\n| \"Prioritize our roadmap\" | Prioritized backlog with scoring framework |\n| \"Evaluate our product portfolio\" | Portfolio map with invest\u002Fmaintain\u002Fkill recommendations |\n| \"Design our product org\" | Org proposal with team topology and PM ratios |\n| \"Prep product for the board\" | Product board section with metrics + roadmap + risks |\n\n## Reasoning Technique: First Principles\n\nDecompose to fundamental user needs. Question every assumption about what customers want. Rebuild from validated evidence, not inherited roadmaps.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n",{"name":5,"license":15,"metadata":57,"description":7},{"author":58,"domain":59,"updated":60,"version":61,"category":62,"frameworks":63,"python-tools":64},"Alireza Rezvani","cpo-leadership",1772668800000,"1.0.0","c-level","pmf-playbook, product-strategy, product-org-design","pmf_scorer.py, portfolio_analyzer.py","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill cpo-advisor",{"tool":80,"command":81},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill cpo-advisor",{"tool":83,"command":84},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill cpo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002FSKILL.md",true,[88,94,98,102,108],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fpmf_playbook.md","REFERENCE","参考文档",11877,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002Freferences\u002Fpmf_playbook.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fproduct_org_design.md",15025,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002Freferences\u002Fproduct_org_design.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fproduct_strategy.md",16866,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002Freferences\u002Fproduct_strategy.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fpmf_scorer.py","SCRIPT","脚本",23692,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002Fscripts\u002Fpmf_scorer.py",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"scripts\u002Fportfolio_analyzer.py",21214,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcpo-advisor\u002Fscripts\u002Fportfolio_analyzer.py",[113,143,166,188,208,231],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":142},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[123,124,125,126,127,128,129,130,131,132,133,134,135,136,47,137,138,139,140,141],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":142},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[149],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[123,151,152,127,153,154,155,156,136,157,47,158,137,159,160,161,162,163,164,165],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":142},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[172],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[123,174,175,127,176,156,177,47,178,158,137,179,180,181,182,183,184,185,186,187],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":195,"publishedAt":142},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[194],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[196,127,197,184,198,199,200,201,187,202,203,204,47,205,158,137,206,207,138,123],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":217,"publishedAt":142},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[214],{"categoryNo":215,"categoryName":216,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[218,219,220,221,176,222,223,224,165,185,156,225,226,177,227,204,228,229,230,47],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":254},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[237],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[239,240,241,242,243,133,244,201,245,136,246,247,47,123,248,249,250,251,252,253],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]