cloud-adoption-framework

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.

Rewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.

Ensures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.

Validates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.

Checks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.

Assesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.

Identifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.

Reviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.

Verifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.

Identifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.

Fixes commas, sentence-ending punctuation, dashes, and filler words per Microsoft Writing Style Guide. Use when asked to fix punctuation.

Identifies and fixes spelling errors, contextual typos, and agreement mistakes in Markdown documentation. Use this when asked to fix typos, correct spelling, or proofread documentation files.

Replaces banned words and phrases per Microsoft Writing Style Guide. Use when asked to fix word choice or apply Microsoft style guidelines.

Checks Markdown formatting including code fences, alert syntax, list markers, and table structure. Use when asked to lint or fix Markdown formatting.

Identifies structural and topical gaps in documentation — missing sections, absent code samples, missing diagrams, incomplete related content, and unaddressed scenarios. Use when asked to assess content completeness.

Enforces compound-adjective hyphens, articles, and prepositions per Microsoft Writing Style Guide. Use when asked to check grammar.

Enforces sentence case for all Markdown headings and bold sub-headings. Use when asked to fix heading capitalization.

Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.

Enforces parallel grammatical structure and consistent punctuation in lists. Use when asked to fix list formatting or consistency.

Validates SEO metadata quality — description length, title/H1 match, and ms.topic correctness. Use when asked to check SEO or metadata optimization.

Enforces current Microsoft product naming, handling renames and retirements. Use when asked to check product names or update terminology.

Validates technical steps, API syntax, and logical gaps in procedural guidance. Use when asked to review technical accuracy or verify procedures.

Detects stale dates, version numbers, and temporal language in body text. Use when asked to check for outdated dates or version references.