clarify

Rewrite unclear UX copy for error messages, labels, prompts, and onboarding.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Mrlyk/SKILLS --skill clarify-mrlyk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Mrlyk/SKILLS/tree/main/skills/ui-design/clarify
Command: npx skills add https://github.com/Mrlyk/SKILLS --skill clarify-mrlyk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams improve unclear UI/UX copy to reduce user confusion, support tickets, and onboarding friction by providing clear, actionable copy guidelines and revisions.

Core Features & Use Cases

  • Clarity-first rewrites: Proposes concise, plain-language alternatives for error messages, labels, tooltips, and prompts.
  • Design-consistent vocabulary: Standardizes terminology across screens to improve recognition and reduce cognitive load.
  • Guided improvements: Provides a repeatable process for critique and rewrite using the Context Gathering Protocol, audience, and intent.
  • Use Case: You have a confusing form label; the skill returns a revised label and an explanation of why it works.

Quick Start

Provide the UI copy you want clarified, and specify the target audience, then ask for improvements following the Context Gathering Protocol.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve UX writing for unclear UI copy?

To improve UX writing for unclear UI copy, provide your existing text and target audience to receive concise, plain-language revisions and explanations based on UX clarity principles. This reduces user confusion and onboarding friction.

What is the best way to rewrite confusing error messages and form labels?

The best way to rewrite confusing error messages and form labels is to apply a Context Gathering Protocol that proposes clarity-first alternatives, standardizes design vocabulary, and explains why the revised text improves usability.

Can I standardize interface terminology across different web and mobile app screens?

Yes, you can standardize interface terminology across web and mobile app screens by generating design-consistent vocabulary that improves recognition, reduces cognitive load, and ensures uniformity throughout the user journey.

Does this approach support localization considerations for onboarding copy?

Yes, this approach supports localization considerations for onboarding copy by evaluating text clarity and intent, ensuring revised prompts and messages can be effectively translated for global audiences without losing context.

Why do I need to specify the target audience when clarifying tooltips and prompts?

You need to specify the target audience when clarifying tooltips and prompts because audience context directly shapes the vocabulary and tone, ensuring the guided rewrite produces actionable and relevant copy improvements.

What are the limitations of using automated principles for UI copy critique?

A limitation of using automated principles for UI copy critique is that revisions rely strictly on provided context and intent, meaning incomplete audience or product descriptions may restrict the accuracy of generated onboarding and error text.