[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730Z04AX8ZJTGVXS37SABQB":3,"skill-same:01M730Z04AX8ZJTGVXS37SABQB":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M730Z04AX8ZJTGVXS37SABQB","flutter-dart-code-review",null,"Library-agnostic Flutter\u002FDart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fflutter-dart-code-review\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: flutter-dart-code-review\ndescription: Library-agnostic Flutter\u002FDart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.\norigin: ECC\n---\n\n# Flutter\u002FDart Code Review Best Practices\n\nComprehensive, library-agnostic checklist for reviewing Flutter\u002FDart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used.\n\n---\n\n## 1. General Project Health\n\n- [ ] Project follows consistent folder structure (feature-first or layer-first)\n- [ ] Proper separation of concerns: UI, business logic, data layers\n- [ ] No business logic in widgets; widgets are purely presentational\n- [ ] `pubspec.yaml` is clean — no unused dependencies, versions pinned appropriately\n- [ ] `analysis_options.yaml` includes a strict lint set with strict analyzer settings enabled\n- [ ] No `print()` statements in production code — use `dart:developer` `log()` or a logging package\n- [ ] Generated files (`.g.dart`, `.freezed.dart`, `.gr.dart`) are up-to-date or in `.gitignore`\n- [ ] Platform-specific code isolated behind abstractions\n\n---\n\n## 2. Dart Language Pitfalls\n\n- [ ] **Implicit dynamic**: Missing type annotations leading to `dynamic` — enable `strict-casts`, `strict-inference`, `strict-raw-types`\n- [ ] **Null safety misuse**: Excessive `!` (bang operator) instead of proper null checks or Dart 3 pattern matching (`if (value case var v?)`)\n- [ ] **Type promotion failures**: Using `this.field` where local variable promotion would work\n- [ ] **Catching too broadly**: `catch (e)` without `on` clause; always specify exception types\n- [ ] **Catching `Error`**: `Error` subtypes indicate bugs and should not be caught\n- [ ] **Unused `async`**: Functions marked `async` that never `await` — unnecessary overhead\n- [ ] **`late` overuse**: `late` used where nullable or constructor initialization would be safer; defers errors to runtime\n- [ ] **String concatenation in loops**: Use `StringBuffer` instead of `+` for iterative string building\n- [ ] **Mutable state in `const` contexts**: Fields in `const` constructor classes should not be mutable\n- [ ] **Ignoring `Future` return values**: Use `await` or explicitly call `unawaited()` to signal intent\n- [ ] **`var` where `final` works**: Prefer `final` for locals and `const` for compile-time constants\n- [ ] **Relative imports**: Use `package:` imports for consistency\n- [ ] **Mutable collections exposed**: Public APIs should return unmodifiable views, not raw `List`\u002F`Map`\n- [ ] **Missing Dart 3 pattern matching**: Prefer switch expressions and `if-case` over verbose `is` checks and manual casting\n- [ ] **Throwaway classes for multiple returns**: Use Dart 3 records `(String, int)` instead of single-use DTOs\n- [ ] **`print()` in production code**: Use `dart:developer` `log()` or the project's logging package; `print()` has no log levels and cannot be filtered\n\n---\n\n## 3. Widget Best Practices\n\n### Widget decomposition:\n- [ ] No single widget with a `build()` method exceeding ~80-100 lines\n- [ ] Widgets split by encapsulation AND by how they change (rebuild boundaries)\n- [ ] Private `_build*()` helper methods that return widgets are extracted to separate widget classes (enables element reuse, const propagation, and framework optimizations)\n- [ ] Stateless widgets preferred over Stateful where no mutable local state is needed\n- [ ] Extracted widgets are in separate files when reusable\n\n### Const usage:\n- [ ] `const` constructors used wherever possible — prevents unnecessary rebuilds\n- [ ] `const` literals for collections that don't change (`const []`, `const {}`)\n- [ ] Constructor is declared `const` when all fields are final\n\n### Key usage:\n- [ ] `ValueKey` used in lists\u002Fgrids to preserve state across reorders\n- [ ] `GlobalKey` used sparingly — only when accessing state across the tree is truly needed\n- [ ] `UniqueKey` avoided in `build()` — it forces rebuild every frame\n- [ ] `ObjectKey` used when identity is based on a data object rather than a single value\n\n### Theming & design system:\n- [ ] Colors come from `Theme.of(context).colorScheme` — no hardcoded `Colors.red` or hex values\n- [ ] Text styles come from `Theme.of(context).textTheme` — no inline `TextStyle` with raw font sizes\n- [ ] Dark mode compatibility verified — no assumptions about light background\n- [ ] Spacing and sizing use consistent design tokens or constants, not magic numbers\n\n### Build method complexity:\n- [ ] No network calls, file I\u002FO, or heavy computation in `build()`\n- [ ] No `Future.then()` or `async` work in `build()`\n- [ ] No subscription creation (`.listen()`) in `build()`\n- [ ] `setState()` localized to smallest possible subtree\n\n---\n\n## 4. State Management (Library-Agnostic)\n\nThese principles apply to all Flutter state management solutions (BLoC, Riverpod, Provider, GetX, MobX, Signals, ValueNotifier, etc.).\n\n### Architecture:\n- [ ] Business logic lives outside the widget layer — in a state management component (BLoC, Notifier, Controller, Store, ViewModel, etc.)\n- [ ] State managers receive dependencies via injection, not by constructing them internally\n- [ ] A service or repository layer abstracts data sources — widgets and state managers should not call APIs or databases directly\n- [ ] State managers have a single responsibility — no \"god\" managers handling unrelated concerns\n- [ ] Cross-component dependencies follow the solution's conventions:\n  - In **Riverpod**: providers depending on providers via `ref.watch` is expected — flag only circular or overly tangled chains\n  - In **BLoC**: blocs should not directly depend on other blocs — prefer shared repositories or presentation-layer coordination\n  - In other solutions: follow the documented conventions for inter-component communication\n\n### Immutability & value equality (for immutable-state solutions: BLoC, Riverpod, Redux):\n- [ ] State objects are immutable — new instances created via `copyWith()` or constructors, never mutated in-place\n- [ ] State classes implement `==` and `hashCode` properly (all fields included in comparison)\n- [ ] Mechanism is consistent across the project — manual override, `Equatable`, `freezed`, Dart records, or other\n- [ ] Collections inside state objects are not exposed as raw mutable `List`\u002F`Map`\n\n### Reactivity discipline (for reactive-mutation solutions: MobX, GetX, Signals):\n- [ ] State is only mutated through the solution's reactive API (`@action` in MobX, `.value` on signals, `.obs` in GetX) — direct field mutation bypasses change tracking\n- [ ] Derived values use the solution's computed mechanism rather than being stored redundantly\n- [ ] Reactions and disposers are properly cleaned up (`ReactionDisposer` in MobX, effect cleanup in Signals)\n\n### State shape design:\n- [ ] Mutually exclusive states use sealed types, union variants, or the solution's built-in async state type (e.g. Riverpod's `AsyncValue`) — not boolean flags (`isLoading`, `isError`, `hasData`)\n- [ ] Every async operation models loading, success, and error as distinct states\n- [ ] All state variants are handled exhaustively in UI — no silently ignored cases\n- [ ] Error states carry error information for display; loading states don't carry stale data\n- [ ] Nullable data is not used as a loading indicator — states are explicit\n\n```dart\n\u002F\u002F BAD — boolean flag soup allows impossible states\nclass UserState {\n  bool isLoading = false;\n  bool hasError = false; \u002F\u002F isLoading && hasError is representable!\n  User? user;\n}\n\n\u002F\u002F GOOD (immutable approach) — sealed types make impossible states unrepresentable\nsealed class UserState {}\nclass UserInitial extends UserState {}\nclass UserLoading extends UserState {}\nclass UserLoaded extends UserState {\n  final User user;\n  const UserLoaded(this.user);\n}\nclass UserError extends UserState {\n  final String message;\n  const UserError(this.message);\n}\n\n\u002F\u002F GOOD (reactive approach) — observable enum + data, mutations via reactivity API\n\u002F\u002F enum UserStatus { initial, loading, loaded, error }\n\u002F\u002F Use your solution's observable\u002Fsignal to wrap status and data separately\n```\n\n### Rebuild optimization:\n- [ ] State consumer widgets (Builder, Consumer, Observer, Obx, Watch, etc.) scoped as narrow as possible\n- [ ] Selectors used to rebuild only when specific fields change — not on every state emission\n- [ ] `const` widgets used to stop rebuild propagation through the tree\n- [ ] Computed\u002Fderived state is calculated reactively, not stored redundantly\n\n### Subscriptions & disposal:\n- [ ] All manual subscriptions (`.listen()`) are cancelled in `dispose()` \u002F `close()`\n- [ ] Stream controllers are closed when no longer needed\n- [ ] Timers are cancelled in disposal lifecycle\n- [ ] Framework-managed lifecycle is preferred over manual subscription (declarative builders over `.listen()`)\n- [ ] `mounted` check before `setState` in async callbacks\n- [ ] `BuildContext` not used after `await` without checking `context.mounted` (Flutter 3.7+) — stale context causes crashes\n- [ ] No navigation, dialogs, or scaffold messages after async gaps without verifying the widget is still mounted\n- [ ] `BuildContext` never stored in singletons, state managers, or static fields\n\n### Local vs global state:\n- [ ] Ephemeral UI state (checkbox, slider, animation) uses local state (`setState`, `ValueNotifier`)\n- [ ] Shared state is lifted only as high as needed — not over-globalized\n- [ ] Feature-scoped state is properly disposed when the feature is no longer active\n\n---\n\n## 5. Performance\n\n### Unnecessary rebuilds:\n- [ ] `setState()` not called at root widget level — localize state changes\n- [ ] `const` widgets used to stop rebuild propagation\n- [ ] `RepaintBoundary` used around complex subtrees that repaint independently\n- [ ] `AnimatedBuilder` child parameter used for subtrees independent of animation\n\n### Expensive operations in build():\n- [ ] No sorting, filtering, or mapping large collections in `build()` — compute in state management layer\n- [ ] No regex compilation in `build()`\n- [ ] `MediaQuery.of(context)` usage is specific (e.g., `MediaQuery.sizeOf(context)`)\n\n### Image optimization:\n- [ ] Network images use caching (any caching solution appropriate for the project)\n- [ ] Appropriate image resolution for target device (no loading 4K images for thumbnails)\n- [ ] `Image.asset` with `cacheWidth`\u002F`cacheHeight` to decode at display size\n- [ ] Placeholder and error widgets provided for network images\n\n### Lazy loading:\n- [ ] `ListView.builder` \u002F `GridView.builder` used instead of `ListView(children: [...])` for large or dynamic lists (concrete constructors are fine for small, static lists)\n- [ ] Pagination implemented for large data sets\n- [ ] Deferred loading (`deferred as`) used for heavy libraries in web builds\n\n### Other:\n- [ ] `Opacity` widget avoided in animations — use `AnimatedOpacity` or `FadeTransition`\n- [ ] Clipping avoided in animations — pre-clip images\n- [ ] `operator ==` not overridden on widgets — use `const` constructors instead\n- [ ] Intrinsic dimension widgets (`IntrinsicHeight`, `IntrinsicWidth`) used sparingly (extra layout pass)\n\n---\n\n## 6. Testing\n\n### Test types and expectations:\n- [ ] **Unit tests**: Cover all business logic (state managers, repositories, utility functions)\n- [ ] **Widget tests**: Cover individual widget behavior, interactions, and visual output\n- [ ] **Integration tests**: Cover critical user flows end-to-end\n- [ ] **Golden tests**: Pixel-perfect comparisons for design-critical UI components\n\n### Coverage targets:\n- [ ] Aim for 80%+ line coverage on business logic\n- [ ] All state transitions have corresponding tests (loading → success, loading → error, retry, etc.)\n- [ ] Edge cases tested: empty states, error states, loading states, boundary values\n\n### Test isolation:\n- [ ] External dependencies (API clients, databases, services) are mocked or faked\n- [ ] Each test file tests exactly one class\u002Funit\n- [ ] Tests verify behavior, not implementation details\n- [ ] Stubs define only the behavior needed for each test (minimal stubbing)\n- [ ] No shared mutable state between test cases\n\n### Widget test quality:\n- [ ] `pumpWidget` and `pump` used correctly for async operations\n- [ ] `find.byType`, `find.text`, `find.byKey` used appropriately\n- [ ] No flaky tests depending on timing — use `pumpAndSettle` or explicit `pump(Duration)`\n- [ ] Tests run in CI and failures block merges\n\n---\n\n## 7. Accessibility\n\n### Semantic widgets:\n- [ ] `Semantics` widget used to provide screen reader labels where automatic labels are insufficient\n- [ ] `ExcludeSemantics` used for purely decorative elements\n- [ ] `MergeSemantics` used to combine related widgets into a single accessible element\n- [ ] Images have `semanticLabel` property set\n\n### Screen reader support:\n- [ ] All interactive elements are focusable and have meaningful descriptions\n- [ ] Focus order is logical (follows visual reading order)\n\n### Visual accessibility:\n- [ ] Contrast ratio >= 4.5:1 for text against background\n- [ ] Tappable targets are at least 48x48 pixels\n- [ ] Color is not the sole indicator of state (use icons\u002Ftext alongside)\n- [ ] Text scales with system font size settings\n\n### Interaction accessibility:\n- [ ] No no-op `onPressed` callbacks — every button does something or is disabled\n- [ ] Error fields suggest corrections\n- [ ] Context does not change unexpectedly while user is inputting data\n\n---\n\n## 8. Platform-Specific Concerns\n\n### iOS\u002FAndroid differences:\n- [ ] Platform-adaptive widgets used where appropriate\n- [ ] Back navigation handled correctly (Android back button, iOS swipe-to-go-back)\n- [ ] Status bar and safe area handled via `SafeArea` widget\n- [ ] Platform-specific permissions declared in `AndroidManifest.xml` and `Info.plist`\n\n### Responsive design:\n- [ ] `LayoutBuilder` or `MediaQuery` used for responsive layouts\n- [ ] Breakpoints defined consistently (phone, tablet, desktop)\n- [ ] Text doesn't overflow on small screens — use `Flexible`, `Expanded`, `FittedBox`\n- [ ] Landscape orientation tested or explicitly locked\n- [ ] Web-specific: mouse\u002Fkeyboard interactions supported, hover states present\n\n---\n\n## 9. Security\n\n### Secure storage:\n- [ ] Sensitive data (tokens, credentials) stored using platform-secure storage (Keychain on iOS, EncryptedSharedPreferences on Android)\n- [ ] Never store secrets in plaintext storage\n- [ ] Biometric authentication gating considered for sensitive operations\n\n### API key handling:\n- [ ] API keys NOT hardcoded in Dart source — use `--dart-define`, `.env` files excluded from VCS, or compile-time configuration\n- [ ] Secrets not committed to git — check `.gitignore`\n- [ ] Backend proxy used for truly secret keys (client should never hold server secrets)\n\n### Input validation:\n- [ ] All user input validated before sending to API\n- [ ] Form validation uses proper validation patterns\n- [ ] No raw SQL or string interpolation of user input\n- [ ] Deep link URLs validated and sanitized before navigation\n\n### Network security:\n- [ ] HTTPS enforced for all API calls\n- [ ] Certificate pinning considered for high-security apps\n- [ ] Authentication tokens refreshed and expired properly\n- [ ] No sensitive data logged or printed\n\n---\n\n## 10. Package\u002FDependency Review\n\n### Evaluating pub.dev packages:\n- [ ] Check **pub points score** (aim for 130+\u002F160)\n- [ ] Check **likes** and **popularity** as community signals\n- [ ] Verify the publisher is **verified** on pub.dev\n- [ ] Check last publish date — stale packages (>1 year) are a risk\n- [ ] Review open issues and response time from maintainers\n- [ ] Check license compatibility with your project\n- [ ] Verify platform support covers your targets\n\n### Version constraints:\n- [ ] Use caret syntax (`^1.2.3`) for dependencies — allows compatible updates\n- [ ] Pin exact versions only when absolutely necessary\n- [ ] Run `flutter pub outdated` regularly to track stale dependencies\n- [ ] No dependency overrides in production `pubspec.yaml` — only for temporary fixes with a comment\u002Fissue link\n- [ ] Minimize transitive dependency count — each dependency is an attack surface\n\n### Monorepo-specific (melos\u002Fworkspace):\n- [ ] Internal packages import only from public API — no `package:other\u002Fsrc\u002Finternal.dart` (breaks Dart package encapsulation)\n- [ ] Internal package dependencies use workspace resolution, not hardcoded `path: ..\u002F..\u002F` relative strings\n- [ ] All sub-packages share or inherit root `analysis_options.yaml`\n\n---\n\n## 11. Navigation and Routing\n\n### General principles (apply to any routing solution):\n- [ ] One routing approach used consistently — no mixing imperative `Navigator.push` with a declarative router\n- [ ] Route arguments are typed — no `Map\u003CString, dynamic>` or `Object?` casting\n- [ ] Route paths defined as constants, enums, or generated — no magic strings scattered in code\n- [ ] Auth guards\u002Fredirects centralized — not duplicated across individual screens\n- [ ] Deep links configured for both Android and iOS\n- [ ] Deep link URLs validated and sanitized before navigation\n- [ ] Navigation state is testable — route changes can be verified in tests\n- [ ] Back behavior is correct on all platforms\n\n---\n\n## 12. Error Handling\n\n### Framework error handling:\n- [ ] `FlutterError.onError` overridden to capture framework errors (build, layout, paint)\n- [ ] `PlatformDispatcher.instance.onError` set for async errors not caught by Flutter\n- [ ] `ErrorWidget.builder` customized for release mode (user-friendly instead of red screen)\n- [ ] Global error capture wrapper around `runApp` (e.g., `runZonedGuarded`, Sentry\u002FCrashlytics wrapper)\n\n### Error reporting:\n- [ ] Error reporting service integrated (Firebase Crashlytics, Sentry, or equivalent)\n- [ ] Non-fatal errors reported with stack traces\n- [ ] State management error observer wired to error reporting (e.g., BlocObserver, ProviderObserver, or equivalent for your solution)\n- [ ] User-identifiable info (user ID) attached to error reports for debugging\n\n### Graceful degradation:\n- [ ] API errors result in user-friendly error UI, not crashes\n- [ ] Retry mechanisms for transient network failures\n- [ ] Offline state handled gracefully\n- [ ] Error states in state management carry error info for display\n- [ ] Raw exceptions (network, parsing) are mapped to user-friendly, localized messages before reaching the UI — never show raw exception strings to users\n\n---\n\n## 13. Internationalization (l10n)\n\n### Setup:\n- [ ] Localization solution configured (Flutter's built-in ARB\u002Fl10n, easy_localization, or equivalent)\n- [ ] Supported locales declared in app configuration\n\n### Content:\n- [ ] All user-visible strings use the localization system — no hardcoded strings in widgets\n- [ ] Template file includes descriptions\u002Fcontext for translators\n- [ ] ICU message syntax used for plurals, genders, selects\n- [ ] Placeholders defined with types\n- [ ] No missing keys across locales\n\n### Code review:\n- [ ] Localization accessor used consistently throughout the project\n- [ ] Date, time, number, and currency formatting is locale-aware\n- [ ] Text directionality (RTL) supported if targeting Arabic, Hebrew, etc.\n- [ ] No string concatenation for localized text — use parameterized messages\n\n---\n\n## 14. Dependency Injection\n\n### Principles (apply to any DI approach):\n- [ ] Classes depend on abstractions (interfaces), not concrete implementations at layer boundaries\n- [ ] Dependencies provided externally via constructor, DI framework, or provider graph — not created internally\n- [ ] Registration distinguishes lifetime: singleton vs factory vs lazy singleton\n- [ ] Environment-specific bindings (dev\u002Fstaging\u002Fprod) use configuration, not runtime `if` checks\n- [ ] No circular dependencies in the DI graph\n- [ ] Service locator calls (if used) are not scattered throughout business logic\n\n---\n\n## 15. Static Analysis\n\n### Configuration:\n- [ ] `analysis_options.yaml` present with strict settings enabled\n- [ ] Strict analyzer settings: `strict-casts: true`, `strict-inference: true`, `strict-raw-types: true`\n- [ ] A comprehensive lint rule set is included (very_good_analysis, flutter_lints, or custom strict rules)\n- [ ] All sub-packages in monorepos inherit or share the root analysis options\n\n### Enforcement:\n- [ ] No unresolved analyzer warnings in committed code\n- [ ] Lint suppressions (`\u002F\u002F ignore:`) are justified with comments explaining why\n- [ ] `flutter analyze` runs in CI and failures block merges\n\n### Key rules to verify regardless of lint package:\n- [ ] `prefer_const_constructors` — performance in widget trees\n- [ ] `avoid_print` — use proper logging\n- [ ] `unawaited_futures` — prevent fire-and-forget async bugs\n- [ ] `prefer_final_locals` — immutability at variable level\n- [ ] `always_declare_return_types` — explicit contracts\n- [ ] `avoid_catches_without_on_clauses` — specific error handling\n- [ ] `always_use_package_imports` — consistent import style\n\n---\n\n## State Management Quick Reference\n\nThe table below maps universal principles to their implementation in popular solutions. Use this to adapt review rules to whichever solution the project uses.\n\n| Principle | BLoC\u002FCubit | Riverpod | Provider | GetX | MobX | Signals | Built-in |\n|-----------|-----------|----------|----------|------|------|---------|----------|\n| State container | `Bloc`\u002F`Cubit` | `Notifier`\u002F`AsyncNotifier` | `ChangeNotifier` | `GetxController` | `Store` | `signal()` | `StatefulWidget` |\n| UI consumer | `BlocBuilder` | `ConsumerWidget` | `Consumer` | `Obx`\u002F`GetBuilder` | `Observer` | `Watch` | `setState` |\n| Selector | `BlocSelector`\u002F`buildWhen` | `ref.watch(p.select(...))` | `Selector` | N\u002FA | computed | `computed()` | N\u002FA |\n| Side effects | `BlocListener` | `ref.listen` | `Consumer` callback | `ever()`\u002F`once()` | `reaction` | `effect()` | callbacks |\n| Disposal | auto via `BlocProvider` | `.autoDispose` | auto via `Provider` | `onClose()` | `ReactionDisposer` | manual | `dispose()` |\n| Testing | `blocTest()` | `ProviderContainer` | `ChangeNotifier` directly | `Get.put` in test | store directly | signal directly | widget test |\n\n---\n\n## Sources\n\n- [Effective Dart: Style](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fstyle)\n- [Effective Dart: Usage](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fusage)\n- [Effective Dart: Design](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fdesign)\n- [Flutter Performance Best Practices](https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fbest-practices)\n- [Flutter Testing Overview](https:\u002F\u002Fdocs.flutter.dev\u002Ftesting\u002Foverview)\n- [Flutter Accessibility](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Faccessibility-and-internationalization\u002Faccessibility)\n- [Flutter Internationalization](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Faccessibility-and-internationalization\u002Finternationalization)\n- [Flutter Navigation and Routing](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Fnavigation)\n- [Flutter Error Handling](https:\u002F\u002Fdocs.flutter.dev\u002Ftesting\u002Ferrors)\n- [Flutter State Management Options](https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions)\n","# Flutter\u002FDart Code Review Best Practices\n\nComprehensive, library-agnostic checklist for reviewing Flutter\u002FDart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used.\n\n---\n\n## 1. General Project Health\n\n- [ ] Project follows consistent folder structure (feature-first or layer-first)\n- [ ] Proper separation of concerns: UI, business logic, data layers\n- [ ] No business logic in widgets; widgets are purely presentational\n- [ ] `pubspec.yaml` is clean — no unused dependencies, versions pinned appropriately\n- [ ] `analysis_options.yaml` includes a strict lint set with strict analyzer settings enabled\n- [ ] No `print()` statements in production code — use `dart:developer` `log()` or a logging package\n- [ ] Generated files (`.g.dart`, `.freezed.dart`, `.gr.dart`) are up-to-date or in `.gitignore`\n- [ ] Platform-specific code isolated behind abstractions\n\n---\n\n## 2. Dart Language Pitfalls\n\n- [ ] **Implicit dynamic**: Missing type annotations leading to `dynamic` — enable `strict-casts`, `strict-inference`, `strict-raw-types`\n- [ ] **Null safety misuse**: Excessive `!` (bang operator) instead of proper null checks or Dart 3 pattern matching (`if (value case var v?)`)\n- [ ] **Type promotion failures**: Using `this.field` where local variable promotion would work\n- [ ] **Catching too broadly**: `catch (e)` without `on` clause; always specify exception types\n- [ ] **Catching `Error`**: `Error` subtypes indicate bugs and should not be caught\n- [ ] **Unused `async`**: Functions marked `async` that never `await` — unnecessary overhead\n- [ ] **`late` overuse**: `late` used where nullable or constructor initialization would be safer; defers errors to runtime\n- [ ] **String concatenation in loops**: Use `StringBuffer` instead of `+` for iterative string building\n- [ ] **Mutable state in `const` contexts**: Fields in `const` constructor classes should not be mutable\n- [ ] **Ignoring `Future` return values**: Use `await` or explicitly call `unawaited()` to signal intent\n- [ ] **`var` where `final` works**: Prefer `final` for locals and `const` for compile-time constants\n- [ ] **Relative imports**: Use `package:` imports for consistency\n- [ ] **Mutable collections exposed**: Public APIs should return unmodifiable views, not raw `List`\u002F`Map`\n- [ ] **Missing Dart 3 pattern matching**: Prefer switch expressions and `if-case` over verbose `is` checks and manual casting\n- [ ] **Throwaway classes for multiple returns**: Use Dart 3 records `(String, int)` instead of single-use DTOs\n- [ ] **`print()` in production code**: Use `dart:developer` `log()` or the project's logging package; `print()` has no log levels and cannot be filtered\n\n---\n\n## 3. Widget Best Practices\n\n### Widget decomposition:\n- [ ] No single widget with a `build()` method exceeding ~80-100 lines\n- [ ] Widgets split by encapsulation AND by how they change (rebuild boundaries)\n- [ ] Private `_build*()` helper methods that return widgets are extracted to separate widget classes (enables element reuse, const propagation, and framework optimizations)\n- [ ] Stateless widgets preferred over Stateful where no mutable local state is needed\n- [ ] Extracted widgets are in separate files when reusable\n\n### Const usage:\n- [ ] `const` constructors used wherever possible — prevents unnecessary rebuilds\n- [ ] `const` literals for collections that don't change (`const []`, `const {}`)\n- [ ] Constructor is declared `const` when all fields are final\n\n### Key usage:\n- [ ] `ValueKey` used in lists\u002Fgrids to preserve state across reorders\n- [ ] `GlobalKey` used sparingly — only when accessing state across the tree is truly needed\n- [ ] `UniqueKey` avoided in `build()` — it forces rebuild every frame\n- [ ] `ObjectKey` used when identity is based on a data object rather than a single value\n\n### Theming & design system:\n- [ ] Colors come from `Theme.of(context).colorScheme` — no hardcoded `Colors.red` or hex values\n- [ ] Text styles come from `Theme.of(context).textTheme` — no inline `TextStyle` with raw font sizes\n- [ ] Dark mode compatibility verified — no assumptions about light background\n- [ ] Spacing and sizing use consistent design tokens or constants, not magic numbers\n\n### Build method complexity:\n- [ ] No network calls, file I\u002FO, or heavy computation in `build()`\n- [ ] No `Future.then()` or `async` work in `build()`\n- [ ] No subscription creation (`.listen()`) in `build()`\n- [ ] `setState()` localized to smallest possible subtree\n\n---\n\n## 4. State Management (Library-Agnostic)\n\nThese principles apply to all Flutter state management solutions (BLoC, Riverpod, Provider, GetX, MobX, Signals, ValueNotifier, etc.).\n\n### Architecture:\n- [ ] Business logic lives outside the widget layer — in a state management component (BLoC, Notifier, Controller, Store, ViewModel, etc.)\n- [ ] State managers receive dependencies via injection, not by constructing them internally\n- [ ] A service or repository layer abstracts data sources — widgets and state managers should not call APIs or databases directly\n- [ ] State managers have a single responsibility — no \"god\" managers handling unrelated concerns\n- [ ] Cross-component dependencies follow the solution's conventions:\n  - In **Riverpod**: providers depending on providers via `ref.watch` is expected — flag only circular or overly tangled chains\n  - In **BLoC**: blocs should not directly depend on other blocs — prefer shared repositories or presentation-layer coordination\n  - In other solutions: follow the documented conventions for inter-component communication\n\n### Immutability & value equality (for immutable-state solutions: BLoC, Riverpod, Redux):\n- [ ] State objects are immutable — new instances created via `copyWith()` or constructors, never mutated in-place\n- [ ] State classes implement `==` and `hashCode` properly (all fields included in comparison)\n- [ ] Mechanism is consistent across the project — manual override, `Equatable`, `freezed`, Dart records, or other\n- [ ] Collections inside state objects are not exposed as raw mutable `List`\u002F`Map`\n\n### Reactivity discipline (for reactive-mutation solutions: MobX, GetX, Signals):\n- [ ] State is only mutated through the solution's reactive API (`@action` in MobX, `.value` on signals, `.obs` in GetX) — direct field mutation bypasses change tracking\n- [ ] Derived values use the solution's computed mechanism rather than being stored redundantly\n- [ ] Reactions and disposers are properly cleaned up (`ReactionDisposer` in MobX, effect cleanup in Signals)\n\n### State shape design:\n- [ ] Mutually exclusive states use sealed types, union variants, or the solution's built-in async state type (e.g. Riverpod's `AsyncValue`) — not boolean flags (`isLoading`, `isError`, `hasData`)\n- [ ] Every async operation models loading, success, and error as distinct states\n- [ ] All state variants are handled exhaustively in UI — no silently ignored cases\n- [ ] Error states carry error information for display; loading states don't carry stale data\n- [ ] Nullable data is not used as a loading indicator — states are explicit\n\n```dart\n\u002F\u002F BAD — boolean flag soup allows impossible states\nclass UserState {\n  bool isLoading = false;\n  bool hasError = false; \u002F\u002F isLoading && hasError is representable!\n  User? user;\n}\n\n\u002F\u002F GOOD (immutable approach) — sealed types make impossible states unrepresentable\nsealed class UserState {}\nclass UserInitial extends UserState {}\nclass UserLoading extends UserState {}\nclass UserLoaded extends UserState {\n  final User user;\n  const UserLoaded(this.user);\n}\nclass UserError extends UserState {\n  final String message;\n  const UserError(this.message);\n}\n\n\u002F\u002F GOOD (reactive approach) — observable enum + data, mutations via reactivity API\n\u002F\u002F enum UserStatus { initial, loading, loaded, error }\n\u002F\u002F Use your solution's observable\u002Fsignal to wrap status and data separately\n```\n\n### Rebuild optimization:\n- [ ] State consumer widgets (Builder, Consumer, Observer, Obx, Watch, etc.) scoped as narrow as possible\n- [ ] Selectors used to rebuild only when specific fields change — not on every state emission\n- [ ] `const` widgets used to stop rebuild propagation through the tree\n- [ ] Computed\u002Fderived state is calculated reactively, not stored redundantly\n\n### Subscriptions & disposal:\n- [ ] All manual subscriptions (`.listen()`) are cancelled in `dispose()` \u002F `close()`\n- [ ] Stream controllers are closed when no longer needed\n- [ ] Timers are cancelled in disposal lifecycle\n- [ ] Framework-managed lifecycle is preferred over manual subscription (declarative builders over `.listen()`)\n- [ ] `mounted` check before `setState` in async callbacks\n- [ ] `BuildContext` not used after `await` without checking `context.mounted` (Flutter 3.7+) — stale context causes crashes\n- [ ] No navigation, dialogs, or scaffold messages after async gaps without verifying the widget is still mounted\n- [ ] `BuildContext` never stored in singletons, state managers, or static fields\n\n### Local vs global state:\n- [ ] Ephemeral UI state (checkbox, slider, animation) uses local state (`setState`, `ValueNotifier`)\n- [ ] Shared state is lifted only as high as needed — not over-globalized\n- [ ] Feature-scoped state is properly disposed when the feature is no longer active\n\n---\n\n## 5. Performance\n\n### Unnecessary rebuilds:\n- [ ] `setState()` not called at root widget level — localize state changes\n- [ ] `const` widgets used to stop rebuild propagation\n- [ ] `RepaintBoundary` used around complex subtrees that repaint independently\n- [ ] `AnimatedBuilder` child parameter used for subtrees independent of animation\n\n### Expensive operations in build():\n- [ ] No sorting, filtering, or mapping large collections in `build()` — compute in state management layer\n- [ ] No regex compilation in `build()`\n- [ ] `MediaQuery.of(context)` usage is specific (e.g., `MediaQuery.sizeOf(context)`)\n\n### Image optimization:\n- [ ] Network images use caching (any caching solution appropriate for the project)\n- [ ] Appropriate image resolution for target device (no loading 4K images for thumbnails)\n- [ ] `Image.asset` with `cacheWidth`\u002F`cacheHeight` to decode at display size\n- [ ] Placeholder and error widgets provided for network images\n\n### Lazy loading:\n- [ ] `ListView.builder` \u002F `GridView.builder` used instead of `ListView(children: [...])` for large or dynamic lists (concrete constructors are fine for small, static lists)\n- [ ] Pagination implemented for large data sets\n- [ ] Deferred loading (`deferred as`) used for heavy libraries in web builds\n\n### Other:\n- [ ] `Opacity` widget avoided in animations — use `AnimatedOpacity` or `FadeTransition`\n- [ ] Clipping avoided in animations — pre-clip images\n- [ ] `operator ==` not overridden on widgets — use `const` constructors instead\n- [ ] Intrinsic dimension widgets (`IntrinsicHeight`, `IntrinsicWidth`) used sparingly (extra layout pass)\n\n---\n\n## 6. Testing\n\n### Test types and expectations:\n- [ ] **Unit tests**: Cover all business logic (state managers, repositories, utility functions)\n- [ ] **Widget tests**: Cover individual widget behavior, interactions, and visual output\n- [ ] **Integration tests**: Cover critical user flows end-to-end\n- [ ] **Golden tests**: Pixel-perfect comparisons for design-critical UI components\n\n### Coverage targets:\n- [ ] Aim for 80%+ line coverage on business logic\n- [ ] All state transitions have corresponding tests (loading → success, loading → error, retry, etc.)\n- [ ] Edge cases tested: empty states, error states, loading states, boundary values\n\n### Test isolation:\n- [ ] External dependencies (API clients, databases, services) are mocked or faked\n- [ ] Each test file tests exactly one class\u002Funit\n- [ ] Tests verify behavior, not implementation details\n- [ ] Stubs define only the behavior needed for each test (minimal stubbing)\n- [ ] No shared mutable state between test cases\n\n### Widget test quality:\n- [ ] `pumpWidget` and `pump` used correctly for async operations\n- [ ] `find.byType`, `find.text`, `find.byKey` used appropriately\n- [ ] No flaky tests depending on timing — use `pumpAndSettle` or explicit `pump(Duration)`\n- [ ] Tests run in CI and failures block merges\n\n---\n\n## 7. Accessibility\n\n### Semantic widgets:\n- [ ] `Semantics` widget used to provide screen reader labels where automatic labels are insufficient\n- [ ] `ExcludeSemantics` used for purely decorative elements\n- [ ] `MergeSemantics` used to combine related widgets into a single accessible element\n- [ ] Images have `semanticLabel` property set\n\n### Screen reader support:\n- [ ] All interactive elements are focusable and have meaningful descriptions\n- [ ] Focus order is logical (follows visual reading order)\n\n### Visual accessibility:\n- [ ] Contrast ratio >= 4.5:1 for text against background\n- [ ] Tappable targets are at least 48x48 pixels\n- [ ] Color is not the sole indicator of state (use icons\u002Ftext alongside)\n- [ ] Text scales with system font size settings\n\n### Interaction accessibility:\n- [ ] No no-op `onPressed` callbacks — every button does something or is disabled\n- [ ] Error fields suggest corrections\n- [ ] Context does not change unexpectedly while user is inputting data\n\n---\n\n## 8. Platform-Specific Concerns\n\n### iOS\u002FAndroid differences:\n- [ ] Platform-adaptive widgets used where appropriate\n- [ ] Back navigation handled correctly (Android back button, iOS swipe-to-go-back)\n- [ ] Status bar and safe area handled via `SafeArea` widget\n- [ ] Platform-specific permissions declared in `AndroidManifest.xml` and `Info.plist`\n\n### Responsive design:\n- [ ] `LayoutBuilder` or `MediaQuery` used for responsive layouts\n- [ ] Breakpoints defined consistently (phone, tablet, desktop)\n- [ ] Text doesn't overflow on small screens — use `Flexible`, `Expanded`, `FittedBox`\n- [ ] Landscape orientation tested or explicitly locked\n- [ ] Web-specific: mouse\u002Fkeyboard interactions supported, hover states present\n\n---\n\n## 9. Security\n\n### Secure storage:\n- [ ] Sensitive data (tokens, credentials) stored using platform-secure storage (Keychain on iOS, EncryptedSharedPreferences on Android)\n- [ ] Never store secrets in plaintext storage\n- [ ] Biometric authentication gating considered for sensitive operations\n\n### API key handling:\n- [ ] API keys NOT hardcoded in Dart source — use `--dart-define`, `.env` files excluded from VCS, or compile-time configuration\n- [ ] Secrets not committed to git — check `.gitignore`\n- [ ] Backend proxy used for truly secret keys (client should never hold server secrets)\n\n### Input validation:\n- [ ] All user input validated before sending to API\n- [ ] Form validation uses proper validation patterns\n- [ ] No raw SQL or string interpolation of user input\n- [ ] Deep link URLs validated and sanitized before navigation\n\n### Network security:\n- [ ] HTTPS enforced for all API calls\n- [ ] Certificate pinning considered for high-security apps\n- [ ] Authentication tokens refreshed and expired properly\n- [ ] No sensitive data logged or printed\n\n---\n\n## 10. Package\u002FDependency Review\n\n### Evaluating pub.dev packages:\n- [ ] Check **pub points score** (aim for 130+\u002F160)\n- [ ] Check **likes** and **popularity** as community signals\n- [ ] Verify the publisher is **verified** on pub.dev\n- [ ] Check last publish date — stale packages (>1 year) are a risk\n- [ ] Review open issues and response time from maintainers\n- [ ] Check license compatibility with your project\n- [ ] Verify platform support covers your targets\n\n### Version constraints:\n- [ ] Use caret syntax (`^1.2.3`) for dependencies — allows compatible updates\n- [ ] Pin exact versions only when absolutely necessary\n- [ ] Run `flutter pub outdated` regularly to track stale dependencies\n- [ ] No dependency overrides in production `pubspec.yaml` — only for temporary fixes with a comment\u002Fissue link\n- [ ] Minimize transitive dependency count — each dependency is an attack surface\n\n### Monorepo-specific (melos\u002Fworkspace):\n- [ ] Internal packages import only from public API — no `package:other\u002Fsrc\u002Finternal.dart` (breaks Dart package encapsulation)\n- [ ] Internal package dependencies use workspace resolution, not hardcoded `path: ..\u002F..\u002F` relative strings\n- [ ] All sub-packages share or inherit root `analysis_options.yaml`\n\n---\n\n## 11. Navigation and Routing\n\n### General principles (apply to any routing solution):\n- [ ] One routing approach used consistently — no mixing imperative `Navigator.push` with a declarative router\n- [ ] Route arguments are typed — no `Map\u003CString, dynamic>` or `Object?` casting\n- [ ] Route paths defined as constants, enums, or generated — no magic strings scattered in code\n- [ ] Auth guards\u002Fredirects centralized — not duplicated across individual screens\n- [ ] Deep links configured for both Android and iOS\n- [ ] Deep link URLs validated and sanitized before navigation\n- [ ] Navigation state is testable — route changes can be verified in tests\n- [ ] Back behavior is correct on all platforms\n\n---\n\n## 12. Error Handling\n\n### Framework error handling:\n- [ ] `FlutterError.onError` overridden to capture framework errors (build, layout, paint)\n- [ ] `PlatformDispatcher.instance.onError` set for async errors not caught by Flutter\n- [ ] `ErrorWidget.builder` customized for release mode (user-friendly instead of red screen)\n- [ ] Global error capture wrapper around `runApp` (e.g., `runZonedGuarded`, Sentry\u002FCrashlytics wrapper)\n\n### Error reporting:\n- [ ] Error reporting service integrated (Firebase Crashlytics, Sentry, or equivalent)\n- [ ] Non-fatal errors reported with stack traces\n- [ ] State management error observer wired to error reporting (e.g., BlocObserver, ProviderObserver, or equivalent for your solution)\n- [ ] User-identifiable info (user ID) attached to error reports for debugging\n\n### Graceful degradation:\n- [ ] API errors result in user-friendly error UI, not crashes\n- [ ] Retry mechanisms for transient network failures\n- [ ] Offline state handled gracefully\n- [ ] Error states in state management carry error info for display\n- [ ] Raw exceptions (network, parsing) are mapped to user-friendly, localized messages before reaching the UI — never show raw exception strings to users\n\n---\n\n## 13. Internationalization (l10n)\n\n### Setup:\n- [ ] Localization solution configured (Flutter's built-in ARB\u002Fl10n, easy_localization, or equivalent)\n- [ ] Supported locales declared in app configuration\n\n### Content:\n- [ ] All user-visible strings use the localization system — no hardcoded strings in widgets\n- [ ] Template file includes descriptions\u002Fcontext for translators\n- [ ] ICU message syntax used for plurals, genders, selects\n- [ ] Placeholders defined with types\n- [ ] No missing keys across locales\n\n### Code review:\n- [ ] Localization accessor used consistently throughout the project\n- [ ] Date, time, number, and currency formatting is locale-aware\n- [ ] Text directionality (RTL) supported if targeting Arabic, Hebrew, etc.\n- [ ] No string concatenation for localized text — use parameterized messages\n\n---\n\n## 14. Dependency Injection\n\n### Principles (apply to any DI approach):\n- [ ] Classes depend on abstractions (interfaces), not concrete implementations at layer boundaries\n- [ ] Dependencies provided externally via constructor, DI framework, or provider graph — not created internally\n- [ ] Registration distinguishes lifetime: singleton vs factory vs lazy singleton\n- [ ] Environment-specific bindings (dev\u002Fstaging\u002Fprod) use configuration, not runtime `if` checks\n- [ ] No circular dependencies in the DI graph\n- [ ] Service locator calls (if used) are not scattered throughout business logic\n\n---\n\n## 15. Static Analysis\n\n### Configuration:\n- [ ] `analysis_options.yaml` present with strict settings enabled\n- [ ] Strict analyzer settings: `strict-casts: true`, `strict-inference: true`, `strict-raw-types: true`\n- [ ] A comprehensive lint rule set is included (very_good_analysis, flutter_lints, or custom strict rules)\n- [ ] All sub-packages in monorepos inherit or share the root analysis options\n\n### Enforcement:\n- [ ] No unresolved analyzer warnings in committed code\n- [ ] Lint suppressions (`\u002F\u002F ignore:`) are justified with comments explaining why\n- [ ] `flutter analyze` runs in CI and failures block merges\n\n### Key rules to verify regardless of lint package:\n- [ ] `prefer_const_constructors` — performance in widget trees\n- [ ] `avoid_print` — use proper logging\n- [ ] `unawaited_futures` — prevent fire-and-forget async bugs\n- [ ] `prefer_final_locals` — immutability at variable level\n- [ ] `always_declare_return_types` — explicit contracts\n- [ ] `avoid_catches_without_on_clauses` — specific error handling\n- [ ] `always_use_package_imports` — consistent import style\n\n---\n\n## State Management Quick Reference\n\nThe table below maps universal principles to their implementation in popular solutions. Use this to adapt review rules to whichever solution the project uses.\n\n| Principle | BLoC\u002FCubit | Riverpod | Provider | GetX | MobX | Signals | Built-in |\n|-----------|-----------|----------|----------|------|------|---------|----------|\n| State container | `Bloc`\u002F`Cubit` | `Notifier`\u002F`AsyncNotifier` | `ChangeNotifier` | `GetxController` | `Store` | `signal()` | `StatefulWidget` |\n| UI consumer | `BlocBuilder` | `ConsumerWidget` | `Consumer` | `Obx`\u002F`GetBuilder` | `Observer` | `Watch` | `setState` |\n| Selector | `BlocSelector`\u002F`buildWhen` | `ref.watch(p.select(...))` | `Selector` | N\u002FA | computed | `computed()` | N\u002FA |\n| Side effects | `BlocListener` | `ref.listen` | `Consumer` callback | `ever()`\u002F`once()` | `reaction` | `effect()` | callbacks |\n| Disposal | auto via `BlocProvider` | `.autoDispose` | auto via `Provider` | `onClose()` | `ReactionDisposer` | manual | `dispose()` |\n| Testing | `blocTest()` | `ProviderContainer` | `ChangeNotifier` directly | `Get.put` in test | store directly | signal directly | widget test |\n\n---\n\n## Sources\n\n- [Effective Dart: Style](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fstyle)\n- [Effective Dart: Usage](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fusage)\n- [Effective Dart: Design](https:\u002F\u002Fdart.dev\u002Feffective-dart\u002Fdesign)\n- [Flutter Performance Best Practices](https:\u002F\u002Fdocs.flutter.dev\u002Fperf\u002Fbest-practices)\n- [Flutter Testing Overview](https:\u002F\u002Fdocs.flutter.dev\u002Ftesting\u002Foverview)\n- [Flutter Accessibility](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Faccessibility-and-internationalization\u002Faccessibility)\n- [Flutter Internationalization](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Faccessibility-and-internationalization\u002Finternationalization)\n- [Flutter Navigation and Routing](https:\u002F\u002Fdocs.flutter.dev\u002Fui\u002Fnavigation)\n- [Flutter Error Handling](https:\u002F\u002Fdocs.flutter.dev\u002Ftesting\u002Ferrors)\n- [Flutter State Management Options](https:\u002F\u002Fdocs.flutter.dev\u002Fdata-and-backend\u002Fstate-mgmt\u002Foptions)\n",{"name":5,"origin":24,"description":7},"ECC","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Fflutter-dart-code-review",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill flutter-dart-code-review",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill flutter-dart-code-review",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill flutter-dart-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Fflutter-dart-code-review\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]