CLAUDE.md: зафиксирован рабочий режим — CAD-задачи как полигон

Три канала обратной связи (патч в src, новый общий тул, правка навыков),
правило «навыки отлаживаются как код» с source of truth в plugin/skills,
запрет утечки внутреннего в публикуемые навыки и ловушка с залоченным
kompas-mcp.exe при пересборке.

CLAUDE.md

@@ -60,6 +60,32 @@ a *general* tool with tests, and describe the method in the `kompas-3d` skill.
 - **Known caveat:** boss/cut direction on a *selected face* depends on the face-normal orientation —
   `forward` may need flipping. Pick the direction from `describe_face` normal or a snapshot before building.
 
+## Working mode: CAD tasks are the proving ground
+
+The user solves small CAD tasks through the MCP tools (or uses the server as an assistant), but **the point
+of those tasks is improving the server and its skills**, not the part being modelled. A task that goes badly
+is a bug report, not a reason to work around it by hand. Three feedback channels, not one:
+
+| Symptom | Where the fix goes |
+|---|---|
+| A tool crashes or returns the wrong result | `src/` → patch + test |
+| No tool exposes the mechanism at all | `src/` → a new **general** tool (never case-specific) |
+| Tools worked, but the route taken was wrong / a trap was unknown | `plugin/skills/kompas-3d/SKILL.md` |
+| Geometry built fine but isn't printable on FDM | `plugin/skills/kompas-fdm-design/` (+ `references/`) |
+
+Reading the sources, proposing patches, editing and rebuilding are all explicitly sanctioned — including
+asking for a session restart when a rebuilt server has to be picked up.
+
+- **Skills are debugged like code.** `kompas-3d` and `kompas-fdm-design` are objects of revision, not fixed
+  inputs. Edit them **only** in `plugin/skills/<name>/` (the source of truth — the other trees are junctions);
+  a skill edit needs no rebuild but is only picked up by a *new* session.
+- **Nothing internal leaks into a published skill** — no local SDK paths, no `usecases/`, no RAG-base
+  references. Internal findings belong in `kompas-mcp-dev`; only reproducible methodology ships.
+- **Rebuild locks the binary.** In a session where `.mcp.json` points `kompas` straight at
+  `src/Kompas.Mcp.Host/bin/x64/Release/net8.0-windows/kompas-mcp.exe`, the running server holds that file —
+  `dotnet build -c Release` fails with «file in use» until the process dies. So batch the changes:
+  accumulate patches → end the session → build → restart → re-run the scenario.
+
 ## Skills and their layout
 
 - **`kompas-3d`** — methodology for *building* things through the MCP tools (playbooks, heuristics).