ui-copy

Writes and reviews UI copy, microcopy, and error messages using ASD-STE100 Simplified Technical English.

5.7k|625|Updated May 7, 2025
One-click install
npx skills add https://github.com/superplanehq/superplane --skill ui-copy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-copy
Source: https://github.com/superplanehq/superplane/tree/main/.agents/skills/ui-copy
Command: npx skills add https://github.com/superplanehq/superplane --skill ui-copy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent, vague, or jargon-heavy interface text confuses users and erodes trust. This Skill provides a structured workflow and review checklist for writing clear, task-oriented UI copy that follows ASD-STE100 Simplified Technical English and matches SuperPlane product vocabulary.

Core Features & Use Cases

  • UI Copy Writing Workflow: A six-step process covering goal identification, vocabulary matching, STE drafting, tightening, expectation-setting, and consistency scanning.
  • Element-Specific Guidance: Concrete rules and before/after examples for buttons, links, empty states, error messages, confirmations, and success messages.
  • Product Vocabulary Guardrails: Enforces correct SuperPlane naming, bans internal code terms in user-facing strings, and keeps terminology consistent across screens.
  • Use Case: When implementing a destructive action dialog, use this Skill to produce copy like "Delete 'Deploy to production'? This removes the canvas for everyone." instead of a vague "Are you sure?"

Quick Start

Use the ui-copy skill to write the button label, helper text, and error message for the new GitHub integration connection form.

Frequently Asked Questions about ui-copy

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

FAQPage Schema
How do I write better UI copy and microcopy?

Identify the user's goal and screen state first, then draft in plain Simplified Technical English with specific verbs like Create, Save, or Archive. Keep instructions under 20 words, match existing product vocabulary, and verify every word earns its place.

What is ASD-STE100 Simplified Technical English in UX writing?

ASD-STE100 is a controlled language specification that restricts vocabulary and sentence structure for clarity. In UI copy it means avoiding jargon, idioms, contractions, and unexplained acronyms while preferring active voice and simple present tense.

How should error messages be written for user interfaces?

Error messages should explain what happened in user terms and provide a recovery path. For example, write "We could not connect to GitHub. Check your credentials and try again." instead of exposing a raw system error code.

When should I not use humor in UI copy?

Never use humor in high-friction, high-risk, error, payment, privacy, or destructive flows. Humor in these contexts can obscure the action, reduce trust, and confuse users who need precise information about consequences.

What are the word limits for interface text in this style?

Instructions should stay at or under 20 words and descriptions at or under 25 words. Short copy is preferred only when it remains specific; clarity always takes priority over brevity or personality.