Use brand-kit

Capture a brand once as a reusable brand.json

Capture a brand once as a reusable brand.json — logo files (and an on-dark version), colour roles as hex codes, heading and body fonts, voice, imagery rules, a PowerPoint template, contact details and the legal footer — plus a one-page BRAND.md, with text contrast checked and every value traced to where it came from.

Reach for it when the user wants decks, flyers or documents in their branding, says "use our brand", "here's our logo and colours", "set up our brand kit", or hands over brand guidelines.

Install it

npx skilldrop-cli install brand-kit                 # Claude Code, your user folder
npx skilldrop-cli install brand-kit --project       # Claude Code, this repo
npx skilldrop-cli install brand-kit --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Design pack: --pack design installs it with its neighbours.

It ships scripts, so it needs Python 3 (standard library only, nothing to install). What they may touch is declared in its manifest.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Here's our logo and brand colours — set up a brand kit we can reuse"
• "Use our brand guidelines PDF so everything matches our style"
• "Capture our fonts, colours and logo rules in one place"
• "Make our decks and flyers on-brand — start with the brand settings"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Build a PowerPoint deck for the board meeting"
• "Make a flyer for our open day"
• "Design a new logo for my startup"

If another skill answers instead, ask for this one by name: "use brand-kit".

Check what you get

A good result:

• Every colour is a hex code with a role. "Our green" is not a brand colour; #0E5A46 used for title bars is.
• Text on background passes 4.5:1, checked by the script rather than by eye.
• Every value says where it came from, and inferred values are marked as inferred.
• Logo files are real paths that exist, with a PNG for PowerPoint and an on-dark version when the brand has one.
• Nothing is invented. A field the user didn't supply and couldn't be read from their sources is left out and listed, not guessed.
• BRAND.md fits on one page. A person checks the brand from it without opening the JSON.

See a worked example

• northwind brand

Use something else when

• Designing a new brand from scratch: this captures a brand, it doesn't invent one
• Building the deck itself; convert its Markdown with md-to-pptx
• A one-off document where the user only wants the default look

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: md-to-pptx, md-to-docx

Edit this page on GitHub · View source