clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for interface clarity.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ssrrb/cerramos-codebase --skill clarify-ssrrb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Ssrrb/cerramos-codebase/tree/main/.codex/skills/clarify
Command: npx skills add https://github.com/Ssrrb/cerramos-codebase --skill clarify-ssrrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text causes user errors, frustration, and support tickets. This Skill identifies jargon, ambiguity, passive voice, and tone mismatches in product copy and rewrites it so users immediately understand what happened and what to do next. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems including jargon, ambiguity, excessive length, wrong assumptions, and tone mismatches based on audience and user mental state. - Systematic Rewriting: Improves error messages, form labels, button text, help text, empty states, success messages, loading states, confirmation dialogs, and navigation labels with before/after patterns. - Clarity Verification: Checks rewritten copy for comprehension, actionability, brevity, consistency, and appropriate tone. - Use Case: A settings page shows "Error 403: Forbidden" and a generic "Submit" button. The Skill rewrites these to "You don't have permission to view this page. Contact your admin for access." and "Save changes". ## Quick Start Review the error messages and button labels in my checkout flow and rewrite any unclear copy.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I write better error messages for my app?▼

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. Replace codes like "Error 403: Forbidden" with "You don't have permission to view this page. Contact your admin for access."

How to improve button and CTA text in a UI?▼

Describe the specific action using active voice, such as "Create account" or "Save changes" instead of "Submit" or "OK". Match the user's mental model and be specific about the outcome.

What makes UX copy unclear or confusing?▼

Common problems include jargon users don't understand, ambiguous wording, passive voice, excessive length, assumed knowledge, missing context, and tone that doesn't match the situation such as humor during errors.

Should empty states just say no items found?▼

No. Explain why the state is empty when not obvious and show the next action clearly, such as "No projects yet. Create your first project to get started." Avoid dead-end messages.

When should confirmation dialogs be used?▼

Use them only for risky or destructive actions. State the specific action and consequences, like "Delete 'Project Alpha'? This can't be undone.", and label buttons with the action rather than "Yes".