Skill Store 33

Coding Guidelines

Use when asking about Rust code style or best practices.

by actionbook

The skill

Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名

This skill's licence does not allow redistribution, so the store does not show its text. Read it at the source.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: actionbook/coding-guidelines-79805643324.

Markdown version

Details

Publisher
actionbook
Category
Software Development › Languages & frameworks
Updated
2026-08-23

References

More from actionbook

  • Core Actionbook Internal support skill for actionbook MCP selectors used by Rust documentation research workflows.
  • Core Agent Browser Internal support skill for agent-browser CLI workflows used by rust-learner, docs-researcher, and…
  • Core Dynamic Skills Internal command support for dynamic Rust crate skill management.
  • Core Fix Skill Docs Internal maintenance support for checking and fixing generated Rust skill documentation references.

Related skills

  • Code Quality General Correctness rules, Rust patterns, comments, avoiding over-engineering.
  • Rust Quality Rust code quality with Clippy, rustfmt, and cargo tools.
  • Rust Best Practices Development guidance for writing idiomatic Rust.
  • Rust Expert Best Practices Code Review Rust best practices and code quality guidelines for writing idiomatic, safe, and performant Rust…
  • Clippy Lints Use when applying Clippy lint categories for Rust code including correctness, performance, style,…