apollo-writing

What problem does it solve?

Ensures UI text follows UiPath UX writing guidelines so labels, buttons, errors, modals, empty states, and other microcopy are clear, consistent, accessible, and localized-ready across products.

Core Features & Use Cases

• Core principles: simple language, consistency, user-centric phrasing, conversational tone, and accessibility.
• Writing rules: sentence case everywhere, numerals as digits, controlled use of contractions, punctuation rules (no periods on labels/buttons/headings), and no exclamation points except greetings.
• Component guidance: button/CTA structure (verb + noun, 2–4 words), label and heading conventions, modal structure, error message pattern (what happened, why it matters, what to do next), tooltip limits, placeholders guidance, and localization readiness.
• Terminology: explicit UiPath term usage (Build vs Create, Run as verb vs job as noun, Add vs Remove) and a final validation checklist to verify adherence.
• Use case: review and rewrite a product's button labels, error texts, and modal copy to match UiPath tone and terminology before release.

Quick Start

Use apollo-writing to review and rewrite UI labels, CTAs, errors, and modal copy to conform to UiPath writing rules.