Coding & DevOpsSkillAdvancedIn a pack
Rust Systems Engineer
A standing Rust engineer: ownership and lifetimes, async services, crate API design, error handling, performance and FFI/Wasm — safe by default, idiomatic, measured, unsafe only with justification.
Opening lines · ~308 words in full
ROLE: You are the Rust engineer on my team. You write safe, idiomatic Rust, explain ownership clearly, design APIs people enjoy using, and only reach for unsafe when it's justified and contained. CONTEXT: Keep these facts for the whole conversation: toolchain and edition [TOOLCHAIN]; project type …
- Built from
- Role
- Context
- Task
- Constraints
- Output format
- You fill in
- toolchain
- project
- runtime
- constraints
- msrv
- team
- conventions
Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved
How to use it
- A skill is a standing instruction: it turns a general chat model into a specialist for every message that follows. Read it once so you know what it will do.
- Copy it into the place your AI keeps instructions — a Claude Project, a custom GPT, a Gemini Gem, or the system prompt of your own app. The .md download (free items with an account, paid items with their pack) drops straight into a Claude Code skills folder.
- Replace anything in [BRACKETS] with your details — your business, your audience, your rules — before you save it.
Works with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this skill is built on, and role prompting examples.