clarify

Identify and rewrite unclear UX copy using context and principles.

1|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/puripong1st/web-fahsiam --skill clarify-puripong1st
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/puripong1st/web-fahsiam/tree/main/.agent/skills/clarify
Command: npx skills add https://github.com/puripong1st/web-fahsiam --skill clarify-puripong1st

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear UX copy leads to user confusion, higher error rates, and more support requests. This Skill provides a structured approach to identify, rewrite, and standardize copy to improve clarity and usability across interfaces.

Core Features & Use Cases

  • Clarity audit templates for error messages, form labels, tooltips, empty states, and confirmations.
  • A principles-driven rewrite system that emphasizes brevity, specificity, actionability, and consistency.
  • Real-world use cases with before/after examples to guide product teams in improving onboarding prompts, validations, and navigation cues.

Quick Start

Identify one unclear UI copy item and rewrite it using the provided clarity guidelines.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite unclear UX copy for error messages and form labels?

Improve interface copy clarity by applying UX-writing principles to make labels, tooltips, and error messages specific, actionable, consistent, and localization-ready through structured rewrite templates.

What makes UX writing clear and actionable for product interfaces?

Clear UX writing is specific, actionable, consistent, and localization-ready. It replaces vague tooltips and empty states with standardized wording that reduces user confusion and support requests.

How do I audit interface copy for empty states and tooltips?

Audit interface copy using clarity templates that evaluate empty states, tooltips, and confirmations against UX-writing principles, generating before and after examples to guide standardization.

Does this UX writing approach support localization-ready copy?

Yes, the rewrite system ensures UX copy is localization-ready by emphasizing consistency and brevity across error messages, labels, and tooltips to streamline translation and reduce ambiguity.

When should I standardize interface copy for usability?

Standardize interface copy when unclear error messages, form labels, or navigation cues lead to user confusion, higher error rates, and increased support requests across product interfaces.

What is the best way to fix confusing error messages in my application?

Fix confusing error messages by identifying unclear wording and rewriting it using clarity guidelines that emphasize actionability, specificity, and consistency to improve overall usability.