Skills nextlevelbuilder ui-ux-pro-max-skill UI/UX Pro Max

brand

Use it when:
You want one source of truth for a brand's colors, fonts and voice that design tokens and generated content follow.
It does:
Keeps docs/brand-guidelines.md as the source, syncs it to design-tokens.json and design-tokens.css, and extracts brand context for prompts.
You get:
An updated guidelines file and token files, a summary of the theme and colors, and checks on asset files and image colors.
Stops:
When your project already has a token source, such as :root variables or a Tailwind theme, rather than build a second one.

Skill 1 of 6 in the UI/UX Pro Max bundle, before design-system.

TL;DR

One of the design skills, written by ClaudeKit, that ship next to ui-ux-pro-max in the UI UX Pro Max repo. It treats docs/brand-guidelines.md as the brand's source of truth, with a starter template for new brands, and a script syncs it to design-tokens.json and design-tokens.css. Its update command asks for a theme name, primary, secondary and accent colors with hex codes, and mood keywords for image generation, or takes one of five presets such as ocean-professional; it then edits the guidelines, runs the sync, checks the output and reports the theme and the files it changed. The sync refuses to run beside an existing token system unless you pass --force for its own earlier output. Other scripts extract brand context to inject into prompts, validate an asset's name, size and format, and pull colors from an image to compare with the palette. References cover voice, visual identity, messaging, consistency, asset organization, color, typography, logo usage and approval checklists.

Summarizes the skill at b7d5353.

npx skills add https://github.com/nextlevelbuilder/ui-ux-pro-max-skill --skill brand
Total Downloads
47,000 on skills.sh, Nov 9, 2026
Repo stars
146,988 nextlevelbuilder/ui-ux-pro-max-skill
First seen
Jun 25, 2026 on skills.sh
Weekly Downloads
3.3K
+68% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 211,978
Sep 281,883
Oct 51,869
Oct 122,212
Oct 192,589
Oct 263,375
Nov 23,809
Nov 93,316
Category

Taste for interfaces that don't look generated: direction, motion and accessibility.

SEO, copy, conversion, social media and e-commerce.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.

Type

Operates a CLI, API, app or bundled script to get something done.

Effect

Its own steps create or change files, git state or local tools.

Needs

Instructions only. Works in any agent that supports skills.

Publisher

Everyone else. Unverified vendor claims default to community.

Topics

SKILL.md

From nextlevelbuilder/ui-ux-pro-max-skill at b7d5353. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: brand
description: Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
argument-hint: "[update|review|create] [args]"
metadata:
  author: claudekit
  version: "1.0.0"

Brand

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

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