copywriting

Standardize UI copy tone, capitalization, pronouns, and messaging across products.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/Qnurye/dotfiles --skill copywriting-qnurye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copywriting
Source: https://github.com/Qnurye/dotfiles/tree/main/agents/skills/copywriting
Command: npx skills add https://github.com/Qnurye/dotfiles --skill copywriting-qnurye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent UI copy across products and components slows onboarding, causes confusion, and reduces perceived quality. This skill provides a centralized, readable standard for tone, style, and usage to ensure clarity and consistency.

Core Features & Use Cases

  • Establishes sentence case across buttons, labels, headings, and placeholders to improve readability.
  • Defines voice, pronoun usage, and tone to create a friendly, professional experience.
  • Serves as a quick reference during copy reviews, onboarding, and design handoffs to maintain consistency across teams.

Quick Start

Copyedit the UI copy for the next component to align with the guidelines.

Frequently Asked Questions about copywriting

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

FAQPage Schema
How do I standardize UI copy across different products and design systems?

Standardize UI copy by applying centralized rules for tone, capitalization, pronouns, and messaging across buttons, labels, placeholders, and error messages. This ensures concise, friendly, accessible language and a consistent voice throughout your products.

What is the best way to fix inconsistent tone and capitalization in onboarding flows?

The best way to fix inconsistent tone is to enforce sentence case across buttons, labels, headings, and placeholders while defining voice and pronoun usage. This creates a friendly, professional experience and maintains consistency across teams.

Can I use a single style guide for both error messages and button labels?

Yes, you can use a single style guide for both error messages and button labels. It provides comprehensive rules for tone, capitalization, and messaging that apply across all UI components to ensure clarity and accessibility.

How do I maintain a consistent voice during design handoffs and copy reviews?

Maintain a consistent voice during design handoffs by using the style guide as a quick reference. It standardizes tone, pronoun usage, and messaging to align copy across teams and reduce onboarding confusion.

Why does inconsistent UI copy slow down product onboarding?

Inconsistent UI copy slows product onboarding because it causes user confusion and reduces perceived quality. Standardizing tone, style, and usage rules ensures clarity and consistency, which accelerates user comprehension across components.

When should I not use sentence case for UI headings and placeholders?

The style guide establishes sentence case across buttons, labels, headings, and placeholders to improve readability. While this approach enforces concise, friendly, and accessible language, specific branding contexts may require overriding it.