From rust-coding-engine
Use when the task is about Rust documentation quality, rustdoc, style, linting, examples, tests, or API-quality posture.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust-coding-engine:docs-and-qualityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read `../../references/quality/INDEX.md`.
../../references/quality/INDEX.md.../../references/quality/rust-quality-testing-benchmarking-documentation.md.../../references/quality/rust-style-and-lint-governance.md and ../../references/quality/rust-workspace-lint-pipeline-discipline.md.../../references/quality/rustdoc-mastery.md, ../../references/quality/rust-doc-examples-discipline.md, and ../../references/quality/rust-public-api-documentation-and-trait-surface-discipline.md.../../rules/style/INDEX.md and ../../rules/testing/INDEX.md for exact subdomain routing.Quality is not decoration. In Rust, docs, examples, lints, and tests are part of the executable contract.
npx claudepluginhub joysusy/violet-plugin-place --plugin rust-coding-engineGuides writing idiomatic Rust code covering borrowing, error handling, performance, linting, testing, and documentation based on Apollo GraphQL's best practices handbook.
Guides writing idiomatic Rust code with patterns for ownership, error handling, generics dispatch, and performance. Includes clippy configuration and documentation standards.
Provides Rust coding conventions on imports (prefer full paths over use), crate:: references, and cargo clippy checks for writing and reviewing Rust code.