sdn0303/rust-backend-rules
.agents/skills/rust-backend-rules/SKILL.md
Comprehensive Rust coding guidelines for Axum/Tokio/SQLx backends. 179 rules across ownership, error handling, memory optimization, API design, async patterns, testing, linting, and anti-patterns. Use when writing, reviewing, or refactoring Rust code, Cargo settings, or services/backend code.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add sdn0303/terrasight rust-backend-rulesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:30 PM4.3s1 file scanned
SKILL.md
- name:
- rust-backend-rules
- description:
- Comprehensive Rust coding guidelines for Axum/Tokio/SQLx backends. 179 rules across ownership, error handling, memory optimization, API design, async patterns, testing, linting, and anti-patterns. Use when writing, reviewing, or refactoring Rust code, Cargo settings, or services/backend code.
- version:
- 1.0.0
Rust Backend Rules
Production Rust guidance for this repository. The full source rulebook is copied verbatim in references/rust-rules.md; keep SKILL.md lean and open the reference file only for the categories you need.
When to Apply
- Writing or refactoring Rust in
services/backend - Reviewing Rust diffs for correctness, performance, and maintainability
- Designing error types, async flows, or public APIs
- Changing
Cargo.toml, profiles, linting, or project structure - Investigating clone pressure, allocation cost, or borrow checker friction
Repository Invariants
- No
.unwrap()in non-test code; prefer?orexpect("invariant") - Keep
src/domain/pure with zero external dependencies - Prefer borrowing over cloning; accept
&str/&[T]over&String/&Vec<T> - Use explicit error types in reusable/library layers; allow
anyhowonly at app boundary - Verify with
cargo fmt,cargo clippy -- -D warnings, andcargo test
Priority Order
| Priority | Category | Prefix | Notes |
|----------|----------|--------|-------|
| 1 | Ownership & Borrowing | own- | Remove unnecessary clones, design for slices/borrows first |
| 2 | Error Handling | err- | Propagate context, avoid panics in production |
| 3 | Memory Optimization | mem- | Cut allocations only after measuring |
| 4 | API Design | api- | Clear types, builders, trait boundaries, DTO shape |
| 5 | Async/Await | async- | Avoid holding locks/borrows across .await |
| 6 | Compiler Optimization | opt- | Profile first; prefer evidence over folklore |
| 7 | Naming Conventions | name- | Keep APIs readable and idiomatic |
| 8 | Type Safety | type- | Encode invariants in types |
| 9 | Testing | test- | Cover success path, failure path, and regressions |
| 10 | Documentation | doc- | Document panics, errors, and public contracts |
| 11 | Performance Patterns | perf- | Focus on hot paths and measurable impact |
| 12 | Project Structure | struct- | Keep module boundaries intentional |
| 13 | Clippy & Linting | lint- | Treat warnings as design feedback |
| 14 | Anti-patterns | anti- | Use during review to catch regressions fast |
How to Use the Full Rules
- Pick the relevant prefix from the table above.
- Open only the matching sections in
references/rust-rules.md. - Apply the rule together with this repo's local constraints from
AGENTS.md.
Useful search patterns:
^# own-for ownership and borrowing^# err-for error handling^# async-for async/Tokio patterns^# anti-for code review sweeps^# err-no-unwrap-prodfor the repo's no-unwrap invariant
Minimal Review Checklist
- Are ownership and lifetime choices minimizing allocations instead of hiding them with
.clone()? - Are failure modes explicit, contextualized, and test-covered?
- Does async code avoid lock guards, mutable borrows, or heavy CPU work across
.await? - Are public APIs accepting the most general borrowed types possible?
- Was any performance-related change justified by measurement?
Related Skills
sdn0303/rust-backend-rules
development
VerifiedTrustedCommunity
Rust coding rules for Axum/Tokio/SQLx backends in services/backend. 179 rules split into 14 category files covering ownership, error handling, async, API design, and more. Use when writing, reviewing, or refactoring Rust code, designing error types, async flows, or public APIs.
SKILL.mdUpdated Apr 16, 2026
sdn0303/postgresql-patterns
content-media
VerifiedTrustedCommunity
PostgreSQL and PostGIS patterns for schema design, spatial queries, query optimization, indexing, and zero-downtime migrations. Use when writing SQL, creating tables, optimizing queries, or writing migration files.
SKILL.mdUpdated Apr 16, 2026
sdn0303/mapbox-gl-js
development
VerifiedTrustedCommunity
Mapbox GL JS v3 development patterns for real estate data visualization. Use when working with Mapbox maps, Standard Style configuration, layer slots, 3D lighting, expressions, react-map-gl/mapbox integration, or migrating from MapLibre GL JS.
SKILL.mdUpdated Apr 16, 2026
sdn0303/geospatial-dev
development
VerifiedTrustedCommunity
MapLibre GL JS + PostGIS integration patterns for real estate data visualization. Use when working on map layers, spatial queries, GeoJSON data pipelines, or 3D extrusion effects.
SKILL.mdUpdated Apr 16, 2026