flutter-skills

Claude Code skills for Flutter development — extracted from production apps and generalised so you can drop them into your own project.

A skill is a folder with a SKILL.md that Claude loads on demand, when the task at hand matches its description. These fifteen cover the parts of a Flutter codebase where the answer is a convention rather than a fact the model can look up: which layer a file belongs in, how a Cubit should emit, where a browser-only import will blow up your test suite.

See them working: flutter-skills-example is a small, complete app built with every convention here — Melos workspace, Clean Architecture, Cubit, offline-first caching, 27 tests, green in CI. Each skill below has a file there you can open.

Using the official skills too? The Flutter and Dart teams publish their own — see Related official skills. They cover different ground and are designed to sit alongside these.

Install

Copy the skills you want into your project's .claude/skills/ (per project) or ~/.claude/skills/ (every project):

git clone https://github.com/gabuldev/flutter-skills.git
cp -r flutter-skills/skills/* your-project/.claude/skills/

Take only what fits — each skill is self-contained, and a skill for a pattern you don't use is just noise in the model's decision to load one.

Verify they registered with /skills inside Claude Code. Claude picks a skill up on its own from the description; you can also invoke one directly by name.

The skills

Code craft

Architecture & structure

State & async

UI

Build, test & platform

What these assume

The skills were written against a particular stack, and the code samples show it. The shapes transfer; the package names may not.

• State — flutter_bloc (Cubit, not Bloc) + rxdart
• DI — flutter_injections
• HTTP — dio
• Monorepo — melos, with a shared core package and a design_system package
• Models — hand-written fromJson/toEntity, no freezed/json_serializable
• Tests — mocktail, bloc_test, maestro for E2E

If you use riverpod, get_it or freezed, the architecture and testing skills still apply — edit the samples in the ones that don't.

flutter-forms is deliberately pt-BR specific in its masks and validators (CPF, CNPJ, CEP). That part is the point of it; the form/Cubit wiring around it is generic.

Related official skills

The Flutter and Dart teams publish their own skill collections, both BSD-3-Clause. Install them too — they cover different ground, and this repo defers to them where they are authoritative.

npx skills add dart-lang/skills --skill '*' --agent universal --yes

How they differ from this repo. The official skills are task recipes on the standard stack — "add a widget test", "set up go_router", "run static analysis". They assume no house style and answer the same for everyone.

These skills are the opposite: an opinionated set of house conventions for a specific stack (Cubit, flutter_injections, Dio, Melos), plus the traps that cost someone here an afternoon. They answer "how do we do it", not "how is it done".

Where they overlap, prefer the official one for mechanics and this one for the convention. flutter-dart-style names the relevant dart-* skill inline wherever the Dart team owns a topic more deeply.

Contributing

Issues and PRs welcome. A good skill here is specific — it encodes a decision that a competent Flutter dev would otherwise have to make from scratch every time, and ideally a mistake that already cost someone an afternoon. A skill that restates the Flutter docs earns nothing.

Two things to keep in mind when adding one:

• The description is the whole loading mechanism. Write it as the situations it should fire in, not as a topic label.
• No project-specific names, URLs or credentials. These run in other people's repos.

License

MIT — see LICENSE.