What architecture does this skill follow?

The skill implements a clean 3-layer architecture consisting of Data (API/Repositories), Domain (Models/Interfaces), and Presentation (UI/State) layers to ensure separation of concerns.

How does it handle offline data?

It uses a cache-first repository pattern with Hive storage and includes an offline queue for synchronizing mutations when connectivity is restored.

Can I use this with Supabase or Firebase?

Yes, the repository and notification patterns are designed to be compatible with major backends like Supabase, Firebase, and standard REST APIs.

Which state management solution is prioritized?

The skill provides specific implementation patterns for Riverpod, including Provider, FutureProvider, and NotifierProvider examples.

Flutter Architecture Patterns

Name: Flutter Architecture Patterns
Author: antoineschaller

byantoineschaller

•

Mobile Development

Implements standardized 3-layer architecture, state management patterns, and offline-first strategies for Flutter applications.

About

This skill provides a comprehensive blueprint for building production-grade Flutter applications using a robust 3-layer architecture (Data, Domain, and Presentation). It includes pre-defined patterns for Riverpod state management, type-safe data modeling with Freezed, and professional repository structures. Beyond basic UI, it offers advanced implementations for offline-first synchronization using Hive and push notification integration with FCM, ensuring your mobile development follows industry best practices for scalability and maintainability.

Key Features

1 GitHub stars
Ready-to-use FCM push notification and local notification services
Comprehensive Riverpod provider patterns and organization
Clean 3-layer architecture scaffolding (Data, Domain, Presentation)
Type-safe data modeling and sealed classes using Freezed
Offline-first repository implementation with Hive storage

Use Cases

Bootstrapping a new production Flutter project with scalable architecture
Implementing complex offline data persistence and mutation queues
Standardizing state management and data flows across a development team

About

Key Features

1 GitHub stars
Ready-to-use FCM push notification and local notification services
Comprehensive Riverpod provider patterns and organization
Clean 3-layer architecture scaffolding (Data, Domain, Presentation)
Type-safe data modeling and sealed classes using Freezed
Offline-first repository implementation with Hive storage

Use Cases

Bootstrapping a new production Flutter project with scalable architecture
Implementing complex offline data persistence and mutation queues
Standardizing state management and data flows across a development team