File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -39,6 +39,9 @@ DEPENDENCIES.md
3939** /logs /**
4040* .stager_app.g.dart
4141
42+ # Ignore Gemini logs
43+ ** /.gemini /
44+
4245# Ignore VS code workspaces that may be configured per-user
4346* .code-workspace
4447
Original file line number Diff line number Diff line change 1+ # Repository rules
2+
3+ When making changes to this code base, follow these rules, which are listed
4+ in no particular order:
5+ - ` packages/devtools_shared ` should never introduce a Flutter dependency or a
6+ dependency on web-only Dart libraries.
7+ - never import the ` packages/devtools_app/lib/devtools_app.dart ` file in code
8+ that lives under ` packages/devtools_app/lib/src/ ` . This file is okay to import
9+ in code that lives under ` packages/devtools_app/test/ ` .
10+
11+ # Running tests
12+
13+ Unit test and widget tests are all contained under a package's ` test/ `
14+ directory. These tests should be run with ` flutter test ` in all packages except
15+ for ` packages/devtools_shared ` , whose tests should be run with ` dart test ` .
16+
17+ # Gemini Guidelines
18+
19+ - Prefer to use MCP server tools over shell commands whenever possible.
20+ - When you are done making code changes, ensure the code does not have analysis
21+ errors or warnings. Also ensure it is formatted properly. You should have MCP
22+ server tools available to you to perform these tasks. If not, you can get
23+ analysis errors and warnings by running the ` dart analyze ` shell command, and
24+ you can perform Dart formatting with the ` dart format ` shell command.
You can’t perform that action at this time.
0 commit comments