clarify

Identify unclear UX copy and propose precise rewrites for prompts, labels, and messages.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Bigalan09/Burohame --skill clarify-bigalan09
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Bigalan09/Burohame/tree/main/.codex/skills/clarify
Command: npx skills add https://github.com/Bigalan09/Burohame --skill clarify-bigalan09

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear interface copy slows users, causes errors, and increases support tickets. This skill helps identify and standardize problematic text across prompts, labels, and messages to improve comprehension and reduce confusion.

Core Features & Use Cases

  • Audits for clarity problems such as jargon, ambiguity, passive voice, length, missing context, and tone mismatches.
  • Provides a guided rewrite plan applying Context Gathering Protocol and frontend design principles to craft clearer copy across onboarding, forms, and in-app messages.
  • Supports collaboration with design and product teams for quick wins and scalable improvements in multiple product areas.

Quick Start

Review and rewrite conflicting or unclear copy in your current interface according to the provided protocol.

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 user interface clarity?

To improve UX copy clarity, audit interface text for jargon, ambiguity, and passive voice, then apply a guided rewrite plan using the Context Gathering Protocol to produce precise, user-friendly labels, prompts, and error messages.

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

Fixing confusing error messages and form validation text involves identifying tone mismatches and missing context, then rewriting the microcopy to align with user mental states and frontend design principles for clearer on-screen instructions.

How do I audit onboarding flows for usability and microcopy issues?

Auditing onboarding flows for usability requires identifying problematic interface text like ambiguous instructions or length mismatches, then documenting recommended changes with rationale and examples to standardize copy across web and mobile interfaces.

Does this approach to copy improvement work for both web and mobile interfaces?

Yes, this copy improvement approach applies within product design and operating contexts across both web and mobile interfaces, supporting collaboration with design and product teams to implement scalable microcopy improvements.

Why does poor microcopy increase support tickets and how can I standardize it?

Poor microcopy increases support tickets because unclear interface text slows users and causes errors; standardize it by applying a Context Gathering Protocol to understand audience technical levels and generate precise rewrites with rationale.

When should I not use a guided rewrite plan for UX writing?

Avoid using a guided rewrite plan for UX writing when you cannot gather the audience technical level or users' mental state in context, as the Context Gathering Protocol requires this input to propose precise, user-friendly rewrites.