The flutter_lints package is a great way to balance recommended style vs. ease-of-use for new Dart and Flutter devs. But for advanced Flutter devs or devs build Dart or Flutter packages, I want a "strict" mode that cranks down the screws and helps me to write much better code.

Personally, I use the all_lint_rules_community package for this and it feels like unlocking the other half of the Dart compiler. It's kept up to date: as the Dash team adds new lints, they're automatically added and I automatically get better code. Frankly, it's amazing.

There are so many things that flutter_lints doesn't flag, like dynamic type usage, the lack of docs on public APIs for packages, unawaited async calls, etc. I wouldn't dream of building an without these lints in place, let alone a package that I expect other folks to use.

It makes sense that flutter_lints is not for that -- but there should be some curated set of lints for folks that really want to use Dart and Flutter like the pros do. Perhaps start with the Flutter team's analysis_options.yaml and build from there (and don't forget these)?

Thoughts? @mit-mit @devoncarew @pq