Update claude conf

Author: jgeudens

.claude/agents/build.md

@@ -3,14 +3,14 @@ name: build
 description: Compile the project using cmake and ninja. Use when code changes need to be built or when checking for compilation errors.
 tools: Bash
 model: Haiku
+effort: low
 ---
 
 Build the project from the project root.
 
-If the build directory doesn't exist yet, run:
-  mkdir -p build && cmake -GNinja -S . -B build
-
-Then always run:
+Run:
+  mkdir -p build
+  cmake -GNinja -S . -B build
   ninja -C build
 
 Report only errors and warnings. If the build succeeds, say so briefly.

.claude/agents/quality.md

@@ -3,6 +3,7 @@ name: quality
 description: Run pre-commit quality checks (clang-format, clang-tidy, clazy) on source files. Use after making code changes before finishing a task.
 tools: Bash
 model: Haiku
+effort: low
 ---
 
 Run quality checks from the project root.

.claude/agents/test-runner.md

@@ -3,6 +3,7 @@ name: test-runner
 description: Run the test suite with ctest. Use after making code changes to verify correctness. The project must be built first.
 tools: Bash
 model: Haiku
+effort: low
 ---
 
 Run the test suite from the project root:

CLAUDE.md

@@ -2,6 +2,8 @@
 
 ## Build
 
+> **Preferred workflow:** use the sub-agents (`@agent-build`, `@agent-test-runner`, `@agent-quality`) defined in `.claude/agents/` — see the [Development](#development) section. The commands below are provided as reference and fallback only.
+
 All commands run from the **project root** unless noted.
 
 **Requirements:** Qt 6, C++20, Ninja. Compiler flags: `-Wall -Wextra -Werror`.
@@ -34,7 +36,7 @@ clang-format -i src/path/to/file.cpp
 ./scripts/run_clazy.sh src/path/to/file.cpp
 ```
 
-**Always run pre-commit after making source file changes.** All three checks must pass before the work is done.
+Always use these agents rather than running the commands directly. After making source file changes: build, then run tests, then run quality checks, then run code review - all required steps must pass before the work is done.
 
 ## Project Structure
 
@@ -77,6 +79,7 @@ Enforced by `.clang-format` (Mozilla-based, C++20):
 - Prefer readability and maintainability over using the latest C++ features (avoid syntax sugar that may be less familiar to new contributors).
 - Avoid lambda expressions with more than 2 captures or multiple statements; use named functions instead for clarity.
 - Make sure to document public functions with brief Doxygen comments in the source file
+- Update json-rpc schema spec when updating json-rpc related code
 - Only use early return for error handling, avoid deep nesting
 - When fixing a bug, add a test that reproduces the issue before implementing the fix.