back
loading skill details...
Build a Flutter plugin that provides native interop for other Flutter apps to use
Scaffolds Flutter plugins with native interop, method channels, FFI integration, and federated architectures. Generates standard plugins, FFI plugins, or federated multi-package architectures based on native code requirements and team structure Configures Android v2 embedding lifecycle interfaces, platform-specific native environments (Kotlin/Java, Swift/Objective-C), and method channel registration Implements package-separated federated plugins with app-facing and platform-specific implementation packages for decoupled multi-team development Includes decision tree logic to determine plugin type: FFI-only, method channels, combined FFI+channels, or federated setup flutter-plugin-generator Goal Scaffolds and configures Flutter plugin packages, handling standard method channels, FFI integrations, and federated plugin architectures. It configures platform-specific native code environments, implements Android v2 embedding lifecycle interfaces, and establishes platform interface packages. Decision Logic Use the following decision tree to determine the plugin architecture and template: Does the plugin require C/C++ native code via dart:ffi? Yes: Use --template=plugin_ffi. Note: FFI plugins support bundling native code and method channel registration, but not method channels themselves. No: Proceed to step 2. Does the plugin require BOTH dart:ffi and Method Channels? Yes: Use --template=plugin (Non-FFI). You must configure FFI manually within the standard plugin structure. No: Proceed to step 3. Will the plugin be developed by multiple teams or require highly decoupled platform implementations? Yes: Implement a Package-Separated Federated Plugin (App-facing package, Platform Interface package, Platform Implementation packages). No: Implement a standard monolithic plugin.
don't have the plugin yet? install it then click "run inline in claude" again.