From rust
Use when asked by the user to invoke the Rust architecture audit skill
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust:auditing-rust-architectureThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Invoke the `rust:standardizing-rust` skill before proceeding. If that skill is unavailable, report the missing skill and continue with the closest available workflow.
Invoke the rust:standardizing-rust skill before proceeding. If that skill is unavailable, report the missing skill and continue with the closest available workflow.
Invoke the rust:standardizing-rust-architecture skill before proceeding. If that skill is unavailable, report the missing skill and continue with the closest available workflow.
Standards are pre-loaded above.
<context_loading>
For spec-tree work items, load full ADR/PDR hierarchy first with spec-tree:contextualizing, then review the target ADR against that hierarchy.
After loading the shared Rust standards, check for spx/local/rust.md, spx/local/rust-architecture.md, and spx/local/rust-tests.md at the repository root. Read each file that exists and apply each as repo-local routing to the product's governing specs and decisions. A local overlay supplements skill behavior; it does not declare product truth.
</context_loading>
spx/local/rust.md, spx/local/rust-architecture.md, spx/local/rust-tests.md)## Verification (### Audit) for real testability constraints and absence of level tables<principles_to_enforce>
</principles_to_enforce>
<failure_modes>
## Verification</failure_modes>
<output_format>
Emit the verdict as JSON conforming to the canonical schema in plugins/spec-tree/skills/auditing/scripts/verdict.py. The skill's entire output is the JSON verdict. The caller captures the JSON and routes it through emit_verdict.py with the requested --format (defaulting to markdown+json for PR-comment delivery).
The skill's overall is PASS iff every concern row is PASS or UNKNOWN (N/A maps to UNKNOWN); FAIL if any concern is FAIL. Findings carry severity REJECT for blocking violations.
{
"schema_version": 1,
"skill": "auditing-rust-architecture",
"target": "<adr-path>",
"overall": "PASS | FAIL | UNKNOWN",
"rows": [
{ "name": "section-structure", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "testability-in-verification", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "atemporal-voice", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "mocking-prohibition", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "level-accuracy", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "anti-patterns", "status": "PASS | FAIL | UNKNOWN", "findings": [] },
{ "name": "ancestor-consistency", "status": "PASS | FAIL | UNKNOWN", "findings": [] }
],
"metadata": { "branch": "<branch>" }
}
Each finding's rule carries the violation pattern (e.g., phantom-section, temporal-voice); file is the ADR path; message carries the one-line "why this fails". Include the correct-approach Rust sample and required-changes summary directly in the finding's message field — the JSON verdict is the complete output of this skill.
</output_format>
<example_reference>
Read references/example-audit.md for a complete rejected architecture review in Rust terms.
</example_reference>
<success_criteria>
/standardizing-rust was read before /standardizing-rust-architecture## Verification (### Audit) contains real DI and no-mocking constraints</success_criteria>
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub outcomeeng/plugins --plugin rust