Labsco
Labsco/Repos/flutter/skills
REPO PACKAGE

flutter skills

OFFICIAL
flutter · publisher2,585 repository starsBSD-3-Clause · Freegithub.com/flutter/skills
20skills
17ready to use

The ten documented skills are cookbook-style Flutter and Dart workflows: flutter-add-widget-test and flutter-add-integration-test write WidgetTester and integration_test coverage, flutter-add-widget-preview wires up the previews.dart system, flutter-fix-layout-issues and flutter-build-responsive-layout handle overflow errors and adaptive layouts with LayoutBuilder/MediaQuery, flutter-apply-architecture-best-practices sets up the recommended UI/Logic/Data layering, flutter-implement-json-serialization writes fromJson/toJson by hand, flutter-use-http-package covers REST calls with the http package, and flutter-setup-declarative-routing and flutter-setup-localization configure go_router and flutter_localizations respectively.

Three more live skills are real and readable but never named in the README's own list: code-review runs a multi-step, generic pull-request review unrelated to Flutter specifically, grill-with-docs stress-tests a plan against a project's existing CONTEXT.md and ADRs and updates them as decisions land, and natural-writing sets rules for authoring longer prose like PR descriptions and analysis documents. None of the three touch Flutter or Dart APIs.

READ THE FULL ANALYSIS

The remaining seven have no description in their own frontmatter at all, so we have nothing to say about what they do beyond their names: add-dart-lint-validation-rule, dart-skills-lint-integration, dart-skills-lint-setup, dart-skills-lint-validation, definition-of-done, NotInvalid, and valid. The last two in particular read like the fixtures a skill-linter's own test suite would use to check a valid case against an invalid one, not skills a Flutter developer would ever invoke directly.

Most run with nothing extra installed. Eighteen of the twenty carry a ready label; flutter-add-integration-test is unverified, and dart-skills-lint-integration needs an account key. Several of the documented ten (flutter-fix-layout-issues, flutter-add-integration-test) lean on Dart and Flutter MCP tools rather than working from the skill file alone, so a Flutter/Dart MCP server may be doing real work behind the scenes even where the dependency label says ready.

Who this is for: a developer already building a Flutter app who wants the ten documented conventions for testing, layout, localization, and routing. If that's what brought you here, ignore the other ten; they're either generic writing/review tooling or internal fixtures with nothing Flutter-specific to offer.

17Work with nothing else to set up.
2,585Stars on the GitHub repository, at last check.