Content Guidelines

MetaMask content design rules for user-facing strings — sentence case, punctuation, voice, tone, and terminology. Use when writing or reviewing copy in locale files, then checking the same standards in stories, constants, and README examples.

metamask 68cd75b 3 files · 8.0 KB Updated

File contents

Content guidelines

Encodes the MetaMask Content Design Style Guide for AI-assisted development. Covers capitalization, punctuation, voice and tone, and the approved terminology list. For component-specific copy rules, refer to the relevant component README in MetaMask/metamask-design-system (exposed via Storybook MCP).

When to use

  • Writing or reviewing user-facing product strings in locale files (locales/**/*.json)
  • Checking the same content standards in component stories, constants, and README examples
  • Auditing terminology (gas fee → network fee, dapp → site, etc.)
  • Reviewing sentence case, punctuation, voice, or tone in any user-facing string

Out of scope

  • Component-specific copy patterns — these live in each MMDS component README
  • Code style, TypeScript conventions, or component API decisions (see ui-development)
  • Marketing or external comms copy

metamask/openclaw-skills/tree/main/domains/ui/skills/content-guidelines commit 68cd75b1fa

Frequently asked questions

npx skillmds@latest add metamask/content-guidelines