Refactor C-style Rust code into idiomatic patterns with newtypes and enums.
npx skills add https://github.com/bearcove/pikru --skill idiomatic-rust
Please help me install this Agent Skill. Skill: idiomatic-rust Source: https://github.com/bearcove/pikru/tree/main/.claude/skills/idiomatic-rust Command: npx skills add https://github.com/bearcove/pikru --skill idiomatic-rust
This Rust port of C code emphasizes idiomatic Rust patterns. Do not write C in Rust; the goal is correct behavior and safe interfaces rather than literal line-by-line translation.
Review or port a C-inspired Rust module using idiomatic patterns to replace boolean flags and improve type safety.
High-intent search queries and answers about installing and using this skill.
Porting C code to Rust should prioritize correct behavior and safe interfaces rather than literal line-by-line translation. You achieve this by applying idiomatic Rust patterns like data-driven design and newtypes to replace C-style structures.
Converting boolean flags to safe Rust types involves replacing them with explicit enums. This refactoring technique improves self-documentation and safety by making each state a distinct variant rather than relying on ambiguous true or false values.
Rust newtypes encode domain concepts by wrapping primitive types in distinct structs, preventing type confusion. This pattern is essential when refactoring C logic to ensure domain boundaries are enforced at compile time.
Preferring methods on structs over standalone functions places behavior directly with data, creating a data-driven design. This idiomatic Rust pattern improves readability and IDE support while replacing disconnected C-style function interfaces.
Refactoring C-style Rust interfaces to be safe can preserve original behavior by adopting idiomatic Rust techniques. You replace unsafe patterns with newtypes and enums while ensuring the underlying logic remains functionally identical.
Literal C to Rust translation limits code quality by ignoring Rust safety features and producing non-idiomatic interfaces. Without adopting data-driven design and explicit types, the ported code remains structurally C while merely using Rust syntax.
fatihkanScan Rust codebases for unsafe blocks, FFI misuse, and concurrency hazards.
RediSearchAutomate Rust unit and integration tests with cargo test.
farmountainEnforce Rust best practices, memory safety, and ownership patterns in code.
lazyFrogLOLCreate source files that compile and execute as both Rust and C/C++ programs.
