mcpbeat

Brand Voice To UI Copy

thegoat395/brand-voice-to-ui-copy

Translate brand voice into UI copy for websites and apps. Use for buttons, labels, empty states, loading states, errors, tooltips, form help, nav labels, product copy, onboarding microcopy, premium tone systems, and making brand voice usable in interface text instead of only marketing prose.

2k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
115
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/TheGoat395/Codex-Skills --skill brand-voice-to-ui-copy

What comes with it

3 947 bytes besides the instruction
agents/openai.yaml
references/brand-voice-to-ui-copy-guide.md

The instruction itself

3 sections, as written by the author

Brand Voice To UI Copy

Use this skill to make interface words feel on-brand without becoming unclear or cute.

Workflow

  • Inspect the page goal, audience, offer/product reality, source copy, proof, IA, forms, SEO/social metadata, brand voice, and verification commands.
  • Read Brand Voice To UI Copy Guide before changing headings, sections, CTAs, metadata, labels, or UI copy.
  • Draft from evidence: real product/service facts, proof, objections, user tasks, and constraints.
  • Replace generic claims with specific language or remove them.
  • Inspect the rendered page on desktop and mobile for hierarchy, wrapping, repetition, and whether copy still matches the UI.

Always Protect

  • Inspect before writing or coding: audience, offer, product/service reality, source copy, assets, proof, claims, conversion goal, information architecture, SEO/metadata needs, forms, legal/trust constraints, and available verification commands.
  • Use copy to make the design more specific: every headline, label, CTA, section, and proof point should reduce ambiguity rather than decorate the layout.
  • Avoid generic premium language, vague transformation claims, placeholder testimonials, fake metrics, empty adjectives, and hero copy that could fit any brand.
  • Write in the user's domain vocabulary while keeping language clear, concise, concrete, and scannable.
  • Tie claims to proof: screenshots, artifacts, reviews, credentials, specifications, case studies, pricing terms, process details, or real outcomes.
  • Keep navigation, forms, pricing, FAQs, and CTAs honest and task-focused; do not create dark patterns or hide material terms.
  • Respect accessibility and structure: semantic headings, meaningful link/button text, labeled forms, useful error/help text, readable line lengths, and no critical copy trapped in images.
  • Before delivery, inspect rendered desktop and mobile copy for hierarchy, wrapping, overflow, repetition, and whether the words still match the implemented page.

How to use it

Copy the folder

Take thegoat395/brand-voice-to-ui-copy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.