Flutter Design System Enforcement
Priority: P0 (CRITICAL)
Zero tolerance for hardcoded design values.
Phase 0: Context Discovery (MANDATORY)
Before any UI refactoring, you MUST identify the project's Theme Archetype:
- Check
main.dart: Look forMaterialApptheme configuration. - Determine Pattern:
- Theme-Driven (Adaptive): If you see
VThemeData(...).toThemeData()or extensiveThemeDataoverrides, you MUST useTheme.of(context).textThemeortheme.textThemefor feature code. - Token-Driven (Static): Only use static tokens (
VTypography.*) if there is no global theme bridge or if you are defining the theme itself.
- Theme-Driven (Adaptive): If you see
Guidelines
- Colors: Use tokens (
VColors.*,AppColors.*), neverColor(0xFF...)orColors.red. - Spacing: Use tokens (
VSpacing.*), never magic numbers like16or24. - Typography: Prioritize
theme.textTheme.*for adaptive UI. UseVTypography.*tokens only for theme definitions or non-contextual logic. Never use inlineTextStyle. - Borders: Use tokens (
VBorders.*), never rawBorderRadius. - Components: Use DLS widgets (
VButton) over raw Material widgets (ElevatedButton) if available.
Anti-Patterns
- No Hex Colors:
Color(0xFF...)is strictly forbidden. - No Color Enums:
Colors.blueis forbidden in UI code. - No Magic Spacing:
SizedBox(height: 10)is forbidden. - No Inline Styles:
TextStyle(fontSize: 14)is forbidden. - No Raw Widgets: Don't use
ElevatedButtonwhenVButtonexists.
Related Topics
mobile-ux-core | flutter/widgets | idiomatic-flutter