Rust Patterns
Idiomatic Rust patterns and best practices for readable, safe, maintainable Rust: ownership, borrowing, API design, enums/traits, error handling, iterators, concurrency, dynamic dispatch/plugins, and low-level/offensive patterns. Use when writing or reviewing `.rs` code, refactoring crates, porting non-idiomatic code into Rust, designing Rust APIs, or building Rust tooling that needs runtime composition or RE-resistance.
Install
npx skills add PanPanFR/oh-my-openkilo --skill rust-patternsgit clone --depth 1 https://github.com/PanPanFR/oh-my-openkilo.git /tmp/oh-my-openkilo
mkdir -p ~/.claude/skills
cp -r /tmp/oh-my-openkilo/archive/skills/rust/rust-patterns ~/.claude/skills/rust-patternsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Rust Patterns This skill is for **day-to-day idiomatic Rust**: clear ownership, small APIs, and code that feels native to the language instead of a direct port from somewhere else. If the task is primarily profiling/benchmarking, use `rust-performance`. If the task is primarily test design or test repair, use `rust-testing`. ## When to activate - Writing or refactoring `.rs` modules, libraries, CLIs, or services - Reviewing Rust PRs for ownership, borrowing, API shape, and common footguns - Porting code from C/C++/Go/Python into idiomatic Rust - Improving error handling, trait design, iterators, module boundaries, concurrency, or docs - Choosing a dispatch/plugin mechanism, or building low-level/offensive Rust with `unsafe`, FFI, or RE-resistant builds --- ## Core rules (high signal) - Make ownership obvious in signatures: **borrow by default, own when storing or crossing boundaries**. - Model the domain with **enums, newtypes, and builders** instead of flag soup and loosely related primitives. - Use `Result` for fallible work; reserve `panic!`, `unwrap`, and `expect` for tests or truly impossible states. - Prefer iterators and pattern matching when they make intent clearer; do not turn readable logic into adapter golf. - Keep public APIs small and deliberate; re-export intentionally and hide implementation details. - Run `cargo fmt` and `cargo clippy`; style should not be negotiated by hand.
Details
- Skill name
rust-patterns- Repository
- PanPanFR/oh-my-openkilo
- Path
archive/skills/rust/rust-patterns/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Rust Patterns skill do?
Idiomatic Rust patterns and best practices for readable, safe, maintainable Rust: ownership, borrowing, API design, enums/traits, error handling, iterators, concurrency, dynamic dispatch/plugins, and low-level/offensive patterns. Use when writing or reviewing `.rs` code, refactoring crates, porting non-idiomatic code into Rust, designing Rust APIs, or building Rust tooling that needs runtime composition or RE-resistance.
How do I install the Rust Patterns skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add PanPanFR/oh-my-openkilo --skill rust-patterns. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Rust Patterns popular?
It lives in PanPanFR/oh-my-openkilo, which has 9 GitHub stars and 1 forks.
Related skills
Adaptive
9PanPanFR/oh-my-openkilo
Instructions to make or update an app's UI so that it adapts to different Android devices including phones, tablets, foldables, laptops, desktop, TV, Auto, and XR. It includes how to handle different window sizes, pointing devices (such as mouse) and text entry devices (such as keyboard) using the Compose MediaQuery API, and how to preserve UI, navigation, scroll, and media playback state across configuration changes (such as folding/unfolding a foldable, rotating a device, or resizing a window). It also covers multi-pane layouts using Navigation3 Scenes, adaptive UI components (such as button
Agentmemory
9PanPanFR/oh-my-openkilo
Index for agentmemory internals: how it is wired into a host agent, its architecture and ports, configuration flags, capture hooks, MCP tool surface, and REST fallback. Use when installing or debugging agentmemory itself, when a memory tool name or parameter is unclear, or when capture is not recording. For normal recall and save work, use agentmemory-ops instead.
Agentmemory History
9PanPanFR/oh-my-openkilo
Read past work: resume the last session, recap recent sessions, list agent-linked commits, trace a line back to the session that wrote it, or compact the current conversation for handoff. Use when the user says "where were we", "resume", "recap", "session history", "what did we do", "why is this code here", "who wrote this", or "handoff".
Rust Performance
9PanPanFR/oh-my-openkilo
Rust performance workflow: benchmark and profile first, identify hotspots, reduce allocations and contention, improve data layout, tune release profiles, and verify gains with repeatable evidence. Use only after you have a real Rust performance symptom, regression, or hotspot in `.rs` code.
Rust Best Practices
9PanPanFR/oh-my-openkilo
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
Rust Testing
9PanPanFR/oh-my-openkilo
Rust testing patterns for unit, integration, async, doc, property, snapshot, fuzz, and benchmark-adjacent tests. Use when writing or reviewing tests for `.rs` code, reducing flakiness, designing fixtures/fakes, improving CI confidence, hardening `unsafe`/FFI/parsers with Miri and sanitizers, or testing concurrent atomics and locks with Loom.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.