[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VPR5FHJKTTHS2V6G2J1XB":3,"skill-same:01M77VPR5FHJKTTHS2V6G2J1XB":63},{"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},"01M77VPR5FHJKTTHS2V6G2J1XB","expo-migrate-module",null,"Migrate an existing Apple\u002FSwift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android\u002FKotlin migrations.","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.cortex\u002Fskills\u002Fexpo-migrate-module\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-migrate-module\ndescription: Migrate an existing Apple\u002FSwift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android\u002FKotlin migrations.\nlicense: MIT\n---\n\n# Migrate an Expo Module\n\nMigrate the Swift side of an existing Expo module without changing its observable JS API. Treat the current JS\u002FTypeScript surface and tests as the compatibility contract. Leave Kotlin on the 1.0 DSL unless the user explicitly expands the task.\n\n## Prerequisite\n\nUse `expo` `57.0.21` or newer. Earlier `57.x` versions can compile the macros but lack many of the 2.0 features and performance optimizations, so do not target them. Before editing, check the target's installed version (`expo` in `package.json`\u002Flockfile, or `npm ls expo`). If it is older, stop and tell the user to upgrade first.\n\nCheck the example app's own `package.json` too, not only the module root. The example app is the integration surface you build and launch in step 4, so it needs the same floor.\n\nThis is a floor, not a guarantee: the exact macro and core surface still varies within `57.x`, so step 2 must still verify the checked-out source.\n\nSDK 57 ships the macros as **experimental and undocumented**, with the official beta in SDK 58. The API can still change under you. Say this to the user before a large migration, and prefer incremental mixed mode over converting a module wholesale.\n\n## References\n\n- Read `references\u002Fmigration-map.md` before changing source. It contains the 1.0-to-2.0 mappings, semantic traps, and mixed-mode rules.\n- Read `references\u002Fexample.md` for a full before\u002Fafter walkthrough of one module through mixed mode to a complete migration. Consult it when you need to see how the per-member rules compose.\n- Read `references\u002Fcompatibility.md` when the checked-out `expo-modules-core` version or branch is not known to support every requested macro. It explains how to verify the actual compile-time and runtime surface instead of guessing from a version number, and lists what the macros plugin gained through `0.10.0`.\n\n## Workflow\n\n### 1. Establish the contract\n\nInspect repository instructions and the worktree before editing. Locate the Swift module classes, records, shared objects, native views, JS\u002FTS bindings, tests, example app, podspec, `expo-module.config.json`, and installed or checked-out `expo-modules-core`.\n\nInventory every exported item before rewriting it:\n\n- module and shared-object JS names\n- function names, arity, labels, defaults, nullability, sync\u002Fasync behavior, errors, and queue\u002Fthread semantics (note which `AsyncFunction` bodies do blocking or long-running work, and any `.runOnQueue(...)`)\n- property names, mutability, and constant caching behavior\n- event wire names and payload shapes\n- record field names, defaults, requiredness, and nullability\n- shared-object constructors and instance\u002Fstatic placement (`Function` vs `StaticFunction`\u002F`StaticAsyncFunction`)\n- lifecycle hooks and views\n\nUse the TypeScript declarations and JS call sites to resolve ambiguity. Do not silently \"improve\" requiredness, rename an event, or change sync behavior during a syntax migration.\n\n### 2. Verify the available 2.0 surface\n\nInspect the macro declarations and matching core hooks in the dependency actually used by the target. Do not assume that all items in the 2.0 design are present because one macro compiles.\n\nClassify each 1.0 item as:\n\n- **Migrate:** both its macro and required core runtime support exist.\n- **Keep in DSL:** mixed mode preserves it safely, or 2.0 lacks an equivalent.\n- **Blocked:** migration would alter the JS contract or requires unavailable runtime support.\n\nPrefer an incremental mixed-mode result over speculative generated code. Keep `definition()` for any remaining DSL elements; delete it only when it is empty and the resolved module name is preserved by `@ExpoModule`.\n\n### 3. Apply the migration\n\nMigrate one semantic group at a time: module naming, functions, properties\u002Fconstants, events, shared objects, then records. Keep the diff narrow.\n\nFollow these invariants:\n\n- Preserve every existing JS-visible name explicitly when Swift naming rules or macro defaults differ.\n- Keep original optional\u002Fdefault behavior. An optional 1.0 record field must not become required merely because 2.0 can express required fields.\n- Do not migrate same-JS-name overloads unless the checked-out macro groups and dispatches them.\n- Preserve async threading behavior. A 1.0 `AsyncFunction` body ran off the JS thread; a 2.0 `async` `@JS` member starts on it and leaves only at the first `await`. A body that never awaits therefore blocks the JS thread, with no change to the JS signature. Audit what runs before the first `await`, and never leave blocking I\u002FO on the JS actor. Fix with `@JS(.concurrent)`, or restructure onto Swift Concurrency or a continuation. Queue-pinned functions get the same treatment. See the threading section in `references\u002Fmigration-map.md`.\n- Verify core support before migrating views, unions, synchronous events, shared-object static members, or free-form `Any` arguments. The macros plugin has shipped ahead of core on every one of these, so check the checked-out core rather than a plugin version, and leave unsupported members on the 1.0 DSL. `references\u002Fcompatibility.md` has the per-capability checks.\n- Keep `expo-module.config.json` listing every module class under `apple.modules`. The entries are bare Swift class names, so renaming a class during migration detaches the module silently: it builds, then is absent at runtime. A migrated class must also stay `public` or `open`. SDK 58's auto-discovery is what retires these entries.\n- Do not change Kotlin, JS wrappers, or public `.d.ts` files unless the user requested an API change.\n- Never write macro-generated symbols into the module's source. The macro emits them; hand-writing or overriding them is not part of a migration.\n\nAfter each group, search for old DSL entries and call sites that should have moved. Avoid broad formatting or unrelated cleanup.\n\n### When a 2.0 equivalent is missing or a group fails\n\nWhen step 2 classified an item as **Blocked**, or a migrated group fails to build or breaks the contract, do not force it. Stop on that group and:\n\n1. **Ask the user how to proceed** for that item, with two options:\n   - **Co-exist:** keep the item in the 1.0 `definition()` DSL alongside the migrated `@ExpoModule` (mixed mode) and continue with the other groups.\n   - **Revert:** back out the group's edits, leaving it untouched on 1.0, and move on.\n\n   Default to co-existence when mixed mode is verified safe, since it preserves the most progress. Revert when the half-applied change left the module in a non-building state and cannot be salvaged incrementally.\n\n2. **Open a tracking issue on `expo\u002Fexpo`** noting the functionality that 2.0 does not yet cover, so the gap is recorded rather than silently worked around. Use `gh issue create --repo expo\u002Fexpo` and confirm with the user before posting (per repo conventions, do not post outward-facing comments without approval). Include:\n   - the 1.0 member and its JS contract\n   - the specific macro or core hook that is missing (cite the evidence gap from `references\u002Fcompatibility.md`)\n   - the `expo-modules-core` version\u002Fbranch checked out\n\n   Reference the issue in the handoff so the remaining DSL entry is traceable to a known limitation.\n\nKeep going with the groups that do migrate cleanly; one blocked member does not block the rest.\n\n### 4. Verify behavior\n\nRun the narrowest available checks first, then the real integration surface:\n\n1. Build or type-check the Apple module against the target `expo-modules-core`.\n2. Run native unit tests and JS\u002FTS tests.\n3. Build and launch the example app when the repository provides one.\n4. Confirm `expo-module.config.json` still names every module class under `apple.modules`, matching the Swift class names as they now stand. A stale entry builds clean and fails only at runtime, so the example app must actually resolve the module, not merely compile.\n5. Compare the final exported surface with the inventory from step 1.\n6. Search for stale `Name`, migrated `Function`\u002F`AsyncFunction`\u002F`StaticFunction`\u002F`StaticAsyncFunction`\u002F`Property`\u002F`Constant`\u002F`Events` entries, old `sendEvent` calls, `@Field`, and duplicate registrations. Search the source you wrote, not macro expansion output.\n\nExpansion tests alone are insufficient: generated macro code can look correct while failing to link or run against a mismatched core. If dependencies changed or macro plugin flags are missing, reinstall JS dependencies as appropriate, run the repository's CocoaPods installation workflow, and restart Xcode before diagnosing plugin communication failures.\n\n## Handoff\n\nNever print macro-generated or core-internal symbol names to the user. `references\u002Fcompatibility.md` cites them so you can grep for them, but they are implementation details that change between plugin revisions, and they are noise in a report. Name a capability by its macro (`@JS static`, `@Event(sync:)`) and by observable JS behavior. Say \"the installed core does not support decoding free-form dictionary arguments yet\", not the name of the missing method. The exception is a tracking issue on `expo\u002Fexpo`, where the specific missing hook is the point.\n\nReport:\n\n- which members moved to 2.0\n- which members intentionally remain in the 1.0 DSL and why\n- any compatibility-sensitive choices, especially event names, record requiredness, constants, and queues\n- the commands run and any verification not completed\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 \"expo-migrate-module\" \"\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","# Migrate an Expo Module\n\nMigrate the Swift side of an existing Expo module without changing its observable JS API. Treat the current JS\u002FTypeScript surface and tests as the compatibility contract. Leave Kotlin on the 1.0 DSL unless the user explicitly expands the task.\n\n## Prerequisite\n\nUse `expo` `57.0.21` or newer. Earlier `57.x` versions can compile the macros but lack many of the 2.0 features and performance optimizations, so do not target them. Before editing, check the target's installed version (`expo` in `package.json`\u002Flockfile, or `npm ls expo`). If it is older, stop and tell the user to upgrade first.\n\nCheck the example app's own `package.json` too, not only the module root. The example app is the integration surface you build and launch in step 4, so it needs the same floor.\n\nThis is a floor, not a guarantee: the exact macro and core surface still varies within `57.x`, so step 2 must still verify the checked-out source.\n\nSDK 57 ships the macros as **experimental and undocumented**, with the official beta in SDK 58. The API can still change under you. Say this to the user before a large migration, and prefer incremental mixed mode over converting a module wholesale.\n\n## References\n\n- Read `references\u002Fmigration-map.md` before changing source. It contains the 1.0-to-2.0 mappings, semantic traps, and mixed-mode rules.\n- Read `references\u002Fexample.md` for a full before\u002Fafter walkthrough of one module through mixed mode to a complete migration. Consult it when you need to see how the per-member rules compose.\n- Read `references\u002Fcompatibility.md` when the checked-out `expo-modules-core` version or branch is not known to support every requested macro. It explains how to verify the actual compile-time and runtime surface instead of guessing from a version number, and lists what the macros plugin gained through `0.10.0`.\n\n## Workflow\n\n### 1. Establish the contract\n\nInspect repository instructions and the worktree before editing. Locate the Swift module classes, records, shared objects, native views, JS\u002FTS bindings, tests, example app, podspec, `expo-module.config.json`, and installed or checked-out `expo-modules-core`.\n\nInventory every exported item before rewriting it:\n\n- module and shared-object JS names\n- function names, arity, labels, defaults, nullability, sync\u002Fasync behavior, errors, and queue\u002Fthread semantics (note which `AsyncFunction` bodies do blocking or long-running work, and any `.runOnQueue(...)`)\n- property names, mutability, and constant caching behavior\n- event wire names and payload shapes\n- record field names, defaults, requiredness, and nullability\n- shared-object constructors and instance\u002Fstatic placement (`Function` vs `StaticFunction`\u002F`StaticAsyncFunction`)\n- lifecycle hooks and views\n\nUse the TypeScript declarations and JS call sites to resolve ambiguity. Do not silently \"improve\" requiredness, rename an event, or change sync behavior during a syntax migration.\n\n### 2. Verify the available 2.0 surface\n\nInspect the macro declarations and matching core hooks in the dependency actually used by the target. Do not assume that all items in the 2.0 design are present because one macro compiles.\n\nClassify each 1.0 item as:\n\n- **Migrate:** both its macro and required core runtime support exist.\n- **Keep in DSL:** mixed mode preserves it safely, or 2.0 lacks an equivalent.\n- **Blocked:** migration would alter the JS contract or requires unavailable runtime support.\n\nPrefer an incremental mixed-mode result over speculative generated code. Keep `definition()` for any remaining DSL elements; delete it only when it is empty and the resolved module name is preserved by `@ExpoModule`.\n\n### 3. Apply the migration\n\nMigrate one semantic group at a time: module naming, functions, properties\u002Fconstants, events, shared objects, then records. Keep the diff narrow.\n\nFollow these invariants:\n\n- Preserve every existing JS-visible name explicitly when Swift naming rules or macro defaults differ.\n- Keep original optional\u002Fdefault behavior. An optional 1.0 record field must not become required merely because 2.0 can express required fields.\n- Do not migrate same-JS-name overloads unless the checked-out macro groups and dispatches them.\n- Preserve async threading behavior. A 1.0 `AsyncFunction` body ran off the JS thread; a 2.0 `async` `@JS` member starts on it and leaves only at the first `await`. A body that never awaits therefore blocks the JS thread, with no change to the JS signature. Audit what runs before the first `await`, and never leave blocking I\u002FO on the JS actor. Fix with `@JS(.concurrent)`, or restructure onto Swift Concurrency or a continuation. Queue-pinned functions get the same treatment. See the threading section in `references\u002Fmigration-map.md`.\n- Verify core support before migrating views, unions, synchronous events, shared-object static members, or free-form `Any` arguments. The macros plugin has shipped ahead of core on every one of these, so check the checked-out core rather than a plugin version, and leave unsupported members on the 1.0 DSL. `references\u002Fcompatibility.md` has the per-capability checks.\n- Keep `expo-module.config.json` listing every module class under `apple.modules`. The entries are bare Swift class names, so renaming a class during migration detaches the module silently: it builds, then is absent at runtime. A migrated class must also stay `public` or `open`. SDK 58's auto-discovery is what retires these entries.\n- Do not change Kotlin, JS wrappers, or public `.d.ts` files unless the user requested an API change.\n- Never write macro-generated symbols into the module's source. The macro emits them; hand-writing or overriding them is not part of a migration.\n\nAfter each group, search for old DSL entries and call sites that should have moved. Avoid broad formatting or unrelated cleanup.\n\n### When a 2.0 equivalent is missing or a group fails\n\nWhen step 2 classified an item as **Blocked**, or a migrated group fails to build or breaks the contract, do not force it. Stop on that group and:\n\n1. **Ask the user how to proceed** for that item, with two options:\n   - **Co-exist:** keep the item in the 1.0 `definition()` DSL alongside the migrated `@ExpoModule` (mixed mode) and continue with the other groups.\n   - **Revert:** back out the group's edits, leaving it untouched on 1.0, and move on.\n\n   Default to co-existence when mixed mode is verified safe, since it preserves the most progress. Revert when the half-applied change left the module in a non-building state and cannot be salvaged incrementally.\n\n2. **Open a tracking issue on `expo\u002Fexpo`** noting the functionality that 2.0 does not yet cover, so the gap is recorded rather than silently worked around. Use `gh issue create --repo expo\u002Fexpo` and confirm with the user before posting (per repo conventions, do not post outward-facing comments without approval). Include:\n   - the 1.0 member and its JS contract\n   - the specific macro or core hook that is missing (cite the evidence gap from `references\u002Fcompatibility.md`)\n   - the `expo-modules-core` version\u002Fbranch checked out\n\n   Reference the issue in the handoff so the remaining DSL entry is traceable to a known limitation.\n\nKeep going with the groups that do migrate cleanly; one blocked member does not block the rest.\n\n### 4. Verify behavior\n\nRun the narrowest available checks first, then the real integration surface:\n\n1. Build or type-check the Apple module against the target `expo-modules-core`.\n2. Run native unit tests and JS\u002FTS tests.\n3. Build and launch the example app when the repository provides one.\n4. Confirm `expo-module.config.json` still names every module class under `apple.modules`, matching the Swift class names as they now stand. A stale entry builds clean and fails only at runtime, so the example app must actually resolve the module, not merely compile.\n5. Compare the final exported surface with the inventory from step 1.\n6. Search for stale `Name`, migrated `Function`\u002F`AsyncFunction`\u002F`StaticFunction`\u002F`StaticAsyncFunction`\u002F`Property`\u002F`Constant`\u002F`Events` entries, old `sendEvent` calls, `@Field`, and duplicate registrations. Search the source you wrote, not macro expansion output.\n\nExpansion tests alone are insufficient: generated macro code can look correct while failing to link or run against a mismatched core. If dependencies changed or macro plugin flags are missing, reinstall JS dependencies as appropriate, run the repository's CocoaPods installation workflow, and restart Xcode before diagnosing plugin communication failures.\n\n## Handoff\n\nNever print macro-generated or core-internal symbol names to the user. `references\u002Fcompatibility.md` cites them so you can grep for them, but they are implementation details that change between plugin revisions, and they are noise in a report. Name a capability by its macro (`@JS static`, `@Event(sync:)`) and by observable JS behavior. Say \"the installed core does not support decoding free-form dictionary arguments yet\", not the name of the missing method. The exception is a tracking issue on `expo\u002Fexpo`, where the specific missing hook is the point.\n\nReport:\n\n- which members moved to 2.0\n- which members intentionally remain in the 1.0 DSL and why\n- any compatibility-sensitive choices, especially event names, record requiredness, constants, and queues\n- the commands run and any verification not completed\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 \"expo-migrate-module\" \"\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",".cortex\u002Fskills\u002Fexpo-migrate-module",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 expo-migrate-module",{"tool":37,"command":38},"bunx","bunx skills add tallermchector\u002F02enviosdosruedas --skill expo-migrate-module",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tallermchector\u002F02enviosdosruedas --skill expo-migrate-module","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-migrate-module\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",306,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-migrate-module\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcompatibility.md",11978,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-migrate-module\u002Freferences\u002Fcompatibility.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fexample.md",7410,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-migrate-module\u002Freferences\u002Fexample.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fmigration-map.md",20376,"https:\u002F\u002Fgithub.com\u002Ftallermchector\u002F02enviosdosruedas\u002Fblob\u002Flocalmente\u002F.cortex\u002Fskills\u002Fexpo-migrate-module\u002Freferences\u002Fmigration-map.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]