[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71CSBHAEFTDFPS3G35D1T93":3,"skill-same:01M71CSBHAEFTDFPS3G35D1T93":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":14,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71CSBHAEFTDFPS3G35D1T93","coo-advisor",null,"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.","agency-black\u002FSkills","agency-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234862658?v=4","01M6HWVFPNGNR5N2CX9ECSAD57","agencia.black","01M719WF77BF3HN0N9FK1APEFY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"coo","coo advisor","advisor","frameworks","for","planning","improvement","setting","analyzing","playbook","2026","tracker","leadership","efficiency","when","design","cadence","up","scaling","process design","2026-11-10 10:12:30",false,"---\nname: \"coo-advisor\"\ndescription: \"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: coo-leadership\n  updated: 2026-03-05\n  python-tools: ops_efficiency_analyzer.py, okr_tracker.py\n  frameworks: scaling-playbook, ops-cadence, process-frameworks\n---\n\n# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\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","# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\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":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":54,"frameworks":55,"python-tools":56},"Alireza Rezvani","coo-leadership",1772668800000,"1.0.0","c-level","scaling-playbook, ops-cadence, process-frameworks","ops_efficiency_analyzer.py, okr_tracker.py","main","681496e0662f4c45c4758fae9d4510ae87311bf2","c-level-advisor\u002Fskills\u002Fcoo-advisor","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills","https:\u002F\u002Fgithub.com\u002Fagency-black","http:\u002F\u002Fwww.dogma.black","Las grandes ideas merecen una ejecución impecable. Construimos plataformas web, aplicaciones y ecosistemas digitales completos. Esta Trinidad es nuestro dogma.","2026-05-29 16:13:55",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add agency-black\u002FSkills --skill coo-advisor",{"tool":71,"command":72},"bunx","bunx skills add agency-black\u002FSkills --skill coo-advisor",{"tool":74,"command":75},"pnpm","pnpm dlx skills add agency-black\u002FSkills --skill coo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002FSKILL.md",true,[79,85,89,93,99],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fops_cadence.md","REFERENCE","参考文档",18849,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002Freferences\u002Fops_cadence.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fprocess_frameworks.md",20077,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002Freferences\u002Fprocess_frameworks.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fscaling_playbook.md",24048,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002Freferences\u002Fscaling_playbook.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fokr_tracker.py","SCRIPT","脚本",43573,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002Fscripts\u002Fokr_tracker.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fops_efficiency_analyzer.py",40590,"https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Fcoo-advisor\u002Fscripts\u002Fops_efficiency_analyzer.py",[104,130,158,188,213,237],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":44},"01M71JZVZ0TVW7Z5DQBRWSBG8A","zarr-python","Chunked N-D arrays for cloud storage (Zarr-Python 3). Compressed arrays, parallel I\u002FO, S3\u002FGCS via fsspec, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fzarr-python\u002FSKILL.md",[],[111,112,113,114,115,116,117,118,119,120,121,122,123,28,124,125,126,127,128,129],"zarr python","python","zarr","arrays","Cloud Storage","remote","workflows","scientific","read","write","edit","parallel","dask","s3fs","use","numpy","s3","scientific computing","scale",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":44},"01M71JYXC5VAEJT8KXN5GRK32S","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fxvary-stock-research\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[141,142,143,144,145,146,147,112,148,117,149,150,151,152,153,154,155,156,157,34],"xvary","stock","research","xvary stock research","sec edgar","community","equity","thesis","analysis","code","Market","compare","market data","analyze","with","codex","cursor",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":162,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":172,"publishedAt":44},"01M71JVSDPDQ5040YBN6J1ASKY","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[166,169],{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[173,174,175,28,176,177,178,179,180,181,182,155,183,184,185,186,187],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots",{"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":162,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":44},"01M71JV64CW7R6FYYK9JWWGW0X","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fweb-artifacts-builder\u002FSKILL.md",[195],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,199,184,200,201,202,28,203,204,178,205,125,206,207,208,209,210,211,212],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":44},"01M71JS4X2FRY41DE84DEP06MN","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\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-view-transitions\u002FSKILL.md",[219],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[208,221,222,223,224,225,226,227,228,202,229,230,231,232,38,207,233,234,235,236],"vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","types","states","element","implementing","api","route","create","libraries",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":44},"01M71JS1WZ1J4F9YVC2203JBJW","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\u002Fagency-black\u002FSkills\u002Fblob\u002Fmain\u002Fvercel-react-native-skills\u002FSKILL.md",[243],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[224,245,208,246,247,248,249,250,251,28,252,232,253,125,254,255,38,256,257,207],"vercel react native skills","react native","native","react native skills","modules","platform","animations","performance","triggers","react native components","apps","best practices","tasks"]