clarify

Rewrite UX copy into specific, actionable, and consistent messaging.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ceshez/VELAR --skill clarify-ceshez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/ceshez/VELAR/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/ceshez/VELAR --skill clarify-ceshez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill improves unclear UX copy so users can understand what something means and what to do next without guessing.

Core Features & Use Cases

  • Error and status message rewrites: Replace vague failures with plain-language causes and actionable fixes.
  • Label, instruction, and microcopy improvements: Turn ambiguous or jargon-heavy text into specific, consistent guidance that matches user intent.
  • UX writing for key interface moments: Strengthen empty states, loading states, confirmations, and navigation wayfinding to reduce confusion under stress.
  • Use case: When users report “I don’t know what to do” or “that error makes no sense,” use this Skill to identify the clarity failure (ambiguity, missing context, tone mismatch, length) and produce improved copy patterns across the affected UI elements.

Quick Start

Ask the AI to run the clarify skill on the confusing labels and error messages in your interface and return improved microcopy plus a brief rationale for each change.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite UX copy to make confusing interface text clear?

Rewriting UX copy involves replacing jargon and ambiguity with plain language, active voice, and actionable next steps. This process transforms confusing interface labels into specific, consistent guidance that matches user intent and mental state.

What makes a good error message in product UIs?

A good error message in product UIs uses plain language to explain the specific cause of a failure and provides an actionable fix, removing ambiguity and matching the user's mental state to reduce confusion under stress.

How do I improve empty states and loading states in microcopy?

Improve empty states and loading states by writing microcopy that provides specific context, removes jargon, and offers clear navigation wayfinding and next-step guidance to orient users during system delays or lack of data.

Can I use UX writing principles for form labels and user instructions?

Yes, you can apply UX writing principles to form labels and user instructions by turning ambiguous or jargon-heavy text into specific, consistent guidance that matches user intent and clearly directs data entry.

When should I update interface labels and CTA microcopy?

Update interface labels and CTA microcopy when users report confusion, encounter vague failures, or struggle with navigation wayfinding, indicating a clarity failure requiring actionable, plain-language messaging.