clarify

Rewrite unclear interface copy into concise, actionable messages.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/djkloop/n --skill clarify-djkloop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/djkloop/n/tree/main/.trae/skills/clarify
Command: npx skills add https://github.com/djkloop/n --skill clarify-djkloop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear, confusing, or poorly written interface text—labels, error messages, microcopy, instructions, and CTAs—so users immediately understand what happened and what to do next.

Core Features & Use Cases

  • Diagnose clarity issues like jargon, ambiguity, passive voice, missing context, and tone mismatch.
  • Rewrite microcopy across error messages, form labels, buttons, tooltips, empty/loading states, and confirmations to be specific, actionable, and concise.
  • Use Case: Convert vague error text such as "Invalid input" into a clear, actionable message like "Email addresses must include an @ symbol. Try: [email protected]", reducing user confusion and support requests.

Quick Start

Improve the error message "Error 403: Forbidden" so it explains why access was denied and what the user should do next.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite vague error messages into clear UX copy that tells users what to do next?

UX copy editing improves labels, microcopy, and instructions by diagnosing jargon, ambiguity, passive voice, and tone mismatch, then providing concise, actionable rewrites that explain the problem and suggest fixes so users immediately understand what happened.

How do I fix unclear microcopy in empty states and onboarding flows?

Fixing unclear microcopy involves diagnosing jargon and passive voice across tooltips, confirmations, and loading states, then rewriting the text to be specific and actionable while matching the tone to the user context and respecting localization constraints.

What is the best way to improve form labels and button copy for better usability?

Improving form labels and button copy for usability requires applying copy-editing to replace confusing interface text with concise, actionable rewrites, ensuring the microcopy explains the problem and suggests fixes while respecting length constraints.

Does UX writing for error messages respect length and localization constraints?

Yes, UX writing for error messages respects length and localization constraints by providing concise, actionable rewrites that match the tone to the user context, ensuring improved interface text like buttons and tooltips remains clear and user-friendly across localized environments.

Why does passive voice in interface text cause usability problems in software products?

Passive voice in interface text causes usability problems by introducing ambiguity and missing context, which prevents users from understanding what happened and what to do next, ultimately increasing user confusion and support requests across product interfaces.