rust-backend

Enforce Rust backend coding standards for Windmill modules.

17.5k|1.1k|Updated May 5, 2022
One-click install
npx skills add https://github.com/windmill-labs/windmill --skill rust-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-backend
Source: https://github.com/windmill-labs/windmill/tree/main/.claude/skills/rust-backend
Command: npx skills add https://github.com/windmill-labs/windmill --skill rust-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides Rust backend coding guidelines to ensure consistent, safe, and maintainable code across the Windmill backend. It prescribes design patterns, error handling, and Rust idioms.

Core Features & Use Cases

  • Enforces data structure design patterns using enums and typed invariants.
  • Standardizes error handling with windmill_common::error types and early returns.
  • Promotes idiomatic Rust patterns: iterator chains, minimal comments, and trait implementations.
  • Real-world use: When contributing Rust code in backend/, apply these guidelines to ensure readability and reliability.

Quick Start

Apply these guidelines when editing backend Rust files to align with the Windmill Rust backend standards.

Frequently Asked Questions about rust-backend

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

FAQPage Schema
How do I enforce Rust backend coding standards in my Windmill project?

Rust backend coding standards enforce consistent patterns across Windmill's backend codebase through guidelines on data structure design, error handling with windmill_common types, and idiomatic Rust practices. Apply these standards when editing backend Rust files to ensure code reliability and maintainability across contributors.

What error handling approach should I use in Windmill Rust backend code?

Windmill Rust backend standards prescribe using windmill_common::error types with early returns for consistent error handling. This approach ensures predictable failure paths and aligns error management across all backend modules.

How should I design data structures in Rust backend code?

Rust backend guidelines recommend using enums and typed invariants for data structure design. This pattern enforces compile-time safety guarantees and prevents invalid state representation in backend modules.

What Rust idioms are prioritized in Windmill backend contributions?

Windmill backend standards prioritize iterator chains for transformations, minimal comments relying on self-documenting code, and trait implementations for abstraction. These idiomatic patterns improve readability and leverage Rust's type system effectively.

Do these coding standards apply to all backend Rust modules?

Yes, Rust backend coding standards apply to all Rust modules in the backend directory during development, code review, and contributor onboarding. Consistency across the entire backend ensures maintainability and prevents fragmented patterns.