Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

flutter-app-engineering

/flutter-app-engineering

Buduje, przegląda i ulepsza aplikacje Flutter: stan, nawigację, sesje, integrację natywną i niezawodność wydań.

Licencja
MIT
Ostatnia zmiana repozytorium
30.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
11
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Buduje, przegląda i ulepsza aplikacje Flutter: stan, nawigację, sesje, integrację natywną i niezawodność wydań.

Oryginalny opis (EN)

Build, review, debug, or improve Flutter applications, including Dart implementation, state and widget lifecycles, API efficiency, navigation, secure sessions, smooth UX, native integration, and release reliability. Use for meaningful Flutter app engineering; skip standalone Dart backend/CLI work, unrelated frameworks, and trivial copy edits.

Jak działa

  1. Establish the app and workflow context
  2. Load only relevant detail
  3. Make the smallest sound change
  4. Verify and finish proportionately
Sekcje z nagłówków SKILL.md, w oryginale · 50 linii, 657 słów
Podgląd SKILL.md
---
name: flutter-app-engineering
description: Build, review, debug, or improve Flutter applications, including Dart implementation, state and widget lifecycles, API efficiency, navigation, secure sessions, smooth UX, native integration, and release reliability. Use for meaningful Flutter app engineering; skip standalone Dart backend/CLI work, unrelated frameworks, and trivial copy edits.
---

# Flutter App Engineering

Improve the requested user workflow and the engineering that supports it. Adapt to the product, supported platforms, existing architecture, and actual failure. Preserve sound conventions; explicit user requirements and repository instructions take precedence over generic recommendations.

## Establish the app and workflow context

Read applicable instructions and trace the affected screen/action through state, data access, backend, persistence, and native integration. Inspect the relevant entrypoint, widget/controller/provider ownership, router, clients, tests, and platform configuration. Determine:

- The task: feature, focused repair, duplicate requests, loading/navigation, security, offline/native lifecycle, review, or measured optimization.
- Flutter/Dart versions and pins, `pubspec.yaml` constraints, lockfile, analyzer rules, generated code and target platforms/flavors.
- Existing state management, dependency scopes, source of server data, storage, auth/session model, and API contracts.
- The affected cold/warm launch, route/tab transition, mutation, background/resume, notification, or restart sequence.
- Data sensitivity, account/tenant scope, freshness, replay/conflict requirements, supported devices, and evidence already available.

Bound investigation to the task. Read installed package APIs, matching Flutter/Dart docs, and relevant OS/plugin requirements before relying on changing behavior. Flutter's bundled Dart version and a standalone Dart installation may differ. Do not upgrade SDKs, change state libraries, add platforms, or restructure the whole app to fix a local problem.

## Load only relevant detail

| Task or decision | Reference |
| --- | --- |
| Dart implementation, widget/element lifecycle, package structure, state/dependency ownership | [Architecture and lifecycle](references/architecture-lifecycle.md) |
| Duplicate requests, client orchestration, mutations, caching, offline persistence/sync | [Data and offline behavior](references/data-offline.md) |
| Routing, auth restoration, deep links, account/tenant transitions, client security | [Navigation and security](references/navigation-security.md) |
| Loading/recovery, forms/lists, adaptive layout, accessibility and localization | [UX and accessibility](references/ux-accessibility.md) |
| Jank, startup, rendering, images, memory, isolates and profiling | [Performance](references/performance.md) |
| Android/iOS lifecycle, permissions, push, real-time and background execution | [Platforms and events](references/platforms-events.md) |
| Diagnostics, focused tests, native/build compatibility and release operations | [Verification and release](references/verification-release.md) |
| Versions, official upstream skills/tooling and authoritative research | [Source and tooling register](references/sources.md) |

Use installed compatible Flutter/Dart/package skills for a genuinely matching specialized workflow, without duplicating their recipes or adopting their examples as universal architecture. Discover actual MCP capabilities when connected; otherwise use existing SDK, DevTools and project tools. Do not install optional plugins, modify agent configuration, or add test-driver hooks automatically.

This skill owns Flutter client behavior and native integration. API/backend/database specialist skills can help at their actual boundaries; none is required. UI permissions are usability measures: the backend must independently authorize sensitive data and operations.

## Make the smallest sound change

State the root problem or required invariant and selected approach before editing. Reuse existing widgets, state owners, HTTP clients, routing, storage, validation and observability. Separate substantial data/business work from rendering without imposing a universal folder tree or layer per simple operation.

For changed async work, identify who starts it, which input/identity it belongs to, how stale results are rejected, and who cancels/disposes resources. A rebuild is not a reason to fetch; mounted is not freshness; a timeout is not cancellation; background execution is not durable delivery.

Represent loading, refresh, empty, filtered-empty, denied, failed and uncertain-mutation states accurately. Preserve useful content and recoverable input. Avoid adding global caches, keep-alives, isolates, polling, shimmer, or a library migration merely to conceal incorrect ownership or state transitions.

## Verify and finish proportionately

Use existing focused checks for the changed behavior: formatting/analyzer, unit/widget tests, integration/device checks, or the relevant build. Choose realistic failure sequences from the actual flow rather than a universal suite. Documentation-only skill work needs normal validation, not an application fixture or agent evaluation campaign.

Claims about reduced requests need network/backend evidence and correct freshness/isolation. Claims about smoothness/performance need relevant interactions and representative profile/release conditions. State clearly when devices, platform toolchains or optional tools were unavailable.

Review the diff for compatibility, resource leaks, stale/private state, duplicate systems and unrelated changes. Report the resulting behavior, checks actually executed, observations, and material limitations; compilation alone does not establish a reliable mobile experience.
Pliki w paczce (11)
  • LICENSE 1 KB
  • SKILL.md 6 KB
  • agents/openai.yaml 1 KB
  • references/architecture-lifecycle.md 5 KB
  • references/data-offline.md 6 KB
  • references/navigation-security.md 5 KB
  • references/performance.md 4 KB
  • references/platforms-events.md 5 KB
  • references/sources.md 12 KB
  • references/ux-accessibility.md 5 KB
  • references/verification-release.md 6 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · lofingoindia/codex-engineering-skills100MIT
anandartin/celestial-skills100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki a018e75dc9d7 (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

  • 100dart-n-flutter
    Prowadzi pisanie kodu Dart i Flutter zgodnie z oficjalnymi zaleceniami dla plików .dart.
  • 95flutter-expertise
    Buduje i przegląda aplikacje Flutter: strukturę, zarządzanie stanem, nawigację, wydajność przebudowań, testy i wydania.
  • 100flutter-dart-code-review
    Przegląda kod Flutter i Dart według niezależnej od biblioteki listy kontrolnej: widgety, stan, wydajność i dostępność.
  • 100flutter-skill
    Automatyzuje i testuje aplikacje Flutter: uruchamia je, sprawdza drzewa widgetów, dotyka elementów, wpisuje tekst, przewija, robi zrzuty ekranu, waliduje stan i debuguje przez Dart VM Service Protocol.
  • 90mobile-flutter
    Pomaga pisać aplikacje Flutter i Dart: układy, formularze, routing go_router, HTTP, bazy lokalne i wtyczki.
  • 100flutter-test-strategy
    Pomaga zdecydować, co testować w kodzie Flutter i Dart na której warstwie (unit, widget, golden, integration) oraz ustawić progi pokrycia.

Uwagi i zgłoszenia

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