rust-project-architecturelisted

Design or review Rust package, crate, module, target, binary/library, workspace, ownership-seam, and test-placement boundaries. Use when creating or restructuring Cargo projects, deciding whether code belongs in an existing crate or a new package, keeping binaries thin, or reducing layout-driven coupling and clone-heavy data flow. Do not use for primarily internal type/API design, async behavior, test implementation, dependency selection, or adding one CLI command; prefer the corresponding specialized Rust skill.
genaptic/skillsets · ★ 1 · API & Backend · score 70

Install: claude install-skill genaptic/skillsets

## Outcome Produce a repository-aligned Rust architecture whose crate, module, target, and test boundaries express real ownership, dependency, deployment, reuse, or release seams without needless packages. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Follow the target repository's Cargo layout, toolchain, edition, MSRV, feature, lockfile, and CI policy. Edition 2024 templates require Rust 1.85 or newer. Optional research may use the network only when authorized; otherwise report freshness gaps. Native-client compatibility remains unverified without a dated exact-SHA report. ## Inputs - The requested architectural outcome and constraints. - Workspace/package manifests, target trees, public APIs, dependency graph, CI, and test layout. - Deployment units, ownership boundaries, reuse consumers, platform constraints, and release policy. - Evidence about existing responsibilities, duplicated behavior, and data ownership seams. ## Safety - Preserve public APIs, package names, feature semantics, paths, and release boundaries unless the request explicitly authorizes migration. - Preview moves and manifest changes before applying them. Preserve unrelated edits and generated files managed by repository tooling. - Do not add crates or dependencies merely to mirror conceptual layers. - Do not install tools, publish packages, run remote Git operations, or execute live/integration infrastructure without explicit authorization. ## Procedure 1. **Inventory