Follow these rules when working in this repository.
packages/devtools_shared: Never introduce a Flutter dependency or a dependency on web-only Dart libraries.- Imports: Never import
packages/devtools_app/lib/devtools_app.dartin code underpackages/devtools_app/lib/src/. It is acceptable in test code.
- Style Guide: Follow the DevTools style guide in STYLE.md.
- Formatting & Analysis: Always ensure code is formatted properly and has no analysis errors or warnings before completing a task.
- Standard Packages: Run unit and widget tests with
flutter test. packages/devtools_shared: Run tests withdart test.- Integration Tests: Refer to the Integration Test README for instructions on running integration tests.
- MCP Tools: Prefer using MCP server tools over shell commands whenever possible.
- Avoid Raw Values: Avoid using raw strings or numbers in UI code. Use named constants instead.
- Use Existing Themes: Use existing theme values and text styles from
packages/devtools_app_shared/lib/src/ui/theme/theme.dart(e.g.,Theme.of(context).regularTextStyle). - Reuse Patterns: Reuse common patterns and styles used in other UI code in the repository.
- Use Shared Components & Utils: Prefer using reusable components from
shared/ui/(such aspackages/devtools_app/lib/src/shared/ui/common_widgets.dart), primitives fromshared/primitives/, and utilities fromshared/utils/rather than creating things from scratch.