apollo-writing

Apply UiPath UX writing guidelines to UI copy and microcopy.

18|7|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/UiPath/apollo-ui --skill apollo-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apollo-writing
Source: https://github.com/UiPath/apollo-ui/tree/main/packages/apollo-wind/skills/apollo-writing
Command: npx skills add https://github.com/UiPath/apollo-ui --skill apollo-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about apollo-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write clear and consistent UI copy for product interfaces?

UI copy guidelines enforce sentence case, numerals as digits, and controlled contractions to produce concise, consistent, and accessible labels, buttons, and microcopy across your products.

What is the best structure for error messages and modal copy in UX writing?

Error messages should follow a three-part structure: explain what happened, why it matters, and what to do next. Modal copy uses component-specific structures to maintain clarity and localization readiness.

How do I make microcopy localization-ready for software interfaces?

Make microcopy localization-ready by using simple language, sentence case, and explicit terminology preferences. Avoid punctuation on labels and limit tooltip length to ensure UI text translations remain clear.

Does UX writing need a style guide for button labels and CTAs?

Yes, UX writing needs a style guide for button labels and CTAs to enforce a verb plus noun structure of two to four words, ensuring UI copy remains concise, actionable, and consistent across components.

What terminology should I use for UI text in automation products?

Use explicit terminology preferences such as Build instead of Create, Run as a verb versus job as a noun, and Add versus Remove to ensure UI text remains consistent, user-centric, and aligned with product conventions.