[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HEGA49933PYV2ZVCS66GH":3,"skill-same:01M71HEGA49933PYV2ZVCS66GH":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M71HEGA49933PYV2ZVCS66GH","board-deck-builder",null,"Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.","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\u002Fboard-deck-builder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"board deck builder","deck builder","deck","board","builder","mistakes","framework","suite","2026","update","delivery","template","structure","perspectives","narrative","common","updates","when","investor update","reviews","2026-11-10 10:12:30",false,"---\nname: \"board-deck-builder\"\ndescription: \"Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: board-governance\n  updated: 2026-03-05\n  frameworks: deck-frameworks, board-deck-template\n---\n\n# Board Deck Builder\n\nBuild board decks that tell a story — not just show data. Every section has an owner, a narrative, and a \"so what.\"\n\n## Keywords\nboard deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review\n\n## Quick Start\n\n```\n\u002Fboard-deck [quarterly|monthly|fundraising] [stage: seed|seriesA|seriesB]\n```\n\nProvide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.\n\n## Deck Structure (Standard Order)\n\nEvery section follows: **Headline → Data → Narrative → Ask\u002FNext**\n\n### 1. Executive Summary (CEO)\n**3 sentences. No more.**\n- Sentence 1: State of the business (where we are)\n- Sentence 2: Biggest thing that happened this period\n- Sentence 3: Where we're going next quarter\n\n*Bad:* \"We had a good quarter with lots of progress across all areas.\"\n*Good:* \"We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR.\"\n\n### 2. Key Metrics Dashboard (COO)\n**6-8 metrics max. Use a table.**\n\n| Metric | This Period | Last Period | Target | Status |\n|--------|-------------|-------------|--------|--------|\n| ARR | $2.4M | $1.97M | $2.3M | ✅ |\n| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |\n| Burn multiple | 1.8x | 2.1x | \u003C2x | ✅ |\n| NRR | 112% | 108% | >110% | ✅ |\n| CAC payback | 11 months | 14 months | \u003C12 months | ✅ |\n| Headcount | 24 | 21 | 25 | 🟡 |\n\nPick metrics the board actually tracks. Swap out anything they've said they don't care about.\n\n### 3. Financial Update (CFO)\n- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn\n- Cash position and runway (months)\n- Burn multiple trend (3-quarter view)\n- Variance to plan (what was different and why)\n- Forecast update for next quarter\n\n**One sentence on each variance.** Boards hate \"revenue was below target\" with no explanation. Say why.\n\n### 4. Revenue & Pipeline (CRO)\n- ARR waterfall: starting → new → expansion → churn → ending\n- NRR and logo churn rates\n- Pipeline by stage (in $, not just count)\n- Forecast: next quarter with confidence level\n- Top 3 deals: name\u002Famount\u002Fclose date\u002Frisk\n\n**The forecast must have a confidence level.** \"We expect $2.8M\" is weak. \"High confidence $2.6M, upside to $2.9M if two late-stage deals close\" is useful.\n\n### 5. Product Update (CPO)\n- Shipped this quarter: 3-5 bullets, user impact for each\n- Shipping next quarter: 3-5 bullets with target dates\n- PMF signal: NPS trend, DAU\u002FMAU ratio, feature adoption\n- One key learning from customer research\n\n**No feature lists.** Only features with evidence of user impact.\n\n### 6. Growth & Marketing (CMO)\n- CAC by channel (table)\n- Pipeline contribution by channel ($)\n- Brand\u002Fawareness metrics relevant to stage (traffic, share of voice)\n- What's working, what's being cut, what's being tested\n\n### 7. Engineering & Technical (CTO)\n- Delivery velocity trend (last 4 quarters)\n- Tech debt ratio and plan\n- Infrastructure: uptime, incidents, cost trend\n- Security posture (one line, flag anything pending)\n\n**Keep this short unless there's a material issue.** Boards don't need sprint details.\n\n### 8. Team & People (CHRO)\n- Headcount: actual vs plan\n- Hiring: offers out, pipeline, time-to-fill trend\n- Attrition: regrettable vs non-regrettable\n- Engagement: last survey score, trend\n- Key hires this quarter, key open roles\n\n### 9. Risk & Security (CISO)\n- Security posture: status of critical controls\n- Compliance: certifications in progress, deadlines\n- Incidents this quarter (if any): impact, resolution, prevention\n- Top 3 risks and mitigation status\n\n### 10. Strategic Outlook (CEO)\n- Next quarter priorities: 3-5 items, ranked\n- Key decisions needed from the board\n- Asks: budget, introductions, advice, votes\n\n**The \"asks\" slide is the most important.** Be specific. \"We'd like 3 warm introductions to CFOs at Series B companies\" beats \"any help would be appreciated.\"\n\n### 11. Appendix\n- Detailed financial model\n- Full pipeline data\n- Cohort retention charts\n- Customer case studies\n- Detailed headcount breakdown\n\n---\n\n## Narrative Framework\n\nBoards see 10+ decks per quarter. Yours needs a through-line.\n\n**The 4-Act Structure:**\n1. **Where we said we'd be** (last quarter's targets)\n2. **Where we actually are** (honest assessment)\n3. **Why the gap exists** (one cause per variance, not excuses)\n4. **What we're doing about it** (specific, dated actions)\n\nThis works for good news AND bad news. It's credible because it acknowledges reality.\n\n**Opening frame:** Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.\n\n---\n\n## Delivering Bad News\n\nNever bury it. Boards find out eventually. Finding out late makes it worse.\n\n**Framework:**\n1. **State it plainly** — \"We missed Q3 ARR target by $300K (12% gap)\"\n2. **Own the cause** — \"Primary driver was longer-than-expected sales cycle in enterprise segment\"\n3. **Show you understand it** — \"We analyzed 8 lost\u002Fstalled deals; the pattern is X\"\n4. **Present the fix** — \"We've made 3 changes: [specific, dated changes]\"\n5. **Update the forecast** — \"Revised Q4 target is $2.6M; here's the bottom-up build\"\n\n**What NOT to do:**\n- Don't lead with good news to soften bad news — boards notice and distrust the framing\n- Don't explain without owning — \"market conditions\" is not a cause, it's a context\n- Don't present a fix without data behind it\n- Don't show a revised forecast without showing your assumptions\n\n---\n\n## Common Board Deck Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |\n| Metrics without targets | Every metric needs a target and a status |\n| No narrative | Data without story forces boards to draw their own conclusions |\n| Burying bad news | Lead with it, own it, fix it |\n| Vague asks | Specific, actionable, person-assigned asks only |\n| No variance explanation | Every gap from target needs one-sentence cause |\n| Stale appendix | Appendix is only useful if it's current |\n| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |\n\n---\n\n## Cadence Notes\n\n**Quarterly (standard):** Full deck, all sections, 20-30 slides. Sent 48 hours in advance.\n**Monthly (for early-stage):** Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.\n**Fundraising:** Opens with market\u002Fvision, closes with ask. See `references\u002Fdeck-frameworks.md` for Sequoia format.\n\n## References\n- `references\u002Fdeck-frameworks.md` — SaaS board pack format, Sequoia structure, investor tailoring\n- `templates\u002Fboard-deck-template.md` — fill-in template for complete board decks\n","# Board Deck Builder\n\nBuild board decks that tell a story — not just show data. Every section has an owner, a narrative, and a \"so what.\"\n\n## Keywords\nboard deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review\n\n## Quick Start\n\n```\n\u002Fboard-deck [quarterly|monthly|fundraising] [stage: seed|seriesA|seriesB]\n```\n\nProvide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.\n\n## Deck Structure (Standard Order)\n\nEvery section follows: **Headline → Data → Narrative → Ask\u002FNext**\n\n### 1. Executive Summary (CEO)\n**3 sentences. No more.**\n- Sentence 1: State of the business (where we are)\n- Sentence 2: Biggest thing that happened this period\n- Sentence 3: Where we're going next quarter\n\n*Bad:* \"We had a good quarter with lots of progress across all areas.\"\n*Good:* \"We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR.\"\n\n### 2. Key Metrics Dashboard (COO)\n**6-8 metrics max. Use a table.**\n\n| Metric | This Period | Last Period | Target | Status |\n|--------|-------------|-------------|--------|--------|\n| ARR | $2.4M | $1.97M | $2.3M | ✅ |\n| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |\n| Burn multiple | 1.8x | 2.1x | \u003C2x | ✅ |\n| NRR | 112% | 108% | >110% | ✅ |\n| CAC payback | 11 months | 14 months | \u003C12 months | ✅ |\n| Headcount | 24 | 21 | 25 | 🟡 |\n\nPick metrics the board actually tracks. Swap out anything they've said they don't care about.\n\n### 3. Financial Update (CFO)\n- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn\n- Cash position and runway (months)\n- Burn multiple trend (3-quarter view)\n- Variance to plan (what was different and why)\n- Forecast update for next quarter\n\n**One sentence on each variance.** Boards hate \"revenue was below target\" with no explanation. Say why.\n\n### 4. Revenue & Pipeline (CRO)\n- ARR waterfall: starting → new → expansion → churn → ending\n- NRR and logo churn rates\n- Pipeline by stage (in $, not just count)\n- Forecast: next quarter with confidence level\n- Top 3 deals: name\u002Famount\u002Fclose date\u002Frisk\n\n**The forecast must have a confidence level.** \"We expect $2.8M\" is weak. \"High confidence $2.6M, upside to $2.9M if two late-stage deals close\" is useful.\n\n### 5. Product Update (CPO)\n- Shipped this quarter: 3-5 bullets, user impact for each\n- Shipping next quarter: 3-5 bullets with target dates\n- PMF signal: NPS trend, DAU\u002FMAU ratio, feature adoption\n- One key learning from customer research\n\n**No feature lists.** Only features with evidence of user impact.\n\n### 6. Growth & Marketing (CMO)\n- CAC by channel (table)\n- Pipeline contribution by channel ($)\n- Brand\u002Fawareness metrics relevant to stage (traffic, share of voice)\n- What's working, what's being cut, what's being tested\n\n### 7. Engineering & Technical (CTO)\n- Delivery velocity trend (last 4 quarters)\n- Tech debt ratio and plan\n- Infrastructure: uptime, incidents, cost trend\n- Security posture (one line, flag anything pending)\n\n**Keep this short unless there's a material issue.** Boards don't need sprint details.\n\n### 8. Team & People (CHRO)\n- Headcount: actual vs plan\n- Hiring: offers out, pipeline, time-to-fill trend\n- Attrition: regrettable vs non-regrettable\n- Engagement: last survey score, trend\n- Key hires this quarter, key open roles\n\n### 9. Risk & Security (CISO)\n- Security posture: status of critical controls\n- Compliance: certifications in progress, deadlines\n- Incidents this quarter (if any): impact, resolution, prevention\n- Top 3 risks and mitigation status\n\n### 10. Strategic Outlook (CEO)\n- Next quarter priorities: 3-5 items, ranked\n- Key decisions needed from the board\n- Asks: budget, introductions, advice, votes\n\n**The \"asks\" slide is the most important.** Be specific. \"We'd like 3 warm introductions to CFOs at Series B companies\" beats \"any help would be appreciated.\"\n\n### 11. Appendix\n- Detailed financial model\n- Full pipeline data\n- Cohort retention charts\n- Customer case studies\n- Detailed headcount breakdown\n\n---\n\n## Narrative Framework\n\nBoards see 10+ decks per quarter. Yours needs a through-line.\n\n**The 4-Act Structure:**\n1. **Where we said we'd be** (last quarter's targets)\n2. **Where we actually are** (honest assessment)\n3. **Why the gap exists** (one cause per variance, not excuses)\n4. **What we're doing about it** (specific, dated actions)\n\nThis works for good news AND bad news. It's credible because it acknowledges reality.\n\n**Opening frame:** Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.\n\n---\n\n## Delivering Bad News\n\nNever bury it. Boards find out eventually. Finding out late makes it worse.\n\n**Framework:**\n1. **State it plainly** — \"We missed Q3 ARR target by $300K (12% gap)\"\n2. **Own the cause** — \"Primary driver was longer-than-expected sales cycle in enterprise segment\"\n3. **Show you understand it** — \"We analyzed 8 lost\u002Fstalled deals; the pattern is X\"\n4. **Present the fix** — \"We've made 3 changes: [specific, dated changes]\"\n5. **Update the forecast** — \"Revised Q4 target is $2.6M; here's the bottom-up build\"\n\n**What NOT to do:**\n- Don't lead with good news to soften bad news — boards notice and distrust the framing\n- Don't explain without owning — \"market conditions\" is not a cause, it's a context\n- Don't present a fix without data behind it\n- Don't show a revised forecast without showing your assumptions\n\n---\n\n## Common Board Deck Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |\n| Metrics without targets | Every metric needs a target and a status |\n| No narrative | Data without story forces boards to draw their own conclusions |\n| Burying bad news | Lead with it, own it, fix it |\n| Vague asks | Specific, actionable, person-assigned asks only |\n| No variance explanation | Every gap from target needs one-sentence cause |\n| Stale appendix | Appendix is only useful if it's current |\n| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |\n\n---\n\n## Cadence Notes\n\n**Quarterly (standard):** Full deck, all sections, 20-30 slides. Sent 48 hours in advance.\n**Monthly (for early-stage):** Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.\n**Fundraising:** Opens with market\u002Fvision, closes with ask. See `references\u002Fdeck-frameworks.md` for Sequoia format.\n\n## References\n- `references\u002Fdeck-frameworks.md` — SaaS board pack format, Sequoia structure, investor tailoring\n- `templates\u002Fboard-deck-template.md` — fill-in template for complete board decks\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50},"Alireza Rezvani","board-governance",1772668800000,"1.0.0","c-level","deck-frameworks, board-deck-template","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fboard-deck-builder",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill board-deck-builder",{"tool":66,"command":67},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill board-deck-builder",{"tool":69,"command":70},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill board-deck-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fboard-deck-builder\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdeck-frameworks.md","REFERENCE","参考文档",6952,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fboard-deck-builder\u002Freferences\u002Fdeck-frameworks.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"templates\u002Fboard-deck-template.md",5885,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fboard-deck-builder\u002Ftemplates\u002Fboard-deck-template.md",[85,117,140,162,182,205],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":116},"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",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[97,98,99,100,101,102,103,104,105,106,107,108,109,110,36,111,112,113,114,115],"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":116},"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",[123],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[97,125,126,101,127,128,129,130,110,131,36,132,111,133,134,135,136,137,138,139],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":116},"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",[146],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[97,148,149,101,150,130,151,36,152,132,111,153,154,155,156,157,158,159,160,161],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":116},"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",[168],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[170,101,171,158,172,173,174,175,161,176,177,178,36,179,132,111,180,181,112,97],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":116},"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",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000010","后端与接口",[192,193,194,195,150,196,197,198,139,159,130,199,200,151,201,178,202,203,204,36],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":228},"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",[211],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[213,214,215,216,217,107,218,175,219,110,220,221,36,97,222,223,224,225,226,227],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]