Design system. Installed once, read by every agent.

    Every page your AI makes, on brand.

    One file your agents read before they build, carrying your colours, type scale and layout rules, so the next page or deck ships looking like your brand instead of the model's defaults.

    Same brief

    The defaults every AI site ships with

    With no design.md loaded, the agent falls back to its defaults, a centred hero on a gradient and three equal cards, so nothing on the page reads as Fieldstone.

    Same brief

    The same page, built in your brand

    The agent loads the design.md first and builds in Fieldstone's navy, sand and paper with their routes, so the page reads as theirs, and every build after it inherits the same file.

    fieldstone.co
    layoutCentred
    paletteModel default
    typeTwo fonts
    What gets installed

    Four parts, written once, read by every tool you build with.

    Brand extraction

    Reads what you already ship, like your live site, logo and last deck, then writes your colours, type scale and spacing into tokens, so the first build already looks like you.

    design.md

    Sits in your repo and tells every agent your tokens, your layout rules and the patterns it must never reach for, so the page it builds comes back looking like yours.

    Component vocabulary

    The cards, buttons, sections and diagram styles every surface is composed from, so a proposal deck and a landing page read as one company.

    Check harness

    Runs eight gates on every build, three by a script and five by a person, so a page that compiles but reads badly gets caught before your customer opens it.

    Extraction

    Your brand, written down so a machine can follow it.

    • Starts from a call about what you want to look like, then turns your answers and your existing pages into tokens your agents load before they build anything.
    • Adds the rules a PDF brand guide never states, like which layouts you use, how much air a section gets and what motion is allowed, so agents build the way your designer would.
    • Hands you the design.md to read in ten minutes. You correct it once, and every build after that inherits the correction.
    Sample
    ▣Live site
    FieldstoneContact
    ☰Assets3 files
    logo.svgwordmark
    deck.pdf12 pages
    photos48, one shoot
    Fonts and colours are read from the files themselves.
    ☰Tokenswritten
    navy 1C2B4A
    sand E8D9B8
    paper F7F4EE
    ink 2B2B2B
    DisplayInter 600, 56
    H2Inter 500, 40
    BodyInter 400, 17
    Radius12
    Section air96
    design.md, 31 tokens
    The check

    Eight gates catch the page that builds fine and still looks wrong.

    • A script walks every scroll position and checks contrast at the worst frame, dead scroll and frozen video, so the faults that only show up mid scroll reach you and never your customer.
    • Five gates stay with a person, who checks the images look like one shoot and the page does what the brief asked, so a build that only passes mechanically never ships.
    • The taste floor lists the patterns that read as generated, like centred heroes over gradients and three equal cards, and fails the build when one shows up.
    Sample
    ✓Check harnessrun 14
    GateWhoResult
    Buildsscriptpass
    Readable at worst framescript7.2:1
    One shootby eyepass
    Read the sheetby eye1 note
    Taste floorby eyepass
    Three gates run by the script. Five need a person, and the report says who ran them.
    ▣Worst frame
    Tracked from the quay
    Every container, every hour.
    Contrast7.2:1
    Copy opacity1.0
    ●Walk
    0
    Dead scroll
    0
    Frozen clips
    Harness passed
    Two ways to start

    Same install. You choose who builds first.

    If your team or your agents already ship pages, take the system and run it. If you want the first one done right, we build it with you.

    You build pages already

    Own it

    We extract your brand, write the design.md and install the harness on your machine. Your team and your agents use it from the next build.

    You want a finished page

    We build the first one

    We install the system, then ship your next site or deck with it and hand over the runbook. Every build after that is yours.

    Try it first

    See what a design.md looks like

    A starter design.md with the check harness already wired in, so you can read the shape of the system before you hand us your brand.

    Download the starter

    Where AI design breaks

    Why does every AI site look the same?

    Because the model reaches for its defaults: a centred hero over a gradient, three equal cards, the same two fonts. It builds that for everyone unless something tells it what you look like. The design.md is that something, and the refuse list is the part that keeps the defaults out.

    Is a design system just a colour palette?

    A palette is about a tenth of it. The parts that make a page read as yours are the type scale, the spacing, how sections are laid out and what motion you allow. Those are the rules a brand PDF never writes down, and they are the ones we extract.

    Can an agent judge its own work?

    Three checks, yes. It can confirm the page builds, that it scrolls without a dead stretch, and that the text stays readable at the worst frame. The other five need a person, because a page can clear every mechanical check and still say nothing to the buyer who lands on it.

    What do I need to give you?

    Your live site, your logo, any brand file you have, and an hour to correct the first draft of the design.md. If you have real photography or a copy of your deck, add those. You never write tokens or rules yourself.

    Ready to look like one company?

    We'll read your current site and show you what the system would extract.

    Book a Call