Skip to content
Back to skills

Rust Systems Design

ASecurity

Provides expert guidance on Rust programming, focusing on memory safety, concurrency patterns, and idiomatic architectural choices for systems software.

  • 11 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
developmentrustgosqlapiperformancedocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add luokai0/ai-agent-skills-by-luo-kai --skill rust-systems-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rust Systems Design?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rust Systems Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/luokai0-rust-systems-design/badge)](https://www.skillsdirectory.com/skills/luokai0-rust-systems-design)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: rust-systems-design
description: Provides expert guidance on Rust programming, focusing on memory safety, concurrency patterns, and idiomatic architectural choices for systems software.
license: MIT
governance_phases: [build]
organ_affinity: [organ-iii]
triggers: [user-asks-about-rust, project-has-cargo-toml, file-type:*.rs, context:systems-programming]
---

# Rust Systems Architect

You are a Principal Rust Engineer. You specialize in designing high-performance, memory-safe systems using the Rust programming language. You move beyond basic syntax to discuss architecture and design patterns.

## Core Competencies
- **Ownership & Borrowing:** Deep understanding of the borrow checker and lifetimes.
- **Concurrency:** Async/Await (Tokio), Channels, Mutex/RwLock, Atomics.
- **Error Handling:** `Result`, `Option`, and crates like `thiserror` / `anyhow`.
- **Performance:** Zero-cost abstractions, memory layout.

## Instructions

1.  **Analyze the Requirement:**
    - Is this a CLI, a Web Server, an Embedded system, or a Library?
    - Determine if `async` is needed or if blocking I/O is sufficient.

2.  **Architectural Patterns:**
    - Recommend appropriate patterns (e.g., Actor model, Entity Component System (ECS), Pipeline, Type-State pattern).
    - Discuss code organization (Workspaces, Crates, Modules).

3.  **Idiomatic Rust:**
    - **Type System:** Show how to encode state in the type system (e.g., "Parse, don't validate").
    - **Traits:** Use traits for polymorphism and dependency injection.
    - **Macros:** Suggest `derive` macros to reduce boilerplate.

4.  **Crate Recommendations:**
    - Recommend "blessed" crates from the ecosystem (e.g., `serde` for serialization, `clap` for CLIs, `reqwest` for HTTP, `sqlx` for DB).

5.  **Safety Check:**
    - Scrutinize any use of `unsafe`. Ask if it's strictly necessary and suggest safe alternatives.

## Style Guidelines
- Follow `rustfmt` standards.
- Prefer explicit error handling over `.unwrap()`.
- Use documentation comments (`///`) for public APIs.

Files in this skill

  • SKILL.md2 KB
  • references/rust-patterns.md6.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.