Agentic engineering infrastructure

A shared design for your products

A standalone microservice that keeps the design of your project — colours for the light and dark theme, fonts, text scale, corner radius, spacing and block settings — and hands it, the moment you save, to the products that follow it — every product on the server or only chosen ones: each product decides.

  1. 01

    Choose

    Colours, fonts, shapes and spacing on one screen

  2. 02

    Save

    Products that follow it re-style in seconds, without a rebuild

  3. 03

    Optional

    For every product on the server or only chosen ones — each product decides

13

colour roles for each theme

3

font roles: headings, text, code

6

services re-styled by one save

MCPDESIGN-CONFIGLight and dark themeGoogle FontsClaude Code Agent
What you design

Five sections, each on its own page

Open a section, change what you need, save. Every service of the project follows at once.

  • Colours — light theme

    Primary, background, text, borders, accents and the chart palette.

  • Colours — dark theme

    The same roles for visitors who prefer the dark theme.

  • Fonts

    Fonts for headings, body text and code — any font from Google Fonts.

  • Text, shapes and spacing

    Text scale and line height, corner radius, borders, spacing and page width.

  • Blocks

    The width and the title sizes of the centered first screen on phone, tablet and computer.

Open the design
How it works

Change once — the whole project follows

No theme files scattered across repositories, no rebuild for a colour.

  1. Change

    The architect changes the design on this screen and saves it. Design keeps it.

  2. Signal

    The moment you save, every subscribed service gets a signal and takes the new design itself over MCP.

  3. See

    Each service re-renders its pages with the new design in seconds — static, fast, without a rebuild.

Open the design

Frequently asked questions

Which services follow the design?
Every service of the project that subscribes to it: the site, sign-in, data, blocks, project settings and this element itself. A service without the Design element keeps its own theme and runs as before.
Does a change need a rebuild?
No. Pages stay static and fast: when you save, each service takes the new design over MCP and re-renders its pages once, in seconds. Visitors see the change after reloading the page.
Who can change the design?
Only the architect of the project, after signing in. Everyone else sees this page and nothing more; services read the design with the key of the node.
Open the design