Loading…
End-to-end procedure for porting any Flutter/Dart file from the poc_vedaxl app into this React Native monorepo (models, repositories, services, state, widgets, screens, navigation, l10n). Use it whenever you start, continue or review the port of a `lib/**/*.dart` file, when you're asked "port X", "convert this Dart file", "where does <dart file> go", or when you need the Flutter→RN concept mapping (widgets, ChangeNotifier, FutureBuilder, Navigator, ThemeData, sheets, animations, CustomPainter, ARB). For a single screen use flutter-screen-to-rn; for models/repositories use dart-model-to-ts; for tests use flutter-test-to-jest.
flutter-to-rn-migration is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Flutter → React Native: porting one file The goal is **parity**: same behaviour, same API calls, same copy and error codes, same edge cases, written as idioma. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding flutter-to-rn-migration to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install Ayush101K/vidaXl-react-nativeReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Flutter → React Native: porting one file The goal is **parity**: same behaviour, same API calls, same copy and error codes, same edge cases, written as idiomatic React Native. `C