Add flutter-app-runtime rule for proactive hot reload - #220
Conversation
jwren
changed the title
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request replaces the old hot reload rules with new proactive Flutter hot reload rules in rules/flutter-app-runtime.md and rules/flutter-app-runtime.mdc. The feedback suggests retaining the trigger: glob field in the frontmatter of the new rule file, and points out that the referenced flutter-app-runtime skill needs to be defined in resources/flutter_skills.yaml to ensure it can be resolved properly.
| --- | ||
| description: Proactively connect to running Dart/Flutter apps and trigger hot reload using the flutter-app-runtime skill workflows upon editing .dart files. | ||
| globs: "**/*.dart" | ||
| --- |
There was a problem hiding this comment.
The previous rule file rules/hot_reload.md included trigger: glob in its frontmatter. If the rule parser requires this field to trigger the rule on glob matches, it should be retained in the new rules/flutter-app-runtime.md file.
| --- | |
| description: Proactively connect to running Dart/Flutter apps and trigger hot reload using the flutter-app-runtime skill workflows upon editing .dart files. | |
| globs: "**/*.dart" | |
| --- | |
| --- | |
| trigger: glob | |
| description: Proactively connect to running Dart/Flutter apps and trigger hot reload using the flutter-app-runtime skill workflows upon editing .dart files. | |
| globs: "**/*.dart" | |
| --- |
| Whenever you edit or modify any `.dart` file in this project, adhere to the runtime management procedures in the `flutter-app-runtime` skill: | ||
|
|
||
| 1. **Refer to Skill**: | ||
| - Activate and follow the `flutter-app-runtime` skill workflows for Dart Tooling Daemon (`dtd`), hot reloading, hot restarting, and runtime error inspection. |
There was a problem hiding this comment.
The rule references the flutter-app-runtime skill, but this skill is currently not defined in resources/flutter_skills.yaml. Please make sure to define the flutter-app-runtime skill in resources/flutter_skills.yaml so that the skill can be generated and successfully resolved by the agent.
| Whenever you edit or modify any `.dart` file in this project, adhere to the runtime management procedures in the `flutter-app-runtime` skill: | ||
|
|
||
| 1. **Refer to Skill**: | ||
| - Activate and follow the `flutter-app-runtime` skill workflows for Dart Tooling Daemon (`dtd`), hot reloading, hot restarting, and runtime error inspection. |
There was a problem hiding this comment.
The rule references the flutter-app-runtime skill, but this skill is currently not defined in resources/flutter_skills.yaml. Please make sure to define the flutter-app-runtime skill in resources/flutter_skills.yaml so that the skill can be generated and successfully resolved by the agent.
There was a problem hiding this comment.
Same as above, will be added
|
|
||
| 3. **Trigger Hot Reload / Hot Restart**: | ||
| - Execute `hot_reload` immediately after making changes to UI widgets or simple methods. | ||
| - Execute `hot_restart` if fundamental logic, state initialization, or `main()` was modified. |
There was a problem hiding this comment.
not just state initialization, but also any stateful widgets or logic affecting variables that stateful widgets use
| @@ -0,0 +1,25 @@ | |||
| --- | |||
| description: Proactively connect to running Dart/Flutter apps and trigger hot reload using the flutter-app-runtime skill workflows upon editing .dart files. | |||
There was a problem hiding this comment.
hot reload or hot restart
dart-lang/ai#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.
77e2dea to
db5ff55
Compare
| 4. **Verify Runtime Stability**: | ||
| - Run `get_runtime_errors` via `dart-mcp-server` to confirm that the hot reload/restart did not introduce new exceptions. |
There was a problem hiding this comment.
This should not be part of this rule IMO. This is expensive to run after each hot reload / hot restart and is a bit of scope creep. Debugging runtime errors is a separate user journey.
2 participants
dart-lang/ai#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: