Build composable interfaces
Create focused widgets, adaptive layouts, themes, forms, navigation, empty and error states, and accessible interaction.
Codex Skills for Flutter give Codex focused instructions for building responsive widget trees, structuring app state, integrating services, testing units and widgets, checking platform behavior, improving performance, and preparing releases. Download the skills for Flutter applications that must feel coherent across Android, iOS, web, and desktop targets.
task: complete cross-platform flutter development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffA dependable Flutter app needs clear state ownership, predictable navigation, adaptive layouts, accessible semantics, lifecycle-aware services, and tests at the right levels.
These skills help Codex work with the repository's chosen architecture rather than replacing it with a fashionable pattern.
Create focused widgets, adaptive layouts, themes, forms, navigation, empty and error states, and accessible interaction.
Follow existing state management, isolate business logic, manage async work and cancellation, and define repository and platform boundaries.
Work with plugins, permissions, storage, networking, deep links, notifications, and platform configuration carefully.
Write unit, widget, golden, and integration tests, profile performance, analyze builds, and verify target-specific packaging.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read pubspec, SDK constraints, targets, flavors, architecture, state management, routing, plugins, themes, and test setup.
Define events, state ownership, async boundaries, persistence, platform behavior, error states, and UI responsibilities.
Reuse design components, handle constraints and text scale, add semantics, and keep expensive work out of build methods.
Run analysis, unit and widget tests, key integration flows, performance checks, and platform builds in proportion to risk.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build Android and iOS experiences with permissions, lifecycle, navigation, input, platform services, and release configuration.
Handle responsive layouts, browser navigation, accessibility, loading, caching, deployment, and web-specific limitations.
Support keyboard and mouse, resizable windows, menus, files, desktop packaging, and platform conventions.
Design reusable Dart APIs, platform implementations, examples, compatibility, tests, and publication metadata.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable cross-platform flutter development work with a visible process.
Build features, debug widgets, manage state, integrate services, test behavior, and support target platforms.
Share one product codebase while preserving platform permissions, lifecycle, accessibility, and release needs.
Move from prototype to maintainable application structure, reliable data flow, testing, and store-ready builds.
Create reusable Dart packages and plugins with clear APIs, examples, tests, and supported platforms.
The skills assist Flutter development, but device-specific behavior, store requirements, signing, privacy declarations, native integrations, and production releases need testing and authorized human approval.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with architecture, widget, platform, testing, performance, and release guidance.
Use project scope for app architecture and versions, or personal scope for reusable Flutter practices.
State Flutter and Dart versions, targets, flavors, state management, routing, plugins, backend environments, and design system.
List supported devices, accessibility requirements, test commands, build commands, signing boundaries, and store constraints.
Practical answers about capabilities, limits, setup, and review.
Yes. They can work with both targets while accounting for permissions, configuration, plugins, lifecycle, signing boundaries, and platform behavior.
Yes. They inspect and preserve the architecture already chosen unless you explicitly request a migration.
Yes. The workflow uses unit tests for logic, widget tests for UI behavior, and integration tests for important complete flows.
They can inspect rebuilds, layout and paint work, lists, images, async work, memory, and profile evidence before optimizing.
Yes, when those targets are configured. The workflow checks their distinct navigation, input, layout, packaging, and platform limitations.
Clear context. Purposeful work. Relevant checks. A result others can understand.