Write and improve Rust documentation comments following Rust's std-dev-guide. Use this skill whenever documenting Rust code, adding doc comments, writing crate-level docs, creating doctests, or when the user asks to document a module/struct/enum/trait/function. Also trigger when the user mentions rustdoc, API guidelines, doc comments, doctests, or asks to check documentation quality. This skill covers both writing new documentation and auditing existing docs for completeness and API guideline compliance.
Analyze staged git changes and draft a commit with a structured message following project conventions
This skill should be used when the user provides one or more POH/AFM chart or table images and asks to transcribe them into libefb performance-type Rust literals (climb, cruise, descent, takeoff, or landing). It converts chart curves or tabular rows into `ClimbDescentBand`, `CumulativeClimbDescentEntry`, `PerformanceTableRow`, or `TakeoffLandingPerformance` table data using the correct measurement constructors.
Design Rust public APIs that are idiomatic, self-explanatory, and follow the official API guidelines. Use this skill when creating new public types, traits, functions, or modules in Rust — or when reviewing existing APIs for naming clarity, type safety, trait implementations, and ergonomics. Also trigger when the user asks about Rust naming conventions, newtype patterns, builder patterns, conversion traits, or asks to review/improve a Rust API surface. This skill covers API shape and naming; for documentation comments and doctests, defer to the rustdoc skill.