kb-flutter

What problem does it solve?

kb-flutter helps you avoid inconsistent Flutter architecture and brittle UI state handling by providing portable, opinionated guidance for layered structure, Provider-based state management, design token discipline, and the required 4-state screen checklist (loading, error, empty, data).

Core Features & Use Cases

• Layered architecture: Screens and widgets compose UI, Providers manage state, Services handle Firebase/API logic, and Models encapsulate data.
• Provider consumption rules: Choose the right mechanism (Consumer, Selector, context.read, context.watch) to control rebuild behavior and performance.
• Mobile-ready screen workflow: Enforces an order-of-creation process and guarantees every screen handles all four runtime states.
• Design tokens & flavor discipline: Centralizes theme tokens (colors/typography/spacing) and supports overrides per flavor/brand.
• Platform conventions: Provides iOS vs Android UX guidance to unify business logic while diverging in navigation, gestures, and modals.
• Firebase integration patterns: Keeps screens UI-only while providers consume services that wrap Firebase SDKs, including Auth/Firestore/Messaging/Storage.
• Localization: Uses ARB and flutter gen-l10n to prevent hardcoded user-visible strings.

Real-world example: You are adding a new “Orders” screen to a Flutter app backed by Firestore; use the skill’s checklist to create the model/service/provider/screen, implement the 4-state UI, wire it into GoRouter, and ensure all ARB strings and tokens are used consistently across flavors.

Quick Start

Use kb-flutter to design and implement a new Firebase-backed Flutter screen with Provider state, ARB localization, Material 3 tokens, and mandatory loading/error/empty/data rendering for a consistent mobile UX.