Enforce RFC 1574 documentation conventions for public Rust items.
npx skills add https://github.com/nubiv/my-nome --skill rustdoc-nubiv
Please help me install this Agent Skill. Skill: rustdoc Source: https://github.com/nubiv/my-nome/tree/main/nix-darwin/config/claude/skills/rust-doc Command: npx skills add https://github.com/nubiv/my-nome --skill rustdoc-nubiv
This Skill helps developers adhere to the official Rust documentation conventions (RFC 1574), ensuring clarity, consistency, and discoverability in their code documentation.
# Examples, # Panics, # Errors, and # Safety.Apply the rustdoc skill to write clear and conventional documentation comments for your Rust code.
High-intent search queries and answers about installing and using this skill.
Rust documentation comments following RFC 1574 require a standardized summary sentence structure, specific comment styles, section headings like # Examples, and American English spelling for public items. This ensures clarity and discoverability for your library.
Documenting a public Rust function should include essential sections such as # Examples, # Panics, # Errors, and # Safety. These sections communicate function behavior, failure conditions, and unsafe usage requirements to consumers.
The correct summary sentence structure for Rust doc comments is a concise, single sentence using American English spelling that summarizes the item. This summary appears first in the documentation block before detailing type references and examples.
Referencing types and linking external documentation in Rust code involves using specific rustdoc syntax to connect module items. Effective linking ensures users can navigate between type definitions and related documentation seamlessly.
Yes, American English spelling is required for Rust module and type documentation to adhere to RFC 1574 conventions. Enforcing this spelling standard maintains consistency across the Rust ecosystem's official documentation.
RFC 1574 documentation conventions specifically target public Rust items, including modules and types, to ensure external API clarity. Private items generally do not require this level of standardized documentation exposure.
uwuEnforce Rust documentation conventions per RFC 1574 for public items.
r3bl-orgStandardize Rust rustdoc structure, voice, and intra-doc links.
ianyimiEnforce global coding style guidelines across multi-language codebases.
launchapp-devEnforce RFC 1574 documentation conventions on public Rust items.