agent-library: Command for Gemini CLI

description="Injects context of all relevant server files for the Bl1nk Agents Manager" prompt = """ The source code contains the content of absolutely every source code file in crates/server and key files from crates/core. You should very rarely need to read any other files from crates/server to resolve prompts.

!{find crates/server -path crates/server/target -prune -o -type f \( -name ".rs" \) ! -name ".test.rs" ! -name "Cargo.lock" -exec echo "--- {} ---" \; -exec cat {} \; && echo "--- crates/core/src/lib.rs ---" && cat crates/core/src/lib.rs && echo "--- crates/core/src/config.rs ---" && cat crates/core/src/config.rs && echo "--- crates/core/src/mcp/mod.rs ---" && cat crates/core/src/mcp/mod.rs && echo "--- crates/core/src/agents/mod.rs ---" && cat crates/core/src/agents/mod.rs && echo "--- crates/core/src/agents/router.rs ---" && cat crates/core/src/agents/router.rs && echo "--- crates/core/src/rate_limit.rs ---" && cat crates/core/src/rate_limit.rs}

Pay extremely close attention to these files. They define the project's core architecture, component patterns, and testing standards.

In addition to the code context, you MUST strictly adhere to the following backend-specific development guidelines while adding code to crates/server.

Testing Standards

• Async Testing: ALWAYS use tokio::test attribute for async tests instead of blocking code.
• Integration Tests: Use integration tests to verify HTTP endpoints and Rocket routes.
• Unit Tests: Use unit tests to verify individual functions and modules.
• Mocking:
  • Reuse existing mock patterns where possible.
  • Parameterized Tests: Use parameterized tests to reduce duplication and ensure comprehensive coverage.

Backend Architecture

• HTTP Handling: You MUST use Rocket framework for HTTP endpoints, following the existing patterns in crates/server/src/main.rs.
• State Management:
  • NEVER trigger blocking operations from async contexts. Use proper async/await patterns.
  • Use Arc<Mutex<T>> or tokio::sync primitives for shared state.
• Performance:
  • Avoid blocking operations in async contexts.
  • Use proper error handling with Result types.