Rust Project Implementation & Acceptance Guide

Use this skill together with /pma. /pma controls workflow, approval, and task tracking; this guide defines the product-grade acceptance baseline for every PMA-Rust project.

This skill names no versions: every crate, toolchain, edition, and base image starts from its latest stable release verified at the registry (see /pma references/workflow.md Dependency Freshness). Versions inside references/evidence.md are evidence, not targets.

Hard Locks

Defined in references/baseline.md Hard Locks; loosening one follows its Known Trade-offs section. /pma refuses implementation approval when they are not enforced.

1. Mature crates first; pure Rust is not required, but every release target must build
2. rustls only, with the aws-lc-rs provider installed in main()
3. #![forbid(unsafe_code)] at every crate root
4. Deny warnings in [workspace.lints], not on the CLI
5. MSRV declared and verified in CI
6. No unwrap / expect / panic! in runtime paths
7. Latest stable edition
8. Quality gates green before merge (references/delivery.md)