flutter-parity

Generate a Flutter-to-React parity register classifying units as COMPOSE, DONE, or PORT.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill flutter-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flutter-parity
Source: https://github.com/Scripsteam/scrips-stack/tree/main/flutter-parity
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill flutter-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produce a Flutter→React port parity register for a module — what to COMPOSE from graduated Signal DS, what's already DONE in the React target, and what's a genuine PORT gap. Use before porting a module so you build the gaps and compose the rest, instead of re-porting components that already exist. Grounded in real files only — never guess.

Core Features & Use Cases

  • Enumerate the Flutter surface units. List the real widget files in the module and classify each leaf widget vs screen.
  • For each unit, check authority: COMPOSE if graduated in Signal DS, DONE if already built in the React target, or PORT if neither.
  • Emit the parity register listing per-unit status so you can prioritize work and avoid re-porting existing components.
  • Grounded in actual files and exports; no guessing.

Quick Start

Identify the Flutter module path and run the parity workflow to generate the per-unit parity register against the React target.

Frequently Asked Questions about flutter-parity

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

FAQPage Schema
How do I track Flutter to React porting progress for a module?

To track Flutter to React porting progress, enumerate real Flutter widget files in the module and classify each leaf widget or screen to produce a grounded parity register. This identifies what needs porting and what already exists.

What is a Flutter React parity register?

A Flutter React parity register is a structured list classifying per-unit status as COMPOSE, DONE, or PORT. It accounts for every leaf widget or screen before porting to prevent re-building components that already exist in the React codebase.

How do I avoid re-porting existing React components when migrating from Flutter?

Avoid re-porting existing React components by running a parity workflow that checks authority against existing React code and design systems. It outputs a structured register with per-unit citations to verify what is already DONE.

How do I check which Flutter widgets need porting versus composing?

Check which Flutter widgets need porting by applying authority checks to each surface unit. Mark units as COMPOSE if available in the design system, DONE if built in React, or PORT if neither exists, producing a cited per-unit register.

Can I generate a porting gap analysis using only actual project files?

Yes, you can generate a porting gap analysis grounded strictly in actual project files and exports. The workflow enumerates real Flutter modules and corresponding React implementations to ensure the parity register never guesses.