What problem does it solve? Public Dart APIs often ship with missing, stale, or name-restating doc comments that give callers no real contract. This Skill enforces Effective Dart documentation standards so every public declaration carries a meaningful /// doc backed by analyzer errors. ## Core Features & Use Cases - Complete public-surface coverage: Requires a /// doc on every public class, method, getter, field, and typedef, enforced by public_member_api_docs as an analyzer error. - Contract-quality content: Mandates one-sentence standalone summaries, verb-phrase method docs, "Whether…" boolean getters, [bracket] cross-links, and explicit units, ranges, nullability, throws, and side effects. - Invariant pinning: Restates enforced invariants at their enforcement point with in-body // comments that explain why, never what. - Use Case: When adding a new Riverpod Notifier or sealed Failure class to a Flutter package, apply this Skill to document every public member, wire the library barrel doc, and pass dart analyze --fatal-infos --fatal-warnings cleanly. ## Quick Start Review the public API in my Dart package and write Effective-Dart-compliant doc comments for every undocumented public declaration.
