General purity standards for Dart development.
Scanned 9/8/2026
Install to Claude Code
Skills Directorynpx -y skills add ngxtm/devkit --skill best-practices --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Best Practices?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ngxtm-best-practices-devkit)More formats (shields.io, HTML) on the badges page.
---
name: Dart Best Practices
description: General purity standards for Dart development.
metadata:
labels: [dart, clean-code]
triggers:
files: ['**/*.dart']
keywords: [import, final, const, var, global]
---
# Dart Best Practices (P1)
- **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).
```dart
import 'models/user.dart'; // Good
import 'package:app/models/user.dart'; // Avoid local absolute
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
