# Brand Diagram > Turn your own brand's colours and type into a publishable, annotated diagram — > then export it as one standalone HTML file with inline SVG and no JavaScript. URL: https://brand-diagram.skillsafe.ai/ API: https://api.skillsafe.ai/v1/app-api (app slug `brand-diagram`) API tutorial: https://brand-diagram.skillsafe.ai/api.html Token management: https://brand-diagram.skillsafe.ai/tokens.html Model: `gpt-terra` (currently resolves to `gpt-5.6-terra`) Pricing: metered per run; the free lanes below cost nothing and need no account. ## What it is for Most diagram tools give you their house style. This one starts from yours. You paste the design material you already have — a stylesheet, a `:root` block, a Style Dictionary or Figma token export, your design-system Markdown table, or a whole exported HTML page — and the browser reads the palette and the families out of it, maps them onto the ten semantic roles a diagram needs, derives the dark variant, and measures the whole thing against WCAG AA. Then you describe what should be drawn and get a real diagram in that skin. The deliverable is a file you own: one `.html` with light and dark inline SVG, a `prefers-color-scheme` swap, a print rule, and no script tag in it at all. ## Three stages, one work object The work object is a diagram you are about to publish in your brand. The app has one system prompt and one model, and routes on a `task` field in the run input. | `task` | What the model does | What it returns | | --- | --- | --- | | `skin` | Judges your palette: which colour is the accent and which is an accident, what to demote, how to repair a contrast failure with the smallest change | The ten roles in light and dark, three font families with an `exact`/`fallback` verdict each, and a brand fidelity receipt | | `design` | Chooses the diagram type from the shape of your material and writes the spec | A normalized diagram spec plus a fidelity ledger of what was merged, collapsed, dropped and kept | | `annotate` | Adds the editorial layer to a diagram that already exists | At most two italic-serif callouts, the focal decision with a reason, the semantic pattern, and the screen-reader description | Stage 2 runs in the skin from stage 1. Stage 3 runs on the spec from stage 2 and is offered as a button on the result, not as a re-paste. ## What is free, with no account and no credits A large part of the app never touches the model: - **The token reader.** Resolves `var()` indirection, walks a Style Dictionary or Figma token tree to its leaf values, reads SCSS and LESS variables, Markdown tables and the `