brand-guidelines_skill

Overview

This skill applies Mastra's brand colors, typography, and writing style to documentation, code examples, and UI artifacts. It enforces technical, implementation-first language and consistent visual tokens for light and dark modes. Use it to make docs and examples match Mastra's identity and developer-focused voice.

How this skill works

The skill inspects content and assets, replacing or annotating colors, typography, and code-syntax tokens with Mastra's official values. It evaluates prose for tone, flags marketing language to avoid, and suggests concrete, implementation-first rewrites. It can emit a style report and a ready-to-use token set for light/dark themes and syntax highlighting.

When to use it

• Preparing developer documentation, API references, or README-style guides
• Styling code examples, syntax highlighting, and code block themes
• Designing docs sites, UI components, diagrams, and flowcharts
• Writing technical tutorials, implementation notes, or code comments
• Standardizing theme tokens for light and dark modes in a project

Best practices

• Write for engineers: prioritize technical precision over marketing copy
• Prefer concrete implementation details and runnable code examples
• Avoid marketing adjectives and vague benefit phrases listed in the guidelines
• Use the provided color tokens and typography scale exactly for consistency
• Apply line-height, letter-spacing, and code font-weight rules for readable output

Example use cases

• Convert a docs site theme to Mastra colors and typography with light/dark tokens
• Scan documentation drafts and rewrite sentences to be technical and implementation-first
• Apply Mastra syntax highlighting palette to code blocks for consistent presentation
• Generate a style token file (CSS/JSON/TS) containing color, typography, and border tokens
• Review tutorial content and replace marketing phrasing with concrete examples and commands