> ## Documentation Index
> Fetch the complete documentation index at: https://content-designer-ux-writing-skill-26.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Quick start

> Learn how to use the UX Writing Skill with practical examples

<Note>
  The skill activates automatically when you write or edit interface copy. You don't need to explicitly call it.
</Note>

## How it works

This skill uses **model-invoked activation**—Claude and Codex automatically decide when to use it based on your request. The AI loads reference materials progressively, using only what's needed for your specific task.

<Note>
  In Codex CLI/IDE, you can also explicitly invoke the skill using `$ux-writing` or through the `/skills` command.
</Note>

## Basic usage

The skill activates when you:

* Write or edit interface copy
* Create error messages, notifications, or empty states
* Work on button labels, form fields, or instructions
* Review product content for consistency
* Establish voice and tone guidelines

## Usage examples

### Write an error message

Ask Claude or Codex to create user-friendly error messages:

```
Write an error message for when a payment fails
```

**Result**: Claude applies the skill automatically and generates clear, actionable error messages following best practices:

* Explains what happened
* Provides context about why it failed
* Offers a clear recovery path
* Uses empathetic, non-blaming language

**Example output**:

```
Payment failed. Your card was declined. Try a different payment method.
```

The skill applies the error message pattern: `[What failed]. [Why/context]. [What to do].`

### Edit existing copy

Review and improve interface copy against the four quality standards:

```
Review this button label: "Submit your information for processing"
```

**Result**: Claude evaluates the copy against the four quality standards (Purposeful, Concise, Conversational, Clear) and suggests improvements.

**Example analysis**:

* **Purposeful**: ✓ Describes action
* **Concise**: ✗ Too wordy (6 words)
* **Conversational**: ✗ Corporate, formal tone
* **Clear**: ✓ Meaning is clear

**Suggested improvement**: "Submit information" or "Continue"

### Create empty state copy

Generate helpful empty states that guide users:

```
Create empty state copy for a task list, keeping voice consistent with:
- Purposeful, Concise, Conversational, Clear
- Professional but friendly tone
```

**Result**: Claude applies the appropriate empty state pattern and maintains voice consistency.

**Example output**:

```
No tasks yet. Add your first task to get started.
```

Includes:

* Explanation of why it's empty
* Clear call-to-action
* Encouraging tone

### Evaluate content quality

Score existing interface copy using the content usability framework:

```
Score this error message:
"An error occurred. Please try again later."
```

**Result**: Claude uses the content usability checklist to provide detailed scoring and improvement suggestions.

**Example scoring**:

* **Purposeful**: 2/5 — Doesn't explain what failed or why
* **Concise**: 5/5 — Brief and direct
* **Conversational**: 3/5 — Sounds robotic
* **Clear**: 2/5 — Vague, no recovery path

**Overall score**: 12/20

**Improvements suggested**:

* Specify what failed
* Explain why it happened
* Provide actionable recovery step
* Use more empathetic tone

### Write consistent button labels

Create action-oriented button labels:

```
Write button labels for:
- Saving user profile changes
- Deleting an account permanently
- Viewing order details
```

**Result**: Claude applies the button pattern `[Verb] [object]` with active imperative verbs.

**Example output**:

* "Save changes"
* "Delete account"
* "View details"

Follows best practices:

* Sentence case
* Active imperative verbs
* Specific, not generic
* 2-4 words each

### Create notification copy

Write timely, valuable notification messages:

```
Create a notification for when a software update is required to continue using the app
```

**Result**: Claude applies notification patterns with verb-first title and contextual description.

**Example output**:

```
Title: Update required
Body: Install the latest version to continue.
CTA: Update now
```

Follows notification best practices:

* Verb-first title
* Clear action required
* Brief explanation
* Actionable CTA

## Understanding the four quality standards

The skill evaluates all UX text against these standards:

<AccordionGroup>
  <Accordion title="1. Purposeful">
    Helps users or the business achieve goals.

    * Does the text help users complete their task?
    * Is the value to the user clear?
    * Are concerns anticipated and addressed?
  </Accordion>

  <Accordion title="2. Concise">
    Uses the fewest words possible without losing meaning.

    * Every word must have a job
    * Remove unnecessary qualifiers
    * Front-load important information
    * Target: 40-60 characters per line maximum
  </Accordion>

  <Accordion title="3. Conversational">
    Sounds natural and human, not robotic.

    * Write how you speak
    * Use active voice 85% of the time
    * Include natural connecting words
    * Avoid corporate jargon
  </Accordion>

  <Accordion title="4. Clear">
    Unambiguous, accurate, and easy to understand.

    * Use plain language (7th grade reading level for general audience)
    * Choose specific, meaningful verbs
    * Use consistent terminology
    * Avoid jargon and technical terms
  </Accordion>
</AccordionGroup>

## Common UX text patterns

The skill includes patterns for:

* **Buttons and links**: Active imperative verbs, sentence case
* **Error messages**: Empathetic, clear, actionable (validation, system, blocking, permission)
* **Success messages**: Past tense, specific, encouraging
* **Empty states**: Explanation + CTA to populate
* **Form fields**: Clear labels, helpful instructions
* **Notifications**: Timely, valuable, verb-first titles
* **Titles**: Noun phrases, orient users

## Tips for best results

<Steps>
  <Step title="Provide context">
    Share relevant information about:

    * User goals and needs
    * Product voice and tone
    * Technical constraints
    * User emotional state
  </Step>

  <Step title="Specify the content type">
    Be clear about what you're creating:

    * Error message
    * Button label
    * Empty state
    * Notification
    * Form instructions
  </Step>

  <Step title="Request specific patterns">
    Reference UX writing principles:

    * "Keep it conversational"
    * "Make it actionable"
    * "Apply the four quality standards"
    * "Use empathetic tone for errors"
  </Step>

  <Step title="Iterate and refine">
    Ask Claude to:

    * Score the copy
    * Suggest alternatives
    * Adapt tone for different contexts
    * Make it more concise
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Core principles" icon="book" href="/concepts/quality-standards">
    Deep dive into the four quality standards and UX writing patterns
  </Card>

  <Card title="Figma integration" icon="figma" href="/guides/figma-integration">
    Review and improve UX copy directly from Figma designs
  </Card>

  <Card title="Voice and tone" icon="message" href="/concepts/voice-and-tone">
    Learn how to adapt content to brand personality and context
  </Card>

  <Card title="Accessibility" icon="universal-access" href="/guides/accessibility">
    Write inclusive UX text for all users
  </Card>
</CardGroup>