Przejdź do treści
Biblioteka skilli
Programowanie · Planowanie

flutter-clean-architect

/flutter-clean-architect

Projektuje, szkieletuje, refaktoryzuje i audytuje kod Flutter w Clean Architecture z warstwami domain, infrastructure i presentation, ręcznym Riverpod DI i kontraktami repozytoriów, bez warstwy usecase.

Repozytorium
skills ↗
Licencja
MPL-2.0
Ostatnia zmiana repozytorium
22.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
7
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MPL-2.0, otwarta.

Co robi i kiedy

Projektuje, szkieletuje, refaktoryzuje i audytuje kod Flutter w Clean Architecture z warstwami domain, infrastructure i presentation, ręcznym Riverpod DI i kontraktami repozytoriów, bez warstwy usecase.

Oryginalny opis (EN)

Design, scaffold, refactor, or audit Flutter code using a Clean Architecture aligned with this repository's real project style: `domain`, `infrastructure`, and `presentation` layers for modular features, manual Riverpod dependency injection, explicit datasource and repository contracts, optional local and remote repositories, Isar-friendly entities, and no `usecase` layer. Use when creating a new module, restructuring an existing feature, wiring datasources/repositories/providers, shaping shared services, or reviewing architectural boundaries in a Flutter codebase.

Jak działa

  1. Skill Profile
  2. Required Resource Map
  3. Operating Procedure
  4. Non-Negotiable Rules
  5. Output Expectations
Sekcje z nagłówków SKILL.md, w oryginale · 75 linii, 537 słów
Podgląd SKILL.md
---
name: flutter-clean-architect
description: >-
  Design, scaffold, refactor, or audit Flutter code using a Clean Architecture
  aligned with this repository's real project style: `domain`,
  `infrastructure`, and `presentation` layers for modular features, manual
  Riverpod dependency injection, explicit datasource and repository contracts,
  optional local and remote repositories, Isar-friendly entities, and no
  `usecase` layer. Use when creating a new module, restructuring an existing
  feature, wiring datasources/repositories/providers, shaping shared services,
  or reviewing architectural boundaries in a Flutter codebase.
---

# Flutter Clean Architecture Architect

Build production-oriented Flutter modules with explicit separation of concerns and predictable generation order.

## Skill Profile

- Preferred state management: manual Riverpod
- Preferred module root: `lib/modules/<feature_name>/`
- Preferred layers: `domain/`, `infrastructure/`, `presentation/`
- Preferred data flow: `ExternalService -> DataSource -> Repository -> Provider/Notifier`
- Preferred local storage strategy: offline-first with Isar-compatible entities when local persistence is needed
- Preferred repository style: thin repositories that delegate to datasources unless aggregation or orchestration is genuinely needed
- Preferred architecture variants:
  - modular feature architecture under `lib/modules/` for medium and large apps
  - simpler root-level `domain/`, `infrastructure/`, `presentation/` layout for smaller apps
- Preferred coding style: classes over helper methods, explicit mappers, explicit barrel files
- Preferred widget bias: `ConsumerWidget` by default; use `ConsumerStatefulWidget` only when controllers or lifecycle are required
- Language policy: write code, comments, and docs in English
- Skill version preserved from previous iteration: `2.1.0`

## Required Resource Map

Read these reference files before generating or refactoring code:

1. [`references/core/architecture.md`](references/core/architecture.md)
   Use for the creation order, folder structure, dependency chain, and canonical implementation patterns.
2. [`references/core/constraints.md`](references/core/constraints.md)
   Use for non-negotiable architectural rules, banned imports, layer boundaries, and widget selection guardrails.
3. [`references/core/data-schema.md`](references/core/data-schema.md)
   Use for the expected shape of entities, models, repositories, failures, notifiers, and provider chains.

Load these examples when the request matches their scenario:

- [`references/examples/products-module.md`](references/examples/products-module.md)
  Use for remote + local + offline-first module creation.
