docs-voice · reactjs — Claude Code skill: what it does, how to install
docs-voice applies react.dev voice, tone, and formatting conventions to technical writing. Helps when authoring guides or API references for React.
CC-BY-4.0 ★ 11,851 updated 2026-10-20
npx skills add reactjs/react.dev --skill docs-voice -a claude-codeWhat docs-voice does
This skill guides the AI to follow the official React documentation guidelines. It enforces capitalization for standalone React concepts like Hook, Context, or Server Action, while requiring lowercase when paired with descriptors. It also splits tone expectations across Learn, Reference, and Blog pages.
The rule set prohibits words like "simple", "easy", and "just", as well as time estimates. It instructs the assistant to describe behavior before introducing technical jargon, replacing words like "memoize" or "idempotent" with direct plain-English explanations.
Top-level code snippets must use named functions and avoid var, with JSX preferred over createElement.
What it helps with
- align technical guides with react.dev writing standards
- eliminate condescending words like simple and easy
- standardize capitalization for React concepts and product names
- format version-specific API differences starting with React 19
Example prompts for the agent
- Review this draft on custom Hooks using the react.dev style guide
- Write an API reference entry for a custom state Hook
- Explain component render phases using the recommended restaurant analogy
How to install docs-voice
1Skills CLI (Vercel)
npx skills add reactjs/react.dev --skill docs-voice -a claude-code2Manually: put the files in place
~/.claude/skills/docs-voice/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/docs-voice/
1Skills CLI (Vercel)
npx skills add reactjs/react.dev --skill docs-voice -a codex2Manually: put the files in place
.agents/skills/docs-voice/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reactjs/react.dev --skill docs-voice -a cursor2Manually: put the files in place
.cursor/skills/docs-voice/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reactjs/react.dev .claude/skills/docs-voice2Manually: put the files in place
.github/skills/docs-voice/SKILL.md1Skills CLI (Vercel)
npx skills add reactjs/react.dev --skill docs-voice -a gemini-cli2Platform CLI
gemini skills install https://github.com/reactjs/react.dev --path .claude/skills/docs-voiceManually: put the files in place
.devin/skills/docs-voice/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reactjs/react.dev --skill docs-voice -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about docs-voice
How to install docs-voice in Claude Code?
Run npx skills add reactjs/react.dev --skill docs-voice -a claude-code in your terminal. The skill file will be placed in ~/.claude/skills/docs-voice/SKILL.md.
What does docs-voice do?
It teaches coding assistants the exact style, capitalization, code patterns, and terminology rules used by the React documentation team.
Which technical terms does docs-voice restrict?
It discourages terms like "atomic", "idempotent", and "memoize" in favor of descriptive phrases, though terms like "stale closures" remain permitted in Reference caveats.
Source text
SKILL.md · CC-BY-4.0
---
name: docs-voice
description: Use when writing any React documentation. Provides voice, tone, and style rules for all doc types.
---
# React Docs Voice & Style
## Universal Rules
- **Capitalize React terms** when referring to the React concept in headings or as standalone concepts:
- Core: Hook, Effect, State, Context, Ref, Component, Fragment
- Concurrent: Transition, Action, Suspense
- Server: Server Component, Client Component, Server Function, Server Action
- Patterns: Error Boundary
- Canary: Activity, View Transition, Transition Type
- **In prose:** Use lowercase when paired with descriptors: "state variable", "state updates", "event handler". Capitalize when the concept stands alone or in headings: "State is isolated and private"
- General usage stays lowercase: "the page transitions", "takes an action"
- **Product names:** ESLint, TypeScript, JavaScript, Next.js (not lowercase)
- **Bold** for key concepts: **state variable**, **event handler**
- **Italics** for new terms being defined: *event handlers*
- **Inline code** for APIs: `useState`, `startTransition`, `<Suspense>`
- **Avoid:** "simple", "easy", "just", time estimates
- Frame differences as "capabilities" not "advantages/disadvantages"
- Avoid passive voice and jargon
## Tone by Page Type
| Type | Tone | Example |
|------|------|---------|
| Learn | Conversational | "Here's what that looks like...", "You might be wondering..." |
| Reference | Technical | "Call `useState` at the top level...", "This Hook returns..." |
| Blog | Accurate | Focus on facts, not marketing |
**Note:** Pitfall and DeepDive components can use slightly more conversational phrasing ("You might wonder...", "It might be tempting...") even in Reference pages, since they're explanatory asides.
## Avoiding Jargon
**Pattern:** Explain behavior first, then name it.
✅ "React waits until all code in event handlers runs before processing state updates. This is called *batching*."
❌ "React uses batching to process state updates atomically."
**Terms to avoid or explain:**
| Jargon | Plain Language |
|--------|----------------|
| atomic | all-or-nothing, batched together |
| idempotent | same inputs, same output |
| deterministic | predictable, same result every time |
| memoize | remember the result, skip recalculating |
| referentially transparent | (avoid - describe the behavior) |
| invariant | rule that must always be true |
| reify | (avoid - describe what's being created) |
**Allowed technical terms in Reference pages:**
- "stale closures" - standard JS/React term, can be used in Caveats
- "stable identity" - React term for consistent object references across renders
- "reactive" - React term for values that trigger re-renders when changed
- These don't need explanation in Reference pages (readers are expected to know them)
**Use established analogies sparingly—once when introducing a concept, not repeatedly:**
| Concept | Analogy |
|---------|---------|
| Components/React | Kitchen (components as cooks, React as waiter) |
| Render phases | Restaurant ordering (trigger/render/commit) |
| State batching | Waiter collecting full order before going to kitchen |
| State behavior | Snapshot/photograph in time |
| State storage | React storing state "on a shelf" |
| State purpose | Component's memory |
| Pure functions | Recipes (same ingredients → same dish) |
| Pure functions | Math formulas (y = 2x) |
| Props | Adjustable "knobs" |
| Children prop | "Hole" to be filled by parent |
| Keys | File names in a folder |
| Curly braces in JSX | "Window into JavaScript" |
| Declarative UI | Taxi driver (destination, not turn-by-turn) |
| Imperative UI | Turn-by-turn navigation |
| State structure | Database normalization |
| Refs | "Secret pocket" React doesn't track |
| Effects/Refs | "Escape hatch" from React |
| Context | CSS inheritance / "Teleportation" |
| Custom Hooks | Design system |
## Common Prose Patterns
**Wrong vs Right code:**
```mdx
\`\`\`js
// 🚩 Don't mutate state:
obj.x = 10;
\`\`\`
\`\`\`js
// ✅ Replace with new object:
setObj({ ...obj, x: 10 });
\`\`\`
```
**Table comparisons:**
```mdx
| passing a function | calling a function |
| `onClick={handleClick}` | `onClick={handleClick()}` |
```
**Linking:**
```mdx
[Read about state](/learn/state-a-components-memory)
[See `useState` reference](/reference/react/useState)
```
## Code Style
- Prefer JSX over createElement
- Use const/let, never var
- Prefer named function declarations for top-level functions
- Arrow functions for callbacks that need `this` preservation
## Version Documentation
When APIs change between versions:
```mdx
Starting in React 19, render `<Context>` as a provider:
\`\`\`js
<SomeContext value={value}>{children}</SomeContext>
\`\`\`
In older versions:
\`\`\`js
<SomeContext.Provider value={value}>{children}</SomeContext.Provider>
\`\`\`
```
Patterns:
- "Starting in React 19..." for new APIs
- "In older versions of React..." for legacy patterns
© reactjs · CC-BY-4.0 · reactjs/react.dev
Similar skills
All skills for Writing and docs →docs-voice by other authors comes first.