Skip to content

Commit 8b4b80a

Browse files
Add a GEMINI.md file and .gitignore entry (#9279)
1 parent fe60fcb commit 8b4b80a

2 files changed

Lines changed: 27 additions & 0 deletions

File tree

.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff 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

GEMINI.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
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.

0 commit comments

Comments
 (0)