https://github.com/dart-lang/ai/issues/498
Add proactive Flutter hot reload rules (flutter-app-runtime.md and
flutter-app-runtime.mdc) to automate the hot reload and runtime error
verification loop when editing Dart and Flutter files.
Problem:
The sub-second Stateful Hot Reload cycle is the cornerstone of the
Flutter development experience. However, during AI-driven workflows:
- Out-of-Sync Execution: Agents modify source code on disk but fail to
update the active session, leaving the simulator/device screen stale.
- Friction in Context Switching: Users must exit the chat interface to
manually initiate a reload via the CLI ('r') or IDE tooling.
- Latent Feedback on Regressions: Build failures and layout issues
(e.g., RenderFlex overflows) are only revealed after manual
intervention, leading to fragmented multi-turn debugging sessions.
Part of https://github.com/dart-lang/ai/issues/498
It is not clear to me exactly which all agents support rules, but AGY does, and this rule has only been tested in AGY. Cursor supports it but seems to want a slightly different format, (`.mdc`).
Should we create separate directories for some of the other agents? I think cursor does support pointing to any directory for the rules in its plugin configuration.
Jaime Wren