# UX/UI Copywriting

> Açık ve anlaşılır eyleme çağrı (CTA), hata mesajları ve kullanıcı arayüzü metinleri yazma kuralları.

- Skill: `gktuoktay/ux-ui-copywriting` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gktuoktay/ux-ui-copywriting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gktuoktay/ux-ui-copywriting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: GktuOktay (https://skillmd.com/u/gktuoktay)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gktuoktay/ux-ui-copywriting

---


# UI/UX Copywriting Guidelines

This skill focuses on writing effective microcopy for user interfaces, marketing assets, and onboarding flows. Good copy guides the user seamlessly while reflecting the brand's personality.

## 1. Tone of Voice

Our tone is **Friendly, Professional, and Concise**.
- **Friendly:** Welcoming, helpful, and empathetic, especially when things go wrong.
- **Professional:** Authoritative without being overly formal. We know what we are doing.
- **Concise:** Respect the user's time. Say more with fewer words.

## 2. Writing Clear CTAs (Calls to Action)

CTAs should clearly indicate what will happen when the user clicks.

* **Use strong verbs:** Start with an action word (e.g., *Get, Create, Save, Subscribe*).
* **Be specific:** Avoid generic terms if a more descriptive term fits.
  * *Bad:* Submit, Click Here, OK
  * *Good:* Create Account, Send Message, Save Changes
* **Keep it short:** Aim for 2-4 words.

## 3. Handling Error Messages

Error messages should never blame the user. They must explain what went wrong and how to fix it.

* **Be empathetic:** Avoid aggressive words like "Failed," "Prohibited," or "Illegal."
* **Provide a solution:** Tell the user what to do next.
* **Examples:**
  * *Bad:* Invalid password. Try again.
  * *Good:* Your password needs to be at least 8 characters long.
  * *Bad:* System error 404.
  * *Good:* We couldn't find that page. Let's get you back to the home page.

## 4. Designing Empty States

Empty states are opportunities to educate and encourage action, not dead ends.

* **Explain the value:** Tell the user what goes here and why they should care.
* **Provide an action:** Always include a CTA to help them get started.
* **Example (Empty Inbox):**
  * *Headline:* You're all caught up!
  * *Body:* When you receive new messages, they'll appear right here.
  * *CTA:* Browse Contacts

## 5. Onboarding Copy

Onboarding should highlight value, not just explain features.

* **Focus on benefits:** Explain *why* a feature matters, not just *how* it works.
* **Keep it digestible:** One concept per screen/tooltip.
* **Allow skipping:** Respect users who prefer to explore independently.

## 6. Avoiding Jargon

Speak the user's language. Avoid technical terms or internal acronyms unless the target audience consists exclusively of domain experts.

* *Avoid:* "Authenticate via OAuth," "CRON job scheduled," "Data mutation successful."
* *Use:* "Log in securely," "Task scheduled," "Changes saved."

### Quick Review Checklist
- [ ] Is the copy scannable?
- [ ] Is the action clear?
- [ ] Is the tone appropriate for the context (e.g., serious for billing, encouraging for onboarding)?
- [ ] Are technical terms simplified?