Rust Configs & Rules

Use a tiered testing approach—iterate quickly, validate thoroughly:

This file provides guidance for AI assistants (like Claude) when working with the Bencher codebase.

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

- LSP integration: You have access to `rust-analyzer`. Before refactoring, use "Go to Definition" or "Hover" to confirm type signatures, and rely as much as possible on deterministic refactors (e.g. use rust analyzer to rename.) - Diagnostics: Always check for compiler warnings/errors after writing...

```bash

1. **NEVER use mock frameworks or mock code:** - FORBIDDEN: `mockall`, `mock` libraries, or any mock implementations - FORBIDDEN: Mock structs, mock functions, or fake implementations - ALLOWED: Real integration tests with temporary files/directories - ALLOWED: Testing with actual data structures...

Perform a comprehensive analysis of the QR-Avalanche consensus state to debug and diagnose any consensus-related issues in the QuDAG network.

Commands for configuring and managing network routing in QuDAG with onion routing and traffic obfuscation.

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Native GUI popup renderer using egui framework. Renders JSON-defined popups as native windows.

Make sure you are not on the main branch. If so, then start by creating a dedicated new one. Use the [commit](./commit.md) command if there are any pending changes.

{ "mcpServers": { "Tool Manager MCP": { "type": "http", "url": "http://127.0.0.1:23847/mcp" } } }

Completes a partial specification implementation by addressing validation gaps and missing requirements.

---

--- name: fe-dev description: Use this agent when the user is developing or modifying frontend pages that need to integrate with backend APIs. This includes:\n\n<example>\nContext: User is implementing a new feature that requires frontend and backend integration.\nuser: "I need to create a user...

--- name: code-standards-reviewer description: Use this agent when you need to verify that recently written or modified code follows the project's established coding standards, patterns, and guidelines defined in the .claude folder. This includes checking Rust code against rust-core.md,...

Completes a partial specification implementation by addressing validation gaps and missing requirements.

- **Dependencies**: Use `default_features = false`; be conservative adding new deps - **Error handling**: Don't use `if let Ok` without a comment explaining why it's safe - **Patches**: Don't use `patch.crates-io` for SDK crates; use git references instead - **Feature gates**: Don't feature-gate...