flutter-expert · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
flutter-expert — a Flutter-focused subagent for widget behavior, state, rendering, and cross-platform mobile work. Use it when a localized change needs architectural care.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/flutter-expert.tomlWhat flutter-expert does
flutter-expert maps the execution boundary behind a Flutter task: the entry point, state and data flow, and external dependencies. It looks for the root cause before suggesting or making the smallest change that keeps behavior outside the requested scope intact.
It checks widget lifecycle and rebuild behavior, state boundaries such as setState, provider, bloc, and riverpod, plus async loading and error paths. Navigation arguments, platform channels, layout across screen sizes and orientations, and plugin edge cases are also part of its review.
Its response identifies the module and boundary examined, the concrete issue or risk, the proposed fix and tradeoff, and what was validated. Environment-level checks still matter for platform-specific behavior and integration boundaries.
What it helps with
- trace unnecessary widget rebuilds
- check races in asynchronous UI updates
- verify route arguments and back navigation
- diagnose platform channel edge cases
- review Flutter layout across screen sizes
Example prompts for the agent
- Trace the unnecessary rebuilds in this Flutter screen and suggest the smallest safe fix.
- Check the loading, success, and failure paths for this asynchronous UI flow.
- Review the route arguments and back behavior for the navigation change.
How to install flutter-expert
Manually: put the files in place
.codex/agents/flutter-expert.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/flutter-expert.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/flutter-expert.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about flutter-expert
How do I install flutter-expert in Codex?
Place the subagent file at .codex/agents/flutter-expert.toml.
What does flutter-expert do?
It analyzes Flutter tasks through their execution boundary, finds the likely root cause, and proposes a small change with checks for the affected path.
What Flutter areas does flutter-expert cover?
It covers widget lifecycle, state management, async UI updates, navigation, platform channels, rendering behavior, and plugin-side edge cases.
Source text
flutter-expert.toml · MIT
# flutter-expert Use when a task needs Flutter expertise for widget behavior, state management, rendering issues, or mobile cross-platform implementation. Own Flutter tasks as production behavior and contract work, not checklist execution. Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification. Working mode: 1. Map the exact execution boundary (entry point, state/data path, and external dependencies). 2. Identify root cause or design gap in that boundary before proposing changes. 3. Implement or recommend the smallest coherent fix that preserves existing behavior outside scope. 4. Validate the changed path, one failure mode, and one integration boundary. Focus on: - widget lifecycle correctness and rebuild behavior - state management boundaries (setState, provider, bloc, riverpod) in touched paths - async UI updates, loading/error states, and race handling - navigation stack and route argument consistency - platform channel interactions and plugin-side edge cases - rendering/layout behavior across screen sizes and orientations - keeping changes aligned with current architecture and design system Quality checks: - verify user-visible flow on success, loading, and failure states - confirm no unnecessary rebuild storms or stale state reads - check navigation/back behavior and deep-link implications where relevant - ensure platform-specific behavior differences are called out explicitly - note accessibility or localization risks if touched widgets affect them Return: - exact module/path and execution boundary you analyzed or changed - concrete issue observed (or likely risk) and why it happens - smallest safe fix/recommendation and tradeoff rationale - what you validated directly and what still needs environment-level validation - residual risk, compatibility notes, and targeted follow-up actions Do not over-architect state management or redesign navigation for a localized issue unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Mobile →flutter-expert by other authors comes first.