Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
madteacher avatar

Flutter Networking

  • 664 installs
  • 105 repo stars
  • Updated May 1, 2026
  • madteacher/mad-agents-skills

flutter-networking is a Claude Code skill that adds timeout-protected HTTP client code with JSON decoding to Flutter apps for developers who need a reusable ApiService wrapper around package:http.

About

flutter-networking is a mad-agents-skills recipe for building robust HTTP networking in Flutter using dart:async, dart:convert, and package:http. It provides an ApiService class with configurable baseUrl, injectable http.Client, default 15-second timeout, optional HeadersProvider for auth tokens, and generic JsonDecoder typing for typed JSON responses. Developers reach for flutter-networking when wiring mobile or agent-based Flutter apps to REST backends without reinventing timeout, header, and client lifecycle handling. The pattern supports owned vs injected clients for testability.

  • Generic JSON GET/POST/PUT methods with automatic decoding
  • Configurable 15-second request timeout
  • Optional dynamic headers provider for auth tokens
  • Automatic client lifecycle management with ownership flag
  • Reusable ApiService class for Flutter networking layer

Flutter Networking by the numbers

  • 664 all-time installs (skills.sh)
  • Ranked #542 of 4,353 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 25, 2026 (Skillselion catalog sync)
npx skills add https://github.com/madteacher/mad-agents-skills --skill flutter-networking

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs664
repo stars105
Security audit2 / 3 scanners passed
Last updatedMay 1, 2026
Repositorymadteacher/mad-agents-skills

How do you add timeout-safe HTTP networking in Flutter?

Add robust, timeout-protected HTTP client capabilities with JSON decoding to their Flutter mobile or agent-based applications.

Who is it for?

Flutter developers integrating REST APIs who want a production-minded http.Client wrapper with timeouts and typed JSON decoding.

Skip if: Projects already standardized on Dio, Chopper, or graphql_flutter with established networking layers.

When should I use this skill?

The user needs HTTP client setup, API service code, JSON decoding, or timeout handling in a Flutter mobile or agent app.

What you get

A reusable ApiService Dart class with base URL, timeout, headers provider, and JsonDecoder-typed response parsing.

  • ApiService Dart class
  • typed JSON decoder methods

By the numbers

  • Default HTTP timeout of 15 seconds

Files

SKILL.mdMarkdownGitHub ↗

Flutter Networking

You are a networking agent for Flutter apps. Turn existing project facts into concrete API calls, clients, services, repositories, error handling, auth flows, and validation steps. Do not treat this skill as a tutorial: inspect, adapt, implement or review, and verify.

Core Contract

1. Confirm the target is a Flutter or Dart package by inspecting pubspec.yaml, lib/, and existing networking, architecture, state-management, DI, auth, persistence, and test conventions. 2. Preserve the project's current client stack unless there is no networking stack yet or the user explicitly asks to migrate. Adapt this skill's http examples to existing Dio, Retrofit, Chopper, generated clients, or custom wrappers instead of adding a parallel client. 3. For implementation tasks, prefer small injectable clients/services with typed decode functions, clear timeouts, explicit status handling, cancellable or disposable resources where available, and testable boundaries. 4. For review and debugging tasks, report broken status handling, leaked clients or subscriptions, unsafe token storage, missing timeouts, generic exceptions, UI-thread parsing of large responses, duplicate in-flight requests, and missing tests before broad style advice. 5. Keep UI networking thin. Widgets may trigger commands or observe state, but services own endpoint calls, repositories own data policies, and state objects/ViewModels own UI state transitions. 6. Validate with the repo's normal commands. Prefer flutter analyze, focused flutter test, and template-only dart format --output=none --set-exit-if-changed checks for copied Dart assets. Explain skipped checks.

Clarification Rules

Ask the user only when a high-impact decision cannot be inferred from the project:

  • API contract, endpoint base URL, auth mechanism, or token lifecycle is absent;
  • realtime behavior needs product semantics such as reconnect policy, ordering,

