Brand Guidelines

Brand Guidelines

The complete Composio brand book — overview, platforms, logo, color, type, layout, and voice in one place.

agent.json

Composio's brand runs on two product surfaces unified by one identity. Write things once and let the surface decide how they look.

Download .md

Overview

There are two worlds. FOR YOU is the light, consumer-facing surface; DEV is the dark, developer-facing one. The same brand color, type, and components render in either context — the brand flips to suit the surface rather than locking to a single look.

  • Achromatic interface. Black, white, and the surface tokens carry the UI. Blue is a spot color at roughly 7% of what you see.
  • Two-surface system with token-flipping — never mix light and dark within one section.
  • Two typefaces, no exceptions — Geist Sans for everything readable; JetBrains Mono for code and chrome. No third face, no fallback shipped in place of either.
  • Sans never goes bold — emphasis comes from size, not weight.
  • No eyebrow text — headings stand alone, with no label, kicker, or overline above them.
  • One spot blue — #51a2ff on both surfaces. On dark, hover and active are #51a2ff too; only light mode darkens them.

The Two Platforms

Every Composio surface belongs to one of two worlds. Keep each section internally consistent.

FOR YOU — consumer, light. Off-white surfaces (#f6f6f6), generous space, the spot blue #51a2ff on marks and interactive state. Marketing, onboarding, the consumer product.

DEV — developer, dark. Warm near-black surfaces (#0f0f0f / #1e1e1e), tight chrome, the same spot blue #51a2ff which reads cleanly against the dark at 7.27:1. Docs, dashboards, code, the developer product.

Do
  • Pick one surface per section and commit to it.
  • Wrap a whole region to flip it from FOR YOU to DEV.
  • Use the same brand blue on both surfaces; on dark, hover and active stay #51a2ff.
Don't
  • Mix light and dark within a single section.
  • Paint a dark card on a light section — flip the section instead.
  • Invent a second blue for dark. There is one brand blue and it works on both.

Color

The interface is achromatic. Blue is a spot color that marks things, and it is about 7% of what you see.

Build with neutrals. Surfaces are deliberately off-pure: background #f6f6f6 / #0f0f0f, card #ffffff / #1e1e1e, popover #fafafa / #2a2a2a, with hairline borders #eaeaea / #2c2c2c. Hierarchy comes from alpha on black or white, not from hue. Every primary CTA is a black fill on light or a white fill on dark. Every secondary is a white fill with a black/15 hairline, or its inverse.

Blue is a spot color, not a UI color. It does one named job: interactive state, such as a focus ring, a checked control, or a selected row. It is not what you build interfaces with, and a section that feels plain is not a reason to reach for it. Plain is the house style.

There is one brand blue, #51a2ff, and it does not flip. It clears contrast on both surfaces, 7.27:1 on the dark page and legible as a fill on light, so a second hue was never needed. The retired dark value #0007cd was 1.75:1 and effectively invisible, which is the only reason the brand ever appeared to need two. --brand is a fill, and the only text allowed on it is --brand-on-brand. It is never a text color on light: #51a2ff there is 2.44:1 and fails.

When blue has to be read rather than seen, use --brand-ink (#0b6fd6 on light, 4.56:1). Links, focus rings and selected rows take ink. This is the token that did not exist before, which is why the old rule about using the brand for links was unfollowable.

Semantic colors (destructive, success, warning) mean what they say. Use them only for errors, confirmations, and cautions, never as a generic accent.

Note that --accent means something different in the product repos, where it is a neutral interaction surface (#f5f5f5 / #262626) used for hover. It carries no brand color. Do not reach for it expecting blue.

Do
  • Build from neutrals. Black, white, and the surface tokens are the default, not the fallback.
  • Spend the brand on interactive state.
  • Use --brand-ink whenever blue has to be legible as text.
  • Put only --brand-on-brand on a brand fill.
  • Use semantic colors for their literal meaning.
Don't
  • Set body text, a heading, or a link in --brand. It fails contrast on both surfaces.
  • Put white text on a brand fill. That pairing is 2.64:1.
  • Fill a card, a section, or anything over 24px with brand blue.
  • Hardcode a blue because the token looks wrong on dark. If the token fails on its surface, the token is wrong, so fix it once.
  • Pick a semantic color because it 'looks nice'.

Typography

Exactly two typefaces: Geist Sans for everything readable, JetBrains Mono for code and developer chrome. These rules are hard constraints, not preferences. There is no context, format, or deadline in which another face or a bold sans is acceptable.

Geist Sans by Vercel is the only sans: headings, body, UI, buttons, names, titles, and stat values. JetBrains Mono is the only mono: code, terminal text, numbers that label a chart mark, badges, version chips, and inline metadata. No third typeface exists, including for display, decorative, or 'just this once' use.

Banned faces. ABC Diatype (retired; the files still under /fonts/ABCDiatype-* are archival and must not be loaded), Geist Pixel (any variant), Geist Mono, Inter, Arial, Helvetica, SF Pro, Roboto, system-ui, and any serif, script, or display face. A fallback stack is a safety net for loading, never a design choice. If the real face cannot load in your environment, stop and fix the loading, do not ship the fallback.

Loading. In Next.js, load Geist Sans from the geist package (geist/font/sans) and JetBrains Mono from next/font/google. In plain HTML, load Geist and JetBrains Mono from Google Fonts. For anything rendered to an image (canvas, SVG, satori, Playwright capture), wait for document.fonts to load the exact weights you use before painting, or embed the font files directly. Write stacks as 'Geist', sans-serif and 'JetBrains Mono', monospace.

Sans never goes bold. Use weight 400 or 500 only — every heading (display and all title tokens) is normal weight; 500 is only for body emphasis through the -medium body tokens. Emphasis comes from size, not weight. 600 is bold. So are font-semibold, font-bold, <b> and <strong> left at the browser default, faux bold from -webkit-text-stroke or a text-shadow smear, and synthesized bold. Style <strong> and <b> to 500 or to a colour change.

Two line heights, three tracking values, all inside the tokens. Leading is 1.1 for display and titles and 1.5 for body and labels. Tracking is -0.025em on headings, -0.011em on body, and 0.05em on the small mono labels (text-label-small, -mini, -micro). Never add leading or tracking next to a token.

Mono can be any weight. It is the only face allowed above 500, and the only face that takes uppercase with wide tracking. Mono is for chrome and code, never for headings or running body copy.

One exception, narrowly scoped. Inside an app-native UI mockup (for example a recreated Slack message or GitHub PR in a use-case post), text inside the mocked app may mirror that app's weights so the mock reads as the real product. The mock is still set in Geist Sans and JetBrains Mono, and everything outside the mock, the Composio frame and any headline, follows these rules exactly.

Check before you ship. Inspect the computed font-family and font-weight of the headings, body, and numbers you produced. Every sans element must resolve to Geist at 400 or 500; every mono element to JetBrains Mono. If any element resolves to a fallback, another family, or a sans weight above 500, it is not done.

No eyebrow text, of any kind. Never put a small label, kicker, overline, or category tag above a heading — not in mono, not in sans, not uppercase or sentence case, not in blue or in muted grey, and not paired with a dot or icon. The heading opens the section on its own. If a heading needs context to make sense, rewrite the heading.

Do
  • Promote to a larger size when you need emphasis.
  • Let the heading open the section. Write it so it needs no label above it.
  • Let the type tokens bundle size, weight, leading, and tracking.
  • Load the real Geist Sans and JetBrains Mono files and confirm they rendered.
  • Set numbers that label a chart mark in JetBrains Mono.
Don't
  • Bold or semibold sans text — ever. That includes weight 600, default <b>/<strong>, and faux bold.
  • Combine a type token with a conflicting weight.
  • Introduce a new weight or a third typeface, for any reason, including display, decorative, pixel, or retro faces.
  • Use ABC Diatype. It is retired; its files in /fonts are archival only.
  • Ship with a fallback face because the real one did not load.
  • Set a heading or body paragraph in mono, or put uppercase-with-tracking on sans.
  • Put eyebrow text above a heading: no kicker, overline, section number, or category label, in any style.

Layout & Elevation

Structure carries the brand as much as color and type do.

Page content sits within a 1240px max width; long-form columns at 720px, forms at 520px, single CTAs at 380px. Don't hardcode pixel widths — use the container tokens.

Elevation has one signature: a two-layer card shadow (shadow-elevated) for primary surface cards, with the standard shadow scale for ordinary lifts. Lead with whitespace and surface contrast before adding decoration.

Voice & Tone

Composio speaks to two audiences without splitting in two: approachable on FOR YOU, precise on DEV, infrastructure-grade throughout.

  • Clear over clever — say the thing plainly.
  • Technical, not cold — precise, never jargon for its own sake.
  • Confident, not loud — let size and space carry emphasis, the way the type system does.