Skip to content
Skills Library
Programming · Building & coding

rust-development

/rust-development

Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.

Licence
MIT
Last repository change
17.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.

Original author description

Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.

How it works

  1. Capabilities
  2. Instructions
  3. Agent Delegation
  4. When to Activate
  5. Guidelines Source
Original SKILL.md headings · 64 lines, 300 words
SKILL.md preview
---
name: rust-development
version: 0.13.0
description: Develop, review, and explore Rust code with strict adherence to Pragmatic Rust Guidelines. Use when the user mentions Rust, .rs files, Cargo, clippy, rustdoc, or requests Rust architecture, implementation, or review.
depends_on:
  rust-architect: 0.x
  rust-code-reviewer: 0.x
  rust-code-explorer: 0.x
  rust-developer: 0.x
---

# Rust Development

This skill coordinates Rust development workflows and enforces Rust coding standards and best practices when creating or modifying Rust code.

## Capabilities

- Rust architecture planning
- Rust code exploration and feature tracing
- Rust code review with high-confidence findings
- Rust implementation and refactoring

## Instructions

When asked about generating new code or making code changes to existing code, make
sure that edits are conformant to the Rust guidelines at `.claude/skills/rust-development/guidelines.txt` if the language to generate is Rust.

Key areas to enforce:
- Idiomatic Rust patterns and conventions
- Proper error handling (Result types, custom errors)
- Memory safety and lifetime management
- Async/await patterns when applicable
- FFI best practices for interop scenarios
- Documentation standards (rustdoc conventions)
- Testing patterns and practices

Only add a compliance comment when the user explicitly asks for a compliance annotation or a compliance-focused review. If requested, add:
```rust
// Rust guideline compliant {date}
```
where {date} is the guideline date/version.

## Agent Delegation

Invoke these agents via Agent Runner using `.claude/agents/registry.yaml`. This keeps Rust delegation registry-enforced and version-audited instead of bypassing the installed agent registry.

- `rust-architect`: Architecture and implementation blueprints
- `rust-code-reviewer`: High-confidence Rust code reviews
- `rust-code-explorer`: Feature tracing and architecture mapping
- `rust-developer`: Rust implementation and refactoring

Task tool template:

```xml
<invoke name="Task">
<parameter name="subagent_type">rust-architect | rust-code-reviewer | rust-code-explorer | rust-developer</parameter>
<parameter name="description">Short description of the Rust work</parameter>
<parameter name="prompt">Detailed Rust task. Require the agent to return fenced JSON using its documented {success,data,error} envelope.</parameter>
</invoke>
```

## When to Activate

This skill activates automatically when:
- Creating new Rust source files (.rs)
- Modifying existing Rust code
- Reviewing Rust code for compliance
- Answering questions about Rust best practices
- Working with Cargo projects

## Guidelines Source

The detailed guidelines are maintained in `.claude/skills/rust-development/guidelines.txt`.
Files in this package (3)
  • SKILL.md 3 KB
  • cross-platform-guidelines.md 3 KB
  • guidelines.txt 88 KB

Versions

RepositoryScoreLicence
This page · randlee/synaptic-canvas100MIT
dreamlab-ai/agentbox100AGPL-3.0
laurigates/claude-plugins100MIT
cosmonic-labs/skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 9928ee1d23fb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95rust-best-practices
    Write idiomatic, robust, maintainable Rust. Use this skill whenever you write, review, refactor, debug, or explain Rust code: new crates, modules, functions, structs, traits, error types, async code, unsafe or FFI code, Cargo.toml, tests, or rustdoc. Trigger on any mention of…
  • 95rust-best-practices
    Write idiomatic, robust, maintainable Rust. Use this skill whenever you write, review, refactor, debug, or explain Rust code: new crates, modules, functions, structs, traits, error types, async code, unsafe or FFI code, Cargo.toml, tests, or rustdoc. Trigger on any mention of…
  • 100rust
    Rust language conventions, idioms, error handling, concurrency (CPU-bound parallelism with threads/rayon and I/O-bound async with Tokio), the cargo/clippy/rustfmt toolchain, and rustdoc. Invoke whenever task involves any interaction with Rust code — writing, reviewing,…
  • 100rust-docs-guidelines
    Guidelines for writing Rust documentation. Use this when you want to write Rust documentation.
  • 100rust-best-practices
    Use when writing, modifying, or reviewing Rust code. ALWAYS invoke before Rust edits; covers Microsoft Pragmatic Rust guidance for error handling, API design, performance, and idiomatic patterns.
  • 100rust-pro
    Use when writing or reviewing Rust code, including Cargo projects, .rs files, ownership and borrowing changes, async Rust, traits, error handling, clippy findings, and Rust tests. # Development skill for this repository; not for installation by users.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.