Design clear Rust APIs
Use ownership, borrowing, lifetimes, traits, enums, generics, modules, and visibility to express valid states.
Codex Skills for Rust help Codex work through ownership, lifetimes, traits, errors, concurrency, Cargo workspaces, unsafe boundaries, testing, and performance. Download the skills for Rust code that needs clear invariants and evidence from the compiler and toolchain.
task: complete rust development task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong rust development work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for rust development while preserving local conventions, important constraints, and human review.
Use ownership, borrowing, lifetimes, traits, enums, generics, modules, and visibility to express valid states.
Model recoverable failures, propagate context, manage cleanup, and avoid panics in ordinary control flow.
Work with threads, channels, synchronization, async runtimes, cancellation, Send, Sync, and bounded resources.
Use formatting, Clippy, tests, documentation tests, benchmarks, sanitizers, and audits where appropriate.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Read Cargo metadata, features, targets, editions, MSRV, workspace structure, unsafe code, and tests.
Define ownership, lifetimes, thread safety, error contracts, resource limits, and compatibility.
Prefer clear types and narrow unsafe boundaries, then document non-obvious decisions.
Compile feature combinations, test, lint, document, benchmark, and examine unsafe or concurrency risks.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Build low-level libraries, agents, services, parsers, storage, networking, and resource-sensitive tools.
Create dependable commands, structured errors, configuration, streams, and distributable binaries.
Develop networked applications with runtime-aware tasks, cancellation, timeouts, and backpressure.
Prepare Rust modules and bindings for browser or portable runtime environments.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable rust development work with a visible process.
Build crates, services, tools, tests, and performance improvements.
Use types and invariants to control memory, concurrency, and integration risks.
Develop efficient services with explicit error and lifecycle behavior.
Understand ownership, borrowing, traits, errors, concurrency, Cargo, and testing.
The skills help with Rust engineering, but unsafe code, cryptography, FFI, security-sensitive systems, and production performance require specialist review.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included rust development guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this rust development work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
Yes. They trace ownership and lifetime intent instead of applying clones blindly.
Yes. They follow the runtime already selected and account for cancellation and blocking work.
They can isolate and document it, but safety invariants require careful expert review.
Yes. They inspect features, packages, targets, lockfiles, and workspace dependencies.
They benchmark and profile before changing allocations, data layout, algorithms, or concurrency.
Clear context. Purposeful work. Relevant checks. A result others can understand.