agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/ux-copy/SKILL.md

ux-copy

Skill4 starsChanged 11 days agoMITView on GitHub

Write or review product UI copy. Use when changing headings, labels, buttons, help, messages, navigation, i18n strings, or product terminology.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read REFERENCE.md for tone, capitalization, budgets, and examples.

    line 8
  2. Distinctive:

    Use project glossary and canonical product names.

    line 11
  3. Distinctive:

    Keep this skill's glossary, endpoint and factual-copy requirements.

    line 17
  4. Distinctive:

    Read changed strings in context.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

For prose, read Poteto.

Read REFERENCE.md for tone, capitalization, budgets, and examples. One point per sentence; no filler/repetition. Preserve safety, limits, uncertainty, and accessible labels. Use project glossary and canonical product names; GLOSSARY.md is product-specific.

Write

For vocabulary, whole-message localization, empty states and destructive flows, load better-writing. Keep this skill's glossary, endpoint and factual-copy requirements.

Draft minimal accurate strings; check the whole view. Make only requested changes. Flag unverified facts; never invent behavior, permissions, causes, or recovery. Do not imply human approval.

Review

Read changed strings in context. Give location, exact quote, named pattern, rewrite/removal. Relocate useful facts. A clean review names files read and distinct UI strings checked. Report missing context; do not claim visual checks from source. Review does not edit.

Scope and checks

Scope: TSX/JSX, navigation, i18n and chat UI; exclude docs, generated reference descriptions and replies. Project rules win.

Install executable PostToolUse Edit|Write hooks from scripts/: ux-copy-check.sh, prose-style-check.sh, _hook-lib.sh. Preserve host configuration. UX checks warn on selected TS/TSX patterns only; JSX/i18n need review. Verify host activation. Escapes need reasons: // allow: ux-copy [reason], <!-- allow: prose-style [reason] -->.

Tone evals: evals/RUBRIC.md. Hook passes do not prove tone.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free