> flutter-feature-based-clean-architecture

Standards for organizing Flutter code by feature for scalability. Use when structuring a Flutter project with feature-based clean architecture. (triggers: lib/features/**, feature, domain, infrastructure, application, presentation, modular)

fetch
$curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/flutter-feature-based-clean-architecture?format=md"
SKILL.mdflutter-feature-based-clean-architecture

Feature-Based Clean Architecture

Priority: P0 (CRITICAL)

Standard for modular Clean Architecture organized by business features in lib/features/.

Structure

See references/folder-structure.md for the complete directory blueprint.

Implementation Guidelines

  • Feature Encapsulation: Keep logic, models, and UI internal to the feature directory.
  • Strict Layering: Maintain 3-layer separation (Domain/Data/Presentation) within each feature.
  • Dependency Rule: Presentation -> Domain <- Data. Domain must have zero external dependencies.
  • Cross-Feature Communication: Features only depend on the Domain layer of other features.
  • Flat features: Keep lib/features/ flat; avoid nested features.
  • No DTO Leakage: Never expose DTOs or Data Sources to UI or other features; return Domain Entities.
  • Shared logic: Move cross-cutting concerns to lib/shared/ or lib/core/.

Reference & Examples

For feature folder blueprints and cross-layer dependency templates: See references/REFERENCE.md.

Related Topics

layer-based-clean-architecture | retrofit-networking | go-router-navigation | bloc-state-management | dependency-injection

🚫 Anti-Patterns

  • Do NOT use standard patterns if specific project rules exist.
  • Do NOT ignore error handling or edge cases.

┌ stats

installs/wk0
░░░░░░░░░░
github stars341
██████████
first seenMar 17, 2026
└────────────

┌ repo

HoangNguyen0403/agent-skills-standard
by HoangNguyen0403
└────────────

┌ tags

└────────────