clarify

Identify and rewrite unclear interface copy for web and app UIs.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Postalocity/template-microsite --skill clarify-postalocity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Postalocity/template-microsite/tree/main/.opencode/skills/impeccable--clarify
Command: npx skills add https://github.com/Postalocity/template-microsite --skill clarify-postalocity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use. This guide helps teams craft precise, actionable copy for errors, forms, labels, buttons, help text, and empty states.

Core Features & Use Cases

  • Clarity audit: Detect jargon, ambiguity, and passive voice, and propose clearer replacements.
  • Copy refinement: Turn vague labels and messages into concise, user-focused wording.
  • Use Case: Improve onboarding error messages to reduce support tickets and increase task completion rates.

Quick Start

Provide the current UI text you want rewritten and specify any brand voice constraints, and I will deliver clearer, ready-to-use copy.

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 microcopy for better user comprehension?

To rewrite unclear UX microcopy, provide your existing interface text and specify any brand voice constraints to receive concise, active, and helpful replacements. This process detects jargon and passive voice, turning vague labels into user-focused wording for instant understanding.

What is the best way to fix confusing form labels and error messages?

The best way to fix confusing form labels and error messages is through a clarity audit that identifies ambiguity and proposes specific, actionable replacements. This ensures your interface copy is concise, active, and helpful, reducing user errors and support tickets.

How do I write clear empty states and help text for web and app interfaces?

Writing clear empty states and help text requires applying clarity principles like being specific, concise, and consistent. By refining vague interface copy into user-focused wording tailored for typical UI constraints, you ensure users understand exactly what to do next.

Can I audit existing interface copy for usability issues and jargon?

Yes, you can audit existing interface copy to detect jargon, ambiguity, and passive voice across web and app interfaces. The audit proposes clearer replacements for buttons, tooltips, and error messages, ensuring all text follows clarity principles for improved usability.

Why does passive voice in error messages cause user friction?

Passive voice in error messages causes user friction because it creates ambiguity around the required action and fails to clearly explain the issue. Rewriting error messages with active, specific, and helpful wording reduces confusion, prevents errors, and lowers support ticket volume.

Does clarifying tooltip text require specific brand voice constraints?

Clarifying tooltip text does not strictly require brand voice constraints, but providing them ensures the rewritten copy remains consistent with your product. Specifying constraints allows the refined microcopy to be concise and helpful while perfectly matching your established tone.