Translate and polish English documentation with consistent, natural, developer-friendly style for nex-ui. Use when translating docs.
This skill defines a consistent style for translating and polishing English docs in nex-ui.
The goal is simple: natural English, stable terminology, and consistent tone—without changing technical meaning.
Prioritize the following, in order:
checked and onCheckedChange to control the Switch state.”Use these terms consistently:
@nex-ui/react, component symbols as-isApply these patterns across docs.
NexUI provides <number> components for building <feature>.Use <prop> to ... / Set <prop> to ...Callback fired when ...If your project uses TypeScript, you can extend ...Follow the current en/docs/components pattern:
If true, disables ...If true, hides ...If true, shows ...If true, opens/shows ... (controlled)If true, opens/shows ... by default. (uncontrolled)If true, keeps ... mounted in the DOM when not open/expanded.Avoid noun-heavy or passive alternatives when an action verb works better.
Run this checklist on edited docs: