techmefr/mentis/flutter-four-async-states
Claude Code and agent skill by techmefr/mentis
- community
Checking that the SKILL.md file is still in the repository.
Use when a screen renders data from an async source: render all four states explicitly — loading, success, empty, error — never a blank screen, never stale content presented as fresh.
Install
npx vskill@latest install techmefr/mentis/flutter-four-async-statesSKILL.md
The same SKILL.md was published earlier as techmefr/mentis/flutter-four-async-states.
flutter-four-async-states
Narrow trigger extracted from skills/flutter-conventions §4.1–§4.2, so an async view routes here directly instead of only through the whole Flutter block.
When
Building or reviewing a screen or widget that renders data coming from an async source — a network call, a database query, a stream.
Steps
- An async view renders all four states explicitly: loading, success, empty, error. Never a
blank screen, never stale content presented as fresh.
- The four states belong to each data source, not to the screen. A screen with two independent
data sources needs four states tracked per source, not one set shared between them.
- Treat the non-success states as the normal experience of the screen, not an edge case — a mobile
network fails constantly (a lift, a tunnel, a handover between cells), so loading/empty/error show up routinely over a week of real use.
Output / checkpoint
Every screen consuming async data has an explicit branch (or widget) for each of loading, success, empty, and error — per data source when the screen has more than one — with nothing defaulting to a blank or stale view.
Guardrails
- A state holding an unresolved
FutureorStreaminstead of its result breaks this — see
skills/flutter-conventions §7.6 for why the result, not the future, belongs in state.
- The full section, including how a retriable error differs from a terminal one, lives in
skills/flutter-conventions §4 — read it before collapsing states for a screen that seems simple.
Origin
Extracted from skills/flutter-conventions §4.1-§4.2 (written 2026-09-09). Checked 2026-10-20 against the Flutter cookbook page on fetching data (its FutureBuilder branches on data, then error, and falls through to a spinner) and the FutureBuilder API page (connection states none, waiting, active, done; a completed future may carry data or an error). Those pages show loading, success and error; they do not show an empty state, and nothing read states that the four belong to each data source rather than to the screen, or that a mobile network fails routinely. Those two steps (2 and 3) stay our guidance, and so does the rule against a blank or stale screen. Site terms not read, facts only. 🟡: never run by us.
Independent verification 2026-10-21: 4 checked, 4 matched, 0 corrected, 0 unverified (fewer than eight checkable points in this block; all were checked).
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/flutter-four-async-states/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/techmefr/mentis/flutter-four-async-states)