Dart Best PracticesSAFE

A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: dart-best-practices
description: "Dart code quality conventions: naming, const/final/var hierarchy, single quotes, trailing commas, collection idioms, tear-offs, and import organization. Use only for Dart style-focused changes or reviews; never activate for configuration-only lint setup, unrelated feature work, or widget tests."
metadata:
  triggers:
    files:
      - "**/*.dart"
    keywords:
      - naming
      - convention
      - trailing comma
      - import
      - tear-off
---

# Dart Best Practices

## **Priority: P1 (HIGH)**

- **Scoping**:
- No global variables.
- Private globals (if required) must start with `_`.
- **Immutability**: Use `const` > `final` > `var`.
- **Config**: Use `--dart-define` for secrets. Never hardcode API keys.
- **Naming**: Follow [effective-dart](https://dart.dev/guides/language/effective-dart) (PascalCase classes, camelCase members).
- **Strings**: Prefer single quotes; use double quotes only for interpolation needs.
- **Trailing Commas**: Always use trailing commas for multi-line literals/params.
- **Expression Bodies**: Prefer `=>` for single-expression functions/getters.
- **Collections**:
- Use `.map`, `.where`, `.fold`, `.any` over manual loops when clarity improves.
- Type empty collections (`<String>[]`, `<String, User>{}`) to avoid `dynamic`.
- Use collection `if`/`for` and spread operators for composable lists/maps.
- **Async**: Always `await` futures unless intentionally fire-and-forget.

```dart
import 'models/user.dart'; // Good
import 'package:app/models/user.dart'; // Avoid local absolute
```

### Anti-Patterns

- **No var for non-obvious types**: Use `final` or explicit type; `var` only for locally-obvious short scopes.
- **No package imports within same package**: Use relative imports for intra-package files.
- **No top-level mutable state**: Encapsulate in class or inject via DI.
- **No anonymous lambdas for tear-offs**: Prefer `list.forEach(doSomething)` over anonymous form.

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.