- [`references/examples/settings-module.md`](references/examples/settings-module.md)
  Use for local-only modules without API integration.

## Operating Procedure

1. Analyze the request.
   Determine whether the feature needs remote data, local persistence, or both.
2. Plan the module surface.
   List entities, abstract contracts, infrastructure implementations, providers, notifiers, screens, widgets, shared services, and barrel files.
3. Enforce architecture boundaries.
   Verify the plan against [`references/core/constraints.md`](references/core/constraints.md) before writing code.
4. Generate in strict layer order.
   Follow the creation order defined in [`references/core/architecture.md`](references/core/architecture.md). Do not jump directly to presentation.
5. Wire dependency injection explicitly.
   Use Riverpod providers to compose services, datasources, repositories, and presentation state.
6. Validate completeness.
   Ensure repository contracts, datasource contracts, repository implementations, providers, mappers, and per-layer barrel files are present when the feature actually needs them.

## Non-Negotiable Rules

- Keep `domain` independent from Flutter UI and transport concerns.
- Keep JSON and `Map<String, dynamic>` limited to models and external boundaries.
- Never return infrastructure models to the domain or presentation layers.
- Never skip mappers between model and entity representations.
- Never instantiate dependencies manually inside notifiers when they should come from `ref`.
- Never replace widget classes with private widget-returning helper methods when a dedicated widget class is clearer.
- Never force a module layout for a small project when a flatter root architecture is more aligned with the existing app.
- Never force a single repository to own both remote and local persistence when separate repositories or providers keep the design clearer.

## Output Expectations

When completing a feature request with this skill:

- Produce the module structure explicitly.
- Keep the dependency chain visible and traceable.
- Use naming suffixes consistently, such as `_entity.dart`, `_model.dart`, `_repository.dart`, `_repository_impl.dart`, `_provider.dart`, `_notifier.dart`.
- Preserve an offline-first strategy when both remote and local datasources exist, but keep local storage repositories/providers separable when the project does so.
- Prefer clean, typed, testable code over brevity.
Pliki w paczce (7)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • references/core/architecture.md 8 KB
  • references/core/constraints.md 2 KB
  • references/core/data-schema.md 3 KB
  • references/examples/products-module.md 4 KB
  • references/examples/settings-module.md 3 KB

Wersje

W bazie nie ma innych skilli o nazwie flutter-clean-architect.

Migawka bazy z 13.11.2026 · wersja paczki c0375a597a1f (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100flutter-feature-scaffold
    Dodaje nowe funkcje do aplikacji Flutter w układzie feature-first Clean Architecture (data, domain, presentation) z Riverpod 3 bez generowania kodu, z układem folderów, regułami warstw i skryptem szkieletu.
  • 100flutter-riverpod-expert
    Projektuje, implementuje, refaktoryzuje i recenzuje zarządzanie stanem Flutter z Riverpod według ręcznych wzorców: providery datasource i repozytoriów, stan i operacje, nasłuchiwanie auth, mosty GoRouter i rodziny providerów.
  • 100flutter-feature-based-clean-architecture
    Organizuje aplikacje Flutter w modułową architekturę clean opartą na funkcjach, z warstwami domain, data i presentation w katalogu lib/features.
  • 100flutter-architecture
    Projektuje, refaktoryzuje i recenzuje architekturę aplikacji Flutter: MVVM, warstwy UI, dane i opcjonalna domena, struktura feature-first, repozytoria, wstrzykiwanie zależności, wzorce Result i Command oraz offline-first.
  • 100flutter-architecture
    Podaje wzorce architektury aplikacji Flutter: struktura feature-first, clean architecture i zarządzanie stanem (Bloc, Riverpod, Provider), wstrzykiwanie zależności i dobór podejścia.
  • 100flutter-clean-arch
    Pomaga tworzyć i audytować warstwy funkcji lub pakietu Flutter: gdzie należy use case, repozytorium, datasource, encja lub model, czy domena może importować Flutter i czy zależności są odwrócone.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.