Enforces best practices for Rust crate structure, module visibility, and stable public API design.
This skill provides domain-specific expertise to organize Rust projects using professional module hierarchies and robust public API patterns. It guides developers in separating internal implementation details from stable interfaces using explicit visibility controls, strategic re-exports in lib.rs, and Cargo feature gates. Ideal for library authors and system architects, it helps prevent breaking changes through API validation workflows and promotes documentation standards that ensure libraries are both intuitive and maintainable.
Key Features
01Strategic re-exports for clean, guide-like API surfaces
02Conditional compilation and API surface management with Cargo feature gates
03Hierarchical module organization (internal vs. public boundaries)
04Visibility control using pub(crate) and pub(super) keywords
05480 GitHub stars
06Public API stability tracking and breaking change validation
Use Cases
01Designing a new Rust library with a clean, user-friendly entry point
02Refactoring a messy crate into a logical module structure while maintaining compatibility
03Implementing strict visibility boundaries to hide internal implementation details
