What problem does it solve? Writing consistent, dartdoc-compatible API documentation in Dart is error-prone: developers misuse Javadoc-style tags, misplace comments relative to annotations, break first-sentence summaries, and create unresolvable symbol links. This Skill enforces the official Effective Dart documentation rules so generated API reference sites render correctly. ## Core Features & Use Cases - Formatting Rules: Enforces /// line comments, proper sentence structure, single-sentence first paragraphs, and correct openers (noun phrases for properties, "Whether" for booleans, third-person verbs for methods). - Anti-Pattern Detection: Bans Javadoc/TSDoc tags like @param and @return, requiring prose-based parameter and exception descriptions instead. - Linking & Placement Guidance: Covers square-bracket symbol links, [ClassName.new] constructor syntax, @docImport for out-of-scope references, and doc placement before annotations like @override. - Use Case: When documenting a public Dart library before publishing to pub.dev, apply these rules so dart analyze reports no comment_references warnings and dart doc renders clean output. ## Quick Start Write dartdoc-compliant documentation comments for all public classes and methods in my Dart file following the Effective Dart guidelines.
