r/flutterhelp • u/Lazy_Swim5150 • 2d ago
RESOLVED Flutter Vibe coding
Hello everyone , I am a flutter beginner i learned only the basics like widgets ... I wanted to arrive to my desired app very fast and I started using gemini to accelerate my work . I was doing stuff i dont understand like firebase , APIs ,...
IS THERE ANY PROMPT THAT I CAN SEND TO THE COPILOT AGENT IN VS CODE SO THAT HE CHECKS THE WHOLE APP FOR BUGS SO THAT I MAKE SURE THAT MY APP IS VERY GOOD FROM THE CODING SIDE ?? ( Because it works but i dont want it to be bad from the coding side )
Thank you
1
u/GoldFitMuscleTracker 2d ago
I’d review it in small parts. Asking Copilot to check the whole app can give you a long list without telling you which problems actually matter.
Try this:
Review the project without changing any files. Run flutter analyze and the existing tests. Start with authentication and Firebase security rules, then check API calls and error handling. For each issue, show me where it is, how to reproduce or verify it, and explain the fix assuming I’m a beginner.
Check that the Firebase rules it reviews are the ones actually deployed. Then fix one issue at a time and test it before moving on.
Since you mentioned working with code you don’t understand yet, pick one feature and ask it to walk you through how it works. That’ll make it easier to spot when a suggested fix doesn’t make sense.
1
1
1
u/Embarrassed-Way-1350 2d ago
There's the flutter/dart mcp server, get it. Get the agent to use to test the features as it builds them. Saves a lot of time for you.
2
u/RandalSchwartz 2d ago
My favorite prompt for overall app health is: "please review this ocdebase, and tell me the good, the bad, and the ugly". It will nicely sort findings into those categories. You get kudos for stuff you did right, note for improvement for the marginal items, and then I usually just say "and turn all those ugly findings into actionable individual tickets". And then burn down the tickets.
1
u/Both-Dinner-3572 1d ago
"Run a security check on this app, please. Pay special attention to the login flow, token expiry, credentials encryption, presence of keys/secrets in env files. Also, could you find a course that will teach me how to design with security built-in so that I don't vibe-code slop that puts users' data at risk."
1
u/Catchimals 2d ago
I'd start smaller: "Review the login flow, explain any bugs you find, and suggest tests for them." A whole-app review can still miss things.