Dart Best Practices

This one keeps your Dart code clean and readable with practical formatting guidance. The main focus is on using multi-line strings instead of ugly concatenation for things like SQL queries or PEM keys, plus staying under 80 characters per line so your code doesn't scroll off the screen in split view. It includes regex patterns to hunt down concatenation candidates in your codebase, which is genuinely helpful if you're cleaning up an existing project. Pretty focused scope, just two core practices, but they're the kind that make pull requests easier to review and prevent those annoying lint warnings.

skills.sh installs: 843
GitHub stars: 148
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add kevmoo/dash_skills --skill dart-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Dart Best Practices

1. When to use this skill

Use this skill when:

Writing or reviewing Dart code.
Looking for guidance on idiomatic Dart usage.

When NOT to use (Abstention Guardrails)

Do NOT apply this skill or refactor code when:

Public API Breaking Changes: Refactoring would alter public API contracts, return types, or parameter signatures in published packages without a coordinated major SemVer bump.
Dogmatic Micro-Optimizations: Rewriting clear, readable code for negligible theoretical gains (e.g. replacing clear string concatenation in a simple one-line log message with multiline quotes).
Domain-Specific or Code-Generated Files: Generated files (*.g.dart, *.freezed.dart, protobufs) or files where line lengths and string layouts are managed by code generators.
Explicit Type Annotations in Public Interfaces: Replacing explicit type annotations with var or final where explicit types document the public API surface or disambiguate complex generics.