跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 react-native-brownfield-migration

React Native Brownfield Migration

使用@callstack/react-native-Brownfield 执行从原生iOS或Android到回放原生或博览会的已接受增量棕地迁移. 在选择了褐地路径后使用,在设置集成时,将 XCFramework 或 AAR 文物进行包装,或者在本土主机中添加回放原生地表面.

4156 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

使用@callstack/react-native-Brownfield 执行从原生iOS或Android到回放原生或博览会的已接受增量棕地迁移. 在选择了褐地路径后使用,在设置集成时,将 XCFramework 或 AAR 文物进行包装,或者在本土主机中添加回放原生地表面.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Migrating to React Native、Overview、Migration Strategy、Agent Guardrails (Global)、Canonical Docs、Path Selection Gate (Must Run First)。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/quick-start.md、references/expo-create-app.md、references/expo-quick-start.md、references/expo-ios-integration.md、references/expo-android-integration.md、references/bare-quick-start.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.

Migrating to React NativeOverviewMigration StrategyAgent Guardrails (Global)Canonical DocsPath Selection Gate (Must Run First)When to ApplyQuick ReferenceProblem -> Skill MappingRelated Skills

· 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
react-native-brownfield-migration
description
Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts.
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 10
  • references/quick-start.md
  • references/expo-create-app.md
  • references/expo-quick-start.md
  • references/expo-ios-integration.md
  • references/expo-android-integration.md
  • references/bare-quick-start.md
  • references/bare-ios-xcframework-generation.md
  • references/bare-android-aar-generation.md
  • references/bare-ios-native-integration.md
  • references/bare-android-native-integration.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「react-native-brownfield-migration」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-944516f1a7d606d1-%E5%8F%8D%E5%BA%94%E5%9C%9F%E8%91%97%E5%B8%83%E6%9C%97%E5%9C%B0%E8%BF%81%E7%A7%BB.html
请存为 .cursor/skills/react-native-brownfield-migration/SKILL.md 或 .claude/skills/react-native-brownfield-migration/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/callstackincubator/agent-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/callstackincubator/agent-skills' --list

