brand.magicblocks.ai · v1.0

One brand kit. Three ways in.

Design tokens, 134 React components, 241 icons, 836+ brand assets, voice guidance, and HTML templates — published as a website, an npm family, and a JSON API. Pick the path that matches what you're building.

  • 16Chapters
  • 134Components
  • 241Icons
  • 836+Brand assets
  • 3npm packages
Foundations

The system, at a glance.

Five warm neutrals, one hero accent, four faces — every component is composed from these atoms.

All tokens →
Palette · 12 of 110+ tokens
warm-1warm-2warm-3warm-5warm-7inkaccentsuccesswarninginfoerrorpaper
Type · four faces
  • DisplayBricolage Grotesque
  • Body copy renders here in DM Sans — quiet, readable, generous.DM Sans
  • A felt italic, set in Fraunces.Fraunces · SOFT 80
  • --accent: #FF3F7A;JetBrains Mono
Spacing · 9-step scale
  • s-1 · 4
  • s-3 · 12
  • s-5 · 24
  • s-7 · 48
  • s-9 · 96
Components · 134 in the package

Real components, rendered live.

Every chapter ships an HTML demo, the matching CSS, and a typed React component — drop in @magicblocksai/ui or paste the markup straight from a chapter page.

All components →
Buttons
Form input
Badges
InfoSuccessWarningDangerAccent
Stat tile
Pipeline value
$2.4M
↑ 18.2% vs last month
Conversations
1,284
↑ 6.4% vs last month
Reply latency
42s
↓ 12s vs last month
For marketing

Pick an icon. Grab a tagline. Drop in a template.

The full library of brand assets, copy, voice notes, and HTML templates — searchable, click-to-copy, ready to drop into a deck, email, or post.

For app builders

npm install and ship.

Three workspace packages on GitHub Packages. Vanilla CSS for any static site, React + Tailwind for modern apps, brand-data JSON for either.

npm install \
  @magicblocksai/ui \
  @magicblocksai/css \
  @magicblocksai/brand
For AI agents

Fetch the JSON. Read the markdown. Use the contract.

Every page mirrors a JSON endpoint at /api/; every chapter HTML serves as Markdown via Cloudflare's auto-transform (append .md). Single source, three surfaces.

Browse the visual library

16 chapters · many demos · three buckets — General (foundations, atoms, molecules), Website (marketing narrative — chapter 11 has 23 hero scenes / engine blocks / journey maps / ROI calcs), App (shell, pipeline, AI). Each chapter HTML is the canonical visual reference.

All chapters & sections →

How it stays in sync

Every component change updates four surfaces in the same commit so what marketing reads, what your app installs, and what an agent fetches always agree.

  1. 1Chapter HTML demoVisual reference + the HTML/CSS snippets you can paste anywhere.
  2. 2_shared.css → @magicblocksai/cssVanilla CSS classes, identical to what the chapter HTML uses.
  3. 3TSX → @magicblocksai/uiTyped React components with the matching API surface.
  4. 4React snippet tab on the chapter pageCopy-pasteable TSX showing exactly how to use it.

A regression script (check-coverage.mjs) and a markup-equivalence test gate every PR — drift between the four surfaces fails the build.

Stable resource URLs

  • /css/v1/magicblocks.cssVersioned vanilla CSS — drop in any HTML/Astro/Hugo project. Pin to a major.
  • /css/latest/magicblocks.cssAlways-latest pointer.
  • /assets/{category}/{path}Brand assets at canonical paths. Mirrored at top-level (/01-logo-full/...) for legacy chapter HTML.
  • /api/components/{Name}.jsonPer-component spec — props, examples, demo URL.