CLAUDE.md for Rust (Axum)

Extractor ordering and Send bounds produce Axum compile errors that send agents in circles without guidance. Below is a complete, committable example for a typical Rust (Axum) project. To get one tailored to your dependencies and scripts, paste your manifest into the free generator (client-side, nothing uploaded) or run npx getagentready in your repo.

Complete example

# CLAUDE.md

This file guides Claude Code when working in this repository.

## Project

**example-server** — Stack: Rust, Axum, cargo test, Clippy, rustfmt.

## Commands

- Install dependencies: `cargo build`
- Build: `cargo build --release`
- Run all tests: `cargo test`
- Run a single test: `cargo test test_name`
- Lint: `cargo clippy -- -D warnings`
- Format: `cargo fmt`

## Testing

Tests use cargo test. Write or update tests alongside behavior changes; run the single-test command during iteration and the full suite before finishing.

## Conventions

- Share state via `State` extractors; convert errors into responses with a central `IntoResponse` error type.
- Prefer small, focused changes; do not refactor unrelated code in the same change.
- Match the existing code style of the file you are editing over any global preference.
- Never commit secrets. `.env*` files are local-only.
- After making changes, run the test and lint commands above before considering work done.

## Gotchas

- Handler type errors produce enormous compiler messages — check extractor order and `Send + Sync` bounds first.

<!-- generated with https://getagentready.dev -->

Going further

This is the generated baseline. The Agent-Ready Pro Pack includes a hand-tuned, deeper Rust (Axum) configuration — architecture guidance, testing strategy, common-task recipes — plus 12 workflow skills and enforcement hooks. See also the CLAUDE.md guide and AGENTS.md guide.