[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VR8BS47HBTY7S93CKF8QW":3,"skill-same:01M77VR8BS47HBTY7S93CKF8QW":75},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77VR8BS47HBTY7S93CKF8QW","eas-app-stores",null,"Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.","tallermchector\u002F02enviosdosruedas","tallermchector","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F196752173?v=4","01M77VMBE7KP4GMF5KJ15E96D5","01M77VMBEYKNBGBXVQBFB2SX4A",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eas-app-stores\ndescription: Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.\nlicense: MIT\n---\n\n# App Store Deployment\n\n> **EAS service - costs apply.** Cloud builds use EAS plan resources, and EAS services have free-tier and paid-plan limits. Apple Developer and Google Play memberships are separate. Check https:\u002F\u002Fexpo.dev\u002Fpricing for the requested service.\n\nThis skill covers building and releasing iOS and Android apps with EAS: Expo and other React Native projects, plus existing native apps. EAS is a delivery service; native apps can use it without adding Expo or React Native to their runtime. The native setup walkthrough currently covers SwiftUI\u002FUIKit on iOS.\n\n## Choose the project path\n\n- **SwiftUI\u002FUIKit app with no React Native runtime:** read [references\u002Fnative-ios.md](references\u002Fnative-ios.md) before changing its build configuration. Keep the Xcode project and Swift code as the app's source of truth. The Expo\u002FReact Native quick-start and development-client examples below do not apply to this path.\n- **Native Android app with no React Native runtime:** preserve its existing native build setup. See [references\u002Fplay-store.md](references\u002Fplay-store.md) for submission; the Swift\u002FiOS setup instructions do not apply. A dedicated native Android setup walkthrough is not yet included.\n- **Expo\u002FReact Native app:** use the quick-start below, then the relevant store reference.\n- **Adding React Native screens to an existing native app:** use `expo-brownfield` for that integration; return here for distribution.\n\nUse the archive and icon checks in [references\u002Fnative-ios.md](references\u002Fnative-ios.md) during initial native iOS setup, after changing versioning, bundle IDs, or icons, or when diagnosing a rejected upload. Routine releases follow the EAS build\u002Fsubmit flow and the processing and availability checks in [references\u002Ftestflight.md](references\u002Ftestflight.md). A successful EAS build or a queued submission does not establish Apple acceptance, tester access, or an App Store release.\n\n## References\n\nConsult these resources as needed:\n\n- .\u002Freferences\u002Fworkflows.md -- CI\u002FCD workflows for automated store releases and PR previews\n- .\u002Freferences\u002Ftestflight.md -- Submitting iOS builds to TestFlight for beta testing\n- .\u002Freferences\u002Fapp-store-metadata.md -- Managing App Store metadata and ASO optimization\n- .\u002Freferences\u002Fplay-store.md -- Submitting Android builds to Google Play Store\n- .\u002Freferences\u002Fios-app-store.md -- iOS App Store submission and review process\n- .\u002Freferences\u002Fnative-ios.md -- Native Swift\u002FSwiftUI\u002FUIKit setup, versioning, and archive verification without an Expo runtime\n\n## Expo \u002F React Native Quick Start\n\n### Install EAS CLI\n\n```bash\nnpm install -g eas-cli\neas login\n```\n\n### Initialize EAS\n\n```bash\nnpx eas-cli@latest init\n```\n\n`eas init` links or creates the EAS project. Run `eas build:configure` to create build profiles in `eas.json`; preserve existing project and store identifiers when a release setup already exists.\n\n## Build Commands\n\n### Production Builds\n\n```bash\n# iOS App Store build\nnpx eas-cli@latest build -p ios --profile production\n\n# Android Play Store build\nnpx eas-cli@latest build -p android --profile production\n\n# Both platforms\nnpx eas-cli@latest build --profile production\n```\n\n### Submit to Stores\n\n```bash\n# iOS: Build and submit to App Store Connect\nnpx eas-cli@latest build -p ios --profile production --auto-submit\n\n# Android: Build and submit to Play Store\nnpx eas-cli@latest build -p android --profile production --auto-submit\n\n# Expo \u002F React Native shortcut for iOS TestFlight\nnpx testflight\n```\n\n## Web & API Route Hosting\n\nDeploying an Expo website or Expo Router API routes to EAS Hosting (`npx expo export -p web` then `eas deploy`) is covered by the `eas-hosting` skill. This skill focuses on native app store releases.\n\n## EAS Configuration\n\nExample for an Expo \u002F React Native project (native Swift profiles are in `references\u002Fnative-ios.md`):\n\n```json\n{\n  \"cli\": {\n    \"version\": \">= 16.0.1\",\n    \"appVersionSource\": \"remote\"\n  },\n  \"build\": {\n    \"production\": {\n      \"autoIncrement\": true,\n      \"ios\": {\n        \"resourceClass\": \"m-medium\"\n      }\n    },\n    \"development\": {\n      \"developmentClient\": true,\n      \"distribution\": \"internal\"\n    }\n  },\n  \"submit\": {\n    \"production\": {\n      \"ios\": {\n        \"appleId\": \"your@email.com\",\n        \"ascAppId\": \"1234567890\"\n      },\n      \"android\": {\n        \"serviceAccountKeyPath\": \".\u002Fgoogle-service-account.json\",\n        \"track\": \"internal\"\n      }\n    }\n  }\n}\n```\n\n## Platform-Specific Guides\n\n### iOS\n\n- For native Swift apps, use the explicit build\u002Fsubmit flow in `references\u002Fnative-ios.md`\n- For Expo \u002F React Native apps, `npx testflight` provides a quick TestFlight flow\n- Configure Apple credentials via `eas credentials`\n- See .\u002Freferences\u002Ftestflight.md for credential setup\n- See .\u002Freferences\u002Fios-app-store.md for App Store submission\n\n### Android\n\n- Set up Google Play Console service account\n- Configure tracks: internal → closed → open → production\n- See .\u002Freferences\u002Fplay-store.md for detailed setup\n\n## Automated Releases\n\nEAS Workflows automate the build → submit → update pipeline for CI\u002FCD. See .\u002Freferences\u002Fworkflows.md for store-release examples. To author or validate workflow YAML, use the `eas-workflows` skill - it works from the live workflow schema.\n\n## Version Management\n\nEAS manages version numbers automatically with `appVersionSource: \"remote\"`:\n\n```bash\n# Check current versions\neas build:version:get\n\n# Manually set version\neas build:version:set -p ios\n```\n\nThe version-set command prompts for the value. When setting up or changing native iOS versioning, or diagnosing a duplicate build number, inspect the archived `CFBundleVersion`: the remote counter alone does not prove that Xcode used it.\n\n## Monitoring\n\n```bash\n# List recent builds\neas build:list\n\n# Check build status\neas build:view BUILD_ID\n\n# Inspect submissions (verified with EAS CLI 23.2.0)\neas submit:list -p ios --json\neas submit:view SUBMISSION_ID --json\n```\n\nCheck the CLI version before interpreting a missing command: these submission commands are available in 23.2.0 but not in the tested 18.6.0 installation. A pinned `npx eas-cli@23.2.0` invocation can use them without changing the global installation. See `references\u002Ftestflight.md` for live Apple status and retry guidance. Follow the returned log URLs when the JSON result omits the underlying failure. Report the exact build ID\u002Fversion and the furthest verified release state.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"eas-app-stores\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n","# App Store Deployment\n\n> **EAS service - costs apply.** Cloud builds use EAS plan resources, and EAS services have free-tier and paid-plan limits. Apple Developer and Google Play memberships are separate. Check https:\u002F\u002Fexpo.dev\u002Fpricing for the requested service.\n\nThis skill covers building and releasing iOS and Android apps with EAS: Expo and other React Native projects, plus existing native apps. EAS is a delivery service; native apps can use it without adding Expo or React Native to their runtime. The native setup walkthrough currently covers SwiftUI\u002FUIKit on iOS.\n\n## Choose the project path\n\n- **SwiftUI\u002FUIKit app with no React Native runtime:** read [references\u002Fnative-ios.md](references\u002Fnative-ios.md) before changing its build configuration. Keep the Xcode project and Swift code as the app's source of truth. The Expo\u002FReact Native quick-start and development-client examples below do not apply to this path.\n- **Native Android app with no React Native runtime:** preserve its existing native build setup. See [references\u002Fplay-store.md](references\u002Fplay-store.md) for submission; the Swift\u002FiOS setup instructions do not apply. A dedicated native Android setup walkthrough is not yet included.\n- **Expo\u002FReact Native app:** use the quick-start below, then the relevant store reference.\n- **Adding React Native screens to an existing native app:** use `expo-brownfield` for that integration; return here for distribution.\n\nUse the archive and icon checks in [references\u002Fnative-ios.md](references\u002Fnative-ios.md) during initial native iOS setup, after changing versioning, bundle IDs, or icons, or when diagnosing a rejected upload. Routine releases follow the EAS build\u002Fsubmit flow and the processing and availability checks in [references\u002Ftestflight.md](references\u002Ftestflight.md). A successful EAS build or a queued submission does not establish Apple acceptance, tester access, or an App Store release.\n\n## References\n\nConsult these resources as needed:\n\n- .\u002Freferences\u002Fworkflows.md -- CI\u002FCD workflows for automated store releases and PR previews\n- .\u002Freferences\u002Ftestflight.md -- Submitting iOS builds to TestFlight for beta testing\n- .\u002Freferences\u002Fapp-store-metadata.md -- Managing App Store metadata and ASO optimization\n- .\u002Freferences\u002Fplay-store.md -- Submitting Android builds to Google Play Store\n- .\u002Freferences\u002Fios-app-store.md -- iOS App Store submission and review process\n- .\u002Freferences\u002Fnative-ios.md -- Native Swift\u002FSwiftUI\u002FUIKit setup, versioning, and archive verification without an Expo runtime\n\n## Expo \u002F React Native Quick Start\n\n### Install EAS CLI\n\n```bash\nnpm install -g eas-cli\neas login\n```\n\n### Initialize EAS\n\n```bash\nnpx eas-cli@latest init\n```\n\n`eas init` links or creates the EAS project. Run `eas build:configure` to create build profiles in `eas.json`; preserve existing project and store identifiers when a release setup already exists.\n\n## Build Commands\n\n### Production Builds\n\n```bash\n# iOS App Store build\nnpx eas-cli@latest build -p ios --profile production\n\n# Android Play Store build\nnpx eas-cli@latest build -p android --profile production\n\n# Both platforms\nnpx eas-cli@latest build --profile production\n```\n\n### Submit to Stores\n\n```bash\n# iOS: Build and submit to App Store Connect\nnpx eas-cli@latest build -p ios --profile production --auto-submit\n\n# Android: Build and submit to Play Store\nnpx eas-cli@latest build -p android --profile production --auto-submit\n\n# Expo \u002F React Native shortcut for iOS TestFlight\nnpx testflight\n```\n\n## Web & API Route Hosting\n\nDeploying an Expo website or Expo Router API routes to EAS Hosting (`npx expo export -p web` then `eas deploy`) is covered by the `eas-hosting` skill. This skill focuses on native app store releases.\n\n## EAS Configuration\n\nExample for an Expo \u002F React Native project (native Swift profiles are in `references\u002Fnative-ios.md`):\n\n```json\n{\n  \"cli\": {\n    \"version\": \">= 16.0.1\",\n    \"appVersionSource\": \"remote\"\n  },\n  \"build\": {\n    \"production\": {\n      \"autoIncrement\": true,\n      \"ios\": {\n        \"resourceClass\": \"m-medium\"\n      }\n    },\n    \"development\": {\n      \"developmentClient\": true,\n      \"distribution\": \"internal\"\n    }\n  },\n  \"submit\": {\n    \"production\": {\n      \"ios\": {\n        \"appleId\": \"your@email.com\",\n        \"ascAppId\": \"1234567890\"\n      },\n      \"android\": {\n        \"serviceAccountKeyPath\": \".\u002Fgoogle-service-account.json\",\n        \"track\": \"internal\"\n      }\n    }\n  }\n}\n```\n\n## Platform-Specific Guides\n\n### iOS\n\n- For native Swift apps, use the explicit build\u002Fsubmit flow in `references\u002Fnative-ios.md`\n- For Expo \u002F React Native apps, `npx testflight` provides a quick TestFlight flow\n- Configure Apple credentials via `eas credentials`\n- See .\u002Freferences\u002Ftestflight.md for credential setup\n- See .\u002Freferences\u002Fios-app-store.md for App Store submission\n\n### Android\n\n- Set up Google Play Console service account\n- Configure tracks: internal → closed → open → production\n- See .\u002Freferences\u002Fplay-store.md for detailed setup\n\n## Automated Releases\n\nEAS Workflows automate the build → submit → update pipeline for CI\u002FCD. See .\u002Freferences\u002Fworkflows.md for store-release examples. To author or validate workflow YAML, use the `eas-workflows` skill - it works from the live workflow schema.\n\n## Version Management\n\nEAS manages version numbers automatically with `appVersionSource: \"remote\"`:\n\n```bash\n# Check current versions\neas build:version:get\n\n# Manually set version\neas build:version:set -p ios\n```\n\nThe version-set command prompts for the value. When setting up or changing native iOS versioning, or diagnosing a duplicate build number, inspect the archived `CFBundleVersion`: the remote counter alone does not prove that Xcode used it.\n\n## Monitoring\n\n```bash\n# List recent builds\neas build:list\n\n# Check build status\neas build:view BUILD_ID\n\n# Inspect submissions (verified with EAS CLI 23.2.0)\neas submit:list -p ios --json\neas submit:view SUBMISSION_ID --json\n```\n\nCheck the CLI version before interpreting a missing command: these submission commands are available in 23.2.0 but not in the tested 18.6.0 installation. A pinned `npx eas-cli@23.2.0` invocation can use them without changing the global installation. See `references\u002Ftestflight.md` for live Apple status and retry guidance. Follow the returned log URLs when the JSON result omits the underlying failure. Report the exact build ID\u002Fversion and the furthest verified release state.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"eas-app-stores\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n",{"name":5,"license":14,"description":7},"localmente","f3b25a2c5cd65a8d0bec3b60db7f86046dabea73",".qwen\u002Fskills\u002Feas-app-stores",2,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas","https:\u002F\u002F02enviosdosruedas.vercel.app","https:\u002F\u002Fgithub.com\u002Ftallermchector","2026-11-02 07:33:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add tallermchector\u002F02enviosdosruedas --skill eas-app-stores",{"tool":37,"command":38},"bunx","bunx skills add tallermchector\u002F02enviosdosruedas --skill eas-app-stores",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tallermchector\u002F02enviosdosruedas --skill eas-app-stores","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002FSKILL.md",true,[45,51,55,59,63,67,71],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",343,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fapp-store-metadata.md",13898,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Fapp-store-metadata.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fios-app-store.md",11545,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Fios-app-store.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fnative-ios.md",10180,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Fnative-ios.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fplay-store.md",5790,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Fplay-store.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Ftestflight.md",5973,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Ftestflight.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fworkflows.md",2175,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Feas-app-stores\u002Freferences\u002Fworkflows.md",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M77VVT9RDRSGP78TQBW156AD","expo-web-to-native","Migrate an existing web React app to a native iOS\u002FAndroid app with Expo. Use when the user wants to turn a website into a mobile app, port a Next.js\u002FVite\u002FCRA React codebase to React Native, reuse web code on native incrementally, or asks how web idioms (the DOM, CSS, React Router, localStorage, window) map to native. This is the end-to-end migration guide; use the `expo-dom` skill for the DOM-component mechanism itself.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-web-to-native\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},"01M77VVR68YB3RFKA4T4W1FSZR","expo-upgrade","Guidelines for upgrading Expo SDK versions and fixing dependency issues","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-upgrade\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M77VVH8HWSZHBQBZNZ539Y0C","expo-ui","Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-ui\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M77VVAMSVHDGRRDWEQX2Q9NR","expo-skill-eval","Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional). Use when the user wants to eval an Expo skill, test that a skill produces working code, benchmark a skill with device screenshots, or verify a skill's output renders correctly.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-skill-eval\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M77VV77S442TTSWHHFVRY9V7","expo-router","Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder organization, Link with previews and context menus, native Stack, page titles, modals and form sheets, NativeTabs, headers and toolbars, and header search bars.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-router\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M77VV428CXNCHFWVPET3TZ4T","expo-project-structure","Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.","https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.qwen\u002Fskills\u002Fexpo-project-structure\u002FSKILL.md",[],[]]