> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryflowy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Flowy is a node-based AI creative platform: you generate images, video, audio, 3D and vector on an infinite Canvas, refine on the Studio timeline, and export or publish from the same project.
> Prefer the Flowy MCP server (https://mcp.tryflowy.ai/mcp) or the REST API at https://apis.tryflowy.ai/v1 for programmatic work. Install with `flowy mcp install` from the @flowy/cli package.
> Credits are workspace-scoped. Generations reserve credits on start and only deduct on success, so failed runs refund automatically.

# Brand Kit Node

> Wire your workspace brand kit into generation to keep every result on-brand.

The Brand Kit node (<kbd>⇧</kbd> <kbd>B</kbd>) connects a [workspace brand kit](/library/brand-kits) (colors, typography, design tokens, and logos) into generation. It has the same effect as attaching a kit directly in a node's prompt bar, but as a standalone node you can share one kit across as many downstream nodes as you like.

## Connect it

The Brand Kit node accepts no inputs of its own. It's a reference source. Wire its output into:

* **Text**
* **Image**
* **Video**
* **Flam**

Every generation downstream of the connection applies the kit's design guidance and assets, so a whole board of nodes can follow the same identity from one Brand Kit node.

## Why use the node instead of attaching in the prompt bar

Attaching a brand kit per-node works fine for a single generation, but a Brand Kit node lets you:

* **Share one kit across many nodes** without attaching it individually to each.
* **Swap the kit in one place**: change which kit the node points to, and everything wired to it picks up the change.
* **See at a glance** which parts of the canvas are on-brand, since the connection is visible on the graph.

## Manage your kits

Brand kits themselves (creating one, extracting colors and fonts from a website, editing tokens) are managed in your [workspace brand kit library](/library/brand-kits), not on the node. The node is only a connector: pick a saved kit, wire it in, generate.