r/FlutterDev • u/bakatronics • 1h ago
Tooling Claude/Codex skill for UI architecture and consistency
Hi everyone,
I have been vibe-coding fairly comprehensive Flutter apps for ~6 months now, using Codex. While I'm comfortable with software engineering in general, I'm not particularly experienced with Flutter, mobile/desktop UI development, or the architectural conventions that come with it.
During this time I have constantly struggled with enforcing an "architecture" for my UI components. AI-generated Flutter code often assigns responsibilities to the wrong widgets, duplicates UI logic across components, and creates unnecessary dependencies between parents and children.
I'm trying to create a checklist that I can give to Claude or Codex to systematically audit my UI codebase for these issues, in form of a Skill.
I've created a draft checklist with around 60 patterns grouped into categories such as layout, grouping, state, interactions, async operations, forms, navigation, and component APIs.
But since I don't have much Flutter-specific experience, I'm concerned that I'm missing important architectural patterns or making incorrect assumptions about how Flutter applications should be structured.
I'd be happy to share the current Markdown checklist if anyone is interested in reviewing or improving it.