clarify

Diagnose and rewrite unclear UX copy for errors, labels, and instructions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear UX copy to make interfaces easier to understand and use.

Core Features & Use Cases

  • Diagnose copy for clarity issues (jargon, ambiguity, passive voice, length, missing context).
  • Propose concrete rewrites for errors, labels, placeholders, and tooltips with rationale.
  • Maintain tone and branding while adapting copy for different contexts and locales.
  • Use Case: When a user sees a confusing error like "Invalid input," provide a clear message such as "Please enter a valid email address (e.g., [email protected])."

Quick Start

Provide a rewritten version of the given UI copy that improves clarity, with brief rationale for each change.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I write clearer UX copy for error messages and form labels?

To write clearer UX copy, replace ambiguous terms like "Invalid input" with explicit, actionable guidance such as "Please enter a valid email address." This reduces user confusion and support tickets by providing exact instructions.

What makes microcopy confusing and how can I fix it?

Microcopy becomes confusing due to jargon, ambiguity, passive voice, and missing context. You can fix it by applying clarity best practices, using concise phrasing and explicit labels to make interfaces instantly easy to understand.

Can I improve interface usability by rewriting instructions without losing my brand voice?

Yes, you can improve interface usability by rewriting instructions while preserving your tone and brand voice. The process diagnoses clarity issues and proposes concrete rewrites that maintain branding across different contexts.

How do I diagnose UX writing issues like passive voice and jargon?

Diagnose UX writing issues by evaluating copy for jargon, ambiguity, passive voice, length, and missing context. Propose concrete rewrites for errors, labels, placeholders, and tooltips with clear rationale for each change.

What is the best way to rewrite UI copy for different locales and contexts?

The best way to rewrite UI copy for different locales is to maintain tone and branding while adapting the text for specific contexts. This ensures the microcopy remains clear, actionable, and culturally appropriate across regions.