Skip to content
Skills Library
Programming · Tool integration

flutter-platform-integration

/flutter-platform-integration

Flutter native/platform integration guidance for FE Dev. Use when a task touches platform channels, plugins, permissions, flavors, dart-define config, deep links, push notifications, secure storage, app lifecycle, native iOS/Android files, or platform-specific behavior.

Repository
talos ↗
Licence
Apache-2.0
Last repository change
12.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Flutter native/platform integration guidance for FE Dev. Use when a task touches platform channels, plugins, permissions, flavors, dart-define config, deep links, push notifications, secure storage, app lifecycle, native iOS/Android files, or platform-specific behavior.

Original author description

Flutter native/platform integration guidance for FE Dev. Use when a task touches platform channels, plugins, permissions, flavors, dart-define config, deep links, push notifications, secure storage, app lifecycle, native iOS/Android files, or platform-specific behavior.

How it works

  1. When to use
  2. Inputs and outputs
  3. Procedure
  4. Hard rules
  5. References
Original SKILL.md headings · 64 lines, 761 words
SKILL.md preview
---
name: flutter-platform-integration
description: Flutter native/platform integration guidance for FE Dev. Use when a task touches platform channels, plugins, permissions, flavors, dart-define config, deep links, push notifications, secure storage, app lifecycle, native iOS/Android files, or platform-specific behavior.
agents: [fe-dev]
sdlc_phase: implementation
owner: Platform Eng
status: active
---

# Flutter Platform Integration

## When to use

Use this for Flutter work that crosses the Dart/native boundary: platform channels, plugins, permissions, flavors, app config, deep links, push notifications, background tasks, secure storage, lifecycle hooks, or iOS/Android-specific behavior. Load it alongside `flutter-implementation`.

## Inputs and outputs

- **Inputs:** SRS/architecture permission and platform requirements, API contracts, env configuration, existing Flutter plugin/channel setup, iOS/Android project files, current flavor/build configuration.
- **Outputs:** platform changes that are approved by architecture, configured per environment, covered by smoke/build checks, and documented in task notes or deploy reports when QA/DevOps needs them.

## Procedure

1. Classify the integration:
   - package/plugin only;
   - MethodChannel/EventChannel/FFI/custom native code;
   - flavor/build-config change;
   - permission/deep-link/push/background lifecycle change.
2. Check authorization before changing platform capabilities:
   - new plugins, permissions, background modes, associated domains, push services, and native APIs require architecture/dependency approval;
   - if the requirement is absent, halt with an OQ instead of silently adding capability.
3. Implement environment-safe config:
   - use SRS §3.4.6 keys and the existing config loader;
   - pass non-secret values through the established `--dart-define`, flavor file, or build-time config path;
   - keep dev/staging/prod endpoints out of Dart and native source literals.
4. Keep permission UX complete:
   - update iOS usage descriptions and Android permission declarations;
   - provide user-facing rationale/copy where required by the feature;
   - handle denied, restricted, unavailable, and recoverable states in UI.
5. Isolate platform differences:
   - wrap platform calls behind services/repositories;
   - keep widgets independent of channel names and native file paths;
   - use typed DTOs for channel payloads and document nullable/error cases.
6. Verify platform behavior:
   - run at least one affected platform build/check when native files, plugins, flavors, or permissions change;
   - test deep links, push/open flows, storage migration, channel error handling, or lifecycle paths on the relevant simulator/emulator/device;
   - record any platform that could not be checked.
