skills.rest
FernandoBade
FernandoBadeCOMMUNITY
Explore all skills by this author →
GitHub

staff-ux-writing

Codify UX writing and localization governance for Zinero i18n workflows.

Updated Aug 23, 2026
Search Tags:#consistency#frontend#localization#i18n#tone-of-voice#ux-writing#content-governance
One-click install
npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-ux-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: staff-ux-writing
Source: https://github.com/FernandoBade/zinero-hack-your-expenses/tree/main/skills/staff-ux-writing
Command: npx skills add https://github.com/FernandoBade/zinero-hack-your-expenses --skill staff-ux-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zinero's UX writing and localization governance ensures that all user-facing copy across frontend and shared i18n uses a consistent tone, terminology, and localization quality, reducing confusion and friction for users.

Core Features & Use Cases

  • Tone governance: maintain Zinero's light, approachable personality across screens, labels, and messages.
  • Localization ownership: manage translations, transcreation decisions, and i18n mappings across en-US, pt-BR, and es-ES.
  • Content governance: establish naming conventions, reduce duplication, and enforce encoding and accessibility considerations.
  • Frontend collaboration: provide implementation-ready copy with clear i18n keys and modular phrasing for reuse.

Quick Start

Review upcoming UI copy against Zinero's voice guidelines and update i18n entries accordingly.

Frequently Asked Questions about staff-ux-writing

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

FAQPage Schema
How do I maintain consistent UX writing tone across multiple frontend languages?▼

Maintain UX writing consistency across frontend languages by applying tone governance rules and i18n mappings to ensure cross-language consistency for English, pt-BR, and es-ES.

What is the process for adding new i18n keys while managing content governance?▼

The process for adding new i18n keys involves following specified content governance steps, enforcing encoding quality, and updating cross-language mappings to reduce copy duplication across frontend workflows.

Can I use this to manage localization ownership for Spanish and Portuguese translations?▼

Yes, you can manage localization ownership for Spanish and Portuguese translations. It handles transcreation decisions and i18n mappings specifically across en-US, pt-BR, and es-ES locales.

What's the best way to review UI copy against voice and tone guidelines?▼

Review UI copy against voice guidelines by checking upcoming frontend text for tone consistency, applying naming conventions, and verifying accessibility considerations before updating i18n entries.

Does this approach work for frontend collaboration without creating duplicate copy?▼

Yes, it supports frontend collaboration by providing implementation-ready copy with clear i18n keys and modular phrasing for reuse, which actively reduces duplication across shared workflows.

Related Skills

Explore More Content & Communication Skills→
NoyoucringeNoyoucringe

content-design

Review and write n8n UI copy against terminology and tone guidelines.

Community
Advanced
VitorMRodovalhoVitorMRodovalho
2

nucleo-ia-hub

Orchestrate platform-wide development patterns for the AI & PM Research Hub.

Community
Advanced
webdriveriowebdriverio
11

Frontend Components

Enforce frontend component coding standards across web UI projects.

Official
Basic
systempromptiosystempromptio
2

brand-review

Review content against systemprompt brand identity and governance standards before publication.

Official
Intermediate