flutter-package-development
Create, evolve, test, or prepare reusable Dart packages and Flutter plugins for distribution. Use when the package itself, its public API, platform support, federation, example app, compatibility, or publication readiness is the deliverable; route app-owned native bridges to flutter-platform-integration.
How do I install this agent skill?
npx skills add https://github.com/thienqo/flutter-skills --skill flutter-package-developmentIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides safe and structured guidance for Flutter package and plugin development, with a strong emphasis on security best practices, such as excluding credentials from packages and requiring explicit user authorization for publication.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Flutter Package Development
Treat reusable packages as versioned contracts consumed by independent projects. Preserve SDK bounds, package architecture, supported platforms, and release conventions unless migration is requested.
Preflight
Inspect pubspec.yaml, public exports, examples, tests, platform folders, CI, changelogs, and consumers.
Choose the smallest viable shape:
- Dart package for reusable Dart-only logic.
- Flutter package for reusable widgets without native code.
- Plugin or FFI package when native platform implementations are required.
- Federated plugin only when independent platform ownership or release cadence justifies multiple packages.
Do not convert app-owned bridges into packages merely because code reuse is possible.
Load references conditionally
- Read public API and package quality for exports, deprecations, semver, and consumer compatibility.
- Read plugins and federation for platform interfaces, registration, FFI, and federated architecture.
- Read publication readiness for dry-run inspection, pub.dev checklist, and release verification.
Boundaries
flutter-platform-integrationowns app-side native code and low-level channel/FFI mechanics.flutter-dependency-upgradesowns consumer-side package upgrades in an application.flutter-build-releaseowns application stores and binary builds, not pub package publication.
Verification
Format, analyze, run tests, and exercise the example fixture across all claimed platforms. When publication readiness is in scope:
- Run
dart pub publish --dry-runand inspect all output, warnings, and included files. A passing dry run proves neither compatibility nor authorization. - Never publish, tag, or create releases without explicit user authorization. A conditional go-ahead ("publish if the dry run passes") does not cover changes you made after it: show the final diff and dry-run result, then ask before publishing.
- When tool or repository access is missing, provide an executable review plan with clear pass/fail criteria covering metadata, license, changelog, and dry-run output rather than fabricating results.
Sources
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/thienqo/flutter-skills/flutter-package-development">View flutter-package-development on skillZs</a>