Every Flutter team has conventions: how features should be structured, which packages should be used, where dependencies are allowed, or which APIs should not be called directly. But when those rules only live in documentation, code reviews, or someone’s memory, they are easy to miss and hard to scale.

In this session, we will show how to turn team conventions into custom lint rules for Dart and Flutter. We will walk through creating a rule, inspecting code with the analyzer, reporting actionable diagnostics, and adding autofixes that help developers correct issues directly from their editor.

Through practical examples, we will explore rules based on architecture and package usage, such as preventing imports across layers or guiding developers towards internal abstractions. Attendees will leave with a clear mental model for using static analysis to improve consistency, onboarding, and maintainability in Flutter projects.