Agent-skills-standard flutter-layer-based-clean-architecture

Enforce inward dependency flow, pure domain layers, and DTO-to-entity mapping in Flutter DDD architecture. Use when structuring lib/domain/, lib/infrastructure/, lib/application/, or lib/presentation/ layers, defining repository interfaces, or wiring BLoCs with get_it. (triggers: lib/domain/**, lib/infrastructure/**, lib/application/**, dto, mapper, Either, Failure)

install

source · Clone the upstream repo

git clone https://github.com/HoangNguyen0403/agent-skills-standard

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/flutter/flutter-layer-based-clean-architecture" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-flutter-layer-based-clean-architecture && rm -rf "$T"

manifest: skills/flutter/flutter-layer-based-clean-architecture/SKILL.md

source content

Layer-Based Clean Architecture

Priority: P0 (CRITICAL)

Workflow: Add New Feature Across Layers

Define domain entity with
```
@freezed
```
in
```
lib/domain/entities/
```
Define repository interface in
```
lib/domain/repositories/
```

Create DTO in

lib/infrastructure/dtos/

with

fromJson

toEntity

mapper

Implement repository in
```
lib/infrastructure/repositories/
```
Wire BLoC/Cubit in
```
lib/application/
```
consuming repository interface
Register bindings in
```
get_it
```
injection container
Build screen in
```
lib/presentation/
```
using
```
BlocBuilder
```

Structure

lib/
├── domain/ # Pure Dart: entities (@freezed), failures, repository interfaces
├── infrastructure/ # Implementation: DTOs, data sources, mappers, repo impls
├── application/ # Orchestration: BLoCs / Cubits
└── presentation/ # UI: Screens, reusable components

Implementation Guidelines

Dependency Flow:

Presentation -> Application -> Domain <- Infrastructure

. Dependencies point inward.

Pure Domain: No Flutter (Material/Store) or Infrastructure (Dio/Hive) dependencies in
```
Domain
```
.
Functional Error Handling: Repositories must return
```
Either<Failure, Success>
```
.
Always Map: Infrastructure must map DTOs to Domain Entities; not leak DTOs to UI.

See DTO-to-Entity mapping example.

Immutability: Use
```
@freezed
```
for all entities and failures.
Logic Placement: No business logic in UI; widgets only display state and emit events.
Inversion of Control: Use
```
get_it
```
to inject repository implementations into BLoCs.

Anti-Patterns

No DTOs in UI: Never import
```
.g.dart
```
or Data class directly in Widget.
No Material in Domain: not import
```
package:flutter/material.dart
```
in
```
domain
```
layer.
No Shared Prefs in Repo: not use
```
shared_preferences
```
directly in Repository; use Data Source.

Reference & Examples

For full implementation templates and DTO-to-Domain mapping examples: See references/REFERENCE.md.

References

feature-based-clean-architecture | bloc-state-management | dependency-injection | error-handling