swe-programming-rust

Enforce Rust coding standards, formatting, and linting for AI-generated code.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill swe-programming-rust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swe-programming-rust
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/swe-programming-rust
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill swe-programming-rust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When AI agents generate Rust code, inconsistent adherence to coding standards, common antipatterns, and non-compliance with project conventions create technical debt, bugs, and extra review overhead. This skill solves that by providing a quick reference for Rust coding standards, best practices, and links to authoritative documentation for deep dives.

Core Features & Use Cases

  • Quick Standards Reference: Covers Rust naming conventions, error handling with thiserror, ownership and borrowing rules, idiomatic iterator usage, newtype patterns for domain types, and Axum async handler best practices.
  • Mandatory Quality Checks: Includes required rustfmt and clippy configuration and pre-commit validation steps to ensure code passes all linting and formatting checks.
  • Comprehensive Documentation Links: Direct links to authoritative docs for coding standards, testing, code quality, build configuration, error handling, concurrency, memory management, and more for in-depth guidance.
  • Use Case: For teams using AI agents to develop Rust backend services in a polyglot monorepo, this skill ensures all generated Rust code adheres to project conventions, avoids common pitfalls like unnecessary unwrap() calls, and is production-ready.

Quick Start

Use the swe-programming-rust skill to generate idiomatic Rust code for a new Axum payment processing handler that complies with project error handling and formatting standards.

Frequently Asked Questions about swe-programming-rust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are idiomatic Rust coding standards for AI-generated code?

Idiomatic Rust coding standards require strict ownership pattern adherence, using newtype domain patterns, avoiding unnecessary unwrap() calls, and applying thiserror for error handling to ensure production-ready backend services.

How do I enforce clippy compliance and rustfmt formatting for Rust code?

To enforce clippy compliance and rustfmt formatting, configure mandatory pre-commit validation steps that run linting and formatting checks, ensuring all generated code passes required quality gates before integration into the monorepo.

Does this support async Axum handler development in a polyglot monorepo?

Yes, it supports async Axum handler development in a polyglot monorepo by providing specific best practices for Axum handlers while enforcing project-wide Rust conventions like naming conventions and error handling implementation.

What is the best way to handle errors in Rust backend services?

The best way to handle errors in Rust backend services is using the thiserror library, which enforces consistent error handling patterns and prevents common antipatterns like unnecessary unwrap() calls in production code.

Why does my AI-generated Rust code fail linting checks?

AI-generated Rust code often fails linting checks due to non-compliance with clippy rules, improper naming conventions, or missing mandatory rustfmt formatting, which requires enforcing strict coding standards during generation.

When do I need to use newtype domain patterns in Rust?

You need to use newtype domain patterns in Rust when defining domain types to enforce type safety, prevent logic errors, and satisfy idiomatic coding standards required for backend service development.