ckm:brand

Verified

by nextlevelbuilder · Updated Apr 16, 2026

opus

4.2Kin4.3Kout

$0.431m 36s

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

brandingstyle-guidedesign-tokenscontentasset-management

See It In Action

1 turns·claude

The project codebase is in your current working directory. Explore the files to understand the code before making changes. webinar banner goes live this afternoon — can you sync the latest brand stuff and check the launch banner matches our updated palette, then send me the outputs

Let me explore the project and pull in the brand skill simultaneously.

Good — I can see the full picture. Here's what's going on:

Design tokens are stale (last synced April 1). The accent color was updated in brand guidelines from #FF6B35 → #FF7043 on April 13, but the token files still have the old value.

The banner SVG has two off-palette colors:

#E53935 on the decorative circle (should be Coral Flame #FF7043)
#9E9E9E on the date text (not in palette — should use Cloud Gray #F8F9FA or similar)

Let me sync the tokens first, then fix the banner.

Tokens synced — accent is now #FF7043 in both files (v2.3.1). Let me verify and then run the color extraction on the current banner to confirm the issues.

Confirmed: two off-palette colors. Fixing the banner now — replacing #E53935 (decorative circle) with Coral Flame #FF7043, and #9E9E9E (date text) with Cloud Gray #F8F9FA for proper contrast on the dark card.

Now let me re-run both validation scripts to confirm everything passes.

Colors all pass. The asset validator flagged the filename prefix — the brand guidelines say files should start with doany-. Let me fix that.

All green. Here's the full rundown:

Brand Sync + Banner Audit Results

1. Design tokens synced (v2.3.0 → v2.3.1)

assets/design-tokens.json and assets/design-tokens.css updated
Key change: accent color #FF6B35 → #FF7043 (Coral Flame) per today's palette tweak

2. Banner color fixes — 2 off-palette colors corrected

Element	Was (off-palette)	Now (on-palette)
Decorative circle	`#E53935` (random red)	`#FF7043` (Coral Flame)
Date line text	`#9E9E9E` (unlisted gray)	`#F8F9FA` (Cloud Gray)

3. Filename renamed

webinar-launch-banner.svg → doany-webinar-launch-banner.svg (brand prefix rule)

4. Final validation — all pass

Color check: 5/5 on-palette, 0 off-palette Asset validation: 5/5 rules pass (format, size, naming, prefix, dimensions 1200x628)

The banner is ready to go live at assets/doany-webinar-launch-banner.svg.

Claude Sonnet 4.6

doany-webinar-launch-banner.svg

assets_design-tokens.css.diff1 KB assets_design-tokens.json.diff2 KB

External Tools

Tool	Type
node	binary

Permissions

Scope	Description
filesystem:read
filesystem:write
process:spawn

SKILL.md

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

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

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

FAQ

What does ckm:brand do?

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

When should I use ckm:brand?

Use it when you need a repeatable workflow that produces code diff, image output.

What does ckm:brand output?

In the evaluated run it produced code diff, image output.

How do I install or invoke ckm:brand?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does ckm:brand support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does ckm:brand need?

It uses node; channels commonly include diff, image; permissions include filesystem:read, filesystem:write, process:spawn.

Is ckm:brand safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is ckm:brand different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does ckm:brand outperform not using a skill?

About ckm:brand

When to use ckm:brand

You need to define or update brand voice, messaging, or visual identity rules. You want to sync brand guidelines into local design token files. You need to review assets for naming, format, or palette consistency.

When ckm:brand is not the right choice

You need live integration with external design platforms or asset management systems. You need code implementation workflows unrelated to brand guidelines or assets.

What it produces

Produces code diff and image output.