effective-dart

Follow the official Effective Dart guidelines: use UpperCamelCase for classes, lowerCamelCase for variables and functions, annotate public API types, prefer final over var, and format with dart format. This Skill codifies those rules for writing and reviewing code.

Check naming conventions, type annotations on public APIs, class modifiers like final and sealed, and doc comments on public members. Then run dart format --set-exit-if-changed and dart analyze to confirm zero issues.

Yes, the same naming, typing, and documentation rules apply to Flutter code. The Skill also covers widget testing patterns using testWidgets and WidgetTester for verifying UI behavior like loading indicators.

Use sealed classes when you need exhaustive pattern matching over a fixed set of subtypes, such as modeling Result types with Success and Failure variants. This lets the compiler verify all cases are handled in switch expressions.

dart format and dart analyze catch formatting and static issues but cannot judge API design quality, naming clarity, or whether documentation explains why code exists. Human or AI-guided review is still needed for semantic guideline compliance.