i-clarify

Identify and rewrite unclear interface text across dialogs, labels, and error messages.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill i-clarify-patkik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-clarify
Source: https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2/tree/main/.agents/skills/i-clarify
Command: npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill i-clarify-patkik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand and use.

Core Features & Use Cases

  • Identify clarity problems in UI text (jargon, ambiguity, passive voice, length, assumptions, missing context, tone mismatch) and recommend concise rewrites.
  • Plan and implement copy improvements using a clear strategy: define the primary message, required user action, tone, and constraints.
  • Apply the clarity framework across error messages, form labels, instructions, empty states, and tooltips to reduce confusion and support requests.
  • Real-world example: rewrite the onboarding error copy and labels to improve task completion and user confidence.

Quick Start

Provide a clear, actionable rewrite for the current screen's copy.

Frequently Asked Questions about i-clarify

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

FAQPage Schema
How do I improve unclear UX copy in interface text?

Rewriting confusing error messages involves identifying jargon, ambiguity, and tone mismatch, then applying a clarity framework to define the primary message and actionable guidance. This ensures your error copy provides clear, actionable steps for users to resolve the issue.

What is the best way to fix confusing form labels and onboarding microcopy?

Fixing confusing form labels and onboarding microcopy requires applying a structured copy-improvement workflow. You define the primary message, required user action, and tone to produce concise rewrites that reduce confusion and improve task completion rates.

How do I write actionable guidance for empty states and tooltips?

Writing actionable guidance for empty states and tooltips involves replacing vague interface text with clear primary messages and specific user actions. This structured approach ensures users understand the context and know exactly what steps to take next within the interface.

Can I use a clarity framework to reduce user support requests for interface text?

Yes, applying a clarity framework to interface text reduces user support requests by eliminating assumptions and missing context in microcopy. Structured rewrites of labels, dialogs, and instructions make the product easier to understand and use independently.

Why does ambiguous interface text cause task completion failures?

Ambiguous interface text causes task completion failures when it relies on jargon, passive voice, or missing context that confuses users. Clarifying these interface messages and labels provides the direct guidance needed to improve user confidence and completion rates.