rust-workspacelisted

# rust-workspace The workspace structure layer: when to split into a workspace, the templates (virtual / single-package / multi-workspace), workspace inheritance, the `Cargo.lock` policy, MSRV coordination, cross-crate patterns, and workspace publishing. For project scaffolding, use `rust-scaffold`. For CI/lint/quality setup, use `rust-quality`. For release/publishing pipeline, use `rust-release`. --- ## §1. When this skill fires **Use this skill when the user says any of:** - "Set up a Cargo workspace" - "Split my project into a workspace" - "Share dependencies across crates" - "Use workspace inheritance" - "Coordinate MSRV across workspace members" - "Publish a workspace to crates.io" - "Add an internal feature flag pattern" - "Should I split my project into a workspace?" **DO NOT use this skill for:** ## CONTRAST - NOT for: scaffold a single project / Cargo.toml layout / edition — use rust-scaffold - NOT for: CI / clippy / lints / testing — use rust-quality - NOT for: version / publish / deprecation — use rust-release - This skill is the workspace structure layer; the others are per-crate concerns --- ## §2. Reference index The mechanism content lives in references/. Read the right one before making the corresponding decision. The hub itself is a router — it points you at the right reference, the references carry the mechanism. You MUST read `references/workspace-decisions.md` BEFORE splitting a project into a workspace or restructuring an existing one. It teach