Merge remote-tracking branch 'upstream/development' into development

Author: github-actions[bot]

.claude/scripts/README.md

@@ -0,0 +1,38 @@
+# Claude Helper Scripts
+
+Utility scripts to support Claude Code when working with this documentation repository.
+
+## resolve-doc-url.sh
+
+Resolves a documentation URL to its source markdown file.
+
+### Usage
+
+```bash
+.claude/scripts/resolve-doc-url.sh "/path/to/page/"
+```
+
+### Examples
+
+```bash
+# Find the file for a specific URL
+.claude/scripts/resolve-doc-url.sh "/community-tools/contribute-to-mendix-docs/"
+# Output: content/en/docs/community-tools/contribute-to-mendix-docs/_index.md
+
+# Check if a URL exists
+.claude/scripts/resolve-doc-url.sh "/some/page/"
+# Exit code 0 if found, 1 if not found
+```
+
+### Benefits
+
+- **Fast**: Uses grep optimized for file-only output
+- **Token-efficient**: Returns only the file path, no surrounding context
+- **Reliable**: Matches exact URL in front matter using fixed-string search
+
+### When to Use
+
+- Following cross-references between documentation pages
+- Validating internal links
+- Finding files by their published URL
+- Checking if a URL is already in use

.claude/scripts/resolve-doc-url.sh

@@ -0,0 +1,15 @@
+#!/bin/bash
+# Resolve a documentation URL to its source markdown file
+# Usage: resolve-doc-url.sh "/path/to/page/"
+
+if [ -z "$1" ]; then
+    echo "Usage: resolve-doc-url.sh <url>"
+    echo "Example: resolve-doc-url.sh '/community-tools/contribute-to-mendix-docs/'"
+    exit 1
+fi
+
+# Search for the URL in front matter
+# Using grep with -l (files only) and -F (fixed string) for speed
+grep -rl --include="*.md" "^url: $1$" content/en/docs/
+
+# Exit code 0 if found, 1 if not found

.claude/skills/add/SKILL.md .claude/skills/docs-add/SKILL.md.claude/skills/add/SKILL.md renamed to .claude/skills/docs-add/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: add
-description: Adds new content to existing documentation pages while preserving the original structure and meaning. Integrates new sections, paragraphs, or information smoothly with appropriate transitions. Use when the user wants to add, insert, include, or append new content to existing pages without rewriting what's already there.
+name: docs-add
+description: Adds new content to a single documentation page while preserving the original structure and meaning. Integrates new sections, paragraphs, or information smoothly with appropriate transitions. Use when the user wants to add, insert, include, or append new content to existing pages without rewriting what's already there.
 user-invocable: true
 disable-model-invocation: true
 ---
 
-> **After adding content:** Consider running `/polish` to improve clarity or `/proofread` to check for errors in the final result.
+> **After adding content:** Consider running `/docs-polish` to improve clarity or `/docs-proofread` to check for errors in the final result.
 
 Ask the user for the new content to add. Determine a suitable place to smoothly integrate the new content into the existing content, with appropriate transitions and formatting, while preserving the original meaning and structure of the page. Don't make changes to existing content unless necessary for clarity or coherence when adding the new content.
 

.claude/skills/enhance/SKILL.md .claude/skills/docs-enhance/SKILL.md.claude/skills/enhance/SKILL.md renamed to .claude/skills/docs-enhance/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: enhance
-description: Performs comprehensive editing including reorganization, restructuring, and rephrasing while preserving original meaning and intent. Improves flow, strengthens weak phrasing, and enhances overall quality. Use when documentation needs significant structural improvements, better organization, or when the user mentions reorganize, restructure, rewrite, or enhance.
+name: docs-enhance
+description: Comprehensively edits a single documentation page including reorganization, restructuring, and rephrasing while preserving original meaning and intent. Improves flow, strengthens weak phrasing, and enhances overall quality. Use when documentation needs significant structural improvements, better organization, or when the user mentions reorganize, restructure, rewrite, or enhance.
 user-invocable: true
 disable-model-invocation: true
 ---
 
-> **Skill progression:** This is the most intensive editing. If restructuring isn't needed, use `/polish` for clarity improvements or `/proofread` for basic fixes.
+> **Skill progression:** This is the most intensive editing. If restructuring isn't needed, use `/docs-polish` for clarity improvements or `/docs-proofread` for basic fixes.
 
 Perform holistic improvements, including reorganization and stronger phrasing, while preserving original intent. This goes beyond basic proofreading and polishing to enhance the overall quality and impact of the text. Consider restructuring sentences, paragraphs, or sections for better flow, replacing weak words with stronger alternatives, and improving clarity and consistency while maintaining the original meaning. However, avoid making changes just for the sake of change; every edit should serve a clear purpose in enhancing the text.

