clarify

Rewrite unclear interface copy with tone guidance and verification checks.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/DanialHaseeb/dotfiles --skill clarify-danialhaseeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/DanialHaseeb/dotfiles/tree/main/codex/skills/clarify
Command: npx skills add https://github.com/DanialHaseeb/dotfiles --skill clarify-danialhaseeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear, confusing, or unhelpful interface text so users immediately understand what happened, why it happened, and what to do next. This reduces user errors, support load, and frustration by turning vague or technical language into concise, actionable messages tailored to the audience and context.

Core Features & Use Cases

  • Assessment: Diagnose clarity problems such as jargon, ambiguity, passive voice, missing context, tone mismatch, and incorrect assumptions.
  • Systematic Improvements: Generate concise rewrites for error messages, form labels, CTAs, tooltips, empty states, loading and success messages, and confirmation dialogs, with tone and action guidance.
  • Planning & Verification: Define the primary message, required action, tone constraints, and verification criteria (comprehension, actionability, brevity, consistency) for testing and iteration.
  • Use Cases: Helpful for UX writers, product designers, and support teams refining onboarding flows, error handling, form UX, and microcopy across web and mobile products.

Quick Start

Provide the unclear interface text, target audience, and desired tone, and ask for concise rewrites, explainers of problems, and 2–3 alternative phrasings.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite confusing UX copy to make it clear and actionable?

To improve unclear UX copy, diagnose clarity problems like jargon and ambiguity, then rewrite labels, error messages, and CTAs with concise, audience-appropriate phrasing, tone guidance, and actionable fixes. This ensures users understand what happened and what to do next.

What is the best way to fix vague error messages in web and mobile interfaces?

Fixing vague error messages involves identifying missing context and passive voice, then generating concise rewrites tailored to your target audience and desired tone, providing 2–3 alternative phrasings with verification checks for comprehension and actionability.

How do I improve form labels and tooltips for better user comprehension?

Improving form labels and tooltips requires assessing current text for incorrect assumptions and tone mismatch, then applying systematic rewrites that deliver concise, actionable guidance and verification criteria for testing user comprehension and brevity.

Can I use microcopy editing for empty states and loading dialogs during design reviews?

Yes, microcopy editing applies to empty states, loading messages, and confirmation dialogs during design reviews. It systematically diagnoses and rewrites interface text to reduce user errors, support load, and frustration across web and mobile products.

Why does my interface copy cause user frustration and support tickets?

Interface copy causes frustration when it uses technical language, ambiguity, or lacks context, leaving users unsure of what happened. Diagnosing these clarity problems and rewriting text into concise, actionable messages reduces support load.

Does this UX writing approach work for both onboarding flows and error handling?

Yes, this UX writing approach works for onboarding flows and error handling by refining interface text across web and mobile products. It helps UX writers, product designers, and support teams turn vague language into concise, actionable messages.