Agent skill

m11-ecosystem

Use when integrating crates or ecosystem questions. Keywords: E0425, E0433, E0603, crate, cargo, dependency, feature flag, workspace, which crate to use, using external C libraries, creating Python extensions, PyO3, wasm, WebAssembly, bindgen, cbindgen, napi-rs, cannot find, private, crate recommendation, best crate for, Cargo.toml, features, crate 推荐, 依赖管理, 特性标志, 工作空间, Python 绑定

View SKILL.md on GitHub Repository
Stars 941
Forks 87

Install this agent skill to your Project

npx add-skill https://github.com/actionbook/rust-skills/tree/main/skills/m11-ecosystem

SKILL.md

Current Dependencies (Auto-Injected)

!grep -A 100 '^\[dependencies\]' Cargo.toml 2>/dev/null | head -30 || echo "No Cargo.toml found"

Ecosystem Integration

Layer 2: Design Choices

Core Question

What's the right crate for this job, and how should it integrate?

Before adding dependencies:

  • Is there a standard solution?
  • What's the maintenance status?
  • What's the API stability?

Integration Decision → Implementation

Need Choice Crates
Serialization Derive-based serde, serde_json
Async runtime tokio or async-std tokio (most popular)
HTTP client Ergonomic reqwest
HTTP server Modern axum, actix-web
Database SQL or ORM sqlx, diesel
CLI parsing Derive-based clap
Error handling App vs lib anyhow, thiserror
Logging Facade tracing, log

Thinking Prompt

Before adding a dependency:

  1. Is it well-maintained?

    • Recent commits?
    • Active issue response?
    • Breaking changes frequency?

  2. What's the scope?

    • Do you need the full crate or just a feature?
    • Can feature flags reduce bloat?

  3. How does it integrate?

    • Trait-based or concrete types?
    • Sync or async?
    • What bounds does it require?

Trace Up ↑

To domain constraints (Layer 3):

"Which HTTP framework should I use?"
    ↑ Ask: What are the performance requirements?
    ↑ Check: domain-web (latency, throughput needs)
    ↑ Check: Team expertise (familiarity with framework)
Question Trace To Ask
Framework choice domain-* What constraints matter?
Library vs build domain-* What's the deployment model?
API design domain-* Who are the consumers?

Trace Down ↓

To implementation (Layer 1):

"Integrate external crate"
    ↓ m04-zero-cost: Trait bounds and generics
    ↓ m06-error-handling: Error type compatibility

"FFI integration"
    ↓ unsafe-checker: Safety requirements
    ↓ m12-lifecycle: Resource cleanup

Quick Reference

Language Interop

Integration Crate/Tool Use Case
C/C++ → Rust bindgen Auto-generate bindings
Rust → C cbindgen Export C headers
Python ↔ Rust pyo3 Python extensions
Node.js ↔ Rust napi-rs Node addons
WebAssembly wasm-bindgen Browser/WASI

Cargo Features

Feature Purpose
[features] Optional functionality
default = [...] Default features
feature = "serde" Conditional deps
[workspace] Multi-crate projects

Error Code Reference

Error Cause Fix
E0433 Can't find crate Add to Cargo.toml
E0603 Private item Check crate docs
Feature not enabled Optional feature Enable in features
Version conflict Incompatible deps cargo update or pin
Duplicate types Different crate versions Unify in workspace

Crate Selection Criteria

Criterion Good Sign Warning Sign
Maintenance Recent commits Years inactive
Community Active issues/PRs No response
Documentation Examples, API docs Minimal docs
Stability Semantic versioning Frequent breaking
Dependencies Minimal, well-known Heavy, obscure

Anti-Patterns

Anti-Pattern Why Bad Better
extern crate Outdated (2018+) Just use
#[macro_use] Global pollution Explicit import
Wildcard deps * Unpredictable Specific versions
Too many deps Supply chain risk Evaluate necessity
Vendoring everything Maintenance burden Trust crates.io

Related Skills

When See
Error type design m06-error-handling
Trait integration m04-zero-cost
FFI safety unsafe-checker
Resource management m12-lifecycle

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

actionbook/rust-skills

meta-cognition-parallel

EXPERIMENTAL: Three-layer parallel meta-cognition analysis. Triggers on: /meta-parallel, 三层分析, parallel analysis, 并行元认知

941 87
Explore
actionbook/rust-skills

domain-cloud-native

Use when building cloud-native apps. Keywords: kubernetes, k8s, docker, container, grpc, tonic, microservice, service mesh, observability, tracing, metrics, health check, cloud, deployment, 云原生, 微服务, 容器

941 87
Explore
actionbook/rust-skills

m07-concurrency

CRITICAL: Use for concurrency/async. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁

941 87
Explore
actionbook/rust-skills

unsafe-checker

CRITICAL: Use for unsafe Rust code review and FFI. Triggers on: unsafe, raw pointer, FFI, extern, transmute, *mut, *const, union, #[repr(C)], libc, std::ffi, MaybeUninit, NonNull, SAFETY comment, soundness, undefined behavior, UB, safe wrapper, memory layout, bindgen, cbindgen, CString, CStr, 安全抽象, 裸指针, 外部函数接口, 内存布局, 不安全代码, FFI 绑定, 未定义行为

941 87
Explore
actionbook/rust-skills

rust-refactor-helper

Safe Rust refactoring with LSP analysis. Triggers on: /refactor, rename symbol, move function, extract, 重构, 重命名, 提取函数, 安全重构

941 87
Explore
actionbook/rust-skills

rust-skill-creator

Use when creating skills for Rust crates or std library documentation. Keywords: create rust skill, create crate skill, create std skill, 创建 rust skill, 创建 crate skill, 创建 std skill, 动态 rust skill, 动态 crate skill, skill for tokio, skill for serde, skill for axum, generate rust skill, rust 技能, crate 技能, 从文档创建skill, from docs create skill

941 87
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results