flutter-post-figma

You can transform raw Figma UI output into production-ready Flutter code by post-processing it into a standardized module layout with Page/Controller/Binding structures. This skill organizes raw design code into testable features with routes and assets, ready for review and integration.

Structuring a Flutter feature after importing a design involves reorganizing raw UI code into a canonical Page/Controller/Binding architecture. This skill automates that restructuring, registering routes and updating manifests to ensure the feature is production-ready and testable.

Yes, this skill directly processes the raw Flutter UI code produced by the figma-implement-design MCP. It takes that specific output and applies an end-to-end post-processing workflow to align it with project conventions.

Updating pubspec.yaml and registering assets for a Flutter feature is handled automatically during the post-processing workflow. This skill extracts images from the MCP output, updates the pubspec file to include them, and generates the necessary manifests.

The best way to generate tests and documentation for a Flutter UI module is to run a post-processing workflow that creates spec/plans/docs for traceability. This skill produces the necessary tests and docs alongside the restructured Page/Controller/Binding feature code.