flutter-smell-build-side-effects

What problem does it solve?

Flutter UI builds often trigger IO, network, telemetry, or side effects during widget lifecycles such as build or didChangeDependencies, leading to fragility and hard-to-test code. This skill enforces guardrails to ensure side effects are controlled and initiated by a controller, not directly from UI widgets.

Core Features & Use Cases

• Controller-driven side effects: Any IO or asynchronous work is initiated by a centralized controller during initialization or explicit actions.
• Guarded init: Prevents side-effectful work from executing multiple times or during widget lifecycle transitions.
• Guidance and best practices: Provides patterns to keep widgets pure and testable.

Quick Start

Create a dedicated controller to initialize and mediate all side-effectful work, keeping widgets pure.