By zhengwu119
Comprehensive Rust development assistant with meta-question routing, coding guidelines, version queries, and ecosystem support
Heavy-weight security and safety audit using os-checker tools.
Clean Rust docs cache
Show Rust docs cache status
Remove dynamically generated crate skills from the local skills directory.
Get information about a Rust crate including latest version, features, and changelog.
Common web fetching strategy for anti-crawler handling.
Generic web content fetcher.
Fetch Clippy lint information.
Fetch crate metadata from lib.rs / crates.io.
Documentation cache helper for agents.
CRITICAL: Use for generics, traits, zero-cost abstraction. Triggers: E0277, E0308, E0599, generic, trait, impl, dyn, where, monomorphization, static dispatch, dynamic dispatch, impl Trait, trait bound not satisfied, 泛型, 特征, 零成本抽象, 单态化
CRITICAL: Use for type-driven design. Triggers: type state, PhantomData, newtype, marker trait, builder pattern, make invalid states unrepresentable, compile-time validation, sealed trait, ZST, 类型状态, 新类型模式, 类型驱动设计
For fetching Rust/crate information, use this priority order:
CRITICAL: Use for mutability issues. Triggers: E0596, E0499, E0502, cannot borrow as mutable, already borrowed as immutable, mut, &mut, interior mutability, Cell, RefCell, Mutex, RwLock, 可变性, 内部可变性, 借用冲突
Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI-powered Rust development assistant with meta-cognition framework
Rust Skills is a Claude Code plugin that transforms how AI assists with Rust development. Instead of giving surface-level answers, it traces through cognitive layers to provide domain-correct architectural solutions.
Traditional AI assistance for Rust:
User: "My trading system reports E0382"
AI: "Use .clone()" ← Surface fix, ignores domain constraints
Rust Skills with meta-cognition:
User: "My trading system reports E0382"
AI (with Rust Skills):
├── Layer 1: E0382 = ownership error → Why is this data needed?
│ ↑
├── Layer 3: Trade records are immutable audit data → Should share, not copy
│ ↓
├── Layer 2: Use Arc<TradeRecord> as shared immutable value
│ ↓
└── Recommendation: Redesign as Arc<T>, not clone()
This method enables all features including hooks for automatic meta-cognition triggering.
# Clone the repository
git clone https://github.com/ZhangHanDong/rust-skills.git
# Launch with plugin directory
claude --plugin-dir /path/to/rust-skills
This method only installs skills without hooks. You need to manually invoke skills.
# Clone and copy skills
git clone https://github.com/ZhangHanDong/rust-skills.git
cp -r rust-skills/skills/* ~/.claude/skills/
⚠️ Note: Without hooks, meta-cognition won't trigger automatically. You must manually call
/rust-routeror specific skills.
| Feature | Full Plugin | Skills Only |
|---|---|---|
| All Skills | ✅ | ✅ |
| Auto meta-cognition trigger | ✅ | ❌ |
| Hook-based routing | ✅ | ❌ |
| Background agents | ✅ | ✅ |
Background agents require permission to run agent-browser. Configure in your project:
# Copy example config
cp /path/to/rust-skills/.claude/settings.example.json .claude/settings.local.json
Or create manually:
mkdir -p .claude
cat > .claude/settings.local.json << 'EOF'
{
"permissions": {
"allow": [
"Bash(agent-browser *)"
]
}
}
EOF
See .claude/settings.example.json for reference.
Don't answer directly. Trace through cognitive layers first.
Layer 3: Domain Constraints (WHY)
├── Domain rules determine design choices
└── Example: Financial systems require immutable, auditable data
Layer 2: Design Choices (WHAT)
├── Design patterns and architectural decisions
└── Example: Use Arc<T> for shared immutable data
Layer 1: Language Mechanics (HOW)
├── Rust language features and compiler rules
└── Example: E0382 is a symptom of ownership design issues
| User Signal | Entry Layer | Trace Direction | Primary Skill |
|---|---|---|---|
| E0xxx errors | Layer 1 | Trace UP ↑ | m01-m07 |
| "How to design..." | Layer 2 | Bidirectional | m09-m15 |
| "[Domain] app development" | Layer 3 | Trace DOWN ↓ | domain-* |
| Performance issues | Layer 1→2 | Up then Down | m10-performance |
rust-router - Master router for all Rust questions (invoked first)rust-learner - Fetch latest Rust/crate version infocoding-guidelines - Coding conventions lookup| Skill | Core Question | Triggers |
|---|---|---|
| m01-ownership | Who should own this data? | E0382, E0597, move, borrow |
| m02-resource | What ownership pattern fits? | Box, Rc, Arc, RefCell |
| m03-mutability | Why does this data need to change? | mut, Cell, E0596, E0499 |
| m04-zero-cost | Compile-time or runtime polymorphism? | generic, trait, E0277 |
| m05-type-driven | How can types prevent invalid states? | newtype, PhantomData |
| m06-error-handling | Expected failure or bug? | Result, Error, panic, ? |
| m07-concurrency | CPU-bound or I/O-bound? | async, Send, Sync, thread |
npx claudepluginhub zhengwu119/rust-skillsEvidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.9.0 with optional Serena LSP intelligence. Includes blast-radius planning, test/cycle gates, independent review, and Windows Git Bash hook auto-resolution.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Complete developer toolkit for Claude Code