[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HG8D95QMSQWSZNC7V5PQP":3,"skill-same:01M71HG8D95QMSQWSZNC7V5PQP":107},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71HG8D95QMSQWSZNC7V5PQP","executive-mentor",null,"Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.","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\u002Fexecutive-mentor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"executive mentor","mentor","tests","postmortem","for","mapper","make","stress","matrix","2026","options","leadership","you","when","stress-test","good","decision","board-prep","thinking partner","thinking","2026-11-10 10:12:30",false,"---\nname: \"executive-mentor\"\ndescription: \"Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: executive-leadership\n  updated: 2026-03-05\n  python-tools: decision_matrix_scorer.py, stakeholder_mapper.py\n  frameworks: pre-mortem, board-prep, hard-call, stress-test, postmortem\n---\n\n# Executive Mentor\n\nNot another advisor. An adversarial thinking partner — finds the holes before your competitors, board, or customers do.\n\n## The Difference\n\nOther C-suite skills give you frameworks. Executive Mentor gives you the questions you don't want to answer.\n\n- **CEO\u002FCOO\u002FCTO Advisor** → strategy, execution, tech — building the plan\n- **Executive Mentor** → \"Your plan has three fatal assumptions. Let's find them now.\"\n\n## Keywords\nexecutive mentor, pre-mortem, board prep, hard decisions, stress test, postmortem, plan challenge, devil's advocate, founder coaching, adversarial thinking, crisis, pivot, layoffs, co-founder conflict\n\n## Commands\n\n| Command | What It Does |\n|---------|-------------|\n| `\u002Fem:challenge \u003Cplan>` | Find weaknesses before they find you. Pre-mortem + severity ratings. |\n| `\u002Fem:board-prep \u003Cagenda>` | Prepare for hard questions. Build the narrative. Know your numbers cold. |\n| `\u002Fem:hard-call \u003Cdecision>` | Framework for decisions with no good options. Layoffs, pivots, firings. |\n| `\u002Fem:stress-test \u003Cassumption>` | Challenge any assumption. Revenue projections, moats, market size. |\n| `\u002Fem:postmortem \u003Cevent>` | Honest analysis. 5 Whys done properly. Who owns what change. |\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_matrix_scorer.py   # Weighted decision analysis with sensitivity\npython scripts\u002Fstakeholder_mapper.py        # Map influence vs alignment, find blockers\n```\n\n## Voice\n\nDirect. Uncomfortable when necessary. Not mean — honest.\n\nQuestions nobody wants to answer:\n- \"What happens if your biggest customer churns next month?\"\n- \"Your burn rate gives you 11 months. What's plan B?\"\n- \"You've been 'almost closing' this deal for 6 weeks. Is it real?\"\n- \"Your co-founder hasn't shipped anything meaningful in 90 days. What are you doing about it?\"\n\nThis isn't therapy. It's preparation.\n\n## When to Use This\n\n**Use when:**\n- You have a plan you're excited about (excitement = more scrutiny, not less)\n- Board meeting is coming and you can't fully defend the numbers\n- You're facing a decision you've avoided for weeks\n- Something went wrong and you're still explaining it away\n- You're about to take an irreversible action\n\n**Don't use when:**\n- You need validation for a decision already made\n- You want frameworks without hard questions\n\n## Commands in Detail\n\n### `\u002Fem:challenge \u003Cplan>`\nTakes any plan — roadmap, GTM, hiring, fundraising — and finds what breaks first. Identifies assumptions, rates confidence, maps dependencies. Output: numbered vulnerabilities with severity (Critical \u002F High \u002F Medium). See `skills\u002Fchallenge\u002FSKILL.md`\n\n### `\u002Fem:board-prep \u003Cagenda>`\n48 hours before investors. What are the 10 hardest questions? What data do you need cold? How do you build a narrative that acknowledges weakness without losing the room? Prepares you for the adversarial board, not the friendly one. See `skills\u002Fboard-prep\u002FSKILL.md`\n\n### `\u002Fem:hard-call \u003Cdecision>`\nReversibility test. 10\u002F10\u002F10 framework. Stakeholder impact mapping. Communication planning. For decisions with no good answer — only less bad ones. See `skills\u002Fhard-call\u002FSKILL.md`\n\n### `\u002Fem:stress-test \u003Cassumption>`\n\"$5B market.\" \"$2M ARR by December.\" \"3-year moat.\" Every plan is built on assumptions. Surfaces counter-evidence, models the downside, proposes the hedge. See `skills\u002Fstress-test\u002FSKILL.md`\n\n### `\u002Fem:postmortem \u003Cevent>`\nLost deal. Failed feature. Missed quarter. No blame sessions, no whitewash. 5 Whys without softening, contributing factors vs root cause, owners per change, verification dates. See `skills\u002Fpostmortem\u002FSKILL.md`\n\n## Agents & References\n\n- `agents\u002Fdevils-advocate.md` — Always finds 3 concerns, rates severity, never gives clean approval\n- `references\u002Fhard_things.md` — Firing, layoffs, pivoting, co-founder conflicts, killing products\n- `references\u002Fboard_dynamics.md` — Board types, difficult directors, when they lose confidence\n- `references\u002Fcrisis_playbook.md` — Cash crisis, key departure, PR disaster, legal threat, failed fundraise\n\n## What This Isn't\n\nExecutive Mentor won't tell you your plan is great. It won't soften bad news.\n\nWhat it will do: make sure bad news comes from you — first, with a plan — not from your board or customers.\n\nAndy Grove ran Intel through the memory chip crisis by being brutally honest. Ben Horowitz fired his best friend to save his company. The best executives see hard things coming and act first.\n\nThat's what this is for.\n\n\n## Proactive Triggers\n\nSurface these without being asked:\n- Board meeting in \u003C 2 weeks with no prep → initiate `\u002Fem:board-prep`\n- Major decision made without stress-testing → retroactively challenge it\n- Team in unanimous agreement on a big bet → that's suspicious, challenge it\n- Founder avoiding a hard conversation for 2+ weeks → surface it directly\n- Post-mortem not done after a significant failure → push for it\n\n## When the Mentor Engages Other Roles\n\n| Situation | Mentor Does | Invokes |\n|-----------|-------------|---------|\n| Revenue plan looks too optimistic | Challenges the assumptions | `[INVOKE:cfo|Model the bear case]` |\n| Hiring plan with no budget check | Questions feasibility | `[INVOKE:cfo|Can we afford this?]` |\n| Product bet without validation | Demands evidence | `[INVOKE:cpo|What's the retention data?]` |\n| Strategy shift without alignment check | Tests for cascading impact | `[INVOKE:coo|What breaks if we pivot?]` |\n| Security ignored in growth push | Raises the risk | `[INVOKE:ciso|What's the exposure?]` |\n\n## Reasoning Technique: Adversarial Reasoning\n\nAssume the plan will fail. Find the three most likely failure modes. For each, identify the earliest warning signal and the cheapest hedge. Never say 'this looks good' without finding at least one risk.\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","# Executive Mentor\n\nNot another advisor. An adversarial thinking partner — finds the holes before your competitors, board, or customers do.\n\n## The Difference\n\nOther C-suite skills give you frameworks. Executive Mentor gives you the questions you don't want to answer.\n\n- **CEO\u002FCOO\u002FCTO Advisor** → strategy, execution, tech — building the plan\n- **Executive Mentor** → \"Your plan has three fatal assumptions. Let's find them now.\"\n\n## Keywords\nexecutive mentor, pre-mortem, board prep, hard decisions, stress test, postmortem, plan challenge, devil's advocate, founder coaching, adversarial thinking, crisis, pivot, layoffs, co-founder conflict\n\n## Commands\n\n| Command | What It Does |\n|---------|-------------|\n| `\u002Fem:challenge \u003Cplan>` | Find weaknesses before they find you. Pre-mortem + severity ratings. |\n| `\u002Fem:board-prep \u003Cagenda>` | Prepare for hard questions. Build the narrative. Know your numbers cold. |\n| `\u002Fem:hard-call \u003Cdecision>` | Framework for decisions with no good options. Layoffs, pivots, firings. |\n| `\u002Fem:stress-test \u003Cassumption>` | Challenge any assumption. Revenue projections, moats, market size. |\n| `\u002Fem:postmortem \u003Cevent>` | Honest analysis. 5 Whys done properly. Who owns what change. |\n\n## Quick Start\n\n```bash\npython scripts\u002Fdecision_matrix_scorer.py   # Weighted decision analysis with sensitivity\npython scripts\u002Fstakeholder_mapper.py        # Map influence vs alignment, find blockers\n```\n\n## Voice\n\nDirect. Uncomfortable when necessary. Not mean — honest.\n\nQuestions nobody wants to answer:\n- \"What happens if your biggest customer churns next month?\"\n- \"Your burn rate gives you 11 months. What's plan B?\"\n- \"You've been 'almost closing' this deal for 6 weeks. Is it real?\"\n- \"Your co-founder hasn't shipped anything meaningful in 90 days. What are you doing about it?\"\n\nThis isn't therapy. It's preparation.\n\n## When to Use This\n\n**Use when:**\n- You have a plan you're excited about (excitement = more scrutiny, not less)\n- Board meeting is coming and you can't fully defend the numbers\n- You're facing a decision you've avoided for weeks\n- Something went wrong and you're still explaining it away\n- You're about to take an irreversible action\n\n**Don't use when:**\n- You need validation for a decision already made\n- You want frameworks without hard questions\n\n## Commands in Detail\n\n### `\u002Fem:challenge \u003Cplan>`\nTakes any plan — roadmap, GTM, hiring, fundraising — and finds what breaks first. Identifies assumptions, rates confidence, maps dependencies. Output: numbered vulnerabilities with severity (Critical \u002F High \u002F Medium). See `skills\u002Fchallenge\u002FSKILL.md`\n\n### `\u002Fem:board-prep \u003Cagenda>`\n48 hours before investors. What are the 10 hardest questions? What data do you need cold? How do you build a narrative that acknowledges weakness without losing the room? Prepares you for the adversarial board, not the friendly one. See `skills\u002Fboard-prep\u002FSKILL.md`\n\n### `\u002Fem:hard-call \u003Cdecision>`\nReversibility test. 10\u002F10\u002F10 framework. Stakeholder impact mapping. Communication planning. For decisions with no good answer — only less bad ones. See `skills\u002Fhard-call\u002FSKILL.md`\n\n### `\u002Fem:stress-test \u003Cassumption>`\n\"$5B market.\" \"$2M ARR by December.\" \"3-year moat.\" Every plan is built on assumptions. Surfaces counter-evidence, models the downside, proposes the hedge. See `skills\u002Fstress-test\u002FSKILL.md`\n\n### `\u002Fem:postmortem \u003Cevent>`\nLost deal. Failed feature. Missed quarter. No blame sessions, no whitewash. 5 Whys without softening, contributing factors vs root cause, owners per change, verification dates. See `skills\u002Fpostmortem\u002FSKILL.md`\n\n## Agents & References\n\n- `agents\u002Fdevils-advocate.md` — Always finds 3 concerns, rates severity, never gives clean approval\n- `references\u002Fhard_things.md` — Firing, layoffs, pivoting, co-founder conflicts, killing products\n- `references\u002Fboard_dynamics.md` — Board types, difficult directors, when they lose confidence\n- `references\u002Fcrisis_playbook.md` — Cash crisis, key departure, PR disaster, legal threat, failed fundraise\n\n## What This Isn't\n\nExecutive Mentor won't tell you your plan is great. It won't soften bad news.\n\nWhat it will do: make sure bad news comes from you — first, with a plan — not from your board or customers.\n\nAndy Grove ran Intel through the memory chip crisis by being brutally honest. Ben Horowitz fired his best friend to save his company. The best executives see hard things coming and act first.\n\nThat's what this is for.\n\n\n## Proactive Triggers\n\nSurface these without being asked:\n- Board meeting in \u003C 2 weeks with no prep → initiate `\u002Fem:board-prep`\n- Major decision made without stress-testing → retroactively challenge it\n- Team in unanimous agreement on a big bet → that's suspicious, challenge it\n- Founder avoiding a hard conversation for 2+ weeks → surface it directly\n- Post-mortem not done after a significant failure → push for it\n\n## When the Mentor Engages Other Roles\n\n| Situation | Mentor Does | Invokes |\n|-----------|-------------|---------|\n| Revenue plan looks too optimistic | Challenges the assumptions | `[INVOKE:cfo|Model the bear case]` |\n| Hiring plan with no budget check | Questions feasibility | `[INVOKE:cfo|Can we afford this?]` |\n| Product bet without validation | Demands evidence | `[INVOKE:cpo|What's the retention data?]` |\n| Strategy shift without alignment check | Tests for cascading impact | `[INVOKE:coo|What breaks if we pivot?]` |\n| Security ignored in growth push | Raises the risk | `[INVOKE:ciso|What's the exposure?]` |\n\n## Reasoning Technique: Adversarial Reasoning\n\nAssume the plan will fail. Find the three most likely failure modes. For each, identify the earliest warning signal and the cheapest hedge. Never say 'this looks good' without finding at least one risk.\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":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50,"python-tools":51},"Alireza Rezvani","executive-leadership",1772668800000,"1.0.0","c-level","pre-mortem, board-prep, hard-call, stress-test, postmortem","decision_matrix_scorer.py, stakeholder_mapper.py","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill executive-mentor",{"tool":67,"command":68},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill executive-mentor",{"tool":70,"command":71},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill executive-mentor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002FSKILL.md",true,[75,81,85,89,93,97,103],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",542,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002F.claude-plugin\u002Fplugin.json",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"agents\u002Fdevils-advocate.md",5602,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fagents\u002Fdevils-advocate.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fboard_dynamics.md",11521,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fboard_dynamics.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fcrisis_playbook.md",13593,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fcrisis_playbook.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fhard_things.md",12250,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Freferences\u002Fhard_things.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fdecision_matrix_scorer.py","SCRIPT","脚本",17751,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fscripts\u002Fdecision_matrix_scorer.py",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fstakeholder_mapper.py",20297,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fexecutive-mentor\u002Fscripts\u002Fstakeholder_mapper.py",[108,140,162,184,204,227],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":139},"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",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[120,121,122,123,124,125,126,127,128,129,130,131,132,133,32,134,135,136,137,138],"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":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":139},"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",[146],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},[120,148,149,124,150,151,152,153,133,154,32,155,134,156,157,158,159,160,161,23],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"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":139},"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",[168],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},[120,170,171,124,172,153,173,32,174,155,134,175,176,177,178,179,180,181,182,183],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":139},"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",[190],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},[192,124,193,180,194,195,196,197,183,198,199,200,32,201,155,134,202,203,135,120],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":213,"publishedAt":139},"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",[210],{"categoryNo":211,"categoryName":212,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000010","后端与接口",[214,215,216,217,172,218,219,220,23,181,153,221,222,173,223,200,224,225,226,32],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":234,"publishedAt":250},"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",[233],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},[235,236,237,238,239,130,240,197,241,133,242,243,32,120,244,245,246,247,248,249],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]