@tank/ux-writing

Write clear interface copy for app screens and product flows.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-ux-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/ux-writing
Source: https://github.com/tankpkg/packages/tree/main/skills/ux-writing
Command: npx skills add https://github.com/tankpkg/packages --skill tank-ux-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams write interface copy that is clear, useful, and consistent so users can understand what to do, recover from errors, and move through flows without friction.

Core Features & Use Cases

  • Microcopy patterns: Button labels, tooltips, dialogs, notifications, loading states, and navigation text.
  • Error and form guidance: Inline validation, submission errors, payment errors, and accessible field copy.
  • Onboarding and empty states: Welcome screens, permission prompts, feature discovery, and zero-data experiences.
  • Voice and tone strategy: Define a stable product voice and adapt tone for success, warning, error, and destructive moments.
  • Use case: Draft the copy for a signup form, then refine the confirmation message, validation errors, and empty state to match the same product voice.

Quick Start

Ask the skill to write or revise interface copy for a specific screen, flow, or component using the provided product context and desired tone.

Frequently Asked Questions about @tank/ux-writing

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

FAQPage Schema
How do I write clear UX writing for app onboarding flows and empty states?

UX writing for onboarding flows and empty states covers welcome screens, permission prompts, and zero-data experiences. It drafts clear interface copy that helps users discover features and navigate product screens without friction.

What's the best way to write error messages and form validation copy?

Error messages and form validation copy should provide inline validation, submission errors, and payment errors with accessible field copy. Clear error guidance helps users understand what went wrong and recover from errors quickly using established UX writing frameworks.

How do I define voice and tone for microcopy across different UI components?

Voice and tone strategy establishes a stable product voice while adapting tone for success, warning, error, and destructive moments. It ensures consistent microcopy across button labels, tooltips, dialogs, and notifications throughout your interface.

Does UX writing support accessibility and localization for interface copy?

UX writing provides accessibility and localization readiness for interface copy. It ensures form labels, error messages, and component patterns meet accessibility standards while remaining translatable for global product screens and diverse user contexts.

When do I need UX writing guidance for product screens?

You need UX writing guidance when drafting copy for signup forms, confirmation messages, validation errors, or navigation text. It helps teams write useful, consistent interface copy that enables users to understand actions and move through flows smoothly.