hdb:rust-dev

Coordinate multi-file Rust changes into a single compile pass.

1|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/hughdbrown/claude-skills --skill hdb-rust-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hdb:rust-dev
Source: https://github.com/hughdbrown/claude-skills/tree/main/hdb-rust-developer
Command: npx skills add https://github.com/hughdbrown/claude-skills --skill hdb-rust-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust development often suffers from long compile times that slow progress and erode feedback loops. This skill guides a batch-first workflow that coordinates multi-file changes and triggers a single compile pass, dramatically reducing turnaround.

Core Features & Use Cases

  • Batch-first code drafting: coordinate leaf modules, core logic, and integration points before compiling.
  • Cross-file planning: identify files to create or modify in dependency order and ensure consistency.
  • Real-world use: when adding a feature touching multiple crates, this skill yields a coherent plan that minimizes rewrites and retries.

Quick Start

Describe the Rust feature to implement and I will generate a batch-first plan that minimizes compile cycles.

Frequently Asked Questions about hdb:rust-dev

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

FAQPage Schema
How do I reduce Rust compile cycles when adding features across multiple modules?

Reduce Rust compile cycles by batching multi-file changes into a single compile pass. Coordinate edits across leaf modules, core logic, and integration points before triggering compilation to maximize throughput and minimize rewrites.

What is a batch-first Rust development workflow for AI-assisted coding?

A batch-first Rust workflow coordinates cross-file changes before compiling. It analyzes existing code, plans file creation and modification in dependency order, and batches fixes to ensure consistency and avoid repeated compile passes.

How do I plan multi-file changes in Rust to minimize rewrites and compile time?

Plan multi-file Rust changes by identifying files to create or modify in dependency order. Analyze existing code first, then coordinate edits across leaves, cores, and integration points to ensure consistency before a single compile pass.

Can I coordinate cross-file edits in Rust before running a single compile pass?

Yes, you can coordinate cross-file edits before compiling. This approach analyzes existing code, plans file creation and modification order, and batches fixes across modules to trigger only one compile pass for the entire feature.

Does batching Rust code changes work for features spanning multiple crates?

Batching Rust code changes works for features spanning multiple crates. It yields a coherent plan that coordinates multi-file edits across dependency boundaries, minimizing rewrites and retries during integration.

When should I avoid a batch-first approach to Rust compilation?

Avoid a batch-first approach when features are isolated to a single file or module, as the overhead of dependency analysis and cross-file planning provides minimal benefit without requiring coordinated multi-file edits.