get-brand-kit
The one place a repository's brand values live. Every skill, prompt and template
that needs a colour, a typeface, a logo, a layout rule or the voice reads it from
here at the moment of need, rather than holding its own copy.
Paths below are relative to this skill's directory; resolve them to absolute
paths before running anything.
Why it exists
Brand values change. When they do, one file should change and every consumer
should pick up the new value. The failure this prevents is concrete: a retired
hex survives a rebrand because it was copied into image prompts, guidelines and
templates "for convenience". Each copy looks correct in isolation, and finding
them all takes longer than the rebrand did.
Where the brand kit lives
This repository's agent configuration should have been provided to you (the
## Agent skills block pointing at docs/agents/). If it is missing, use the
default below and suggest the user run the setup-aclarify-skills skill.
- A configured brand folder wins. If
docs/agents/workspace.md has a
**Brand kit:** line naming a folder (for example brand/ inside the
conventions folder), read the brand from there and ignore this skill's own
reference files. The folder uses the same file names as references/ below,
and its logos.md gives logo paths relative to that folder. Those names are
also how brand-review, design-expert and create-html-slides read the
folder when this skill is not installed, so keep them.
- Otherwise, this skill's own files are the brand kit:
references/ and
assets/. A user makes them theirs by forking or editing them in place.
A configured folder is taken whole. If it lacks a dimension (say, no
voice-and-tone.md), that dimension is not yet defined: never fill it from this
skill's placeholder files.
The placeholder brand
As shipped, every reference file opens with Status: placeholder. The values
are a neutral slate and the logos are a generic wordmark reading "YOUR BRAND", so
a deck or card made before anyone sets a brand looks deliberate rather than
broken, and never carries someone else's identity.
When a file you read is still a placeholder, use its values, and tell the user
in your reply that the asset uses placeholder brand values, not theirs. Never
present placeholder values as the user's brand.
How to use it
- Find where the kit lives (above).
- Identify the dimension you need and read only that file.
- Use the values exactly. Do not paraphrase, derive, or interpolate a value.
- If a value is not documented, stop and ask the user. Do not guess. Once they
give it, add it to the kit first, then use it.
| File |
Read it when you need |
| references/color-palette.md |
any colour: backgrounds, text, accents, borders, data marks |
| references/typography.md |
a typeface, weight, type scale or web-font source |
| references/logos.md |
a logo file, or the choice between light and dark variants |
| references/visual-design-system.md |
to compose an asset: background, cards, badges, hierarchy, data marks, spacing |
| references/voice-and-tone.md |
to write or align copy to the brand voice |
Replacing the placeholder with your brand
Pick where your kit will live:
- Edit this skill in place, when it is installed as files you own (a fork, or
a copy in the repository). Simplest, and nothing else needs configuring.
- Keep it in a repository folder, when this skill is installed somewhere an
update would overwrite (a plugin or a shared install), or when the brand should
sit with the repository's other conventions. Copy
references/ and assets/
into the folder, then add one line to docs/agents/workspace.md:
- **Brand kit:** \docs/standards/brand/`` (your path).
Then, in whichever copy is the kit:
- Colours. Replace the hex values in
color-palette.md. Keep the token
names: consumers reference tokens, not hexes.
- Typography. Name your faces, weights, scale and where the web fonts load
from in
typography.md.
- Logos. Replace the two SVGs and keep their file names, so nothing that
points at them changes. Add a variant only as a new file listed in
logos.md.
- Visual design system. Rewrite
visual-design-system.md to describe how
your assets are composed. Name tokens from the palette, never hexes.
- Voice. Fill
voice-and-tone.md from your real brand voice, with example
sentences.
- Flip each file's status from
Status: placeholder to Status: defined as
you finish it, so consumers stop warning about it.
- Grep for the values you retired across the whole repository (see the last
rule in
color-palette.md) and update every copy you find.
Rules for every consumer
- Never hardcode a brand value in another skill, template or note. Name the
token and read this kit when you need it.
- Never invent one. If it is not documented, the answer is "not yet
defined". Raise it rather than fabricating.
- Change the kit, not a local copy. When the brand evolves, it evolves here.
- Renaming or removing a value is a brand-level change. Update every
consumer in the same change.
1---2name: get-brand-kit3description: >-4 Look up a brand value BEFORE making anything that must look or sound on-brand: a slide,5 an image prompt, an infographic, a social asset, a landing page, an email graphic. The6 repository's single source of truth for colours, typography, logos, the visual design7 system and voice; other skills load it by name. Ships a placeholder brand to replace with8 your own. Do NOT use to review copy (use `seven-copy-critics`), to audit a finished asset9 (use `brand-review`), or to redesign a product interface (use `design-expert`, which10 loads this for its values).11license: MIT12metadata:13 source: https://skillmd.com/skills/spencermarx/get-brand-kit14---1516# get-brand-kit1718The one place a repository's brand values live. Every skill, prompt and template19that needs a colour, a typeface, a logo, a layout rule or the voice reads it from20here at the moment of need, rather than holding its own copy.2122Paths below are relative to this skill's directory; resolve them to absolute23paths before running anything.2425## Why it exists2627Brand values change. When they do, one file should change and every consumer28should pick up the new value. The failure this prevents is concrete: a retired29hex survives a rebrand because it was copied into image prompts, guidelines and30templates "for convenience". Each copy looks correct in isolation, and finding31them all takes longer than the rebrand did.3233## Where the brand kit lives3435This repository's agent configuration should have been provided to you (the36`## Agent skills` block pointing at `docs/agents/`). If it is missing, use the37default below and suggest the user run the `setup-aclarify-skills` skill.38391. **A configured brand folder wins.** If `docs/agents/workspace.md` has a40 `**Brand kit:**` line naming a folder (for example `brand/` inside the41 conventions folder), read the brand from there and ignore this skill's own42 reference files. The folder uses the same file names as `references/` below,43 and its `logos.md` gives logo paths relative to that folder. Those names are44 also how `brand-review`, `design-expert` and `create-html-slides` read the45 folder when this skill is not installed, so keep them.462. **Otherwise, this skill's own files** are the brand kit: `references/` and47 `assets/`. A user makes them theirs by forking or editing them in place.4849A configured folder is taken whole. If it lacks a dimension (say, no50`voice-and-tone.md`), that dimension is not yet defined: never fill it from this51skill's placeholder files.5253## The placeholder brand5455As shipped, every reference file opens with **`Status: placeholder`**. The values56are a neutral slate and the logos are a generic wordmark reading "YOUR BRAND", so57a deck or card made before anyone sets a brand looks deliberate rather than58broken, and never carries someone else's identity.5960When a file you read is still a placeholder, use its values, and tell the user61in your reply that the asset uses placeholder brand values, not theirs. Never62present placeholder values as the user's brand.6364## How to use it65661. Find where the kit lives (above).672. Identify the dimension you need and read only that file.683. Use the values exactly. Do not paraphrase, derive, or interpolate a value.694. If a value is not documented, stop and ask the user. Do not guess. Once they70 give it, add it to the kit first, then use it.7172| File | Read it when you need |73|---|---|74| [references/color-palette.md](references/color-palette.md) | any colour: backgrounds, text, accents, borders, data marks |75| [references/typography.md](references/typography.md) | a typeface, weight, type scale or web-font source |76| [references/logos.md](references/logos.md) | a logo file, or the choice between light and dark variants |77| [references/visual-design-system.md](references/visual-design-system.md) | to compose an asset: background, cards, badges, hierarchy, data marks, spacing |78| [references/voice-and-tone.md](references/voice-and-tone.md) | to write or align copy to the brand voice |7980## Replacing the placeholder with your brand8182Pick where your kit will live:8384- **Edit this skill in place**, when it is installed as files you own (a fork, or85 a copy in the repository). Simplest, and nothing else needs configuring.86- **Keep it in a repository folder**, when this skill is installed somewhere an87 update would overwrite (a plugin or a shared install), or when the brand should88 sit with the repository's other conventions. Copy `references/` and `assets/`89 into the folder, then add one line to `docs/agents/workspace.md`:90 `- **Brand kit:** \`docs/standards/brand/\`` (your path).9192Then, in whichever copy is the kit:93941. **Colours.** Replace the hex values in `color-palette.md`. Keep the token95 names: consumers reference tokens, not hexes.962. **Typography.** Name your faces, weights, scale and where the web fonts load97 from in `typography.md`.983. **Logos.** Replace the two SVGs and keep their file names, so nothing that99 points at them changes. Add a variant only as a new file listed in `logos.md`.1004. **Visual design system.** Rewrite `visual-design-system.md` to describe how101 your assets are composed. Name tokens from the palette, never hexes.1025. **Voice.** Fill `voice-and-tone.md` from your real brand voice, with example103 sentences.1046. **Flip each file's status** from `Status: placeholder` to `Status: defined` as105 you finish it, so consumers stop warning about it.1067. **Grep for the values you retired** across the whole repository (see the last107 rule in `color-palette.md`) and update every copy you find.108109## Rules for every consumer1101111. **Never hardcode a brand value in another skill, template or note.** Name the112 token and read this kit when you need it.1132. **Never invent one.** If it is not documented, the answer is "not yet114 defined". Raise it rather than fabricating.1153. **Change the kit, not a local copy.** When the brand evolves, it evolves here.1164. **Renaming or removing a value is a brand-level change.** Update every117 consumer in the same change.