What problem does it solve?
Provides a Dart-specific layer on top of the universal coding rules so that Flutter and Dart teams do not inadvertently violate Effective Dart naming, formatting, or testing conventions when using a shared rulebook.
Core Features & Use Cases
- Naming and formatting: Enforces PascalCase for public types, camelCase for variables, snake_case filenames, dart format, and consistent import ordering suited to Dart idioms.
- Type safety and async guidance: Recommends null safety, judicious var usage, final and const policies, and best practices for futures, streams, and error handling to keep Dart projects sound.
- Testing and dependency management: Encourages package test structures, focus on business logic, constructor injection, and clear dispose patterns for Flutter widgets and services during reviews or new implementations.
Quick Start
Ask for Dart coding rules before writing or reviewing Dart files to ensure all naming, formatting, and error handling follow Effective Dart guidance.