Improve automated doc writing instructions

Author: 4ian

scripts/update-docs-from-commits.js

@@ -209,9 +209,19 @@ IMPORTANT CONSTRAINTS
 • NEVER create new files unless a major new feature truly requires it.
 • NEVER edit files outside docs/gdevelop5/.
 • Do NOT touch images or binary files.
-• Do not specify the default values. Don't feel forced to list all the properties of a behavior/object/condition/action: prefer to explain use cases, examples and how it's useful for the end user which will create a game with it.
 • If no documentation updates are needed, do nothing.
 
+IMPORTANT WRITING STYLE AND ARCHITECTURE CONSTRAINTS
+----------------------------------------------------
+
+• Do NOT document non-user-facing implementation details. Focus only on information
+  that is relevant to users creating games with GDevelop, not internal engine behavior.
+• Do NOT list all actions/conditions in a list or table: the reference documentations are already
+  automatically generated for this.
+• Do not specify the default values. Don't feel forced to list all the properties of a 
+  behavior/object/condition/action: prefer to explain use cases, examples and how it's useful
+  for the end user which will create a game with it.
+
 WHEN YOU ARE DONE
 -----------------
 1. Output a brief summary (2-3 lines) of the documentation changes you made,