# Visual Guidelines Structure your brand's visual identity so every AI-generated asset looks on-brand Your brand isn't just words. It's what people see. Colors, typography, logo usage, visual rules. The Visual Guidelines tab lets you capture all of this in a structured, governed format that your AI tools can access directly. Using the Brand Kit MCP, you can configure your visual identity (populate it via Claude, for example) and retrieve it just as easily, so that every output is grounded not only in what to say but in how to present it. The Visual Guidelines tab is organized into several sections: **Logos**, **Colors**, **Typography**, and **Visual Examples**. *** ## Use Cases Visual Guidelines can be read and written via MCP, so any connected AI tool can produce on-brand visual output. Here are some examples. **Generate on-brand reports and one-pagers.** An AI tool connected via MCP retrieves your exact colors, fonts, type scale, and logo rules, then applies them when generating a report, one-pager, or data summary. AEO performance reports, for example, can be fully branded out of the box. **Produce data visualizations with your brand palette.** When your chart color palette and color usage rules are stored in Visual Guidelines, an AI agent can pull them to render charts, graphs, and dashboards that match your brand. Flat fills, specific accent colors, correct axis label fonts. **Build slide decks that look like your brand.** Claude or another MCP-connected tool can retrieve your full type scale, logo variants, and color palettes to generate presentation slides that follow your visual identity. *** ## Getting Started Instead of manually entering every color, font, and rule, **you can use Claude via MCP to read your existing brand guidelines**, whether that's a PDF, a slide deck, or any other document, and write the structured fields directly into your Brand Kit. This is the fastest way to populate Visual Guidelines. You can also add fields manually through the Visual Guidelines tab: 1. Navigate to the **Visual Guidelines** tab in your Brand Kit 2. Under **Logos**, add variants with logo files, background colors, and usage instructions. Define sizes and logo usage rules. 3. Under **Colors**, build palettes with named groups and individual colors. Add color usage rules. 4. Under **Typography**, register fonts with usage context and font file uploads. Define your type scale. Add typography usage rules. 5. Upload **Visual Examples** with reference screenshots. Add visual examples usage rules for illustration and creative direction. 6. Save your changes > **Tip**: You can populate Visual Guidelines via MCP from your brand guidelines or visual assets. [Learn more about the Brand Kit MCP →](https://docs.airops.com/mcp/tools) *** ## Example A company might configure their Visual Guidelines like this: **Logos:** Four variants for different surfaces (light, dark, forest green, neon green). Multiple size tiers from large (hero sections) to minimum (footers and favicons). Rules covering clear-space, no stretching, and background pairing. **Colors:** Five palettes covering core brand, text hierarchy, strokes, dark mode, and a dedicated chart palette. Rules enforcing sharp corners everywhere and flat fills for charts. **Typography:** Three typefaces with hosted font files. A serif for headlines, sans-serif for body, monospace for labels. A full type scale from Display down to Caption. Rules restricting serif to headlines and requiring all-caps monospace for labels. **Visual Examples:** Multiple screenshots covering product UI, data viz charts, landing pages, and feature sections. Rules defining editorial illustration style (risograph aesthetic, layered composition, retro visual metaphors). *** ## Section Details ### Logos **Logo Variants** Define different versions of your logo for different background contexts. | Field | Description | | ---------------------- | -------------------------------------------------------------------------------------------------------- | | **Name** | A descriptive name for this variant (e.g., "Full Color on White," "White Reversed on Near Black"). | | **Background Color** | The hex color this variant is designed for (e.g., `#ffffff`, `#002910`). | | **Usage Instructions** | When and how to use this variant. Include clear-space rules, restrictions, and background pairing logic. | | **Logo File** | Upload your logo image (SVG, PNG, JPG, GIF, or WebP). | **Logo Sizes** Define allowed rendering sizes so AI tools never render your logo too small or too large. | Field | Description | | ---------------------- | ------------------------------------------------------------------ | | **Name** | A label for this size tier (e.g., "Large," "Minimum"). | | **Width** | Width in pixels (optional if height is set). | | **Height** | Height in pixels (optional if width is set). | | **Usage Instructions** | Where this size should be used (e.g., "hero sections," "footers"). | **Logo Usage Rules** Freeform rules governing logo treatment. | Field | Description | | -------- | ---------------------------------------------------------------------------------------------------------------------------------- | | **Rule** | The rule text (e.g., "Minimum clear space equals the height of the A on all sides," "Never stretch, rotate, or recolor the logo"). | *** ### Colors **Color Palettes** Group your brand colors into named palettes. Each palette contains individual colors with hex values and usage instructions. You can create multiple palettes to separate concerns, for example: Primary, Text, Strokes, Dark Mode, and Charts. | Field | Description | | ---------------------- | --------------------------------------------------------------------------------------------------------- | | **Palette Name** | A name for this group of colors (e.g., "Primary," "Charts"). | | **Color Name** | A descriptive name for each color (e.g., "Interaction Green," "Text Secondary"). | | **Color Value** | The hex value (e.g., `#00ff64`). | | **Usage Instructions** | When and where to use this color (e.g., "hover states and interactive accents," "captions and metadata"). | **Color Usage Rules** Freeform rules governing color usage. | Field | Description | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Rule** | The rule text (e.g., "All large surfaces must use dark green #002910," "Sharp corners only, border-radius: 0," "Data viz: flat fills only, no gradients"). | *** ### Typography **Fonts** Register the typefaces your brand uses. | Field | Description | | ---------------------- | --------------------------------------------------------------------------------------- | | **Name** | The font name exactly as it should be referenced (e.g., "Saans," "Serrif VF"). | | **Usage Instructions** | Which contexts this font applies to, fallback fonts, and platform-specific substitutes. | | **Google Font Link** | A Google Fonts URL, if the font is hosted there. | | **Font File** | Upload a custom font file (e.g., .woff2). Agents can load these via @font-face. | **Type Scale** Define your full typographic scale by linking specific size, weight, and line-height configurations to a font. | Field | Description | | ---------------------- | ------------------------------------------------------------------------------ | | **Font** | Which registered font this type size belongs to. | | **Name** | A label for this step in the scale (e.g., "Display," "H1," "Body," "Caption"). | | **Weight** | Font weight (e.g., "400," "600"). | | **Size** | Font size in pixels. | | **Line Height** | Line height in pixels. | | **Usage Instructions** | Where this type size should be applied. | **Typography Usage Rules** Freeform rules governing typographic treatment. | Field | Description | | -------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Rule** | The rule text (e.g., "Serrif VF is for large editorial headlines only," "Monospace labels must always be all-caps, 11-12px, weight 500"). | *** ### Visual Examples Upload reference screenshots that show your brand applied in real contexts. These serve as visual anchors for AI agents when written rules alone are not enough to convey the intended look and feel. You can upload as many visual examples as needed. Common examples include product UI screenshots, data visualization charts, landing page sections, and report layouts. | Field | Description | | ---------------------- | --------------------------------------------------------------------------------- | | **Title** | A descriptive name (e.g., "Data viz: bar chart," "Brand Kit: Visual Guidelines"). | | **Sample URL** | A link to the live page, if available. | | **Image File** | Upload a screenshot (PNG, JPG, SVG, GIF, or WebP). | | **Usage Instructions** | Optional guidance on when agents should reference this example. | **Visual Examples Usage Rules** Freeform rules governing illustration style, composition, and creative direction for editorial imagery. | Field | Description | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Rule** | The rule text (e.g., "Illustrations use a risograph/screen-print style with flat color and halftone grain," "Avoid clean corporate vector or flat-design icon style"). | *** ## FAQ **How do I access Visual Guidelines in my AI tools?** Visual Guidelines are available through the Brand Kit MCP. Connect it to Claude, Cursor, or any MCP-compatible tool to read and write your visual identity programmatically. Workflow Liquid variables are not yet available for Visual Guidelines fields. **Can I populate Visual Guidelines using AI?** Yes. Using the Brand Kit MCP, you can have Claude read your existing brand guidelines PDF and write the structured fields directly into your Brand Kit. **What use cases does this unlock?** Any AI tool connected via MCP can retrieve your visual identity to produce on-brand reports, slide decks, one-pagers, and data visualizations with your exact colors, fonts, and rules. **What's the difference between usage rules and field-level instructions?** Field-level instructions describe when to use a specific item (e.g., a particular color or logo variant). Usage rules are broader guardrails that apply across an entire category, such as "never use rounded corners" or "all large surfaces must use dark green."