clarify

Diagnoses and rewrites unclear UI text for better comprehension.

Updated Jan 22, 2025
One-click install
npx skills add https://github.com/SL-A-SH/my-portfolio --skill clarify-sl-a-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/SL-A-SH/my-portfolio/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/SL-A-SH/my-portfolio --skill clarify-sl-a-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce user confusion and errors caused by unclear interface text by identifying problems like jargon, ambiguity, passive voice, missing context, and tone mismatch, then producing concise, actionable rewrites tailored to the user's context.

Core Features & Use Cases

  • Assess current copy: Diagnose clarity issues across error messages, form labels, buttons, tooltips, empty states, and confirmations.
  • Context-aware recommendations: Incorporate audience technical level, user mental state, and design constraints to choose tone, specificity, and action-oriented language.
  • Systematic improvements: Propose primary message, next action, tone, and concise rewrites while following the frontend-design Context Gathering Protocol and recommending when to run teach-impeccable first.
  • Use case: Turn a vague "Invalid input" error into "Enter a valid email address (e.g., [email protected])" with a suggested microcopy for the submit button and a brief help tooltip.

Quick Start

Improve the following interface text for clarity, specify the user's technical level and likely mental state, and provide a concise replacement plus a short rationale.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear UX microcopy for error messages and form labels?

To improve unclear UX microcopy, diagnose text for jargon, ambiguity, and passive voice, then produce concise, action-focused rewrites. This process replaces vague interface text like "Invalid input" with specific guidance such as "Enter a valid email address" to reduce user errors.

What is the best way to rewrite vague user interface text for empty states and CTAs?

The best way to rewrite vague user interface text is to systematically propose a primary message, next action, and adjusted tone. This ensures your empty states and CTAs become actionable and tailored to the user's technical level and mental state.

How do I write clear error messages that match my audience's technical level?

Writing clear error messages requires incorporating the audience's technical level, mental state, and design constraints. This context-aware approach helps choose specific, action-oriented language that increases user comprehension and reduces frustration.

Do I need to provide design context when editing user experience copy for mobile interfaces?

Yes, you need to provide design context when editing user experience copy for mobile interfaces. Contextual inputs including audience technical level, users' mental state, and design constraints are required to choose the appropriate tone, specificity, and action-oriented language.

Why does my onboarding copy cause user confusion during product setup?

Onboarding copy causes user confusion when it contains jargon, ambiguity, missing context, or tone mismatch. Identifying these specific clarity issues allows you to produce concise, actionable rewrites tailored to the user's initial experience.

What are the limitations of automated copy editing for tooltips and confirmations?

Automated copy editing for tooltips and confirmations is limited when context is missing. You must supply audience technical level, user mental state, and design context, or run context gathering protocols beforehand to ensure actionable rewrites.