sentry-dart / flutter
AGENTS.md878 starsChanged 32 days agoMITView on GitHub
Flutter SDK with native integrations across all platforms. lib/sentry_flutter.dart is the public barrel file. Changes here affect all downstream packages and users. Feature integrations and processors live with their owning feature. Tests mirror feature directories.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- packages/dart/AGENTS.mdAGENTS.md
- code-guidelinesSkill
- design-firstSkill
- diagnosing-bugsSkill
- reviewSkill
- specSkill
- test-guidelinesSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Every new public type must be exported from lib/sentry_flutter.dart
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
sentry_flutter
Flutter SDK with native integrations across all platforms.
Public API Surface
lib/sentry_flutter.dart is the public barrel file. Changes here affect all downstream packages and users.
- Every new public type must be exported from
lib/sentry_flutter.dart
Native Code
| Platform | Language | Path |
| Android | Kotlin | android/src/main/kotlin/io/sentry/flutter/ |
| iOS/macOS | Swift/ObjC | darwin/sentry_flutter/ |
| Linux | C++ | linux/ |
| Windows | C++ | windows/ |
- JNI bindings use
package:jni; FFI bindings usedart:ffi - JNI should pass primitives directly. Small, controlled
Map/Listpayloads may use direct conversion; arbitrary or large payloads should cross as UTF-8 JSON bytes and deserialize on Kotlin/Java. - JNI and FFI can currently only be tested through integration test since they cannot be injected / mocked or faked.
Key Directories
lib/src/native/— Native SDK interop, generated bindings, and platform adapterslib/src/web/— JavaScript SDK interop and script loadinglib/src/replay/— Replay lifecycle, scheduling, and configurationlib/src/screenshot/— Event screenshot integration and processinglib/src/screen_capture/— Shared screenshot/replay capture, masking, and capture-widget lifecyclelib/src/bindings/— Shared Flutter bindings, frame callbacks, and lifecycle supportlib/src/frames_tracking/— Frame metrics collectionlib/src/navigation/— Route observation and display timinglib/src/exception/— Flutter/platform exception handling, including JVM parsinglib/src/enrichment/— Context, release, feature-flag, and thread enrichmentexample/integration_test/— Native and end-to-end tests
Feature integrations and processors live with their owning feature. Tests mirror feature directories.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

