flutter-widget

To prevent design system drift in Flutter widgets, reuse existing repository theme tokens, spacing, typography, and localization helpers. This ensures UI consistency and keeps components theme-aware as the application scales.

Keep business logic out of Flutter UI widgets by avoiding networking, persistence, and heavy transformations inside them. Limit StatefulWidget usage strictly to local mutable UI state to maintain a clean separation of concerns.

The best way to refactor Flutter widgets for composition is to prefer small, composable widgets that remain theme-aware. Use a refactoring checklist to restructure layout behavior and validate correctness, accessibility, and text-scaling.

Validate accessibility and text-scaling behavior in Flutter components by applying repository patterns for tokens and localization. Review widgets to ensure they handle loading, empty, and error UI states while remaining fully accessible.

Yes, this guidance works for reviewing existing Flutter UI code. It provides a practical checklist to evaluate layout behavior, design-system alignment, and maintainability when restructuring or reviewing an existing widget.

Avoid using StatefulWidget in Flutter UI development when dealing with networking, persistence, or business logic. Restrict its use strictly to managing local mutable UI state to prevent accidental UI-layer coupling.