ux-copy

Generate clear UX microcopy for buttons, errors, and dialogs.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Avihusitton/gil-therapy --skill ux-copy-avihusitton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-copy
Source: https://github.com/Avihusitton/gil-therapy/tree/main/.agents/skills/ux-copy
Command: npx skills add https://github.com/Avihusitton/gil-therapy --skill ux-copy-avihusitton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of unclear, generic, or robotic UI microcopy that confuses users, disrupts task completion, and creates inconsistent product experiences across different interface states.

Core Features & Use Cases

  • Multi-surface copy generation: Creates tailored microcopy for buttons, empty states, error messages, toasts, form helper text, and confirmation dialogs.
  • Consistent tone adherence: Follows a Toss-inspired voice (casual but polite, active, specific) to maintain uniform brand messaging across all user flows.
  • Real-world use case: If your app uses generic "Submit" buttons or surfaces raw internal error codes that leave users stuck, this Skill generates clear, actionable copy that guides users to complete tasks or resolve issues independently.

Quick Start

Ask the AI to generate microcopy for your app's payment failure error state, empty saved items screen, and account deletion confirmation dialog to get ready-to-use, on-brand copy for all three surfaces.

Frequently Asked Questions about ux-copy

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

FAQPage Schema
How do I generate UX microcopy for common user interface states like empty screens and form errors?

To generate UX microcopy for user interface states, provide the AI with your app's specific UI context like a payment failure error or empty saved items screen. The Skill outputs clear, actionable copy for buttons, toasts, and form guidance that eliminates confusing, robotic messaging without internal jargon.

What is the best way to write on-brand copy for frontend confirmation dialogs and error messages?

The best way to write on-brand copy for confirmation dialogs and error messages is to apply a consistent, active voice across all UI surfaces. This Skill generates polite, specific text that guides users to resolve issues independently and understand product state, avoiding passive phrasing and generic text.

Can I use this to generate microcopy for both web and mobile applications?

Yes, you can generate microcopy for both web and mobile applications. The Skill applies to frontend product development workflows requiring user-facing text for any platform, ensuring consistent tone and actionable messaging across all device types and interface states.

Does UX copy generation work for fixing raw internal error codes that leave users stuck?

UX copy generation works for fixing raw internal error codes by translating them into clear, actionable text. Instead of surfacing confusing codes, the Skill generates user-facing error messages that guide users to resolve issues independently while maintaining an active, specific brand voice.

How do I ensure consistent tone across multiple UI surfaces like buttons, empty states, and toasts?

To ensure consistent tone across UI surfaces like buttons, empty states, and toasts, the Skill follows a Toss-inspired voice that is casual but polite. It maintains uniform brand messaging across all user flows by eliminating generic product messaging and enforcing active phrasing.