[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AE4XJFG15FP2MBGEH9Y28G":3,"skill-same:01M7AE4XJFG15FP2MBGEH9Y28G":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7AE4XJFG15FP2MBGEH9Y28G","expo-brownfield",null,"Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR\u002FXCFramework, or adding Expo to an existing Kotlin\u002FSwift project. Covers both the isolated approach and the integrated approach.","fehim-asghar\u002Fadhd","fehim-asghar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264333168?v=4","01M7AE3HCH4K8R46ZHS6BYJVXC","01M7AE3HDH5P3501GKXQ87TH0F",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-brownfield\ndescription: Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR\u002FXCFramework, or adding Expo to an existing Kotlin\u002FSwift project. Covers both the isolated approach and the integrated approach.\n---\n\n# Expo Brownfield\n\nA **brownfield** app is an existing native iOS or Android app that adopts React Native incrementally, as opposed to a **greenfield** app that is React Native from day one.\n\nExpo supports two distinct ways to add React Native to a brownfield project:\n\n| Approach       | What ships to the native app                                        | When to choose                                                                   |\n| -------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------- |\n| **Isolated**   | Prebuilt AAR \u002F XCFramework                                          | Native team doesn't need Node or RN tooling; RN code can live in a separate repo |\n| **Integrated** | React Native sources added to the existing Gradle \u002F CocoaPods build | One team owns everything; comfortable with RN tooling; wants a single build      |\n\nFor the full decision matrix, see [.\u002Freferences\u002Fcomparison.md](.\u002Freferences\u002Fcomparison.md).\n\n## Pick an approach\n\nUse these quick rules — fall through to `comparison.md` for anything ambiguous.\n\n- **Choose isolated** if the iOS\u002FAndroid team must consume RN as a regular library dependency (AAR or XCFramework), without installing Node, Yarn, or the React Native build toolchain.\n- **Choose isolated** if RN code and native code live in separate repositories or release on independent cadences.\n- **Choose integrated** if a single team owns both the native and RN code and is willing to add React Native + Expo to the native project's Gradle and CocoaPods setup.\n- **Choose integrated** if you want hot reload and JS source maps to work seamlessly inside the existing native build process.\n\n## References\n\n- .\u002Freferences\u002Fbrownfield-isolated.md -- Build RN as AAR\u002FXCFramework and consume from the native app (BrownfieldActivity, ReactNativeViewController, ReactNativeView)\n- .\u002Freferences\u002Fbrownfield-integrated.md -- Add RN and Expo directly to existing Gradle and CocoaPods builds (ReactActivity, RCTRootView, Podfile)\n- .\u002Freferences\u002Fcomparison.md -- Decision criteria, trade-offs, and scenario mapping for choosing an approach\n- .\u002Freferences\u002Ftroubleshooting.md -- Metro connection, build, signing, and module-resolution issues common to both approaches\n\nMore information available at https:\u002F\u002Fdocs.expo.dev\u002Fbrownfield\u002Foverview\u002F\n\n## Shared prerequisites\n\nBoth approaches require, in the environment that _builds_ the React Native side:\n\n- **Node.js (LTS)** — runs the Expo CLI and JavaScript code.\n- **Yarn** — manages JavaScript dependencies.\n\nThe integrated approach additionally requires **CocoaPods** on iOS (`sudo gem install cocoapods`). The isolated approach does **not** require CocoaPods or any RN tooling in the consuming native app.\n\n## Versioning note\n\n**Expo SDK 55 is the minimum supported version for brownfield integration.** Earlier SDKs lack `expo-brownfield`, the required `ExpoReactHostFactory` \u002F `ExpoReactNativeFactory` entry points, and the current autolinking surface. When creating the Expo project, always pin the SDK explicitly:\n\n```sh\nnpx create-expo-app@latest my-project --template default@sdk-55\n```\n\nPin the same Expo SDK across both the RN project and any embedded dependencies.\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 submit-expo-feedback@latest --category skills --subject \"expo-brownfield\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\n","# Expo Brownfield\n\nA **brownfield** app is an existing native iOS or Android app that adopts React Native incrementally, as opposed to a **greenfield** app that is React Native from day one.\n\nExpo supports two distinct ways to add React Native to a brownfield project:\n\n| Approach       | What ships to the native app                                        | When to choose                                                                   |\n| -------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------- |\n| **Isolated**   | Prebuilt AAR \u002F XCFramework                                          | Native team doesn't need Node or RN tooling; RN code can live in a separate repo |\n| **Integrated** | React Native sources added to the existing Gradle \u002F CocoaPods build | One team owns everything; comfortable with RN tooling; wants a single build      |\n\nFor the full decision matrix, see [.\u002Freferences\u002Fcomparison.md](.\u002Freferences\u002Fcomparison.md).\n\n## Pick an approach\n\nUse these quick rules — fall through to `comparison.md` for anything ambiguous.\n\n- **Choose isolated** if the iOS\u002FAndroid team must consume RN as a regular library dependency (AAR or XCFramework), without installing Node, Yarn, or the React Native build toolchain.\n- **Choose isolated** if RN code and native code live in separate repositories or release on independent cadences.\n- **Choose integrated** if a single team owns both the native and RN code and is willing to add React Native + Expo to the native project's Gradle and CocoaPods setup.\n- **Choose integrated** if you want hot reload and JS source maps to work seamlessly inside the existing native build process.\n\n## References\n\n- .\u002Freferences\u002Fbrownfield-isolated.md -- Build RN as AAR\u002FXCFramework and consume from the native app (BrownfieldActivity, ReactNativeViewController, ReactNativeView)\n- .\u002Freferences\u002Fbrownfield-integrated.md -- Add RN and Expo directly to existing Gradle and CocoaPods builds (ReactActivity, RCTRootView, Podfile)\n- .\u002Freferences\u002Fcomparison.md -- Decision criteria, trade-offs, and scenario mapping for choosing an approach\n- .\u002Freferences\u002Ftroubleshooting.md -- Metro connection, build, signing, and module-resolution issues common to both approaches\n\nMore information available at https:\u002F\u002Fdocs.expo.dev\u002Fbrownfield\u002Foverview\u002F\n\n## Shared prerequisites\n\nBoth approaches require, in the environment that _builds_ the React Native side:\n\n- **Node.js (LTS)** — runs the Expo CLI and JavaScript code.\n- **Yarn** — manages JavaScript dependencies.\n\nThe integrated approach additionally requires **CocoaPods** on iOS (`sudo gem install cocoapods`). The isolated approach does **not** require CocoaPods or any RN tooling in the consuming native app.\n\n## Versioning note\n\n**Expo SDK 55 is the minimum supported version for brownfield integration.** Earlier SDKs lack `expo-brownfield`, the required `ExpoReactHostFactory` \u002F `ExpoReactNativeFactory` entry points, and the current autolinking surface. When creating the Expo project, always pin the SDK explicitly:\n\n```sh\nnpx create-expo-app@latest my-project --template default@sdk-55\n```\n\nPin the same Expo SDK across both the RN project and any embedded dependencies.\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 submit-expo-feedback@latest --category skills --subject \"expo-brownfield\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\n",{"name":5,"description":7},"main","0f4b02346353a7cdc33bf2a5df07c405d2ca6c2d",".agents\u002Fskills\u002Fexpo-brownfield","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd","https:\u002F\u002Fgithub.com\u002Ffehim-asghar","we don't say goodbye , we say until we meet again , until we meet again with  victory  of blood over the sword ","2026-08-12 12:50:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add fehim-asghar\u002Fadhd --skill expo-brownfield",{"tool":36,"command":37},"bunx","bunx skills add fehim-asghar\u002Fadhd --skill expo-brownfield",{"tool":39,"command":40},"pnpm","pnpm dlx skills add fehim-asghar\u002Fadhd --skill expo-brownfield","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002FSKILL.md",true,[44,50,54,58,62],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",409,"https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fbrownfield-integrated.md",18884,"https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002Freferences\u002Fbrownfield-integrated.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fbrownfield-isolated.md",19884,"https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002Freferences\u002Fbrownfield-isolated.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fcomparison.md",6813,"https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002Freferences\u002Fcomparison.md",{"path":63,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Ftroubleshooting.md",6342,"https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-brownfield\u002Freferences\u002Ftroubleshooting.md",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AE74WWHW445Z75HTX8GN01","expo-web-to-native","Framework (OSS). 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\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-web-to-native\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AE7232HBHFSAYEYD7DNZ0C","expo-upgrade","Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-upgrade\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AE6S871A7WBTQ7CB9NC9BP","expo-ui","Framework (OSS). Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo\u002Fui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo\u002Fui\u002Fswift-ui, iOS only) and Jetpack Compose (@expo\u002Fui\u002Fjetpack-compose, Android only) trees and modifiers. Use when adding or reviewing @expo\u002Fui Host\u002FRNHostView trees, building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles, sections, menus, sheets, pickers, sliders), choosing between universal and platform-specific components, or replacing an RN community UI library with a native @expo\u002Fui equivalent. Not for custom native modules, Expo Router navigation, Reanimated, or data fetching.","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7AE6NH5YS4NYBPQKF6GEXJ3","expo-tailwind-setup","Framework (OSS). Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-tailwind-setup\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7AE6FKQ4FPF3YVT3MRGPZBJ","expo-skill-feedback","Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default \u002F opt-in). Submit feedback with: npx --yes submit-expo-feedback@latest \"ACTIONABLE_FEEDBACK\". Optionally add either or both: --category \"CATEGORY\" and --subject \"SUBJECT\". Replace the uppercase placeholders before running. Use when a skill was useful, confusing, broken, missing context, or worth improving; when Expo, Expo CLI, EAS CLI, docs, or MCP worked well or fell short; or when the user explicitly asks to enable or disable telemetry, check its status, or understand what it collects.","https:\u002F\u002Fgithub.com\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-skill-feedback\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M7AE67HJ7FRM7F5PRKY0SME5","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\u002Ffehim-asghar\u002Fadhd\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-skill-eval\u002FSKILL.md",[],[]]