VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin

feat: add performance optimization skill

Open
#79 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature p2
Dominant language
Shell
Stars
162
Forks
23
Avg merge
2d 22h
Merged PRs (30d)
4

Description

Description

Add a skill that identifies and fixes common Flutter performance issues. The skill should guide through diagnosing performance bottlenecks using Flutter DevTools and applying targeted optimizations.

Areas to cover:

  • Widget rebuild minimizationconst constructors, splitting widgets, RepaintBoundary, selective rebuilds with ValueListenableBuilder/BlocSelector
  • List & scroll performanceListView.builder/GridView.builder for lazy loading, itemExtent for fixed-height lists, AutomaticKeepAliveClientMixin trade-offs
  • Image optimization — caching with CachedNetworkImage, proper cacheWidth/cacheHeight for decode-time savings, precaching
  • Build & render pipeline — identifying expensive layouts, avoiding Opacity widget for hiding (use Visibility), minimizing saveLayer triggers
  • Debug tooling — using Flutter DevTools (Performance overlay, Widget rebuild tracker, Timeline), debugPrintRebuildDirtyWidgets, debugProfileBuildsEnabled, profile mode vs debug mode for accurate measurements
  • Shader compilation jank — warm-up strategies with ShaderWarmUp, --cache-sksl for SkSL shaders
  • Async & isolate patterns — offloading heavy computation to isolates via Isolate.run/compute, debouncing rapid state changes
  • Common anti-patterns — building widgets inside build() methods, unnecessary setState scope, using GlobalKey excessively, deep widget trees
Requirements
  • All CI/CD checks are passing.
  • There is no drop in the test coverage percentage.
Additional Context

This skill complements the existing vgv-bloc (state management efficiency), vgv-testing (golden tests for visual regressions), and vgv-ui-package (reusable widget design) skills by focusing on runtime performance characteristics.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing vgv-bloc, vgv-testing, and vgv-ui-package skills to understand the repository's skill structure and conventions. Add a performance-focused skill covering the listed Flutter DevTools, widget, rendering, image, shader, and isolate topics; done means CI/CD passes with no drop in test coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
mobile-dev, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.