rust-sdk-specialist

Rust SDK development with zero-cost abstractions

509 stars

Best use case

rust-sdk-specialist is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Rust SDK development with zero-cost abstractions

Teams using rust-sdk-specialist should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/rust-sdk-specialist/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/sdk-platform-development/skills/rust-sdk-specialist/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/rust-sdk-specialist/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How rust-sdk-specialist Compares

Feature / Agentrust-sdk-specialistStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Rust SDK development with zero-cost abstractions

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Rust SDK Specialist Skill

## Overview

This skill specializes in developing high-performance Rust SDKs with zero-cost abstractions, memory safety guarantees, and async support through tokio or async-std.

## Capabilities

- Design Rust SDK architecture with traits and generics
- Implement async with tokio or async-std runtimes
- Configure cargo publishing to crates.io
- Ensure memory safety patterns without runtime overhead
- Design ergonomic APIs with builder patterns
- Implement proper error handling with thiserror/anyhow
- Support feature flags for optional functionality
- Configure no_std support where applicable

## Target Processes

- Multi-Language SDK Strategy
- SDK Architecture Design
- SDK Testing Strategy

## Integration Points

- crates.io package registry
- cargo for building and testing
- tokio async runtime
- reqwest/hyper for HTTP
- serde for serialization
- tracing for observability

## Input Requirements

- API specification
- Async runtime preference (tokio/async-std)
- MSRV (Minimum Supported Rust Version)
- Feature flag requirements
- no_std requirements (if any)

## Output Artifacts

- Rust crate source code
- Cargo.toml configuration
- Integration and unit tests
- Examples directory
- Documentation (rustdoc)
- CI configuration

## Usage Example

```yaml
skill:
  name: rust-sdk-specialist
  context:
    apiSpec: ./openapi.yaml
    msrv: "1.70"
    asyncRuntime: tokio
    httpClient: reqwest
    errorHandling: thiserror
    features:
      - blocking
      - native-tls
      - rustls
```

## Best Practices

1. Use traits for abstraction without overhead
2. Implement From/Into for type conversions
3. Provide both async and blocking APIs via features
4. Use the newtype pattern for type safety
5. Document with rustdoc and examples
6. Follow Rust API guidelines

Related Skills

typescript-sdk-specialist

509
from a5c-ai/babysitter

TypeScript SDK development with Node.js and browser support. Design SDK architecture, implement type-safe API clients, support ESM and CommonJS modules, and configure bundling for browsers.

python-sdk-specialist

509
from a5c-ai/babysitter

Python SDK development with async support and type hints

java-sdk-specialist

509
from a5c-ai/babysitter

Java SDK development for enterprise environments

go-sdk-specialist

509
from a5c-ai/babysitter

Go SDK development with idiomatic patterns

csharp-sdk-specialist

509
from a5c-ai/babysitter

C#/.NET SDK development with async patterns

process-builder

509
from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509
from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)

yolo

509
from a5c-ai/babysitter

Run Babysitter autonomously with minimal manual interruption.

user-install

509
from a5c-ai/babysitter

Install the user-level Babysitter Codex setup.

team-install

509
from a5c-ai/babysitter

Install the team-pinned Babysitter Codex workspace setup.

retrospect

509
from a5c-ai/babysitter

Summarize or retrospect on a completed Babysitter run.

resume

509
from a5c-ai/babysitter

Resume an existing Babysitter run from Codex.