.claude/skills/docs-polish/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: docs-polish
+description: Proofreads a single documentation page and improves clarity, readability, and word choice without changing meaning or reorganizing structure. Simplifies complex sentences, applies style guide standards, and converts passive voice to active voice. Use when the user wants to polish, improve language and clarity, make more readable, check style guide compliance, or clean up documentation while preserving its structure.
+user-invocable: true
+disable-model-invocation: false
+---
+
+> **Skill progression:** This does everything `/docs-proofread` does plus clarity improvements and style guide enforcement. If only grammar and spelling fixes are needed, use `/docs-proofread`. For deeper reorganization, suggest `/docs-enhance`.
+
+Improve clarity and readability without changing meaning, structure, or paragraph order:
+
+**docs-polish should**:
+* Read Mendix style guides first (in parallel): `grammar-formatting.md`, `terminology.md`, and `product-naming-guide.md` from `/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/`
+* Fix all spelling, grammar, and punctuation errors
+* Add missing alt text to images (use simple, factual descriptions)
+* Ensure required front matter fields are present (title, url, description) and make descriptions concise and action-oriented
+* Fix broken Markdown syntax
+* Fix capitalization and terminology inconsistencies
+* Break up long, complex sentences for better readability
+* Simplify wordy or awkward phrasing
+* Improve word choice (more precise or accessible terms)
+* Change passive voice to active voice where appropriate
+* Remove bold and italics used for emphasis (reword or use alerts if needed)
+* Apply Mendix style guide standards (overrides the Microsoft Writing Style Guide)
+* Apply Microsoft Writing Style Guide standards, unless they conflict with the Mendix style guide standards
+
+**docs-polish should NOT**:
+* Move paragraphs or restructure sections (that's `/docs-enhance`)
+* Change technical meaning or accuracy
+* Significantly increase document length
+* Change command syntax, code identifiers, variable names, placeholders, or any other text that appears in code formatting (inline backticks or code blocks). Code-formatted text represents literal technical content that must remain unchanged. If you notice an issue with code-formatted text, flag it in the chat but don't edit it directly.
+
+Every edit should serve a clear purpose in making the text easier to read, scan, and understand.
+
+Priority order for determining scope:
+1. If the user has selected text in a file (check for `ide_selection` tags), only polish the selected text in that file. Don't polish the entire document.
+2. If there's one open file (check for `ide_opened_file` tags) and no selection, work on the entire file.
+3. If there are multiple open files, list them and ask which to process.
+4. If no files are open, ask for a file path.

.claude/skills/docs-pr-review/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: docs-pr-review
+description: Analyzes all changes in a pull request and generates suggestions for improvements, clarifications, inconsistencies, and structural changes without making any edits. Use when the user asks to review, analyze, audit, or provide feedback on a pull request, or when they want suggestions before making changes.
+user-invocable: true
+disable-model-invocation: false
+---
+
+Compare changes between the current branch and the base branch (typically `development`). Read the complete final state of each modified file, not just the diff, to ensure changes don't introduce inconsistencies with unchanged content.
+
+Analyze all the changes in the current pull request or branch and return a list of suggestions or questions about any points to clarify, potential inconsistencies, and sections to restructure, add, or remove. Read the whole of each document modified in the pull request to ensure the changes do not make inconsistencies.
+
+Follow links to other documents in the repo to check for inconsistencies if they seem to provide important related information.
+
+Do not worry about possible invalid internal links to anchors in the repo as these will be picked up by a separate testing tool after the site has been built.
+
+Make no edits.

.claude/skills/docs-proofread/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: docs-proofread
+description: Checks a single documentation page and fixes spelling, grammar, punctuation, basic Markdown formatting, and required front matter fields. Makes minimal corrections without rewording or restructuring. Use when the user asks to proofread, check for spelling and grammar errors, or fix typos.
+user-invocable: true
+disable-model-invocation: false
+---
+
+> **Skill progression:** This is the lightest touch. If more clarity and style guide work is needed, suggest `/docs-polish`. For deeper restructuring, suggest `/docs-enhance`.
+
+Do NOT rewrite, rephrase, or improve clarity. Proofread only:
+
+* **Spelling**: Fix typos and misspellings
+* **Grammar**: Fix grammatical errors (subject-verb agreement, tense consistency, etc.)
+* **Basic formatting checks**:
+  * Ensure required front matter fields are present (title, url, description)
+  * Fix broken Markdown syntax
+  * Fix any capitalization and terminology inconsistencies
+
+Do NOT:
+* Rewrite sentences for clarity or conciseness
+* Shorten or improve descriptions
+* Change passive voice to active voice
+* Simplify complex sentences
+* Reorganize content
+
+Priority order for determining scope:
+1. If the user has selected text in a file (check for `ide_selection` tags), only proofread the selected text in that file. Don't proofread the entire document.
+2. If there's one open file (check for `ide_opened_file` tags) and no selection, work on the entire file.
+3. If there are multiple open files, list them and ask which to process.
+4. If no files are open, ask for a file path.
+
+If you notice style or clarity issues that need improvement, finish proofreading first, then suggest that the user run `/docs-polish` for those improvements.

.claude/skills/docs-review/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: docs-review
+description: Analyzes a single documentation page and generates suggestions for improvements, clarifications, inconsistencies, and structural changes without making any edits. Use when the user asks to review, analyze, audit, or provide feedback on a documentation page or section, or when they want suggestions before making changes.
+user-invocable: true
+disable-model-invocation: false
+---
+
+Analyze the page and return a list of suggestions or questions about any points to clarify, potential inconsistencies, and sections to restructure, add, or remove. Make no edits.