update: clarification of found weak points.

CLAUDE.md

@@ -2,11 +2,9 @@
 
 ## General behaviour
 
-I'm an engineer. I know what I want. You must not propose next actions, unless I ask for that.
-
 - Read memory files before creating any plan.
 - Single sentence questions are not commands, answer and wait for instructions. Do not initiate actions after being asked.
-- Comments pointing to a bug or misunderstood action must be considered as requests to fix the problem, not as a request to explain the problem.
+- Comments pointing to a bug or misunderstood action must be considered as requests to analyze the problem and provide a solution or options, and are not a call to make a change.
 
 ## Exploration
 
@@ -17,15 +15,15 @@ I'm an engineer. I know what I want. You must not propose next actions, unless I
 ## General editing
 
 - Use available edit tools like Read, ReadFile, Edit, EditFile, Write, WriteFile, etc.
-- Don't use Python, scripting languages or command-line tools to edit-create-write content unless asked or given permission.
+- Bulk edits must always be justified and then approved by the user before execution. Use Perl for bulk edits, unless instructed otherwise.
 
 ## Running command line utilities
 
-- Avoid creating single line multiple command invocations. These construct make it harder to configure allowed commands for the session.
+- Avoid creating single line multiple command invocations. These constructs make it harder to configure allowed commands for the session.
 
 ## Coding
 
-- Prefer using standard library functions or modules, unless instructed to do otherwise or minimize the size of generated code.
+- Prefer using standard library functions or modules in standalone scripts or utilites.
 - Avoid creating single use code fragments like functions, methods, etc.
 - Your built-in knowledge is most likely obsolete for APIs, command syntax and software versions. Check on-line upstream documentation, if in plan mode or asked by the end user at the start of the session.
 - Do not guess nor infere syntax, API, commands and arguments.
@@ -37,8 +35,8 @@ I'm an engineer. I know what I want. You must not propose next actions, unless I
 ### Documentation and code comments
 
 - Documentation (README.md, GUIDE.md, docs/*, etc) describes the current state and does not include past state nor things that are missing.
-- Reasoning and decision explanations go to the ADR.md - architecture decision records file if it has been created by the user.
+- Reasoning and decision explanations related to the current state of the codebase/repository - go to the ADR.md. ADR is not for documenting history of the decisions.
-- Change history goes to the CHANGELOG.md, if it has been created by the user.
+- Change history goes to the CHANGELOG.md.
 - Do not place documentation like content into comments.
 - Use heredocs to describe code fragments like functions, classes or methods.
 - Use terse single sentence comments to describe code paths and purpose of parts of the long functions or code blocks.
@@ -52,7 +50,7 @@ You will ocassionally be asked to translate a program from one language to anoth
 
 ### Terraform
 
-- Do not create passthrough output variables, e.g. in an object or modules that take an input, do not expose the exact same value as output.
+- Do not create passthrough output variables, e.g. in an object or modules that take an input, do not expose the exact same value as output, unless the output is used as an input to a report or will be passed to another tool or module.
 
 ## Markdown style