delivery guarantees, or offline behavior;

  • cache freshness, optimistic updates, pagination, or retry policy would change

user-visible data correctness;

  • the project already has multiple networking stacks and the intended target is

ambiguous.

If the project is unavailable or is not a Flutter project, give an implementation plan or review based on the provided context, do not invent repository facts, and state that code validation could not be performed.

Resource Routing

Read only the references and assets needed for the current task:

NeedReadUse for
Basic HTTP CRUD or JSON modelshttp-basics.mdGET/POST/PUT/DELETE, query parameters, typed parsing, FutureBuilder examples
Auth headers, token storage, login, refresh, OAuthauthentication.mdBearer/basic/API key auth, secure token handling, refresh flow, auth retry
Status codes, exceptions, timeouts, retries, UI errorserror-handling.mdAPI exception model, timeout/connection handling, retry policy, user-facing errors
Large JSON, caching, pagination, dedupe, timingperformance.mdcompute(), cache TTLs, request deduplication, pagination, instrumentation
WebSocket connection, JSON messages, reconnect, authwebsockets.mdChannels, stream subscriptions, connection status, reconnection, secure sockets
Reusable HTTP service templatehttp_service.dartCopy only after adapting base URL, decode functions, timeout, auth, and DI fit
Repository/cache templaterepository_template.dartCopy only when the app lacks an equivalent repository/cache boundary
Standalone examplesexamplesUse as illustrative snippets, then adapt imports, state management, disposal, and errors

Every copied asset must be adapted to the target app's package name, lints, client stack, state-management style, and architecture before validation.

Networking Defaults

  • Use http: ^1.6.0 and web_socket_channel: ^3.0.3 only for new simple

clients. For existing Dio, Retrofit, Chopper, or generated clients, follow the established stack.

  • Inject clients instead of constructing them deep inside services. Close owned

http.Client, WebSocket channels, stream subscriptions, timers, and text controllers.

  • Treat 200..299 as success only when the endpoint contract allows it. Handle

204 as empty and model methods as nullable or void instead of using unsafe casts.

  • Decode JSON into typed models at service/repository boundaries. Use

background isolates for large responses, but avoid isolate overhead for small payloads.

  • Add request timeouts and retry only transient failures. Do not retry unsafe

mutations unless the API is idempotent or the user confirms the product policy.

  • Store sensitive tokens with flutter_secure_storage: ^10.0.0 or the app's

existing secure storage. Do not store access tokens in source code, shared_preferences, logs, or crash reports.

  • Use wss:// for WebSockets. Custom WebSocket headers via

IOWebSocketChannel are IO-only; provide a browser-compatible alternative for Flutter web.

  • Do not manually set Accept-Encoding as a default with package:http; let the

platform/client negotiate compression unless the project has a measured need.

Validation

Before finishing an implementation or review:

1. Check that endpoint calls are behind testable services or repositories and that UI code does not own raw HTTP/WebSocket details. 2. Check that every request has status handling, timeout/error handling, and typed parsing or an explicitly raw response contract. 3. Check that auth secrets are stored and refreshed according to the app's existing secure storage and lifecycle rules. 4. Check that clients, channels, subscriptions, controllers, and timers are disposed when owned by the code being changed. 5. Run the closest available validation:

  • flutter analyze
  • focused flutter test suites for changed network/auth/repository code
  • dart format --output=none --set-exit-if-changed for copied Dart assets
  • this skill's scripts/verify-examples.sh when changing bundled examples or

templates 6. Report commands run, failures, skipped checks, and residual networking risks.

Related skills

FAQ

What HTTP package does flutter-networking use?

flutter-networking builds on package:http with dart:async and dart:convert. The ApiService class wraps http.Client with a configurable base URL, default 15-second timeout, and optional HeadersProvider for dynamic headers.

Does flutter-networking support typed JSON responses?

Yes. flutter-networking defines a JsonDecoder typedef so each endpoint method can parse responses into typed Dart models. HeadersProvider enables async auth token injection before requests fire.

Is Flutter Networking safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Backend & APIsintegrationsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.