Update cross links and make descriptins more consistent

Author: MarkvanMents

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

@@ -1,11 +1,11 @@
 ---
 name: docs-add
-description: Adds new content to an existing 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.
+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/docs-enhance/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: docs-enhance
-description: On a single documentation page, 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.
+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

@@ -5,9 +5,9 @@ user-invocable: true
 disable-model-invocation: false
 ---
 
-> **Skill progression:** This preserves structure. If only basic fixes are needed, use `/proofread`. For deeper reorganization, suggest `/enhance`.
+> **Skill progression:** This preserves structure. If only basic fixes are needed, use `/docs-proofread`. For deeper reorganization, suggest `/docs-enhance`.
 
-First, use the Skill tool to invoke the `proofread` skill.
+First, use the Skill tool to invoke the `docs-proofread` skill.
 
 Then immediately continue: improve clarity and readability without changing meaning, structure, or paragraph order:
 
@@ -22,7 +22,7 @@ Then immediately continue: improve clarity and readability without changing mean
 * Ensure consistent application of Microsoft Writing Style Guide
 
 **Polish should NOT**:
-* Move paragraphs or restructure sections (that's `/enhance`)
+* Move paragraphs or restructure sections (that's `/docs-enhance`)
 * Change technical meaning or accuracy
 * Significantly increase document length
 * Modify code samples (flag issues instead)

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

@@ -1,11 +1,11 @@
 ---
 name: docs-proofread
-description: In a documentation page, checks and fixes spelling, grammar, punctuation, basic Markdown formatting, alt text, and required front matter fields. Makes minimal technical corrections without rewording or restructuring. Use when the user asks to proofread, check for errors, fix typos, or perform a light technical review of documentation.
+description: Checks a single documentation page and fixes spelling, grammar, punctuation, basic Markdown formatting, alt text, and required front matter fields. Makes minimal technical corrections without rewording or restructuring. Use when the user asks to proofread, check for errors, fix typos, or perform a light technical review of documentation.
 user-invocable: true
 disable-model-invocation: false
 ---
 
-> **Skill progression:** This is the lightest touch. If more clarity work is needed, suggest `/polish`. For deeper restructuring, suggest `/enhance`.
+> **Skill progression:** This is the lightest touch. If more clarity work is needed, suggest `/docs-polish`. For deeper restructuring, suggest `/docs-enhance`.
 
 Proofread the document for technical correctness only. Do NOT rewrite, rephrase, or improve clarity:
 
@@ -24,4 +24,4 @@ Do NOT:
 * Simplify complex sentences
 * Reorganize content
 
-If you notice style or clarity issues that need improvement, finish proofreading first, then suggest that the user run `/polish` for those improvements.
+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

@@ -1,6 +1,6 @@
 ---
 name: docs-review
-description: Analyzes a 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 documentation, or when they want suggestions before making changes.
+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 documentation, or when they want suggestions before making changes.
 user-invocable: true
 disable-model-invocation: false
 ---

content/en/docs/community-tools/contribute-to-mendix-docs/using-ai-tools.md

@@ -50,11 +50,11 @@ Do not modify `.claude/settings.json` or other files in the `.claude/` directory
 
 This repository includes custom Claude Code skills optimized for documentation work:
 
-* `/proofread` - Checks spelling, grammar, punctuation, and basic Markdown formatting
-* `/polish` - Improves clarity, readability, and word choice without changing meaning
-* `/enhance` - Performs comprehensive editing including reorganization, restructuring, and stronger phrasing
-* `/review` - Analyzes documentation and generates suggestions for improvements
-* `/add` - Adds new content to an existing page while preserving original structure
+* `/docs-proofread` - Checks spelling, grammar, punctuation, and basic Markdown formatting
+* `/docs-polish` - Improves clarity, readability, and word choice without changing meaning
+* `/docs-enhance` - Performs comprehensive editing including reorganization, restructuring, and stronger phrasing
+* `/docs-review` - Analyzes documentation and generates suggestions for improvements
+* `/docs-add` - Adds new content to an existing page while preserving original structure
 
 These skills are available to all contributors using Claude Code with this repository.