Skip to content
Back to skills

Rust Docs Guidelines

ASecurity

Guidelines for writing Rust documentation

  • 8 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 29, 2026
documentationrustdocumentation

Security analysis

A100/100

Scanned May 29, 2026

npx -y skills add zjunlp/Skills --skill rust-docs-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rust Docs Guidelines?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rust Docs Guidelines
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zjunlp-rust-docs-guidelines/badge)](https://www.skillsdirectory.com/skills/zjunlp-rust-docs-guidelines)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: rust-docs-guidelines
description: Guidelines for writing Rust documentation
---

# Rust Docs Guidelines

Standards to follow when writing Rust documentation.

## Guidelines

- Key concepts should be explained only once. All other documentation should use an intra-documentation link to the first explanation.
- Always use an intra-documentation link when mentioning a Rust symbol (type, function, constant, etc.).
- Avoid referring to specific lines or line ranges, as they may change over time.
  Use line comments if the documentation needs to be attached to a specific code section inside
  a function/method body.
- Focus on why, not how.
  In particular, avoid explaining trivial implementation details in line comments.
- Refer to constants using intra-documentation links. Don't hard-code their values in the documentation of other items.
- Intra-documentation links to private items are preferable to duplication. Add `#[allow(rustdoc::private_intra_doc_links)]` where relevant.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.