migrate-to-rn

Orchestrates React Native migration of Blade components through plan, execute, and verify agent phases.

649|197|Updated Jan 28, 2020
One-click install
npx skills add https://github.com/razorpay/blade --skill migrate-to-rn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-rn
Source: https://github.com/razorpay/blade/tree/main/.agents/skills/migrate-to-rn
Command: npx skills add https://github.com/razorpay/blade --skill migrate-to-rn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blade components that only have web implementations need React Native support, but migrating them involves planning, implementation, TypeScript checks, tests, and iOS simulator visual verification. This Skill automates that entire pipeline with parallel agents and human approval gates.

Core Features & Use Cases

  • Multi-Agent Pipeline: Coordinates Plan, Execute, and Verify agents in isolated git worktrees, one branch and PR per component.
  • Parallel Batch Migration: Migrates up to 5 components simultaneously with dedicated Metro ports, iOS simulators, and agent-device sessions.
  • Visual Verification: Compares web vs native rendering via simulator screenshots using agent-device and agent-browser, with self-healing patch iterations.
  • Use Case: Say "add native support to Drawer" and the Skill validates the component, plans the migration, creates .native.tsx files, verifies on an iPhone simulator, and opens a PR after your approval.

Quick Start

Ask the assistant to add native support to a Blade component, for example by saying migrate Drawer to native.

Frequently Asked Questions about migrate-to-rn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add React Native support to a Blade component?

Run the migrate-to-rn skill with the component name, such as "add native support to Drawer". It validates the component, plans the migration, creates .native.tsx files, verifies them on an iOS simulator, and opens a PR after your approval.

Can I migrate multiple Blade components to React Native at once?

Yes, batch migration supports up to 5 components in parallel. Each component gets its own git worktree, Metro port, iOS simulator device, and agent session, with remaining components queued after the first batch finishes verification.

What tools are required to run React Native migration verification?

The skill requires jq, agent-device, and agent-browser installed globally on PATH, plus a working Blade dev environment with yarn, Xcode, and pods. The gh CLI is only needed at the final gate to create pull requests.

Does the migration skill commit or push code automatically?

No, it never commits, pushes, or creates PRs without explicit human approval at the Final Gate. Verification passing is not treated as approval, and approval for one component does not cover others in a batch.

What happens if a component already has partial native support?

The skill detects genuine stubs versus real native files using throwBladeError checks with a line-count threshold. For partial migrations, the Plan phase only creates or replaces stub and missing files while skipping real implementations.