Skip to content
livery
Design kits for coding agents

Give your app a new livery.

Paste any website. Get a design kit your coding agent installs in one step. It audits your project, asks before it changes anything, and applies the look one commit at a time.

Try
$ curl -fsSL livery.site/<any-site>

Works with Claude Code, Codex, Cursor, Windsurf and any agent that reads Markdown.

Open a kit

Values, and the reasons behind them.

This is Livery's own kit, built from this page. Plain Markdown and JSON your agent reads one file at a time, only when a step needs it.

.claude/skills/livery-livery-site
v1
---name: livery-livery-sitedescription: Apply the livery.site design kit (Livery v1) to this  project. Use only when the user asks to apply this kit.---# livery.site design kit · v1 · flow 1**Never edit a file before step 5. Ask, don't assume.**Soft paper tones, hairline borders and a single teal accentthat only ever marks the next step.## 1. AuditFind theme files, tokens, fonts, the icon library and howcolours are used. Do not edit anything yet.## 3. Report the gapRate tokens, components, layout, motion and voice:small / medium / large.## 4. AskWhich areas to apply. What must not change.## 7. ApplyOne area per commit: tokens → components → layout →motion → voice.

How it works

From any link to your codebase. Nothing changes until you say so.

A kit is plain Markdown and JSON. It carries the reasons behind a design, not just its values, so your agent knows what to keep and what to never do.

  1. livery.site/example.com
    Palette, type, spacing, icons
    01

    Paste a link

    Put livery.site/ in front of any public website. Livery renders it at three screen sizes and reads its design: colours, type, spacing, icons, motion.

  2. $curl -fsSL …/k/example-com/v1/kit.tar.gz
    sha256 verified
    .claude/skills/livery-example-com
    SKILL.md · tokens.json · rules.md
    02

    Install the kit

    Your agent downloads the kit, checks its hash, and saves it as a skill. Every file is visible on the kit page before you run anything.

    03

    Your agent asks, then applies

    It audits your project, rates the gap for each area, and asks what to change. Approved areas land as separate commits you can revert one by one.

The flow

Your agent asks before it touches anything.

Every kit carries the same eleven steps. Nothing is edited until you've seen the gap, chosen the areas and settled any conflict with your own project rules.

  1. 00Prepare
  2. 01Audit
  3. 02Scan rules
  4. 03Report gap
  5. 04Ask
  6. 05Resolve conflicts
  7. 06Licences
  8. 07Apply
  9. 08Verify
  10. 09Keep it
  11. 10Summary

  1. Your agent

    Audited your project. Tailwind v4, tokens in app/globals.css, and 41 hard-coded colours across 12 files. I can centralise those first.

  2. Your agent

    Here is how far your design is from this kit:

    TokensLarge
    ComponentsMedium
    LayoutSmall
    MotionMedium
    VoiceSmall

    Which areas should I apply, and is there anything that must not change?

  3. You

    Tokens and components. Keep our logo colour.

  4. Your agent

    One conflict with your project rules:

    CLAUDE.md:14

    “Primary buttons are blue (#2563eb).”

  5. Your agent

    9f2c1ablivery(example.com v1): tokens

    4e8d0f2livery(example.com v1): components

    Contrast checked in both themes. To undo one area: git revert <hash>.

Style, never assets

Every item in a kit says what you can ship.

Free to reuse

Reused as is

Values and open-source pieces your agent can install straight from the source.

Colours, spacing, radii, easing · Lucide, Phosphor · Google Fonts

Needs a licence

Needs your licence

Paid fonts and icon sets. The kit names them and always offers a free alternative.

Adobe Fonts, commercial typefaces · Font Awesome Pro

Style only

Described, never copied

Anything that belongs to the site. Your agent recreates the feel, not the file.

Logos, photos, illustrations, custom icons, the site's own words

The library

Every link becomes a kit anyone can use.

Explore all kits

rize.roggy.site

Homepage

darkDM Sansv1

Guardrails

Built to be trusted, by you and by the sites you love.

Never works around protection

LiveryBot says who it is and respects robots.txt. When a site blocks it, Livery stops and says so.

No login, payment or bank pages

Sign-in, checkout and banking pages are refused outright, so a kit can never become a look-alike.

Permanent, verifiable versions

A published version never changes. Your agent checks its sha256 before installing anything.

Owners stay in charge

Site owners can opt in for richer kits, or opt out and have their kits withdrawn, with one file.

Questions

The short answers.

Start here

Found a site you love?Give your app its livery.

Try