7. **When you cannot build — operator-run build handoff.** If your sandbox has no Flutter/Android/Xcode toolchain, a build-config, plugin, SDK-level or native change is *unverified* until someone else builds it. Do not describe a static read as "compatibility confirmed". Instead:
   - **Read the failing component's own source before proposing a fix.** For a plugin build error, open the plugin's `android/build.gradle` / `ios/*.podspec` in the package cache (`~/.pub-cache/hosted/pub.dev/<pkg>-<ver>/`) or the pub.dev archive. A plugin that hard-codes `compileSdk 34` cannot be fixed from the app's Gradle files, and no amount of root-project override will make it so. Cite the file and line in the task notes.
   - **Write the build handoff into the deploy report / task notes**, so the operator's build can be checked against it — not just "run `flutter build apk`":
     - exact command, flavor and `--dart-define-from-file` used;
     - host prerequisites (`sdkmanager "platforms;android-NN"`, Xcode/CocoaPods version, FVM pin);
     - **release-signing check** — the release build type must be signed with the registered key, not the debug fallback. Name how signing engages (env vars or `android/key.properties`) and give the verification: `apksigner verify --print-certs build/app/outputs/flutter-apk/app-release.apk | grep SHA-1` must equal the SHA-1 registered for Google Sign-In / Firebase / Play. A debug-signed release builds and launches fine and then fails every Google sign-in with `ApiException: 10`;
     - the smoke the operator should run on the installed build (sign-in, the changed flow) and what "pass" looks like.
   - Propose `ready-for-deploy` with the verification explicitly marked operator-owed. A failed operator build is a reopen; the second one routes to diagnosis (`orchestrator-operating-rules.md` §9 Step 7.6), not to another speculative attempt.

   Why: a plugin that hard-codes its own `compileSdk` cannot be fixed from the app's Gradle files, and guessing from the error message costs an operator build per guess. Separately, a rebuild that silently falls back to debug signing installs and launches normally and then fails every Google sign-in — a handoff that names SDK prerequisites but not the signing check lets that ship.

## Hard rules

- Do not add platform capabilities, permissions, plugins, or native APIs without SRS/architecture coverage.
- Do not store tokens or secrets in plain local storage.
- Do not hardcode environment endpoints in Dart, Gradle, Xcode, plist, or manifest files.
- Do not mark a native/build-config change verified from a static read. If you could not build it, say so and hand off the build with the checks in Procedure step 7.
- Do not let platform-channel errors disappear into generic UI failure; map them to user-visible or logged failure states per architecture.

## References

- [`../flutter-implementation/SKILL.md`](../flutter-implementation/SKILL.md) - baseline Flutter implementation discipline.
- [`../flutter-performance/SKILL.md`](../flutter-performance/SKILL.md) - performance review for channel-heavy or platform-heavy changes.
- [`../third-party-dependency-evaluation/SKILL.md`](../third-party-dependency-evaluation/SKILL.md) - dependency approval for plugins.
- [`../local-deployment/SKILL.md`](../local-deployment/SKILL.md) - deploy/env evidence consumed by QA.
Files in this package (2)
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · evolplus/talos90Apache-2.0
thienqo/flutter-skills90BSD-3-Clause
thiennc-tesoglobal/flutter-skills90BSD-3-Clause

Database snapshot: 13.11.2026 · package version 8a69e3a49655 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90react-native-platform-integration
    React Native and Expo native/platform integration guidance for FE Dev. Use when a task touches Expo config, native iOS/Android files, permissions, deep links, push notifications, secure storage, app lifecycle, native modules, build settings, or platform-specific behavior.
  • 90flutter-core:flutter-platform-integration
    Comprehensive guidance on Flutter platform integration including platform channels, native code integration, plugin development, and platform views. Use when working with platform-specific features, creating plugins, or integrating native Android/iOS code with Flutter applications.
  • 100flutter-config
    Use when configuring build flavors, passing environment variables via dart-define-from-file, or setting up stage-specific credentials.
  • 90mobile-push-notifications
    Use this skill when the user says 'push notification', 'APNs', 'FCM', 'remote notification', 'push token', 'notification payload', 'notification channel'. This skill enforces platform-specific push notification patterns: permission flow, token management, payload structure,…
  • 100flutter-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…
  • 100flutter
    Flutter cross-platform development with Dart. Widgets, state management (Riverpod, BLoC), navigation, platform channels, and production patterns. USE WHEN: user mentions "Flutter", "Dart", "flutter widget", "Riverpod", "BLoC", "flutter build", "pubspec.yaml" DO NOT USE FOR:…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.