Skip to content
Skills Library
Programming · Review & audit

flutter-performance

/flutter-performance

Flutter performance guidance for FE Dev. Use for slow widgets, rebuild churn, jank, large lists, image-heavy UI, animations, startup time, memory pressure, isolates, expensive layout/paint, or performance review of Flutter code.

Repository
talos ↗
Licence
Apache-2.0
Last repository change
12.10.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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.10.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

Flutter performance guidance for FE Dev. Use for slow widgets, rebuild churn, jank, large lists, image-heavy UI, animations, startup time, memory pressure, isolates, expensive layout/paint, or performance review of Flutter code.

Original author description

Flutter performance guidance for FE Dev. Use for slow widgets, rebuild churn, jank, large lists, image-heavy UI, animations, startup time, memory pressure, isolates, expensive layout/paint, or performance review of Flutter code.

How it works

  1. When to use
  2. Inputs and outputs
  3. Procedure
  4. Hard rules
  5. References
Original SKILL.md headings · 58 lines, 434 words
SKILL.md preview
---
name: flutter-performance
description: Flutter performance guidance for FE Dev. Use for slow widgets, rebuild churn, jank, large lists, image-heavy UI, animations, startup time, memory pressure, isolates, expensive layout/paint, or performance review of Flutter code.
agents: [fe-dev]
sdlc_phase: implementation
owner: Platform Eng
status: active
---

# Flutter Performance

## When to use

Use this when a Flutter task touches performance-sensitive UI: large lists, image-heavy layouts, charts, animations, startup, memory pressure, expensive rebuilds, platform-channel traffic, or jank. Load it alongside `flutter-implementation`.

## Inputs and outputs

- **Inputs:** affected widgets/pages, existing profiling or QA evidence, device/emulator target, design manifest, data size assumptions, current state/image/list/animation libraries.
- **Outputs:** targeted performance changes with preserved behavior, measurable before/after evidence when feasible, and tests/checks that prove no manifest or accessibility regression.

## Procedure

1. Define the performance surface:
   - name the slow path, expected data volume, device class, platform, and success criterion;
   - inspect existing Flutter DevTools/profile evidence before changing code when available.
2. Control rebuilds:
   - prefer `const` constructors and immutable inputs;
   - keep state close to the widget subtree that changes;
   - use selectors/consumers/builders from the project's state library to narrow rebuild scope;
   - avoid allocating expensive derived collections in `build()`.
3. Tune lists and scrolling:
   - use `ListView.builder`, `SliverList`, grids, or project virtualized components for dynamic collections;
   - provide stable keys where item identity matters;
   - avoid `shrinkWrap` and nested scrollables on large lists unless the layout truly requires them;
   - keep empty/loading/refresh states explicit.
4. Handle image and asset cost:
   - request appropriately sized images;
   - use caching through the project image pipeline;
   - avoid decoding oversized images in hot list cells;
   - use placeholders and error widgets that match the visual spec.
5. Keep animation smooth:
   - prefer implicit animations or existing animation primitives for simple transitions;
   - keep animation controllers scoped and disposed;
   - avoid work in listeners that runs every frame unless it is trivial;
   - respect reduced-motion behavior when the project supports it.
6. Move heavy work off the UI isolate:
   - use existing repository/background mechanisms first;
   - consider isolates/`compute` for CPU-heavy transforms only when serialization cost is worth it;
   - do not parse large payloads synchronously in widget code.
7. Verify:
   - run the narrowest repeatable check: profile build smoke, DevTools frame capture, list scroll test, animation test, or memory check;
   - record unmeasured performance assumptions in task notes instead of presenting them as proof.

## Hard rules

- Do not optimize by weakening accessibility, selector stability, state coverage, or manifest completeness.
- Do not add a new image/list/state/performance library without dependency approval.
- Do not solve rebuild churn by making shared mutable global state.
- Do not tune only in debug mode when the issue is production performance.

## References

- [`../flutter-implementation/SKILL.md`](../flutter-implementation/SKILL.md) - baseline Flutter implementation discipline.
- [`../third-party-dependency-evaluation/SKILL.md`](../third-party-dependency-evaluation/SKILL.md) - dependency approval for new performance libraries.
- [`../ui-test-execution/SKILL.md`](../ui-test-execution/SKILL.md) - UI regression checks after performance changes.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · evolplus/talos100Apache-2.0
thienqo/flutter-skills100BSD-3-Clause
HoangNguyen0403/agent-skills-standard100MIT
thiennc-tesoglobal/flutter-skills100BSD-3-Clause
zakariaf/flutter-skills100MIT
Albaylar/Mobile-Development-Kit90MIT
Dee9975/cc-skills-flutter90MIT

Database snapshot: 13.11.2026 · package version 40a446b05937 (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

  • 100react-native-performance
    React Native and Expo performance guidance for FE Dev. Use for slow screens, large lists, image-heavy UI, animations, startup time, memory pressure, expensive renders, bridge/native-module overhead, or performance review of React Native code.
  • 100flutter-performance-profiling
    Use when a Flutter app janks, drops frames, is slow to start, or feels heavy — diagnose with DevTools timeline, profile mode, the raster vs UI thread split, shader jank, and startup tracing, then fix the specific cause. Goes beyond the official flutter-fix-layout-issues (which…
  • 85flutter-core:flutter-performance
    Comprehensive Flutter performance optimization covering build optimization, rendering performance, memory management, profiling tools, isolates/concurrency, and app size reduction. Use when optimizing Flutter apps for speed, implementing performance monitoring, debugging jank,…
  • 85flutter
    Flutter framework for building beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Use when building Flutter apps, working with widgets, state management, navigation, animations, or Material Design components.
  • 100flutter-concurrency
    Use when dealing with asynchrony in Flutter - async/await inside a Cubit, Streams and RxDart, Isolates for heavy work, cancelling an in-flight operation, or choosing between FutureBuilder and BlocBuilder. Triggers on UI freezes, jank, race conditions, or "setState after dispose".
  • 100flutter-expert
    Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use for Flutter architecture, UI implementation, or cross-platform features.

Feedback and reports

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