What problem does it solve? Flutter apps often crash silently at cold start, flash the wrong theme on the first frame, block the UI with slow warm-up work, or hide real errors behind zones and retry loops. This Skill enforces a fixed, ordered main() launch sequence so failures surface loudly and the first frame paints correctly. ## Core Features & Use Cases - Ordered launch sequence: Installs a crash-log sink plus FlutterError.onError and PlatformDispatcher.onError before any code that can throw, with exactly two handlers and no runZonedGuarded. - Composition-root DI: Builds real infrastructure (database, settings, notifications) in a bootstrap() function and injects it via ProviderScope overrideWithValue over throwing placeholder providers, so forgotten wiring fails loudly. - First-frame correctness: Reads theme, locale, and settings before runApp, defers warm-up to addPostFrameCallback, and flushes durable state on background via a single WidgetsBindingObserver. - Use Case: When editing lib/main.dart or bootstrap.dart in a Flutter app, apply this Skill to reorder startup code so a database migration never leaves the user staring at a blank window and a crash on frame one is always recorded. ## Quick Start Review my lib/main.dart and bootstrap.dart and reorder the startup sequence so error handlers install first, settings load before runApp, and warm-up is deferred past the first frame.