clean-architecture-flutter

What problem does it solve?

Flutter apps often struggle with inconsistent architecture as projects scale; this Skill defines a three-layer structure (presentation, domain, data) and strict rules to keep concerns separated, improving maintainability and testability.

Core Features & Use Cases

• Three-layer architecture: presentation → domain → data with clear directional dependencies.
• Layer rules: presentation imports domain; data imports domain; domain remains pure Dart/logic.
• Guided feature layout: per-feature folders with di, data, domain, and presentation modules; ensures consistent code organization across features.
• Use case guidance: when to introduce a use case, and how to structure repository interfaces and implementations.
• Mapper and repository contracts: demonstrates mapping DTOs to domain models and API/DAO integration.

Quick Start

Create a new feature folder with di/module, data/domain/presentation layers, and a sample use case to bootstrap development.