flutter-networking
/flutter-networking
Build or review Flutter remote data and transport boundaries across HTTP, GraphQL, WebSocket, SSE, or Socket.IO. Use for API contracts, authenticated request transport, pagination, retries, reconnection, caching, and error mapping; route sign-in and session semantics to flutter-authentication and local storage ownership to flutter-persistence.
- Author
- thienqo ↗
- Repository
- flutter-skills ↗
- Licence
- BSD-3-Clause
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
BSD-3-Clause, otwarta.
What it does and when to use it
Build or review Flutter remote data and transport boundaries across HTTP, GraphQL, WebSocket, SSE, or Socket.IO. Use for API contracts, authenticated request transport, pagination, retries, reconnection, caching, and error mapping; route sign-in and session semantics to flutter-authentication and local storage ownership to flutter-persistence.
Original author description
Build or review Flutter remote data and transport boundaries across HTTP, GraphQL, WebSocket, SSE, or Socket.IO. Use for API contracts, authenticated request transport, pagination, retries, reconnection, caching, and error mapping; route sign-in and session semantics to flutter-authentication and local storage ownership to flutter-persistence.
How it works
- Select the mode
- Inspect
- Rules
- Verification
- Sources
SKILL.md preview
--- name: flutter-networking description: Build or review Flutter remote data and transport boundaries across HTTP, GraphQL, WebSocket, SSE, or Socket.IO. Use for API contracts, authenticated request transport, pagination, retries, reconnection, caching, and error mapping; route sign-in and session semantics to flutter-authentication and local storage ownership to flutter-persistence. --- # Flutter Networking Keep transport concerns at the service boundary and expose domain-meaningful results to the rest of the app. ## Select the mode - Handle ordinary HTTP request-response work with the rules below. - For GraphQL operations, generated models, normalized caches, optimistic writes, or subscriptions, read [GraphQL clients](references/graphql.md). - For WebSocket, SSE, Socket.IO, connection recovery, or live event delivery, read [Realtime transports](references/realtime-transports.md). - For REST or HTTP response debugging, undocumented fields, decoding drift, or comparing Swagger/OpenAPI with deployed behavior, read [HTTP response evidence](references/http-response-evidence.md). - Read both references for GraphQL subscriptions. Route stream races or subscription leaks to `dart-concurrency`, durable offline queues to `flutter-persistence`, and terminated-app alerts to `flutter-notifications`. - Audio/video capture, media tracks, playback, and call sessions belong to `flutter-media`; keep text/data transport and upload behavior here. ## Inspect Read current client, generated API code, interceptors, model generation, authentication, environment configuration, and tests. Preserve `http`, Dio, generated clients, or another established choice when it meets the requirement. ## Rules - Centralize base URLs, headers, timeouts, and environment selection without committing secrets. - Decode untrusted responses and messages defensively and distinguish transport, protocol, decoding, authentication, and domain failures. - Map wire models to domain models at an explicit boundary. - Retry or reconnect only when the operation and protocol make recovery safe; bound backoff, queues, and cancellation. - Refresh credentials through one coordinated path to avoid request storms. - Define pagination identity, ordering, duplicate handling, terminal conditions, and refresh behavior. - Apply cache policy deliberately; do not silently return stale data as fresh. - Avoid logging tokens, personal data, or full sensitive payloads. - Keep documented schema, documentation examples, controlled fixtures, and observed server responses as separate evidence. Do not present one observed payload as the complete contract or a mock as proof of deployed behavior. ## Verification Use deterministic fake servers or mock transports to cover success, malformed data, timeouts, cancellation, unauthorized refresh, retry exhaustion, pagination boundaries, reconnect and resume behavior, and offline behavior. Run integration tests against a real service only when credentials and environment are explicitly in scope. Report the execution surface and data source separately. ## Sources - [Flutter networking](https://docs.flutter.dev/data-and-backend/networking) - [JSON serialization](https://docs.flutter.dev/data-and-backend/serialization/json)
Files in this package (4)
- SKILL.md 3 KB
- references/graphql.md 5 KB
- references/http-response-evidence.md 2 KB
- references/realtime-transports.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thienqo/flutter-skills | 100 | BSD-3-Clause |
| thiennc-tesoglobal/flutter-skills | 100 | BSD-3-Clause |
| madteacher/mad-agents-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version e242ff28047c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90flutter-core:flutter-data-networking
Master HTTP clients, REST APIs, GraphQL integration, WebSockets, and JSON serialization in Flutter applications. Use when implementing API calls, handling network requests, parsing JSON, or working with real-time data. - 90flutter-persistence
Design or review Flutter on-device persistence, caching, schema migrations, and offline synchronization. Use for preferences, files, local databases, cache lifecycle, or durable queues while preserving the existing package; route remote transport to flutter-networking and broad… - 90mobile-networking
Use this skill when the user asks about mobile networking, REST client, GraphQL, offline-first, API caching, retry, pagination, background sync, or API interceptors. - 100mobile-networking
Implements and reviews mobile API integration across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for HTTP clients, pagination, request cancellation, concurrent token refresh, resumable uploads and WebSocket lifecycle. Durable offline mutation queues belong… - 100flutter-openapi-client
Discover, inspect, generate, or update Flutter and Dart API clients from Swagger or OpenAPI contracts. Use when spec inventory, operation selection, client generation, or contract drift is the task; route ordinary HTTP behavior to flutter-networking and login or token lifecycle… - 90flutter-authentication
Implement, repair, or review Flutter user authentication and session lifecycle, including OAuth or OIDC redirects, PKCE, token refresh, logout, account switching, passkeys, and device re-authentication. Use when sign-in identity or session behavior is the task; route broad…