agentleFS
Sign inStart free
SentryKnown publishergetsentry/sentry-dart/packages/dart/AGENTS.md

sentry-dart / dart

AGENTS.md878 starsChanged 32 days agoMITView on GitHub

Core Dart SDK — foundation for all other packages in this monorepo. lib/sentry.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.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every new public type must be exported from lib/sentry.dart

    line 9
  2. Very specific:

    Do not export internal helpers from lib/sentry.dart only for sibling packages.

    line 11
  3. Very specific:

    Avoid exporting extensions on common Dart/core types like Iterable, String, or Map.

    line 12
  4. Distinctive:

    If a helper truly must be public, prefer an explicit named API over extension methods for common types

    line 13

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

sentry

Core Dart SDK — foundation for all other packages in this monorepo.

Public API Surface

lib/sentry.dart is the public barrel file. Changes here affect all downstream packages and users.

  • Every new public type must be exported from lib/sentry.dart
  • Integration packages (sentry_flutter, sentry_dio, etc.) depend on this package — regressions here cascade everywhere
  • Do not export internal helpers from lib/sentry.dart only for sibling packages; prefer direct src/ imports within this monorepo when the API is not meant for SDK users
  • Avoid exporting extensions on common Dart/core types like Iterable, String, or Map; they affect user extension resolution and can conflict with dart:* or popular packages
  • If a helper truly must be public, prefer an explicit named API over extension methods for common types

Key Directories

  • lib/src/protocol/ — Shared event and context representations
  • lib/src/envelope/ — Envelope payloads and serialization
  • lib/src/transport/ — Delivery, queuing, and rate limiting
  • lib/src/telemetry/span/ — Transaction and streaming spans, shared sampling, propagation, and instrumentation
  • lib/src/telemetry/ — Logs, metrics, spans, and shared processing pipelines
  • lib/src/exception/ — Exception identification, extraction, and processing
  • lib/src/enrichment/ — Event enrichment and runtime information
  • lib/src/http_client/ — HTTP client instrumentation
  • lib/src/client_reports/ — Client-side outcome reporting
  • lib/src/utils/ — Shared internal utilities including SentryInternalLogger

Feature integrations and processors live with their owning feature. Tests mirror feature directories.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free