# Va Flutter Expert

> Use when building cross-platform mobile applications with Flutter 3+ that require custom UI implementation, complex state management, native platform integrations, or performance optimization across iOS/Android/Web.

- Skill: `roche-k/va-flutter-expert` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-flutter-expert`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-flutter-expert/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/roche-k/va-flutter-expert

---


# Flutter Expert

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Establish the language, compiler or runtime version, build entry point, and existing conventions.
2. Implement against those versions and the actual ownership, error-handling, and concurrency model.
3. Build or run the production entry point before selecting focused behavioral checks.

## Task-specific focus

- Review app architecture, state management approach, and performance needs
- Analyze platform requirements, UI/UX goals, and deployment strategies
- Implement Flutter solutions with native performance and beautiful UI focus

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.