Flutter

Build performant cross-platform apps with Flutter widgets, state management, and platform integration.

Security Scan

The skill is an instruction-only Flutter guidance tool that only requires the local flutter binary and its docs align with its stated purpose.

Purpose & Capability

Name/description match the provided files and required binary. The only required binary is `flutter`, which is appropriate for a Flutter development helper.

Instruction Scope

SKILL.md and the included markdown files contain static guidance about Flutter pitfalls (state, async, navigation, performance, platform channels). They do not instruct reading unrelated files, accessing environment variables, contacting external endpoints, or performing system-wide operations.

Install Mechanism

No install spec and no code files — the skill is instruction-only so nothing will be written or downloaded by the skill itself.

Credentials

The skill declares no environment variables, credentials, or config paths. That is proportionate for documentation/guide functionality.

Persistence & Privilege

always is false and there is no request to modify other skills or agent-wide config. The skill does not request persistent presence or elevated privileges.

Assessment

This is an instruction-only Flutter best-practices guide and appears internally consistent. Before installing, ensure you trust the runtime that will execute the skill (the agent may invoke the local `flutter` binary if it runs commands). Because the skill can be invoked by the agent, consider limiting agent permissions if you do not want it to run arbitrary local binaries or modify your workspace. No credentials, downloads, or external endpoints are requested by this skill.

Quick Reference

Topic	File
setState, state loss, keys	state.md
build method, context, GlobalKey	widgets.md
FutureBuilder, dispose, mounted	async.md
Context after pop, deep linking	navigation.md
const, rebuilds, performance	performance.md
Platform channels, null safety	platform.md

Critical Rules

• setState after dispose — check mounted before calling, crashes otherwise
• Key missing on list items — reordering breaks state, always use keys
• FutureBuilder rebuilds on parent rebuild — triggers future again, cache the Future
• BuildContext after async gap — context may be invalid, check mounted first
• const constructor — prevents rebuilds, use for static widgets
• StatefulWidget recreated — key change or parent rebuild creates new state
• GlobalKey expensive — don't use just to access state, pass callbacks instead
• dispose incomplete — cancel timers, subscriptions, controllers
• Navigator.pop with result — returns Future, don't ignore errors
• ScrollController not disposed — memory leak
• Image caching — use cached_network_image, default doesn't persist
• PlatformException not caught — platform channel calls can throw