[Claude PR] Add claude_feedbacks.md for writing style feedback (#1008)

* internal: add claude_feedbacks.md for writing style feedback

- Create claude_feedbacks.md to collect raw feedback about Claude's writing style
- Update CLAUDE.md to reference feedback file before writing new docs
- Add first feedback about avoiding overly marketing language

Co-authored-by: Ruben Fiszel <[email protected]>

* Update CLAUDE.md

* fix

* fix

* adjust

* Update writing_style_guide.md

Sentence case

---------

Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: Ruben Fiszel <[email protected]>
Co-authored-by: centdix <[email protected]>
Co-authored-by: centdix <[email protected]>
Co-authored-by: Henri Courdent <[email protected]>

Author: 4 people

CLAUDE.md

@@ -5,6 +5,7 @@ These guidelines ensure consistency and quality when writing or modifying Windmi
 ## Content
 
 - The doc should focus on the user experience, not on the engineering behind it, unless it's important (e.g. feature related to performance)
+- **Before writing new documentation, review @writing_style_guide.md for guidance about how to write good documentation**
 
 ## File structure and naming
 

writing_style_guide.md

@@ -0,0 +1,22 @@
+# Claude writing style guide
+
+This file contains writing style guidance when creating Windmill documentation. Review this guide before writing new documentation.
+
+## General writing style issues
+
+### Overly marketing language
+
+**Problem example:**
+"Windmill can automatically fill your script and flow input forms using AI to save you time and effort. This intelligent feature analyzes your form parameters and can populate them with contextually appropriate values based on your requirements."
+
+**Issues:**
+
+- Too long and verbose for technical documentation
+- Marketing language like "This intelligent feature" sounds promotional rather than technical
+- Users prefer concise, direct explanations over flowery descriptions
+
+**Better approach:**
+
+- Keep descriptions short and technical
+- Focus on what the feature does, not how "intelligent" or "smart" it is
+- Use straightforward language: "Windmill can auto-fill script and flow inputs using AI" instead of verbose marketing copy