rust-worker

Implement Rust features, refactors, and bug fixes with test-first validation.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/LudwigAJ/swell --skill rust-worker-ludwigaj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-worker
Source: https://github.com/LudwigAJ/swell/tree/main/.factory/skills/rust-worker
Command: npx skills add https://github.com/LudwigAJ/swell --skill rust-worker-ludwigaj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an AI complete Rust implementation work reliably from start to finish, including feature development, refactors, bug fixes, wiring changes, and tests, while keeping changes aligned with existing project conventions.

Core Features & Use Cases

  • Test-first development: Writes failing tests before implementation so behavior is verified against the feature request.
  • Rust code changes: Covers new types, traits, functions, APIs, and integration wiring across crates.
  • Validation workflow: Confirms quality with cargo check, cargo test, cargo clippy, and workspace builds.
  • Safe implementation habits: Encourages idiomatic Rust, strong error context, concurrency discipline, and use of project-specific references.
  • Use case: A developer asks for a new parser, a refactor in a shared crate, or a bug fix with regression coverage, and this Skill drives the full implementation loop.

Quick Start

Use the rust-worker skill to implement the requested Rust change by reading the relevant code and references first, then adding failing tests, implementing the fix, and validating the result with Cargo checks.

Frequently Asked Questions about rust-worker

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

FAQPage Schema
How do I implement Rust features using a test-first workflow?

Rust feature implementation using a test-first workflow requires writing failing tests before code changes, then implementing new types, traits, or functions, and finally validating with cargo check, cargo test, and cargo clippy. This approach verifies behavior against the feature request.

What's the best way to refactor existing Rust crates without breaking functionality?

Refactoring existing Rust crates safely involves reading project conventions first, adding failing tests to capture current behavior, making the code changes, and verifying the workspace build passes with cargo check, test, and clippy.

How do I add regression tests when fixing bugs in a Rust codebase?

Adding regression tests for Rust bug fixes starts by writing a failing test reproducing the bug, implementing the fix, and validating the workspace with cargo test and cargo check to ensure the regression is resolved.

Can I use this test-driven approach for adding new APIs and integration wiring across multiple crates?

Yes, this test-driven approach applies to Rust crates needing new APIs, types, traits, and integration wiring. It validates end-to-end behavior by running cargo test and workspace builds after writing the initial failing tests.

Does this Rust workflow require specific project conventions before starting implementation?

Yes, the Rust workflow requires reading existing project conventions and references first. This ensures new functions, error handling, and concurrency discipline align with the codebase before adding failing tests and validating with cargo clippy.

Why should I run cargo clippy and workspace builds after Rust code changes?

Running cargo clippy and workspace builds after Rust code changes confirms idiomatic code quality and verifies that integration wiring across crates compiles successfully. This validation loop prevents regressions and ensures strong error context.