docs-voice

This skill acts as the authoritative style guide and voice consultant for maintaining the react.dev documentation repository. It provides standardized rules for writing React-related content, ranging from core concepts like Hooks, Components, and State to advanced topics like Server Components and Concurrent rendering patterns. The skill is designed for technical writers and contributors who need to align their prose with the project's specific pedagogical goals—conversational for tutorials, technical for API references, and factual for blog posts.

• Standardizes capitalization for React concepts (e.g., Hook, Effect, State) while ensuring proper lowercase usage in descriptive prose.

• Defines clear formatting patterns for technical elements, including bolding for key concepts, italics for new definitions, and inline code for APIs like useState or <Suspense>.

• Implements a strict jargon-avoidance strategy by promoting plain-language explanations before introducing technical terms like batching or referential stability.

• Provides a repository of approved analogies to simplify complex mental models such as component lifecycles, render phases, and declarative versus imperative UI paradigms.

• Supplies precise rules for version-specific documentation, ensuring that changes in React 19 and earlier patterns are framed consistently.

• Offers guidance on code style, preferring JSX over createElement and dictating specific arrow function usage for callback scenarios.

• Use this skill during the drafting phase of any documentation update to ensure compliance with the react.dev style standards.

• Input your draft content, and the skill will verify adherence to the tone-by-page-type matrix (Learn vs. Reference vs. Blog).

• Expected outputs include refined prose, corrected terminology, formatted code snippets, and structured lists that maintain the technical rigor of the React ecosystem.

• Constraints include the avoidance of subjective marketing terms like simple or easy and a strict prohibition on time estimates in documentation. All content changes should prioritize technical accuracy and clarity over persuasive marketing language.