# Specific Copy

> Write interface and marketing copy that is concrete and verifiable instead of sloganeering — headlines that say what the product does, claims backed by sources, button labels that name the action, and useful empty and error states. Use this skill when writing or reviewing landing page copy, headlines, CTAs, onboarding text, empty states, error messages, or when copy sounds like every other product. Activate when: UX writing, microcopy, landing page copy, headline, call to action, button label, empty state, error message, marketing copy, generic copy, sloganeering.

- Skill: `latestaiagents/specific-copy` (Agent Skill)
- Install (CLI): `npx get-skill add latestaiagents/specific-copy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/latestaiagents/specific-copy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: latestaiagents (https://skillmd.com/u/latestaiagents)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/latestaiagents/specific-copy

---


# Specific Copy

**Say what the thing does, for whom, with facts you can stand behind. Cut every sentence that would fit any product.**

Copy is part of the design. The same generic headline on a carefully styled page still reads as a template. This skill is about precision, not tone; a playful brand can be specific too.

## When to Use

- Drafting or reviewing landing pages, product pages, app store text
- Writing buttons, form labels, empty states, error and confirmation messages
- `ui-template-audit` flagged sloganeering headlines, filler words, or unverifiable stats

## When NOT to Use

- Legal, regulatory, or medical wording — route to the people who own it
- Brand voice guidelines already define the copy — follow them, but still apply the verification rules below

## Workflow

### Step 1: Collect the Facts First

Before writing a word, list what is true and checkable:

- What the product does, as a verb and an object ("splits a restaurant bill by item")
- Who it is for, specifically ("groups of 3-10 paying in different currencies")
- What the user does first, and what they get
- Real numbers you are allowed to publish, each with its source and date
- Real customers or quotes you have written permission to use

If the list is thin, the copy will be thin. Get facts; don't decorate.

### Step 2: Run the "Any Product" Test

Read each headline and sentence and ask: could a competitor in a different category paste this onto their site unchanged? If yes, rewrite or delete.

| Sloganeering | Specific |
|--------------|----------|
| Supercharge your workflow | Turn a Figma frame into a Jira ticket with the screenshot attached |
| The all-in-one platform for modern teams | Rota, timesheets, and payroll export for restaurants with one or more sites |
| Built for the future of work | Works offline; syncs when the tablet reconnects |
| Unlock the power of your data | Ask a question about last month's orders in plain English; see the SQL it ran |
| Seamless integration | Connects to Shopify and Stripe; setup takes the two API keys and nothing else |

Watch-list words that usually signal filler: seamless, powerful, robust, cutting-edge, next-generation, all-in-one, supercharge, unlock, revolutionize, effortless, world-class. They are not banned; they need a fact next to them or they go.

### Step 3: Make Every Claim Verifiable

| Claim type | Rule |
|------------|------|
| Numbers ("10x faster", "saves 5 hours a week") | Publish only with a named source, method, and date you can show. Otherwise remove |
| Customer counts and logos | Only real, current, and with permission |
| Testimonials | Real person, real role and company (with consent); never composites |
| Superlatives ("the fastest", "the only") | Avoid unless you can prove and maintain them |
| Compatibility ("works with everything") | List what you actually support |
| Future features | Label clearly as planned, or leave them out |

Invented or unsupported performance claims damage trust and can create legal exposure under advertising rules in many jurisdictions. When in doubt, describe the mechanism instead of the outcome: "caches each response for 5 minutes" instead of "blazing fast".

### Step 4: Write Buttons That Name the Action

A button label should say what happens when pressed, ideally verb + object.

| Vague | Specific |
|-------|----------|
| Submit | Send request |
| Get started | Create your first invoice |
| Learn more | See pricing for teams |
| OK (on a delete dialog) | Delete 3 files |
| Continue | Continue to payment |

Keep the visible label as the start of the accessible name (WCAG 2.5.3 Label in Name, Level A) so voice-control users can say what they see. Avoid adding decorative arrows or icons in place of words.

### Step 5: Write Empty, Error, and Success States

**Empty state** — say why it's empty and give the next action:

```text
Before: No data.
After:  No invoices yet. Invoices you create or import appear here.
        [Create invoice]  [Import CSV]
```

**Error** — what happened, why if known, and what to do; never blame the user:

```text
Before: Error 422.
After:  We couldn't save this invoice: the due date is before the issue date.
        Change the due date and save again.
```

**Success** — confirm the specific outcome:

```text
Before: Success!
After:  Invoice INV-0042 sent to accounts@client.example.
```

### Step 6: Edit for Scanning

- Lead with the point; put qualifications after
- One idea per sentence in UI text
- Active voice, second person for instructions ("Choose a plan"), consistent terms (pick "workspace" or "project", not both)
- Sentence case for headings and buttons unless the brand system says otherwise; long all-caps text is harder to scan
- Remove headings and labels that only repeat what the content already says

### Step 7: Review Pass

Checklist before shipping:

- [ ] Every headline passes the "any product" test
- [ ] Every number has a source you can produce
- [ ] Every logo and testimonial is real and approved
- [ ] Every button says what it does
- [ ] Every empty and error state names the next action
- [ ] No placeholder words left (lorem ipsum, "Feature one", "Company name")

## Best Practices

1. Facts before phrasing: research what is true, then write
2. Prefer mechanism over adjective
3. Remove claims you cannot source rather than softening them
4. Button labels are verb + object
5. Empty and error states are part of onboarding; write them with the same care as the hero
6. Keep terms consistent across the product
7. Read copy aloud at the size and place it will appear; long lines and all-caps read differently in context

## References

- Understanding WCAG 2.5.3 Label in Name: https://www.w3.org/TR/WCAG22/ (SC 2.5.3)
- Anthropic `frontend-design` skill ("writing as design" guidance): https://github.com/anthropics/skills/blob/main/skills/frontend-design/SKILL.md

