Flutter

Flutter's own docs (docs.flutter.dev, every page also served as markdown at <page-url>.md) and the Flutter team's agent skills (flutter/agent-plugins) set the guidance this skill follows. Most outcomes in a Flutter app come down to a few mechanisms: widgets stay free of data logic while a repository owns each piece of data, page-backed routes are the ones that deep-link, and tests and profiling only mean something when frames are pumped and builds are measured in profile mode. Third-party material is marked where it appears: parts of VERSIONS.md (the full history matrix, deprecation table and upgrade runbook) come from the [RandalSchwartz] changelog skill; RIVERPOD.md is ApparenceKit's Riverpod practice; APP-EVENTS.md holds ApparenceKit's global service events dispatcher; TESTING-RECIPES.md is ApparenceKit's widget-test recipes; and sections tagged [ApparenceKit] or [FlutterPro] in the other files (project rules for agents, Drift, server reachability, writing and testing a plugin, Slang) are community practice. Each marks where it differs from the official sources. Screen layout, themes, typography, reusable widgets and visual animation are in flutter-ui SKILL.md. Community UX and app-polish tips with a design-review mode are flutter-ux SKILL.md; custom RenderObjects (layout, painting, hit testing, semantics) are flutter-render-objects SKILL.md. The Dart language, packages and Dart-only tests are dart SKILL.md; store submission is app-store-connect SKILL.md and google-play SKILL.md; Patrol and Maestro end-to-end tests are e2e-testing SKILL.md; in-app subscriptions are revenuecat SKILL.md; crash and error reporting is sentry SKILL.md.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]