What problem does it solve? Flutter teams struggle to keep architecture, state management, error handling, and testing consistent across a codebase, and developers often do not know which convention applies to a given task. This Skill acts as the front door for a Flutter/Dart app: it states the non-negotiable house rules every task obeys, then routes each concern to the correct deep-dive skill. ## Core Features & Use Cases - Cross-cutting house rules: Fourteen non-negotiable rules covering feature-first layered MVVM, dumb widgets, Riverpod 3.x as state plus DI, a single write path through repositories, typed Result/Failure errors, injected side effects, and strict lint gates. - Routing table: Maps every task type (architecture, state, widgets, persistence, testing, i18n, release) to the specialized skill that governs it. - Feature build order: A recommended nine-step sequence from pure model to release, with a canonical Repository/Notifier/View code shape and a definition-of-done checklist. - Use Case: Before writing a new feature, a developer consults this Skill to confirm which layer the code belongs in, which skill to open for depth, and which checklist items must pass before the PR. ## Quick Start Ask the AI to review your planned Flutter feature against the house rules and tell you which specialized convention skills to consult before writing code.