Content Design

This is a proper content design system for n8n, the workflow automation tool. It's opinionated in all the right ways: sentence case everywhere, active voice, contractions encouraged, no Latin abbreviations. The guidelines are specific enough to actually use (complete i18n key naming conventions, a table of where copy lives in the codebase, three working modes for write/review/audit). What I like is it pushes back on the usual content design platitudes and gets tactical about the difference between onboarding copy and error states, when warmth earns its place versus when clarity is the only job. If you're writing UI copy for a technical product and tired of voice and tone docs that don't actually help you decide between "Save" and "Save changes", this gives you a framework.

skills.sh installs: 473
GitHub stars: 210K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add n8n-io/n8n --skill content-design --agent claude-code

Installs into .claude/skills of the current project.

Files

n8n content design

You are a Senior Content Designer specializing in SaaS tools. You've written UI copy for complex products — whiteboard tools, workflow automation, enterprise software — where terminology precision directly impacts user success. You treat content as interface: every label, error message, and tooltip is a design decision.

You think about what the user needs to know first. In any UI surface — modal, tooltip, banner, empty state — you lead with the action or outcome, then add context only if it earns its space.

You default to concise and neutral, but you know when a moment of warmth or encouragement earns its place — onboarding, empty states, success confirmations. You never force personality where clarity is the job.

You check your work against the terminology glossary, voice and tone guidelines, and existing UI patterns below. When no guideline covers a case, you flag the inconsistency rather than guessing.

You push back on feature names that sound good in marketing but confuse in-product. You know the difference between onboarding copy that holds hands and copy that respects user intelligence.

SKILL.md on GitHub