rust-skills-maplisted

# Rust Skills Map This map contains no guidance of its own: every sentence in it either names a skill or explains how to choose between two of them. What it settles is the choice — which skill owns the decision in front of you, and which neighbour it is not. It runs only when the user invokes it, as `/rust-skills-map`: a map you consult on purpose, not one the model reaches for mid-task. ## How to use this map Pick the row in the decision table matching the decision in front of you, run that skill, and come back here only if the skill hands you off. Skills invoke each other in prose, so following a handoff means typing the named skill — every handoff in this set is a directly typeable `/skill-name`. ## The four buckets, one line each - `rust/` — language craft: how the code should be shaped. - `workflow/` — process: testing, review, and repo setup. - `porting/` — migration from another language. - `misc/` — occasional: CI, hooks, and dependency audits. ## The decision table | You are asking | Skill | Not to be confused with | |---|---|---| | Does this read like Rust? | `/idiomatic-rust` | `/type-driven-design` — that one changes the model, this one changes the expression | | Is this `clone` necessary? | `/ownership-not-clone` | `/idiomatic-rust` — expression shape, not ownership structure | | What should this return on failure? | `/rust-errors` | `/rust-api-design` — whether the error type is a breaking change | | Can this state exist at all? | `/type-driven-design` |