rustdoc-authoring

Structure and content rules for Rust doc comments and inline comments. Use whenever the task involves a comment in Rust source — writing a new one, editing or rewriting an existing one, reviewing one, deciding whether an item needs one, or comparing two versions. Covers the four content slots and their order, why the first paragraph rather than the first sentence is the summary, what the signature already says so the comment need not, the headings that stand in for tags (# Errors, # Panics, # Safety, # Examples), intra-doc links and the lints that check them, doc examples that compile and run as tests and the blocks that become one by accident, // SAFETY: comments, how far a rewrite may grow, and the extra rules for traits, unsafe code, tests, module and crate comments, and docs that ship to docs.rs. Applies to a one-line comment as much as to a twenty-line block. Language and wording are governed by english-developer-style, which this skill defers to and does not replace.