Dart Coding Practices
Application skill for Dart style learning (from the archived awesome-guidelines style capsules). For Flutter UI patterns, combine with stack-specific foundations.
Core Principle
Dart quality is Effective Dart consistency, formatted mechanically, documented publicly, null-safe and briefly expressed.
When to Use / NOT
- Dart/Flutter libraries, CLI tools, server apps.
- Setting up
dart format, dart analyze, dart test, linter rules in CI.
NOT when:
- Non-Dart code.
- Generated
.g.dart / protobuf, validate generators.
Workflow
- Format & names, dart format, imports, casing (
dart-style-formatting-names.md).
- Docs,
/// summaries, dart doc (dart-style-documentation.md).
- Usage, null, collections, async, errors (
dart-style-usage-idioms.md).
- Design, types, classes, equality (
dart-style-design-api.md).
- Verify,
dart format, dart analyze, dart test on changed packages.
Red Flags
- Unformatted code
- Leading
_ on public symbols
- Missing docs on exported API
- Explicit
= null initialization
.length == 0 emptiness checks- Bare catch swallowing errors
new keyword / redundant const- Import from package
src/
- Missing return type on public function
- Mutable class with custom
==
- Positional boolean parameters
Verification
dart format --set-exit-if-changed .dart analyze (project strictness)dart test for changed packagesdart doc or doc coverage review- Capsule checklist on public API
References
awesome-guidelines/references/dart-style-learning-note.mdawesome-guidelines/references/dart-style-formatting-names.mdawesome-guidelines/references/dart-style-documentation.mdawesome-guidelines/references/dart-style-usage-idioms.mdawesome-guidelines/references/dart-style-design-api.md
1---2name: dart-coding-practices3description: Use when authoring or reviewing Dart, dart format, UpperCamelCase/lowerCamelCase naming, /// documentation, null-safe idioms, async/await, typed public API, class modifiers, and dart analyze/test in CI.4---56# Dart Coding Practices78Application skill for Dart style learning (from the archived `awesome-guidelines` style capsules). For Flutter UI patterns, combine with stack-specific foundations.910## Core Principle1112Dart quality is **Effective Dart consistency**, formatted mechanically, documented publicly, null-safe and briefly expressed.1314## When to Use / NOT1516- Dart/Flutter libraries, CLI tools, server apps.17- Setting up `dart format`, `dart analyze`, `dart test`, linter rules in CI.1819**NOT when:**2021- Non-Dart code.22- Generated `.g.dart` / protobuf, validate generators.2324## Workflow25261. **Format & names**, dart format, imports, casing (`dart-style-formatting-names.md`).272. **Docs**, `///` summaries, dart doc (`dart-style-documentation.md`).283. **Usage**, null, collections, async, errors (`dart-style-usage-idioms.md`).294. **Design**, types, classes, equality (`dart-style-design-api.md`).305. **Verify**, `dart format`, `dart analyze`, `dart test` on changed packages.3132## Red Flags3334- Unformatted code35- Leading `_` on public symbols36- Missing docs on exported API37- Explicit `= null` initialization38- `.length == 0` emptiness checks39- Bare catch swallowing errors40- `new` keyword / redundant `const`41- Import from package `src/`42- Missing return type on public function43- Mutable class with custom `==`44- Positional boolean parameters4546## Verification4748- `dart format --set-exit-if-changed .`49- `dart analyze` (project strictness)50- `dart test` for changed packages51- `dart doc` or doc coverage review52- Capsule checklist on public API535455## References5657- `awesome-guidelines/references/dart-style-learning-note.md`58- `awesome-guidelines/references/dart-style-formatting-names.md`59- `awesome-guidelines/references/dart-style-documentation.md`60- `awesome-guidelines/references/dart-style-usage-idioms.md`61- `awesome-guidelines/references/dart-style-design-api.md`
ryan-brosas