chunkytofustudios

Run, debug, screenshot, and interact with a Flutter app on an Android emulator. Gives the agent eyes (screenshots, accessibility tree) and hands (tap, hold, swipe, multi-touch pinch).

4 skills

Polish Flutter app UI screens for visual hierarchy, readability, and section clarity. First reads a representative reference screen (the home page or a polished page the user points at) to lock in the app's existing design tone, then drives the running app on the Android emulator via the `android-emulator` skill — screenshots, taps, swipes — to observe each target screen, makes targeted widget and `ThemeData` changes, and spawns an independent evaluator sub-agent to score the result on design quality, originality, craft, and functionality. Use this skill whenever the user wants to improve, polish, refine, critique, audit, or tighten the visual design of a Flutter screen — even when they don't say "polish" explicitly (e.g. "make this look better", "fix the layout on settings", "tighten up the home screen", "this screen feels off"). Stops and asks for a reference screen if the app's design tone can't be established with confidence.

4 skills

Preview a single Flutter widget in isolation using the built-in Flutter Widget Previewer (`flutter widget-preview`) — wires up a project-specific `previewWrapper` so the widget renders against the app's real theme and providers, launches the local preview server, and lets the agent take headless-Chrome screenshots of the live preview while a human follows along in their own browser. Use whenever the user wants to design, iterate on, dogfood, share, audit, or sanity-check a standalone Flutter widget — even when they don't say "previewer" (e.g. "let me see the new button", "show me dark mode for this card", "throw this widget on a preview", "iterate on the empty state", "preview just the badge", "what does this look like at tablet width"). For full-screen design polish on a running app, use `design-polish` + `android-emulator` instead. Skips: non-Flutter UIs, full-app QA flows, projects on Flutter < 3.35.

4 skills

De-obfuscate (symbolize) an Android crash or ANR stacktrace exported from the Google Play Console for a Flutter app whose release build came from Codemagic CI/CD — fetches the matching `android_native_debug_symbols.zip` and `<AppName>_<N>_artifacts.zip` from Codemagic, then resolves every `pc 0x…` native frame and obfuscated Flutter frame to file:line via `llvm-addr2line`. Use whenever the user has a stacktrace (.txt/.log/pasted text) and wants to know which line of code crashed, even if they don't say "symbolize" — e.g. "what's causing this ANR?", "debug this Play Console crash", "translate this stack", "resolve these pc 0x… frames", "Codemagic build N crashed, here's the trace". Skips: iOS/dSYM symbolication, non-Codemagic builds (no symbol upload step), Crashlytics-only Dart exceptions with no native or Flutter frames.

4 skills