clarify

Identify and rewrite unclear interface text for clarity.

1.0k|140|Updated Sep 18, 2022
One-click install
npx skills add https://github.com/childrentime/reactuse --skill clarify-childrentime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/childrentime/reactuse/tree/main/packages/website-astro/.agents/skills/clarify
Command: npx skills add https://github.com/childrentime/reactuse --skill clarify-childrentime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand and use.

Core Features & Use Cases

  • Assess copy for clarity issues such as jargon, ambiguity, passive voice, length, and missing context
  • Plan and implement copy improvements following established clarity principles
  • Use-case example: rewrite a confusing error message into a helpful, actionable prompt

Quick Start

Identify unclear copy in the current interface and rewrite it for clarity.

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 and error messages to be more actionable?

Rewrite confusing UX copy by identifying jargon, ambiguity, and passive voice, replacing them with specific, concise, and actionable text. This process transforms vague interface text into clear instructions that preserve brand voice and guide users effectively.

What makes microcopy unclear and how do I fix it?

Microcopy becomes unclear due to missing context, excessive length, or technical jargon. Fix it by applying clarity principles to audit existing text, ensuring form labels, placeholders, and empty states deliver concise, actionable guidance validated against established standards.

How do I audit UI copy for clarity issues across web and mobile interfaces?

Audit UI copy by assessing error messages, form labels, help texts, and CTAs for clarity issues like ambiguity and missing context. The review identifies poorly written interface text across web and mobile platforms, enabling targeted rewrites that improve product comprehension.

Can I improve interface text while preserving brand voice?

Yes, you can improve interface text while preserving brand voice by validating copy changes against established clarity principles. The rewrite process delivers specific, concise text that aligns with your existing tone while resolving issues like jargon and passive voice.

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

The best way to fix poorly written error messages is to rewrite them into helpful, actionable prompts. This involves removing jargon and ambiguity, adding necessary context, and ensuring the text directly guides the user toward resolving the issue.

When should I not use automated copy improvement for UX writing?

You should avoid automated copy improvement when interface text requires deep cultural localization or highly specific legal phrasing that falls outside standard clarity principles, as the rewrite focuses on general conciseness, actionability, and preserving brand voice.