Brand kit
Assemble or audit a brand kit - logo, colors, typography, spacing, usage rules - and pull real brand data via Brand.dev. Use when starting brand work, onboarding a client, or standardizing a brand.From its SKILL.md
npx -y skills add m-binimran/design-pack --skill brand-kitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 244 tokens by cl100k_base, as published. Nobody here has run it
brand-kit
The single reference every asset is built from. Get the real values, don't guess.
Process
- Pull what exists via Brand.dev (logos, colours, industry by domain) and/or the client's Figma/files. Use real hex values, not approximations.
- Assemble the kit (
templates/BRAND-KIT.md):- Logo: versions (full/mark/mono), minimum size, clear space, misuse don'ts.
- Colour: primary/secondary/neutrals with hex + usage; check contrast for text pairs.
- Type: display + body pairing, weights, sizes, web/print licenses.
- Spacing/grid, iconography style, photography/illustration direction, voice.
- Tokenize the colours/type/spacing (hand to
design-tokens).
Output
- A complete brand kit doc + tokens, with logo files referenced and licenses recorded.
Guardrails
- Real values from Brand.dev / the client, not invented hex codes.
- Record font and asset licenses (the
license-guardhook). Flag any contrast-failing colour pairs.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most marketing audience skills give in 244 tokens
Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07
- Apply Poppins font to headingsin 41 of 690, across 6 files
- Apply Lora font to body textin 41 of 690, across 6 files
- Use Arial fallback for headingsin 39 of 690, across 4 files
- Use Georgia fallback for body textin 39 of 690, across 4 files
- Maintain text hierarchy and formattingin 39 of 690, across 4 files
- Use accent colors for non-text shapesin 38 of 690, across 3 files
- Use RGB values for precise color matchingin 38 of 690, across 3 files
- Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
- Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
- Use active voice instead of passive voicein 26 of 690, across 10 files
- Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
- Prioritize clarity over clevernessin 22 of 690, across 8 files
Said here and by no other author read
- check text contrast over imagery
- pull real brand values via Brand.dev
- assemble the brand kit
- tokenize colors type and spacing
- record font and asset licenses
- flag contrast-failing color pairs
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.