[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HF50XB7SFER0FCPVGJ2JB":3,"skill-same:01M71HF50XB7SFER0FCPVGJ2JB":110},{"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":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M71HF50XB7SFER0FCPVGJ2JB","ciso-advisor",null,"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.","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\u002Fciso-advisor\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"ciso advisor","ciso","advisor","security","defense","Budget","reporting","2026","tracker","zero-trust","leadership","architecture","soc","incident response","when","roadmap","managing incidents","iso","defense-in-depth","incident","2026-11-10 10:12:30",false,"---\nname: \"ciso-advisor\"\ndescription: \"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ciso-leadership\n  updated: 2026-03-05\n  python-tools: risk_quantifier.py, compliance_tracker.py\n  frameworks: risk-based-security, zero-trust, defense-in-depth\n---\n\n# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\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","# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\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":55,"description":7},{"author":56,"domain":57,"updated":58,"version":59,"category":60,"frameworks":61,"python-tools":62},"Alireza Rezvani","ciso-leadership",1772668800000,"1.0.0","c-level","risk-based-security, zero-trust, defense-in-depth","risk_quantifier.py, compliance_tracker.py","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-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":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill ciso-advisor",{"tool":78,"command":79},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill ciso-advisor",{"tool":81,"command":82},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill ciso-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002FSKILL.md",true,[86,92,96,100,106],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcompliance_roadmap.md","REFERENCE","参考文档",16627,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fcompliance_roadmap.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fincident_response.md",16423,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fincident_response.md",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fsecurity_strategy.md",12079,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002Freferences\u002Fsecurity_strategy.md",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fcompliance_tracker.py","SCRIPT","脚本",31058,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002Fscripts\u002Fcompliance_tracker.py",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Frisk_quantifier.py",28429,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fciso-advisor\u002Fscripts\u002Frisk_quantifier.py",[111,143,166,188,207,230],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"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",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[123,124,125,126,127,128,129,130,131,132,133,134,135,136,44,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":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[123,151,152,127,153,154,155,156,136,157,44,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":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[123,174,175,127,176,156,177,44,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":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[196,127,197,184,198,199,200,201,187,202,203,204,44,205,158,137,41,206,138,123],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","react composition",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":216,"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",[213],{"categoryNo":214,"categoryName":215,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000010","后端与接口",[217,218,219,220,176,221,222,223,165,185,156,224,225,177,226,204,227,228,229,44],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":237,"publishedAt":253},"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",[236],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[238,239,240,241,242,133,243,201,244,136,245,246,44,123,247,248,249,250,251,252],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]