agentleFS
wrsilvawrsilva/reis-mobile/skills/mobile-flutter/SKILL.md

mobile-flutter

Skill8 starsChanged 58 days agoMITView on GitHub

Builds Flutter apps with guides for everything specific to Flutter and Dart — layouts, responsive UI, forms, animations, theming, declarative routing with go_router, widget previews and home screen widgets; HTTP, JSON serialization, local databases and caching; plugins, platform channels and native views; isolates and app size; accessibility and localization; Effective Dart, Dart 3 features and pattern matching; and macOS setup. Use when writing or changing Flutter UI, data or native integration code, or when the user asks how to do something in Flutter, even if they do not name the topic.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow the project: its state management, folder structure, lints and packages already in pubspec.yaml.

    line 28
  2. Very specific:

    Check the Flutter SDK pin (.fvmrc, toolchain config or CI) and the installed flutter --version before using newer APIs.

    line 29
  3. Distinctive:

    Prefer packages the project already depends on over adding new ones.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mobile Flutter

Guides for building Flutter apps. Cross-platform topics live in their own skills and have Flutter references there: architecture and state management in mobile-architecture, tests in mobile-test, debugging in mobile-debug, code review in mobile-code-review, security in mobile-security and Firebase in mobile-firebase.

Pick the topic

TopicRead
UI, layout and navigationreferences/ui.md
Data and networkingreferences/data.md
Native code and pluginsreferences/native.md
Performance and sizereferences/performance.md
Accessibility and internationalizationreferences/accessibility-i18n.md
Dart languagereferences/dart.md
Environmentreferences/setup.md

Each topic file lists its guides; open only the ones the task needs.

Before writing code

  • Follow the project: its state management, folder structure, lints and packages already in pubspec.yaml.
  • Check the Flutter SDK pin (.fvmrc, toolchain config or CI) and the installed flutter --version before using newer APIs; pubspec.lock records resolved packages, not the exact Flutter SDK version.
  • Prefer packages the project already depends on over adding new ones; when adding one, check that it supports every platform the app targets.

Interface design

For UI/UX reviews, wireframes, design systems and screen redesigns, use mobile-ui-ux and its reference for this stack. For Apple targets, also consult its Apple design workflow; validate platform claims against current official guidance and the installed toolkit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.