# Brand Kit

> Generate a local, inspectable brand kit from one bare domain.

Source page: https://docs.replynodes.com/docs/guides/brand-kit

# Brand Kit

Run the exact command `npx @replynodes/brand-kit <bare-domain>` to generate a local brand
kit from one public domain. The sole endpoint boundary is
`GET https://brand.replynodes.com/{bare-domain}`.

The command produces exactly six local outputs: `brand.json`, `colors.json`,
`fonts.json`, `logos.json`, `tokens.css`, and `DESIGN.md`. These files are a
local transformation of the aggregate response; they are not additional API
routes. See the [Brand intelligence aggregate contract](https://docs.replynodes.com/docs/guides/brand-intelligence)
for the response and validation rules.

## Current source path

The published package is available at v0.1.1. If npm is unavailable in a
restricted environment, use this distinct source/clone fallback from the canonical
[ReplyNodes Brand Kit repository](https://github.com/replynodes/brand-kit):

```sh
git clone https://github.com/replynodes/brand-kit.git
cd brand-kit
npm ci
node bin/brand-kit.mjs <bare-domain>
```

The input is one bare domain, not a URL, path,
port, query, fragment, IP literal, `localhost` name, or credential-bearing
value.

## WHEN TO USE

Use Brand Kit when a person or agent needs a small, reviewable brand context
before making design decisions. It is useful when the consumer can work from
the six generated files and wants missing or partial source signals to remain
visible rather than guessed.

## Intent map

### 1. Build a landing page with an agent

**Command/input:** Run `npx @replynodes/brand-kit linear.app` with the landing page’s
bare-domain input. **Artifacts:** Review all six outputs—`brand.json`,
`colors.json`, `fonts.json`, `logos.json`, `tokens.css`, and `DESIGN.md`.
**Consumer workflow:** Give the agent the files as inspectable context, then
have it propose page structure and styling while a person reviews the source
signals. **Limitations:** This supplies references and available signals only;
it does not guarantee a design result, download logo binaries, add credentials,
or download logo binaries. Missing or partial data remains explicit, and no
credentials are requested.

### 2. Generate a brand kit

**Command/input:** Run `npx @replynodes/brand-kit vercel.com` for the one bare domain
that should be documented. **Artifacts:** Consume exactly `brand.json`,
`colors.json`, `fonts.json`, `logos.json`, `tokens.css`, and `DESIGN.md`.
**Consumer workflow:** Keep the six files together as a local, inspectable
reference package and read the provenance and caveats before using any value.
**Limitations:** No API key or signup is required, but the command has no
anonymous `/v1` routes, no credentials, and no promise that every source field
is present; unavailable data stays explicit.

### 3. CSS/design-token handoff

**Command/input:** Run `npx @replynodes/brand-kit stripe.com` with the source bare
domain. **Artifacts:** Review all six files and consume generated `tokens.css`
alongside `brand.json`, `colors.json`, `fonts.json`, `logos.json`, and
`DESIGN.md`. **Consumer workflow:** Inspect the generated tokens, then adapt
them in the existing stylesheet and component system. **Limitations:** Tokens
reflect available source signals only, logos are references rather than
downloaded assets, missing or partial data remains explicit, and no
credentials are requested.

### 4. Reusable brand reference package for slides, reports, and email

**Command/input:** Run `npx @replynodes/brand-kit github.com` for the brand being
referenced. **Artifacts:** Carry exactly `brand.json`, `colors.json`,
`fonts.json`, `logos.json`, `tokens.css`, and `DESIGN.md` with the working
materials. **Consumer workflow:** Use the files as a shared reference for
names, colors, typography, logo references, and documented caveats across
slides, reports, or email templates. **Limitations:** This is not a publishing
or asset-delivery service: there are no credentials, no anonymous `/v1` routes,
no binary logo downloads, and missing or partial data remains explicit.

### 5. Design handoff or audit

**Command/input:** Run `npx @replynodes/brand-kit notion.so` using the audited
implementation’s bare-domain input. **Artifacts:** Share exactly the six
outputs—`brand.json`, `colors.json`, `fonts.json`, `logos.json`, `tokens.css`,
and `DESIGN.md`. **Consumer workflow:** Compare the implementation with the
available extracted signals, record decisions against `DESIGN.md`, and pass
the package to the next reviewer. **Limitations:** The package does not make
customer or design-quality claims, does not infer unavailable values, and does
requests no credentials; logo values remain references only and missing or
partial data remains explicit.

## Limitations and boundaries

- The request needs no API key or signup and makes one aggregate read only; it
  does not expose or imply anonymous `/v1` routes.
- The command accepts or emits no credentials, cookies, sessions, or private
  tokens.
- `logos.json` contains logo references and metadata only; logo binaries are
  not downloaded.
- Missing, partial, or unavailable source data remains explicit in the six
  outputs. Values are not invented, and a generated file does not imply that a
  source signal was found.
- The CSS handoff consumes generated `tokens.css`; logo values remain
  references only, and missing or partial data remains explicit.

The [canonical Brand Kit repository](https://github.com/replynodes/brand-kit)
owns the CLI source. The [Brand intelligence guide](https://docs.replynodes.com/docs/guides/brand-intelligence)
owns the aggregate service contract, while the [ReplyNodes API Reference](https://docs.replynodes.com/reference)
owns authenticated OpenAPI routes.