skills.rest
Uguryldz
UguryldzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

content-design

Writes, reviews, and audits UI copy for n8n interfaces against terminology and tone guidelines.

Updated Apr 9, 2026
Search Tags:#microcopy#ux writing#i18n#n8n#content design#ui copy#copy audit
One-click install
npx skills add https://github.com/Uguryldz/n8nclean --skill content-design-uguryldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-design
Source: https://github.com/Uguryldz/n8nclean/tree/main/.claude/plugins/n8n/skills/content-design
Command: npx skills add https://github.com/Uguryldz/n8nclean --skill content-design-uguryldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent UI copy — mixed terminology, title case drift, Latin abbreviations, and user-blaming error messages — erodes trust in a product. This Skill enforces n8n's content design standards when writing, reviewing, or auditing user-facing text across i18n files, Vue components, and node descriptions. ## Core Features & Use Cases - Write mode: Drafts button labels, error messages, tooltips, empty states, and confirmation dialogs with suggested i18n keys and rationale. - Review mode: Checks existing copy against the terminology glossary, tone rules, and grammar conventions, returning a severity-grouped issue table. - Audit mode: Greps en.json and Vue files for common violations like Latin abbreviations, missing contractions, and passive voice. - Use Case: A developer adds a new settings panel and asks for empty-state copy; the Skill drafts options following sentence case, suggests the key settings.communityNodes.empty.title, and flags any hardcoded strings that should use i18n. ## Quick Start Ask the assistant to review the error messages in a Vue component or i18n locale file against n8n's content guidelines.

Frequently Asked Questions about content-design

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

FAQPage Schema
How do I write error messages for a SaaS product UI?▼

Structure error messages as what happened plus why, if known, plus what to do next. Never blame the user — write "The API key isn't valid" instead of "You entered an invalid API key" — and avoid bare codes like "Error 403".

How to audit i18n JSON files for copy violations?▼

Grep the locale file for patterns like Latin abbreviations (e.g., i.e., etc.), missing contractions (cannot, do not), overused "please", and user-blaming phrases (You must, You entered). Triage results by severity: terminology first, then tone, then grammar.

What naming convention should i18n keys follow?▼

Use hierarchical dot-notation matching the feature area, such as settings.communityNodes.empty.title. Reserve generic.* for universal labels and _reusableBaseText.* for shared constants, matching the nesting depth of nearby existing keys.

Should UI copy use sentence case or title case?▼

Use sentence case for all titles, headings, menu items, labels, and buttons — capitalize only the first word and proper nouns. Write "Zoom in" and "What triggers this workflow?", not "Zoom In" or title-cased headings.

When should hardcoded strings in Vue templates be flagged?▼

Flag any hardcoded user-facing string in Vue templates because it bypasses localization. Copy should live in the i18n locale file and be referenced via i18n.baseText('key') or the $t('key') shorthand.

Related Skills

Explore More Design & Creative Skills→
ousiassousiass

design-request-en

Gather design change requests via dialog and generate GitHub Issues or Markdown files.

Community
Intermediate
streamlitstreamlit
45.7k

fixing-flaky-e2e-tests

Diagnose and fix flaky Playwright end-to-end tests in Streamlit CI pipelines.

Official
Intermediate
getcrew44getcrew44
358

accessibility-review

Audit web UI against WCAG 2.1 AA and report categorized accessibility issues.

Official
Intermediate
htlin222htlin222
77

vale

Run Vale prose linter on markdown and text files to identify and auto-fix writing issues.

Community
Intermediate