Senior Rust Practices
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "Senior Rust Practices" from https://skillstore.io/skills/clementwalter-senior-rust-practices.md and its manifest at https://skillstore.io/api/skills/clementwalter-senior-rust-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Senior Rust Practices". Design a workspace for an API service with PostgreSQL storage.
Expected outcome:
- Recommended crates: core, adapters, app, and api binary.
- Keep database code in adapters behind a trait boundary.
- Run formatting, Clippy, tests, and dependency checks in CI.
Using "Senior Rust Practices". Improve test coverage for a parsing library.
Expected outcome:
- Keep deterministic parser tests near the implementation.
- Add public API integration tests under the crate tests directory.
- Use property tests and fuzzing for untrusted input formats.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (50)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/clementwalter-senior-rust-practices/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/clementwalter-senior-rust-practices?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/clementwalter-senior-rust-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/clementwalter-senior-rust-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/clementwalter-senior-rust-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
ClementWalter. (2026). Senior Rust Practices security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/clementwalter-senior-rust-practices/audits/9BibTeX citation
@techreport{clementwalter-clementwalter-senior-rust-practices-2026,
author = {ClementWalter},
title = {Senior Rust Practices security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/clementwalter-senior-rust-practices/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Senior Rust Practices security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "ClementWalter"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/clementwalter-senior-rust-practices/audits/9"
identifiers:
- type: other
value: "skillstore:clementwalter-senior-rust-practices:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Design a Cargo workspace for a Rust CLI and library. Explain each crate and its dependencies.
Review this Rust workspace layout and recommend boundaries between core logic, adapters, and application code: [layout].
Create a layered Rust testing strategy for this service. Include unit, integration, end-to-end, and property tests: [service description].
Assess this Rust project against senior practices for dependencies, features, errors, tracing, and CI. Prioritize changes with reasons: [project details].
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.
Avoid
- 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.
Frequently Asked Questions
Who should use this skill?
Does it create files automatically?
Does it support single-crate projects?
Does it recommend specific dependencies?
Can it help with CI?
Does it replace a security audit?
Developer Details
Author
ClementWalterLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Repository
https://github.com/ClementWalter/rookie-marketplace/tree/main/rust-dev/skills/senior-rust-practicesRef
c68df504887c54bf71d2d467a1fbebde49467868
Maintenance freshness
7/19/2026
Usage
9 downloads · 304 views
File structure
📄 SKILL.md