Skip to content
Skills Library
Programming · Analysis

flutter-fix

/flutter-fix

Finds the root cause of a bug, crash, slowdown or size problem in a Flutter app and fixes it, refactors code without changing behaviour, or upgrades packages, Dart and Flutter (with FVM) one step at a time. Use when asked to debug, fix or investigate an error or crash, find why the app is slow, janky or too large, refactor existing code, or upgrade packages, Dart or Flutter versions; for new functionality use flutter-feature.

Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Finds the root cause of a bug, crash, slowdown or size problem in a Flutter app and fixes it, refactors code without changing behaviour, or upgrades packages, Dart and Flutter (with FVM) one step at a time. Use when asked to debug, fix or investigate an error or crash, find why the app is slow, janky or too large, refactor existing code, or upgrade packages, Dart or Flutter versions; for new functionality use flutter-feature.

Original author description

Finds the root cause of a bug, crash, slowdown or size problem in a Flutter app and fixes it, refactors code without changing behaviour, or upgrades packages, Dart and Flutter (with FVM) one step at a time. Use when asked to debug, fix or investigate an error or crash, find why the app is slow, janky or too large, refactor existing code, or upgrade packages, Dart or Flutter versions; for new functionality use flutter-feature.

How it works

  1. Steps
  2. Refactor rules
  3. Rules
Original SKILL.md headings · 35 lines, 653 words
SKILL.md preview
---
name: flutter-fix
description: Finds the root cause of a bug, crash, slowdown or size problem in a Flutter app and fixes it, refactors code without changing behaviour, or upgrades packages, Dart and Flutter (with FVM) one step at a time. Use when asked to debug, fix or investigate an error or crash, find why the app is slow, janky or too large, refactor existing code, or upgrade packages, Dart or Flutter versions; for new functionality use flutter-feature.
license: Apache-2.0
---

# Flutter fix

Three kinds of work that change existing code without adding a feature. Pick one, say which, and do not mix them in one change.

## Steps

1. **Load the project rules** (`AGENTS.md`, project rules folders); project rules win over this skill. If there is no profile, read the files around the problem and go on; do not run `flutter-project-profile` for a small fix.
2. **Pick the mode and open its reference:**
   - **Bug or crash:** `references/debugging-playbook.md`.
   - **Slow, janky, too much memory, or an app that is too large:** `references/performance-and-app-size.md` (measure in profile mode first, then fix; report before and after numbers).
   - **Refactor:** the rules below. No reference needed.
   - **Upgrade** (packages, Dart, Flutter, FVM pin): `references/upgrade-checklist.md` and `references/native-platform-requirements.md` (dated Gradle, AGP, Kotlin, Java, Xcode, 16 KB, target API, UIScene and SwiftPM facts).
   - Failures that appear only in a store build or in CI, or come from keys, consoles or fingerprints, start in `flutter-release` or `flutter-service-setup`.
3. **Bug: reproduce, find the cause, then fix.** Get the exact error text, the steps, the platform, the build mode and the versions; if the report is vague, ask for those (at most three questions) before searching the code. Read the whole error and stack trace, not the last line. State the cause with the evidence (file, line, log) before editing. If the app cannot be run, label the cause "found by reading, not reproduced", list the other plausible causes you could not rule out, and say what would confirm it (a log line, a debug print, DevTools); change code only if the developer agrees, since two readers of the same code can pick different causes. If you cannot find the cause, say what you ruled out and what you need (a log, a device, a build mode); do not patch around it.
4. **Make the smallest change that removes the cause.** Do not fix neighbouring things in the same change; list them instead. Never edit generated files; change the source and run code generation.
5. **Check.** Run `flutter analyze` (with `fvm` when `.fvmrc` exists). Re-run the reproduction steps if the app can be run, and say if it could not be. Tests only if the developer asks (`flutter-testing`); then a regression test for the bug is the natural one.
6. **Report:** cause (one or two lines with evidence), change (files), how it was checked and what was not, what else you noticed but left alone, and the risk to other places that use the same code.

## Refactor rules

- Behaviour stays the same. If a change would alter behaviour, stop and say so; it is a feature or a fix, not a refactor.
- Agree the scope first (which files, which pattern, what is out). Do it in small steps, and run the analyzer after each.
- Follow the project's written conventions, not new ones. Do not introduce a package, a state-management change or a folder-structure change unless that is the request.
- If there are no tests around the code, say that nothing proves the behaviour is unchanged, and offer characterization tests through `flutter-testing` before the change.
- Keep formatting-only and rename-only changes apart from logic changes so a reviewer can read them (`flutter-git` for commits).

## Rules

- Never claim a bug is fixed without saying how you checked. "Analyzer is clean" is not "bug fixed".
- Logs and crash reports can hold tokens, keys and personal data: redact them before quoting them in a report, a commit message or a file.
- Do not run destructive clean-ups (`flutter clean`, deleting `pubspec.lock`, `.dart_tool` or `Pods`) as a first guess; say what you are clearing and why.
- Do not upgrade anything during a bug fix or refactor, and do not fix bugs during an upgrade, unless the upgrade itself causes them.
- Ask before major-version upgrades, new packages, or changes to native files (`android/`, `ios/`); name what changes.
Files in this package (5)
  • SKILL.md 4 KB
  • references/debugging-playbook.md 8 KB
  • references/native-platform-requirements.md 9 KB
  • references/performance-and-app-size.md 9 KB
  • references/upgrade-checklist.md 9 KB

Versions

The database has no other skills named flutter-fix.

Database snapshot: 13.11.2026 · package version a4d082381709 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flutter-feature
    Adds or changes a feature, screen, form or list in an existing Flutter project by following the project's own conventions, then regenerates code and runs the analyzer. Use when asked to build, extend or modify app functionality; for bug fixes, refactors and upgrades use…
  • 100dart-n-flutter
    Instructions for writing Dart and Flutter code following the official recommendations. Triggers on: **/*.dart
  • 95build-agent-dart
    Dart/Flutter build agent for mobile apps, Flutter widgets, and Dart packages. Extends build-agent with Dart-specific conventions. Use when building Flutter apps, Dart packages, or mobile (iOS/Android) features.
  • 90flutter-dependency-upgrades
    Plan, execute, or review Flutter and Dart SDK upgrades, dependency resolution, lockfile changes, package breaking changes, and compatible native toolchain migrations. Use when versions or compatibility are the task; route ordinary Dart refactoring to dart-language, security…
  • 100flutter-package-development
    Create, evolve, test, or prepare reusable Dart packages and Flutter plugins for distribution. Use when the package itself, its public API, platform support, federation, example app, compatibility, or publication readiness is the deliverable; route app-owned native bridges to…
  • 100flutter-app
    Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs. Use when the user wants to start, scaffold, or set up a new Flutter app, a cross-platform mobile app, an Android or iOS app in Dart, or asks to "create…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.