copy

Audit and rewrite UI copy across web app screens with i18n-safe updates.

3|Updated May 16, 2026
One-click install
npx skills add https://github.com/dawitlabs/ui-skills --skill copy-dawitlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copy
Source: https://github.com/dawitlabs/ui-skills/tree/main/skills/copy
Command: npx skills add https://github.com/dawitlabs/ui-skills --skill copy-dawitlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test, fs, curl, grep, find, sleep, node, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The copy across your product becomes vague, generic, inconsistent, or misleading, which makes users hesitate, misunderstand errors, and struggle to complete key flows.

Core Features & Use Cases

  • Screen-by-screen copy audits: Finds user-facing strings across CTAs, headings, errors, empty states, placeholders, loading text, tooltips, confirmations, microcopy, and marketing copy.
  • Category-specific rewrites: Applies strict UX copy rules (benefit-first CTAs, actionable errors, specific placeholders, and non-filler loading/empty-state messaging).
  • Visual verification with screenshots (desktop + mobile): Ensures rewrites fit layouts without truncation and read naturally in context.
  • i18n-safe updates: When i18n libraries are detected, applies copy changes to message files rather than hardcoding UI text.

Quick Start

Run the UI project and use the /copy skill to audit and rewrite the copy on your highest-priority user screens until the wording fits and looks correct on both desktop and mobile.

Frequently Asked Questions about copy

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

FAQPage Schema
How do I audit and fix vague UI copy across my web app screens?

To audit UI copy, extract user-facing strings from source files and take Playwright screenshots to verify context. Apply category-specific UX copy rules to rewrite CTAs, errors, and empty states, ensuring the text reads clearly on both desktop and mobile layouts.

What is the best way to rewrite error messages and microcopy for better UX?

The best way to rewrite error messages and microcopy is by enforcing category-specific UX rules, such as making errors actionable and removing filler text from loading states. This ensures users understand issues and know exactly what action to take next.

Does this UX writing audit process support internationalization message files?

Yes, the UX writing audit supports internationalization by detecting translation libraries. When present, all copy updates are applied directly to i18n message files rather than modifying hardcoded component text, preserving translation workflow integrity.

How do I verify my rewritten CTA labels and UI text fit without truncation?

You can verify rewritten CTA labels and UI text by taking Playwright screenshots during the audit. This visual verification checks both desktop and mobile layouts to ensure the new copy fits naturally without truncation or layout disruption.

Can I use this to fix empty states and placeholders in an auth-protected dashboard?

Yes, you can fix empty states and placeholders in auth-protected dashboards. The process audits onboarding, settings, and conversion-critical screens, applying specific UX rules to ensure empty state messaging is helpful rather than generic filler.

What dependencies do I need to run automated UI copy audits?

To run automated UI copy audits, you need a running UI project and dependencies including Playwright for visual testing, Node.js, and file system utilities like grep and find to extract and update strings from your source files.