brand

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/brand/SKILL.md

The canonical home for this skill is brand in nextlevelbuilder/ui-ux-pro-max-skill

Brand

Name: brand
Rating: 60.8 (1 reviews)
Author: nextlevelbuilder

Brand identity, voice, messaging, asset management, and consistency frameworks.

When to Use

Brand voice definition and content tone guidance
Visual identity standards and style guide development
Messaging framework creation
Brand consistency review and audit
Asset organization, naming, and approval
Color palette management and typography specs

Script Paths

Script paths in this skill and its references/ are relative to the directory that contains this SKILL.md, not to the project: scripts/<file> is this skill's own scripts/ folder, and ../<skill>/scripts/<file> is a sibling sub-skill installed alongside it. Build the full path from that directory (Claude Code reports it as the skill's base directory when the skill loads) and keep the working directory at the project root — the scripts read and write project files such as docs/brand-guidelines.md, assets/design-tokens.json or src/ relative to it.

Quick Start

Inject brand context into prompts:

node scripts/inject-brand-context.cjs
node scripts/inject-brand-context.cjs --json

Validate an asset:

node scripts/validate-asset.cjs <asset-path>

Extract/compare colors:

node scripts/extract-colors.cjs --palette
node scripts/extract-colors.cjs <image-path>

Brand Sync Workflow

# 1. Edit docs/brand-guidelines.md (or use /brand update)
# 2. Sync to design tokens
node scripts/sync-brand-to-tokens.cjs
# 3. Verify
node scripts/inject-brand-context.cjs --json | head -20

The sync stops when it detects existing token files, :root custom properties or Tailwind v4 @theme variables in common CSS entry points and their local CSS imports, or Tailwind theme colors and presets. Review the reported source before proceeding. If the detected files are the managed assets/design-tokens.* outputs from an earlier sync and replacing them is intentional, re-run with --force.

Files synced:

docs/brand-guidelines.md → Source of truth
assets/design-tokens.json → Token definitions
assets/design-tokens.css → CSS variables

Subcommands

Subcommand	Description	Reference
`update`	Update brand identity and sync to all design systems	`references/update.md`

References

Topic	File
Voice Framework	`references/voice-framework.md`
Visual Identity	`references/visual-identity.md`
Messaging	`references/messaging-framework.md`
Consistency	`references/consistency-checklist.md`
Guidelines Template	`references/brand-guideline-template.md`
Asset Organization	`references/asset-organization.md`
Color Management	`references/color-palette-management.md`
Typography	`references/typography-specifications.md`
Logo Usage	`references/logo-usage-rules.md`
Approval Checklist	`references/approval-checklist.md`

Scripts

Script	Purpose
`scripts/inject-brand-context.cjs`	Extract brand context for prompt injection
`scripts/sync-brand-to-tokens.cjs`	Sync brand-guidelines.md → design-tokens.json/css
`scripts/validate-asset.cjs`	Validate asset naming, size, format
`scripts/extract-colors.cjs`	Extract and compare colors against palette

Templates

Template	Purpose
`templates/brand-guidelines-starter.md`	Complete starter template for new brands

Routing

Parse subcommand from $ARGUMENTS (first word)
Load corresponding references/{subcommand}.md
Execute with remaining arguments

Repository: nextlevelbuilder/ui-ux-pro-max-skill
Path: .claude/skills/brand/SKILL.md
Commit: 09170ee

Last updated: 2 hours ago
First committed: 7 months ago

Canonical home

nextlevelbuilder/ui-ux-pro-max-skill

In sync

since Sep 6, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.