← SkillSafe / Brand Diagram

Your brand's colours. Your diagram. One file you can publish.

Paste your stylesheet or your design tokens and this page reads your palette and your type in the browser — no account, no credits — then maps them onto the ten roles a good diagram needs and tells you where they fail WCAG. Describe what to draw and get real inline SVG in your own skin, across eleven diagram types, exported as one self-contained HTML file with no JavaScript in it.

Both examples ship with a saved model run for every stage, so you can see the whole thing — brand mapping, diagram, annotation and every export — without signing in and without spending a credit.

Current skin

Stage 2 — describe what should be drawn

nothing typed yet

Arrow chains, owner-prefixed step lists (Design: brief, mock, review), dated bullets, indented trees and numbered stages are all read here for free — you get a real draft diagram before you spend anything.

Describe the diagram to price the run.

What this does, and what it does not

The token reader is a real reader, not a hex-code grep. It resolves var() indirection, walks a Style Dictionary or Figma token tree to its leaf values, understands #rgb, #rrggbbaa, rgb(), rgba(), hsl() and hsla(), and knows that a colour declared on body is your page background while the same colour on a .cta is your accent. The WCAG numbers are computed the way the spec defines them — relative luminance, with translucent values composited over their background first, because a hairline declared at 12 per cent opacity is not the contrast its hex suggests.

The diagram is drawn here, in your browser, from a spec. That is why editing it is free and why the export is one file with no script in it: there is no image service, no headless browser and no round trip. The model's job is judgement — which type this material actually is, which colour is the brand's accent and which is an accident, what earns the one accent, what a reader would miss without a callout. The parts a parser can do, a parser does, for nothing.

What it does not do: fetch your website. The page cannot reach a third-party origin, so "point it at my URL" is not on offer — paste the stylesheet or the tokens instead, which is the same information without the guesswork of a screenshot. And the exported file names your webfont rather than embedding it — a licensed family stays licensed, and the export says plainly which families a reader's machine will have to substitute.

Nothing to hand? Load the , a checkout architecture drawn in a warm editorial brand, or the , a signup funnel with real drop-off numbers. Both replay saved runs for free.