[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F94EAST6MKB4RWA49ABG12":3,"skill-same:01M7F94EAST6MKB4RWA49ABG12":74},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7F94EAST6MKB4RWA49ABG12","expo-brownfield",null,"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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: expo-brownfield\ndescription: 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.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-brownfield\nsource_repo: expo\u002Fskills\nsource_type: official\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Expo Brownfield\n## When to Use\n\nUse this skill when you need 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\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## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Expo Brownfield\n## When to Use\n\nUse this skill when you need 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\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## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-brownfield",1782864000000,"expo\u002Fskills","official","https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fexpo-brownfield",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill expo-brownfield",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill expo-brownfield",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill expo-brownfield","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"agents\u002Fopenai.yaml","REFERENCE","参考文档",409,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002Fagents\u002Fopenai.yaml",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fbrownfield-integrated.md",18888,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002Freferences\u002Fbrownfield-integrated.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fbrownfield-isolated.md",15692,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002Freferences\u002Fbrownfield-isolated.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcomparison.md",6813,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002Freferences\u002Fcomparison.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftroubleshooting.md",6342,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fexpo-brownfield\u002Freferences\u002Ftroubleshooting.md",[75,82,87,94,101,108],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":83,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]