technical-clarity

Technical clarity improves accessibility by analyzing readability gaps, defining jargon on first use, and adjusting language for specific audience levels. It reviews API references, guides, and manuals to ensure terms are introduced before use and examples precede abstract rules, removing gatekeeping barriers that block comprehension.

Jargon management in technical clarity involves auditing terminology, defining each term on first use, and limiting undefined terms per paragraph. The Skill identifies where terms lack definitions and recommends concrete examples before abstract explanations, ensuring readers at all levels grasp concepts.

A readability gap analysis compares your documentation against specific learner levels—such as A2 readers or domain novices—and identifies opacity points where language, structure, or missing examples prevent comprehension. The Skill delivers actionable rewrite recommendations with concrete examples justifying each edit.

Yes. Technical clarity reviews onboarding content, user manuals, API references, and developer guides for both readability and accessibility, checking for alt text, semantic structure, and inclusive language while reducing gatekeeping and ensuring terms are defined on first use.

A readability review analyzes audience comprehension level, audits terminology for undefined jargon, checks whether examples precede explanations, and evaluates accessibility features like alt text and semantic structure. It returns targeted rewrite recommendations with justification and concrete inline examples for each gap.

Show-before-tell applies whenever learners benefit from concrete examples before abstract rules—especially in API references, developer guides, and onboarding content. Technical clarity identifies paragraphs where this pattern would improve comprehension and recommends placing examples first, then rules, to reduce cognitive load.