rust-refactor

Apply 91 architectural refactoring rules across 10 Rust categories.

193|17|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/pproenca/dot-skills --skill rust-refactor-pproenca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-refactor
Source: https://github.com/pproenca/dot-skills/tree/main/skills/.curated/rust-refactor
Command: npx skills add https://github.com/pproenca/dot-skills --skill rust-refactor-pproenca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of maintaining and evolving Rust codebases by providing a comprehensive set of best practices for architectural refactoring, ensuring code quality, safety, and maintainability.

Core Features & Use Cases

  • Architectural Refactoring: Guides on improving type safety, ownership patterns, error handling, API design, project organization, and module structure.
  • Code Quality: Enforces consistent naming conventions and idiomatic Rust patterns.
  • Use Case: When refactoring a large Rust application, use this Skill to systematically apply best practices for type safety and error handling, preventing bugs and improving long-term maintainability.

Quick Start

Apply the rust-refactor skill to improve the type safety of the current Rust module.

Frequently Asked Questions about rust-refactor

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

FAQPage Schema
What are the best practices for refactoring Rust codebases to improve type safety and error handling?

Refactoring Rust codebases requires applying architectural guidelines across 10 categories, including type safety and error handling. Systematically applying these 91 rules prevents bugs and ensures long-term maintainability for large Rust applications.

How do I enforce idiomatic Rust patterns and naming conventions during a project refactor?

To enforce idiomatic Rust patterns during a refactor, apply architectural guidelines covering naming conventions, conversions, and iterators. This ensures code quality and consistent API design across the evolving Rust project structure.

Does this Rust refactoring guidance cover project organization and module structure?

Yes, Rust refactoring guidance explicitly covers project organization and module structure. It provides architectural rules to help agents and LLMs systematically maintain, generate, and refactor large Rust applications.

What is the best way to improve ownership patterns and API design in a large Rust application?

The best way to improve ownership patterns and API design is to apply architectural refactoring guidelines. This approach targets robust codebases by systematically enforcing type safety and ownership rules across the codebase.

Can I use these refactoring rules to generate new Rust modules or only for maintaining existing code?

You can use these Rust refactoring rules for both generating new modules and maintaining existing code. The guidelines target agents and LLMs to ensure code quality, safety, and maintainability across all Rust codebase evolution tasks.