[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72AP4DBM8SYR0Q0XNDA8BPS":3,"skill-same:01M72AP4DBM8SYR0Q0XNDA8BPS":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72AP4DBM8SYR0Q0XNDA8BPS","upgrading-expo",null,"Upgrade Expo SDK versions","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fupgrading-expo\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: upgrading-expo\ndescription: \"Upgrade Expo SDK versions\"\nrisk: safe\nsource: \"https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fupgrading-expo\"\ndate_added: \"2026-02-27\"\n---\n\n# Upgrading Expo\n\n## Overview\n\nUpgrade Expo SDK versions safely, handling breaking changes, dependencies, and configuration updates.\n\n## When to Use This Skill\n\nUse this skill when you need to upgrade Expo SDK versions.\n\nUse this skill when:\n- Upgrading to a new Expo SDK version\n- Handling breaking changes between SDK versions\n- Updating dependencies for compatibility\n- Migrating deprecated APIs to new versions\n- Preparing apps for new Expo features\n\n## Instructions\n\nThis skill guides you through upgrading Expo SDK versions:\n\n1. **Pre-Upgrade Planning**: Review release notes and breaking changes\n2. **Dependency Updates**: Update packages for SDK compatibility\n3. **Configuration Migration**: Update app.json and configuration files\n4. **Code Updates**: Migrate deprecated APIs to new versions\n5. **Testing**: Verify app functionality after upgrade\n\n## Upgrade Process\n\n### 1. Pre-Upgrade Checklist\n\n- Review Expo SDK release notes\n- Identify breaking changes affecting your app\n- Check compatibility of third-party packages\n- Backup current project state\n- Create a feature branch for the upgrade\n\n### 2. Update Expo SDK\n\n```bash\n# Update Expo CLI\nnpm install -g expo-cli@latest\n\n# Upgrade Expo SDK\nnpx expo install expo@latest\n\n# Update all Expo packages\nnpx expo install --fix\n```\n\n### 3. Handle Breaking Changes\n\n- Review migration guides for breaking changes\n- Update deprecated API calls\n- Modify configuration files as needed\n- Update native dependencies if required\n- Test affected features thoroughly\n\n### 4. Update Dependencies\n\n```bash\n# Check for outdated packages\nnpx expo-doctor\n\n# Update packages to compatible versions\nnpx expo install --fix\n\n# Verify compatibility\nnpx expo-doctor\n```\n\n### 5. Testing\n\n- Test core app functionality\n- Verify native modules work correctly\n- Check for runtime errors\n- Test on both iOS and Android\n- Verify app store builds still work\n\n## Common Issues\n\n### Dependency Conflicts\n\n- Use `expo install` instead of `npm install` for Expo packages\n- Check package compatibility with new SDK version\n- Resolve peer dependency warnings\n\n### Configuration Changes\n\n- Update `app.json` for new SDK requirements\n- Migrate deprecated configuration options\n- Update native configuration files if needed\n\n### Breaking API Changes\n\n- Review API migration guides\n- Update code to use new APIs\n- Test affected features after changes\n\n## Best Practices\n\n- Always upgrade in a feature branch\n- Test thoroughly before merging\n- Review release notes carefully\n- Update dependencies incrementally\n- Keep Expo CLI updated\n- Use `expo-doctor` to verify setup\n\n## Resources\n\nFor more information, see the [source repository](https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fupgrading-expo).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Upgrading Expo\n\n## Overview\n\nUpgrade Expo SDK versions safely, handling breaking changes, dependencies, and configuration updates.\n\n## When to Use This Skill\n\nUse this skill when you need to upgrade Expo SDK versions.\n\nUse this skill when:\n- Upgrading to a new Expo SDK version\n- Handling breaking changes between SDK versions\n- Updating dependencies for compatibility\n- Migrating deprecated APIs to new versions\n- Preparing apps for new Expo features\n\n## Instructions\n\nThis skill guides you through upgrading Expo SDK versions:\n\n1. **Pre-Upgrade Planning**: Review release notes and breaking changes\n2. **Dependency Updates**: Update packages for SDK compatibility\n3. **Configuration Migration**: Update app.json and configuration files\n4. **Code Updates**: Migrate deprecated APIs to new versions\n5. **Testing**: Verify app functionality after upgrade\n\n## Upgrade Process\n\n### 1. Pre-Upgrade Checklist\n\n- Review Expo SDK release notes\n- Identify breaking changes affecting your app\n- Check compatibility of third-party packages\n- Backup current project state\n- Create a feature branch for the upgrade\n\n### 2. Update Expo SDK\n\n```bash\n# Update Expo CLI\nnpm install -g expo-cli@latest\n\n# Upgrade Expo SDK\nnpx expo install expo@latest\n\n# Update all Expo packages\nnpx expo install --fix\n```\n\n### 3. Handle Breaking Changes\n\n- Review migration guides for breaking changes\n- Update deprecated API calls\n- Modify configuration files as needed\n- Update native dependencies if required\n- Test affected features thoroughly\n\n### 4. Update Dependencies\n\n```bash\n# Check for outdated packages\nnpx expo-doctor\n\n# Update packages to compatible versions\nnpx expo install --fix\n\n# Verify compatibility\nnpx expo-doctor\n```\n\n### 5. Testing\n\n- Test core app functionality\n- Verify native modules work correctly\n- Check for runtime errors\n- Test on both iOS and Android\n- Verify app store builds still work\n\n## Common Issues\n\n### Dependency Conflicts\n\n- Use `expo install` instead of `npm install` for Expo packages\n- Check package compatibility with new SDK version\n- Resolve peer dependency warnings\n\n### Configuration Changes\n\n- Update `app.json` for new SDK requirements\n- Migrate deprecated configuration options\n- Update native configuration files if needed\n\n### Breaking API Changes\n\n- Review API migration guides\n- Update code to use new APIs\n- Test affected features after changes\n\n## Best Practices\n\n- Always upgrade in a feature branch\n- Test thoroughly before merging\n- Review release notes carefully\n- Update dependencies incrementally\n- Keep Expo CLI updated\n- Use `expo-doctor` to verify setup\n\n## Resources\n\nFor more information, see the [source repository](https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fupgrading-expo).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"source":24,"date_added":25,"description":7},"safe","https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fupgrading-expo","2026-02-27","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fupgrading-expo","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Sansar35\u002Fclaude-agent --skill upgrading-expo",{"tool":38,"command":39},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill upgrading-expo",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill upgrading-expo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fupgrading-expo\u002FSKILL.md",true,[],[47,54,61,68,75,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]