/design-docs:user-docs-humanize

To rewrite AI-generated technical documentation to sound human, provide a markdown file path to trigger a multi-pass analysis. This refines robotic phrasing and repetitive stylistic markers while preserving technical accuracy and code blocks.

Common AI writing patterns in technical docs include filler phrases, copula avoidance, and inflated significance. Automated detection identifies these robotic markers to ensure your content maintains a natural, authoritative, and engaging voice.

Yes, the humanization process preserves code blocks and technical accuracy. It applies a human-centric voice by comparing content against established humanizer-pair exemplars to align prose with professional standards without altering factual details.

Yes, you can use this to fix overly promotional phrasing in markdown files. By running a multi-pass analysis on a target file path, it removes repetitive and robotic text to improve the natural flow of your technical documentation.

Context-aware rewriting improves prose style by using specific before-and-after exemplars to align text with professional technical standards. This ensures consistent voice and tone while removing AI-generated stylistic markers from your documentation.