clarify

Rewrite unclear UI copy to reduce jargon and ambiguity.

60|7|Updated Oct 18, 2020
One-click install
npx skills add https://github.com/bfree-trainer/bfree --skill clarify-bfree-trainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/bfree-trainer/bfree/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/bfree-trainer/bfree --skill clarify-bfree-trainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear, confusing, or poorly written interface text to make products easier to understand.

Core Features & Use Cases

  • Assess and rewrite copy to reduce jargon, ambiguity, and passive voice.
  • Improve labels, error messages, buttons, and help text for clarity.
  • Use case: When a user complains about a confusing label or error, run this skill to rewrite copy for clarity and tone.

Quick Start

Identify unclear UI copy and propose concrete rewrites that improve clarity and tone.

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 better usability?

To rewrite unclear UX copy for usability, identify jargon, passive voice, and ambiguity in interface text, then apply specific rewrites that preserve meaning and tone while improving clarity across labels, help content, and tooltips.

What is the best way to improve confusing error messages in UI text?

The best way to improve confusing error messages is to identify ambiguous or jargon-heavy phrasing and replace it with clear, actionable UI copy that reduces user friction while preserving the product's intended tone.

How do I reduce jargon and passive voice in interface text?

To reduce jargon and passive voice in interface text, evaluate existing labels and help content, identify complex phrasing, and generate concrete copy rewrites that communicate meaning clearly and directly to the user.

Can I use this to fix poorly written help content and tooltips?

Yes, you can fix poorly written help content and tooltips by identifying unclear UI copy and proposing concrete rewrites that reduce ambiguity and passive voice while preserving the original meaning and tone.

Does rewriting UI copy for clarity change the product's tone?

Rewriting UI copy for clarity preserves the product's tone while reducing jargon, ambiguity, and passive voice. It targets unclear interface text to improve usability without altering the intended meaning or voice.

When should I review UX writing for clarity and usability?

You should review UX writing for clarity and usability when users complain about confusing labels or errors, or when interface text contains jargon, passive voice, and ambiguity that hinders product understanding.