Flutter Layer Based Clean ArchitectureSAFE

A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: flutter-layer-based-clean-architecture
description: Enforce inward dependency flow, pure domain layers, and DTO-to-entity mapping in Flutter DDD architecture. Use when structuring layers or boundaries; defer navigation-only routing and feature implementation such as notifications.
metadata:
  triggers:
    files:
    - 'lib/domain/**'
    - 'lib/infrastructure/**'
    - 'lib/application/**'
    keywords:
    - dto
    - mapper
    - Either
    - Failure
---
# Layer-Based Clean Architecture

## **Priority: P0 (CRITICAL)**


## Workflow: Add New Feature Across Layers

1. Define domain entity with `@freezed` in `lib/domain/entities/`
2. Define repository interface in `lib/domain/repositories/`
3. Create DTO in `lib/infrastructure/dtos/` with `fromJson`/`toEntity` mapper
4. Implement repository in `lib/infrastructure/repositories/`
5. Wire BLoC/Cubit in `lib/application/` consuming repository interface
6. Register bindings in `get_it` injection container
7. Build screen in `lib/presentation/` using `BlocBuilder`

## Structure

```text
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](references/REFERENCE.md).

- **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/REFERENCE.md).

## References

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

## Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- Flutter

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.