flutter-dart-code-review

What it does

The skill provides a library-agnostic checklist for reviewing Flutter/Dart applications, covering widget best practices, various state management patterns, Dart idioms, performance, accessibility, security, and clean architecture. It instructs the agent to verify project health, language pitfalls, widget structure, state management discipline, performance considerations, testing, accessibility, platform concerns, security, and dependency review.

How it works

It lists explicit checklists split into sections (General Project Health, Dart Language Pitfalls, Widget Best Practices, State Management, Performance, Testing, Accessibility, Platform-Specific Concerns, Security, Package/Dependency Review). Each item is a boolean check to be evaluated (e.g., [ ] Project follows consistent folder structure, [ ] No print() statements in production code). It includes concrete recommendations like avoiding business logic in widgets, avoiding print() in production, using log() from dart:developer, ensuring up-to-date generated files, and enforcing architecture boundaries. For state management, it prescribes immutability, proper separation of concerns, and lifecycle/disposal discipline. For performance, it highlights localization of state changes, use of const widgets, and avoiding heavy work in build. For testing, it enumerates unit, widget, integration, and golden tests with coverage targets. Accessibility and security sections enumerate semantic labeling, input validation, secure storage, and network security practices. Finally, it covers dependency hygiene with pub.dev considerations and versioning norms.

When to use it

Use when conducting code reviews or architecture assessments of Flutter/Dart projects to ensure best practices across UI, state management, performance, testing, accessibility, platform differences, and security.

What it can touch

• Tooling and code patterns are described as checks; it references generic concepts like pubspec.yaml, analysis_options.yaml, dart:developer, copyWith(), Equatable, freezed, Semantics, SafeArea, MediaQuery, pumpWidget, pump, and various state-management concepts. It does not specify modifying files or executing commands within this summary, only the checks to verify.

Caveats

• License: MIT. - The skill is described as library-agnostic and does not commit to a particular framework beyond generic state-management patterns. - It requires interpretation to apply in projects with different architectures. - No procedural outcomes are guaranteed by the checklist itself; it only codifies review criteria.