rust-convention
Rust code convention reference. Load this skill when generating or modifying Rust source files (.rs).
What this skill does
# Rust Code Convention
---
## 1. Error Handling
### Library code → `thiserror`
Crates and public modules define concrete error types.
```rust
use thiserror::Error;
#[derive(Debug, Error)]
pub enum ParseError {
#[error("invalid header: {0}")]
InvalidHeader(String),
#[error("unexpected EOF at position {position}")]
UnexpectedEof { position: usize },
}
pub fn parse(input: &str) -> Result<Parsed, ParseError> {
// ...
}
```
### Application code → `anyhow`
Binaries and entry points propagate errors with `anyhow::Result`.
```rust
use anyhow::{Context, Result};
fn main() -> Result<()> {
let config = load_config()
.context("failed to load config")?;
run(config)?;
Ok(())
}
```
### Boundary rule
- Public module boundaries within the same crate follow the library rule
- `anyhow` is only used in `main`, CLI handlers, and test code
---
## 2. Panic-Free
`unwrap()`, `expect()`, `panic!()`, `todo!()`, `unimplemented!()`, `unreachable!()` are denied.
Enforced at compile time via `[lints.clippy]` deny rules.
### Replacement patterns
| Denied | Replacement |
|--------|-------------|
| `.unwrap()` | `?`, `.unwrap_or_default()`, `.ok_or_else(\|\| ...)` |
| `.expect("msg")` | `.context("msg")?` (anyhow) |
| `panic!("msg")` | `return Err(...)` |
| `todo!()` | Compile error or return an `unimplemented` error variant |
| `unreachable!()` | `unreachable` error variant, or eliminate impossible states via the type system |
### Example
```rust
// BAD
let value = map.get("key").unwrap();
// GOOD
let value = map.get("key")
.ok_or_else(|| AppError::MissingKey("key".into()))?;
```
---
## 3. Polymorphism — Trait vs Enum Dispatch
### Open (externally extensible) → Trait dispatch
Use when external crates need to add implementations.
```rust
pub trait Storage: Send + Sync {
fn get(&self, key: &str) -> Result<Option<Vec<u8>>, StorageError>;
fn put(&self, key: &str, value: &[u8]) -> Result<(), StorageError>;
}
// External crates can freely implement:
// impl Storage for RedisStorage { ... }
// impl Storage for S3Storage { ... }
```
### Closed (internally fixed) → Enum dispatch
Use when variants are fixed and dispatched via pattern matching.
```rust
pub enum Command {
Create { name: String },
Delete { id: u64 },
Update { id: u64, payload: Payload },
}
impl Command {
pub fn execute(&self, ctx: &Context) -> Result<(), AppError> {
match self {
Self::Create { name } => ctx.create(name),
Self::Delete { id } => ctx.delete(*id),
Self::Update { id, payload } => ctx.update(*id, payload),
}
}
}
```
### Decision criteria
- **"Should external crates be able to add variants of this type?"** → Yes: trait, No: enum
- Use `#[non_exhaustive]` on enums to allow future variant additions
---
## 4. Module Style
Use `{module}.rs` pattern. Do not use `mod.rs`.
```
src/
├── lib.rs
├── parser.rs # mod parser
├── parser/
│ ├── lexer.rs # mod parser::lexer (declared in parser.rs: mod lexer;)
│ └── token.rs # mod parser::token
└── config.rs # mod config
```
---
## 5. Naming Rules
| Target | Style | Example |
|--------|-------|---------|
| Files | snake_case | `order_handler.rs` |
| Types (struct, enum, trait) | PascalCase | `OrderHandler` |
| Functions, methods | snake_case | `process_order` |
| Constants | SCREAMING_SNAKE_CASE | `MAX_RETRY_COUNT` |
| Type parameters | Single uppercase or PascalCase | `T`, `Item` |
| Crate names | kebab-case (Cargo.toml) / snake_case (code) | `my-crate` / `my_crate` |
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.