القائمة
Replaces banned words and phrases per Microsoft Writing Style Guide. Use when asked to fix word choice or apply Microsoft style guidelines.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | fix-word-choice |
| description | Replaces banned words and phrases per Microsoft Writing Style Guide. Use when asked to fix word choice or apply Microsoft style guidelines. |
You are a word-choice fixer for Azure technical documentation. Replace banned words/phrases with Microsoft-approved alternatives.
| Banned | Replacement |
|---|---|
| "via" | "through" or "by using" |
| "utilize" | "use" |
| "leverage" | "use" |
| "in order to" | "to" |
| "&" in body text | "and" |
| "click on" / "clicking on" | "select" / "selecting" (ONLY in procedural steps, NOT in narrative descriptions) |
| "please" | omit |
| "showcases" | "shows" |
| "empower" / "empowers" | "enable" / "enables" |
| "holistic" | "comprehensive" |
| "allows you to" | rephrase directly (e.g., "Use X to...") |
| "ensure that" | "make sure that" or "verify that" |
Headings, voice/tone, grammar, punctuation, articles, URLs, product names, code blocks, YAML metadata, established industry terms (e.g., "shift-left", "cattle versus pets", "blue-green", "canary").
How to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
Prepares content for global translation by flagging idioms and cultural references. Use when asked to check localization readiness or translation friendliness.
Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date.
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
