First MCP design contracts

open source · fail-closed

Design systems that install as MCP

Not DESIGN.md alone. Not skills alone. Each contract installs a fail-closed MCP get_contract before UI, validate_ui before done — with markdown as the law book and skills as an optional cookbook.

Agent stack

Law book. Skills. Gates that fail the PR. MCP optional.

Inspired by how v0 grounds agents in real source and verified starters — not protocol theater. Every contract on this platform ships the same stack shape with its own DNA.

  1. 01

    Law book

    Required · source of truth

    design.md · agents.md · DNA docs agents reread.

    Persistent why, negatives, and load order per DNA. Negotiated HTML for humans, raw for machines. Not optional vibes.

    • design.md
    • agents.md
    • docs/{id}.md
  2. 02

    Verified skills

    Required · cookbook

    On-demand playbooks grounded in real primitives.

    Every contract ships a native skill pack. Skills teach reuse and recipes — they are not a Meridian monopoly.

    • {id}-compose
    • {id}-theme
    • specialty
  3. 03

    Fail-closed gates

    Required · bailiff

    CI + check:* agents cannot skip.

    The real enforcement. Lint bans, route parity, contrast on every skin. Done means validate is green — not that a tool was called.

    • check:design
    • check:platform
    • check:contrast
  4. 04

    Contract MCP

    Optional · accelerator

    Queryable kit for tool-calling sessions.

    Useful when agents are MCP-wired. Never the only bailiff — schemas cost context and tools are skippable.

    • get_contract
    • validate_ui
    • get_recipe

Why not one layer

Honest comparison

ApproachStrengthGap
DESIGN.md onlyPortable prose identityEasy to ignore · no PR fail
Skills onlyGreat proceduresOpt-in · invent APIs without catalogs
MCP onlyQueryable toolsContext tax · agents skip tools
Law + skills + CI (+ optional MCP)Context · procedure · enforcementSlightly more surface — intentional

Catalog

Systems — each with its own skin

Preview panes use that contract's tokens. Open the page for the full experience.

How it works

Catalog for discovery. MCP for install.

The agent stack is MCP + markdown + optional skills. This section is the install loop once you've picked a DNA.

  1. 01

    Pick a design contract

    This homepage is the catalog shell. Open /meridian (or Harbor, Atlas, Vellum) and the whole route becomes that DNA — proof the system is real.

  2. 02

    Install the contract MCP

    One npx line into any project. Agents get get_contract / validate_ui / recipes. Pair with shadcn MCP for atom delivery — different jobs.

    Open Meridian install
  3. 03

    Compose fail-closed

    Golden path: get_contract → get_recipe → list_primitives → compose → validate_ui. Creativity stays in content and composition — never new tokens.

Pricing

Open source — $0 / month

Fail-closed design-contract MCPs run on your machine over stdio — $0 COGS. Install into any project with npx; pick a DNA and agents stay inside its skin.

Cost notes live on Meridian's system doc: why we open-sourced.

What you get

  • Contract MCP — required fail-closed runtime
  • design.md / agents.md — law book on every contract
  • Optional skills cookbook (theme · compose · cinema)
  • Closed prefs via apply_prefs · shared JSON keys

Read why we ship all three layers