skills.rest
Kevin-Liu-01
Kevin-Liu-01COMMUNITY
Explore all skills by this author →
Website𝕏@kevskgsGitHub

rust-neckbeard

Enforces Rust correctness and style across host-agent, enclave, and workspace crates.

16|3|Updated May 5, 2026
Search Tags:#style#rust#coding-standards#lint#raii#error-design
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill rust-neckbeard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-neckbeard
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/rust-neckbeard
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill rust-neckbeard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust correctness and style guidelines are enforced across host-agent, enclave, and workspace crates to help teams write safer, more maintainable Rust code and prevent common style violations.

Core Features & Use Cases

  • Enforces naming conventions for return values and public APIs, ensuring consistent readability.
  • Standardizes error design and visibility, guiding choice between thiserror vs anyhow and appropriate variants.
  • Emphasizes RAII discipline, must_use attributes, and fail-closed design to reduce runtime surprises.
  • Use Case: during writing, reviewing, or refactoring Rust code in host-agent, enclave, or packages/rust workspaces to retain a consistent Rust coding standard.

Quick Start

Review and apply Rust correctness and style rules to your host-agent, enclave, or workspace crates.

Frequently Asked Questions about rust-neckbeard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Rust coding standards for error design and visibility across workspace crates?▼

Standardize Rust error design by enforcing style rules for visibility and naming across host-agent, enclave, and workspace crates during writing, reviewing, or refactoring.

When should I use thiserror vs anyhow for Rust error handling?▼

Standardize Rust error design by choosing between thiserror and anyhow based on visibility rules and appropriate variant usage to ensure maintainable code.

Does this Rust linter apply RAII discipline and must_use attributes to prevent runtime surprises?▼

Yes, it emphasizes RAII discipline, must_use attributes, and fail-closed design to reduce runtime surprises, actively enforcing these constraints when you write or refactor Rust code.

Can I apply these Rust naming conventions to public APIs and return values?▼

Yes, you can enforce naming conventions for public APIs and return values to ensure consistent readability across all host-agent, enclave, and workspace Rust crates.

What is the best way to lint Rust code for fail-closed design and RAII discipline?▼

Lint Rust code for fail-closed design and RAII discipline by applying these style constraints from style.md and rust.mdx during your regular writing and refactoring workflow.

Related Skills

Explore More Software Engineering Skills→
iamcapoteiamcapote

setup-stellar-contracts

Automate Stellar Soroban contract setup with Rust toolchains and OpenZeppelin crates.

Community
Advanced
actionbookactionbook
1.4k

coding-guidelines

Standardize Rust naming, formatting, and linting conventions across codebases.

Official
Basic
heikopanjasheikopanjas

rust-conventions

Apply Rust coding conventions to error handling, RAII, naming, and editions.

Community
Intermediate
systempromptiosystempromptio
24

Rust Standards

Enforce Rust coding standards with cargo clippy and cargo fmt.

Official
Advanced