npx skills add 'https://github.com/callstackincubator/agent-skills' --skill 'react-native-brownfield-migration'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: react-native-brownfield-migration description: Implements an accepted incremental brownfield migration from native iOS or Android to React Native or Expo using @callstack/react-native-brownfield. Use after the brownfield path has been selected, when setting up the integration, packaging XCFramework or AAR artifacts, or adding React Native surfaces to native hosts. license: MIT --- # Migrating to React Native Use this skill only after the decision to adopt brownfield migration has been made. When the user is still choosing between brownfield, greenfield, a checkpoint-based path, defer, or no migration, use [assess-react-native-migration](../assess-react-native-migration/SKILL.md) first. ## Overview Prescriptive workflow for incremental adoption of React Native in existing native apps using `@callstack/react-native-brownfield`, from initial setup through phased host integration. - Expo track - Bare React Native track Use one track per task unless the user explicitly asks for migration or comparison. ## Migration Strategy Use this strategy for brownfield migration planning and execution: 1. Assess app state and select Expo or bare path. 2. Perform initial setup with `@callstack/react-native-brownfield`. 3. Package RN artifacts (`XCFramework`/`AAR`) from the RN source app. 4. Integrate one RN surface into the host app and validate startup/runtime. 5. Repeat integration by feature/screen for incremental rollout. ## Agent Guardrails (Global) Apply these rules across all reference files: 1. Select one path first (Expo or bare) and do not mix steps. 2. Use placeholders from the docs (``, ``, ``) and resolve from project files. 3. Validate each packaging command before moving to host integration. 4. Prefer official docs for long platform snippets and CLI option details. 5. Keep host apps isolated from direct React Native APIs when possible (facade approach). 6. For startup/runtime verification, use `agent-device` to open the host app, navigate to the RN surface, capture snapshots/screenshots, and collect device evidence. If it is missing and verification needs it, install it through the environment's approved/trusted path or ask the user to install or enable it. ## Canonical Docs - [Quick Start](https://oss.callstack.com/react-native-brownfield/docs/getting-started/quick-start.md) - [Expo Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/expo.md) - [iOS Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/ios.md) - [Android Integration](https://oss.callstack.com/react-native-brownfield/docs/getting-started/android.md) - [Brownfield CLI](https://oss.callstack.com/react-native-brownfield/docs/cli/brownfield.md) - [Guidelines](https://oss.callstack.com/react-native-brownfield/docs/guides/guidelines.md) - [Troubleshooting](https://oss.callstack.com/react-native-brownfield/docs/guides/troubleshooting.md) ## Path Selection Gate (Must Run First) Before selecting any reference file, classify the project: 1. If no React Native app exists yet, use Expo creation path: - [expo-create-app.md][expo-create-app] -> [expo-quick-start.md][expo-quick-start] 2. If React Native app exists, inspect `package.json` and `app.json`: - Expo if `expo` is present or Expo plugin workflow is requested. - Bare RN if native folders and direct RN CLI workflow are used without Expo path requirements. 3. If still unclear, ask one disambiguation question. 4. Continue with exactly one path. ## When to Apply Reference this package when: - Implementing an accepted incremental migration from native-only apps to React Native or Expo - Creating brownfield integration flows for Expo or bare React Native projects - Performing initial setup with `@callstack/react-native-brownfield` - Generating iOS XCFramework artifacts from a React Native app - Generating and publishing Android AAR artifacts from a React Native app - Integrating generated artifacts into host iOS/Android apps ## Quick Reference | File | Description | |------|-------------| | [quick-start.md][quick-start] | Shared preflight and mandatory path-selection gate | | [expo-create-app.md][expo-create-app] | Scaffold a new Expo app before Expo brownfield setup | | [expo-quick-start.md][expo-quick-start] | Expo plugin setup and packaging readiness | | [expo-ios-integration.md][expo-ios-integration] | Expo iOS packaging and host startup integration | | [expo-android-integration.md][expo-android-integration] | Expo Android packaging, publish, and host integration | | [bare-quick-start.md][bare-quick-start] | Bare React Native baseline setup | | [bare-ios-xcframework-generation.md][bare-ios-xcframework-generation] | Bare iOS XCFramework generation | | [bare-android-aar-generation.md][bare-android-aar-generation] | Bare Android AAR generation and publish | | [bare-ios-native-integration.md][bare-ios-native-integration] | Bare iOS host integration | | [bare-android-native-integration.md][bare-android-native-integration] | Bare Android host integration | ## Problem -> Skill Mapping | Problem | Start With | |---------|------------| | Need migration path decision first | [assess-react-native-migration](../assess-react-native-migration/SKILL.md) | | Need Expo vs bare path decision | [quick-start.md][quick-start] | | Need to create a new Expo app for brownfield | [expo-create-app.md][expo-create-app] | | Need Expo brownfield setup and plugin wiring | [expo-quick-start.md][expo-quick-start] | | Need Expo iOS brownfield integration | [expo-ios-integration.md][expo-ios-integration] | | Need Expo Android brownfield integration | [expo-android-integration.md][expo-android-integration] | | Need bare RN baseline setup | [bare-quick-start.md][bare-quick-start] | | Need bare RN iOS XCFramework generation | [bare-ios-xcframework-generation.md][bare-ios-xcframework-generation] | | Need bare RN Android AAR generation/publish | [bare-android-aar-generation.md][bare-android-aar-generation] | | Need bare RN iOS host integration | [bare-ios-native-integration.md][bare-ios-native-integration] | | Need bare RN Android host integration | [bare-android-native-integration.md][bare-android-native-integration] | ## Related Skills - [Assess React Native migration](../assess-react-native-migration/SKILL.md) before selecting the migration path. [quick-start]: references/quick-start.md [expo-create-app]: references/expo-create-app.md [expo-quick-start]: references/expo-quick-start.md [expo-ios-integration]: references/expo-ios-integration.md [expo-android-integration]: references/expo-android-integration.md [bare-quick-start]: references/bare-quick-start.md [bare-ios-xcframework-generation]: references/bare-ios-xcframework-generation.md [bare-android-aar-generation]: references/bare-android-aar-generation.md [bare-ios-native-integration]: references/bare-ios-native-integration.md [bare-android-native-integration]: references/bare-android-native-integration.md

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…