From f1abfd362c8c0bc7d62013116382e49e0cbabbd2 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 13 Oct 2026 18:37:19 +0000 Subject: [PATCH] AGENTS.md: statements about PyMoDAQ must be checked in the code Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_01Tdiso1u1ZhikSutj2Qs5Cg --- AGENTS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index fc1ef4a..5057520 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -45,7 +45,9 @@ python install-packages.py -d -qt pyside6 # choose the Qt backend (pyqt5, py Do not consider a task finished until `check_plugin` and `pytest` pass. Do not invent PyMoDAQ APIs: if a method or attribute is not in the base classes (`DAQ_Move_base`, `DAQ_Viewer_base`, `CustomExt`) or in an existing -plugin, look it up in the installed `pymodaq` package instead of guessing. +plugin, look it up in the installed `pymodaq` package instead of guessing. The same holds for what you write: a comment, +a docstring or a documentation sentence that says how PyMoDAQ behaves must come from reading the code that +implements it, not from memory or from a guess. If you could not verify something, say so. ## 3. Instrument plugins