
rust-toolkit
Build and maintain Rust crates, services, and CLIs.
- version
- 0.1.6
- GitHub stars
- 347
Install
/plugin install rust-toolkit@khanelinix-ai-toolsRun it inside Claude Code after adding the marketplace with /plugin marketplace add khaneliman/khanelinix.
Contents
Discovered from sourceSkills 1
Rust Toolkit
Route Rust engineering work through repository evidence, then load only the reference needed for the current decision.
Start Here
- Read contributor instructions and existing manifests, toolchain files, CI, features, and validation commands before proposing structure.
- Run
scripts/project-context.py <path>for a bounded first-pass inventory. Read scripts.md for behavior and limitations. - Preserve the repository's MSRV, edition, feature matrix, target platforms, and public API policy unless the user requests change.
- Pick one primary mode below. Load another reference only when work crosses that boundary.
Routing
- project architecture: crate/module/workspace boundaries, dependency direction, visibility, errors, features, and project initialization. Read architecture.md.
- type-driven design: typestate, runtime state machines, builders, newtypes, trait dispatch, ownership, and concurrency boundaries. Read type-driven-design.md.
- correctness and testing: test placement, property/model testing, unsafe review, Miri, Loom, fuzzing, sanitizers, and validation ladders. Read correctness-and-testing.md.
- performance: compile-time and runtime measurement, data layout, allocations, SIMD, custom allocators, PGO, profiles, linkers, and caching. Read performance.md.
- toolchain evolution: edition or MSRV migrations, release and target changes, unstable language/Cargo features, and nightly experiments. Read toolchain-evolution.md.
- repeatable checks: use the inventory and quality-gate helpers. Read scripts.md.
Core Rules
- Make the smallest boundary that enforces a real invariant. Do not split a crate, add a trait, or encode typestate only for visual symmetry.
- Measure before changing profiles, linkers, codegen backends, data layout, or allocators. Report baseline, changed variable, and comparable result.
- Derive version-sensitive APIs from manifests and matching official docs. Never silently rewrite code to the newest Rust release.
- Treat RFCs, project goals, tracking issues, and accepted nightly syntax as research leads, not proof that a feature is stable.
- Prefer repository-native checks. Use
scripts/rust-verify.shonly when its command shape matches project policy.
Cross-Skill Boundaries
- Use
memory-profilerfor leak, OOM, fragmentation, or heap-profile work. - Use
bevy-toolkitfor Bevy ECS, plugins, lifecycle, MCP/BRP, runtime control, rendering, and visual validation. - Use
security-toolkitfor explicit security audits or threat models. - Use
git-toolkitfor commit structure and history operations.
Sponsors
Details
- Marketplace
- khaneliman/khanelinix
- Source
- modules/common/ai-tools/skills/rust-toolkit
- Author
- khaneliman
- Category
- Developer Tools
More from khaneliman/khanelinix
All 43- sarif-toolkitv0.1.5
- security-toolkitv0.1.7
- show-me-your-workv0.1.7
- skill-creatorv0.1.8
- software-engineeringv0.1.9
- tddv0.1.4
- technical-writingv0.2.0
- to-specv0.1.1
- to-ticketsv0.1.1
- typescript-best-practicesv0.1.6
- unslopv0.1.7
- verification-harnessv0.1.5
- whyv0.1.6
- ai-tools-architectv0.1.21
- architectv0.1.7
- arenav0.1.5
- bevy-toolkitv0.1.6
- blast-radiusv0.1.6
- blender-toolkitv0.3.2
- develop-web-gamev0.1.7
- diagnosing-bugsv0.1.3
- dotnet-toolkitv0.1.2
- engineering-principlesv0.1.22
- engineering-workflowv0.1.27