actionbook/rust-skills/m11-ecosystem

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

Thinking Prompt

Before adding a dependency:

1. Is it well-maintained?

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

1. What's the scope?

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

1. 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)

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

Cargo Features

Error Code Reference

Crate Selection Criteria

Anti-Patterns

Related Skills