agentsclimarketplace

Product surface copy

Skill thanhaq/interface-compass-skills/skills/product-surface-copy

Frontend design skill pack for AI coding agents: briefs, design systems, audits, motion, copy, and ship checks.

Install
npx -y skills add thanhaq/interface-compass-skills --skill product-surface-copy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write and revise concise product interface copy. Use when Codex needs to improve button labels, navigation, form helper text, empty states, loading states, error messages, success messages, onboarding steps, settings descriptions, or UX microcopy inside an app or website.

SKILL.md

1.4 KB, 241 tokens by cl100k_base, as published. Nobody here has run it

Product Surface Copy

Goal

Make interface text useful under pressure. The copy should help users decide, act, recover, and trust what happened.

Workflow

  1. Identify the user's state: exploring, deciding, entering data, waiting, recovering, confirming, or managing.
  2. Rewrite labels around the action or object, not internal implementation language.
  3. Keep CTAs specific and short.
  4. Pair errors with recovery steps.
  5. Replace feature explanations with visible next actions in empty states.
  6. Check text fit in buttons, tabs, badges, cards, sidebars, and mobile widths.

Voice Rules

  • Use concrete verbs.
  • Prefer one clear sentence over a clever phrase.
  • Remove hype unless the surface is explicitly marketing.
  • Do not blame the user.
  • Avoid vague success text like "Done" when the object can be named.
  • Keep technical terms only when the audience expects them.

Output Shape

When revising copy, return:

  • Current issue.
  • Replacement copy.
  • Why it works.
  • Layout risk, if the copy may overflow.

Resources

  • Read references/copy-patterns.md for common UI copy patterns.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.