# Build Production-Ready Rust Workspaces

Rust projects can become difficult to test and maintain as crates and dependencies grow. This skill provides practical patterns for workspace structure, boundaries, testing, tracing, and quality gates.

## Install

```bash
npx skillstore add clementwalter/senior-rust-practices
```

## Metadata

- Status: approved
- Slug: clementwalter-senior-rust-practices
- Skillstore revision: r2
- Version status: missing
- Tree hash: 7df6c986bf0587daaf974d673cebb36ae6697cf3ebe19df226aace4cd7195226
- Author: ClementWalter
- GitHub username: ClementWalter
- License: MIT
- Repository: https://github.com/ClementWalter/rookie-marketplace/tree/main/rust-dev/skills/senior-rust-practices
- Ref: c68df504887c54bf71d2d467a1fbebde49467868
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/clementwalter-senior-rust-practices
- Manifest: https://skillstore.pages.dev/api/skills/clementwalter-senior-rust-practices/manifest

## Capabilities

- Proposes workspace layouts with clear core, adapter, application, and binary boundaries.
- Explains shared Cargo dependency management and feature design.
- Recommends Rust visibility and error-handling patterns for library and binary crates.
- Designs layered unit, integration, end-to-end, property, and fuzz testing strategies.
- Recommends tracing, Clippy, formatting, and dependency-audit quality gates.

## Use Cases

- Design a new workspace: Create a small Cargo workspace with deliberate crate boundaries and shared dependencies.
- Refactor a growing service: Separate domain logic from adapters and reduce dependency coupling in an existing Rust service.
- Strengthen delivery checks: Define repeatable tests, linting, formatting, and dependency checks for a Rust CI pipeline.

## Prompt Templates

### Plan a starter workspace

```
Design a Cargo workspace for a Rust CLI and library. Explain each crate and its dependencies.
```

### Improve crate boundaries

```
Review this Rust workspace layout and recommend boundaries between core logic, adapters, and application code: [layout].
```

### Create a test strategy

```
Create a layered Rust testing strategy for this service. Include unit, integration, end-to-end, and property tests: [service description].
```

### Audit engineering practices

```
Assess this Rust project against senior practices for dependencies, features, errors, tracing, and CI. Prioritize changes with reasons: [project details].
```

## Limitations

- Does not inspect or modify a repository unless the host agent provides those capabilities.
- Does not replace project-specific performance profiling or security review.
- Dependency versions and tool compatibility require verification against the current Rust ecosystem.
- Guidance is general and may need adjustment for embedded, WebAssembly, or regulated systems.

## Best Practices

- Keep domain logic independent from network, database, and filesystem adapters.
- Pin the Rust toolchain and verify the minimum supported Rust version in CI.
- Use small public APIs and test behavior at each system boundary.

## Anti Patterns

- Do not split a project into many crates before clear boundaries exist.
- Do not expose all modules publicly for convenience.
- Do not rely only on end-to-end tests for core business logic.

## Security Audit

- Audited at: 2026-07-18T10:49:30.127\+00:00
- Summary: All 68 static findings are false positives from Markdown backticks, fenced examples, and benign Rust terminology. The only shell command is documented Git worktree guidance for local development, and no prompt injection, data exfiltration, or executable payload was found.

## Stats

- Views: 304
- Downloads: 10
- Favorites: 1
- Popularity score: 0