Slingshot brand kit

fyi.slingshotv0.1.0Updated Oct 7, 2026

Slingshot's brand guides, design tokens and an off-brand colour check, for any MCP client.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Gives an assistant Slingshot's brand guides, design tokens, and an off-brand colour check while it works.

What it does
Exposes three tools: brand_guide, which routes to the right guide or returns one guide (voice, layout, typography, colour, mark); brand_tokens, which returns the design tokens as CSS custom properties; and check_colors, which inspects files for colours that are not brand tokens. The guides are written so every rule carries its reason, letting an agent apply them to cases not explicitly covered.
When to use it
Useful when producing or reviewing design and front-end work that must follow Slingshot's brand, or when you want an assistant to flag off-brand colours in stylesheets. It is aimed at anyone building with this specific brand system rather than general design tooling.
Requirements
Runs locally over stdio via the npm package @slingshot-fyi/brand-kit, so Node.js and npx are needed. No accounts, API keys, environment variables, or headers are declared. The statement font Exposure is licensed separately and is not included.
Before you install
The colour check reads the files you point it at and exits non-zero when it finds off-brand colours; it is a read-only check rather than an editor. No credentials or payments are involved. The bundled fonts Geist and Geist Mono are under the SIL Open Font License, while Exposure is not included and must be licensed separately.

Installation

In SourceWeft

  1. Open Slingshot brand kit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Slingshot brand kit

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.

PartWhat it is
Kitbrand/: 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.
Tokensbrand/tokens.json holds every value once; dist/tokens.css is generated from it.
CLIslingshot-brand prints the guides and tokens, and checks files for colours that are not brand tokens.
MCPslingshot-brand-mcp gives any MCP client (Claude Code, Claude Desktop, Cursor) the guides, the tokens and the colour check while it works.

Use it

bash
npx -p @slingshot-fyi/brand-kit slingshot-brand guide            # which guide to read for the tasknpx -p @slingshot-fyi/brand-kit slingshot-brand guide voice      # one guidenpx -p @slingshot-fyi/brand-kit slingshot-brand tokens           # tokens as CSS custom propertiesnpx -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:

bash
claude mcp add slingshot-brand -- npx -y @slingshot-fyi/brand-kit

It exposes three tools: brand_guide, brand_tokens and check_colors.

How it is tested

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.

Fonts

The statement face, Exposure, is licensed separately and is not in this repository. Geist and Geist Mono are under the SIL Open Font License.

Licence

The code is MIT (see LICENSE). The Slingshot name, mark and copy belong to Slingshot.

Source: README.md at commit d45ed31

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.0LatestOct 7, 2026