Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client.
Slingshot's own brand, built as an agentic brand system: the same parts the company builds for others, used on itself first. It is the brand behind slingshot.fyi.
| Part | What it is |
|---|---|
| Kit | brand/: a router (readme.md) and five guides (voice, layout, typography, colour, mark). Every rule carries its reason, so a person or an agent can apply it to a case nobody wrote down. |
| Tokens | brand/tokens.json holds every value once; dist/tokens.css is generated from it. |
| CLI | slingshot-brand prints the guides and tokens, and checks files for colours that are not brand tokens. |
| MCP | slingshot-brand-mcp gives any MCP client (Claude Code, Claude Desktop, Cursor) the guides, the tokens and the colour check while it works. |
npx -p @slingshot-fyi/brand-kit slingshot-brand guide # which guide to read for the task
npx -p @slingshot-fyi/brand-kit slingshot-brand guide voice # one guide
npx -p @slingshot-fyi/brand-kit slingshot-brand tokens # tokens as CSS custom properties
npx -p @slingshot-fyi/brand-kit slingshot-brand check src/*.css # exits 1 if any colour is off-brand
In a clone of this repository, run npm install once and the same commands work as npx slingshot-brand ….
Add the MCP server to Claude Code:
claude mcp add slingshot-brand -- npx -y @slingshot-fyi/brand-kit
It exposes three tools: brand_guide, brand_tokens and check_colors.
npm test checks that every rule has a reason, that the generated CSS covers every token, that the colour check names brand colours and flags the rest, and starts the MCP server to call each tool over stdio.
The kit itself is tested the way Slingshot tests every kit: hand it to a fresh agent with no other context, ask it to make something new, and treat every guess it makes as a missing rule.
The statement face, Exposure, is licensed separately and is not in this repository. Geist and Geist Mono are under the SIL Open Font License.
The code is MIT (see LICENSE). The Slingshot name, mark and copy belong to Slingshot.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @slingshot-fyi/brand-kitMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"fyi-slingshot-brand-kit": {
"command": "npx",
"args": [
"-y",
"@slingshot-fyi/brand-kit"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@slingshot-fyi/brand-kitnpmSlingshot brand kit works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.