Skip to content

Cata Design System [design system]

One set of design rules, so a PM prototypes a feature in 3 hours and sales makes a deck in one.

Role
Design lead and owner of the system
With
An engineer who reviews each change
At
Cata, the platform behind 20 restaurant and retail brands
Status
Shipped
Year
2026

Designers, engineers and AI tools each worked from their own rules, so every screen drifted a little and every new thing waited on design. Now they all read the same source. A product manager prototypes a feature in 2 to 3 hours, where before it didn't happen. A sales deck tailored to a prospect takes 30 to 60 minutes, not 2 to 4 days. Engineers build internal tools without waiting a sprint for a roadmap slot.

My role
I own the system. I make every rule decision and build it with Claude Code, and an engineer reviews each change before it ships.
At a glance
  • A PM prototypes a feature in 2 to 3 hours. Before, it didn't happen: a spec, then a wait for design
  • A sales deck on the guidelines in 30 to 60 minutes, tailored to the prospect. It took 2 to 4 days
  • Internal tools built by engineers on the system, with no design review and no sprint-long wait for a roadmap slot. I stay the gate for what customers see
  1. The problem. Every screen looked a little different.

    Colours were copied by hand, so no two screens quite matched and every fix went through design. One charcoal had three names, and the code held 235 hard-coded values across 70 files. Now there are 49 named tokens, one per role, and a change made once lands everywhere.

  2. The fix. Decide once, and let every tool follow.

    Each decision is written once. The AI skill reads the latest rules, Claude Design gets generated tokens, and the product gets a reviewed pull request.

    The main action colour is changed once, from light blue to charcoal, and its contrast on white goes from 1.9 to 1 to 16.1 to 1. The product, prototypes, Claude Design and the AI skill each take the new button in turn.

  3. Built for AI tools to read.

    Every draft follows the same rules, whoever asks for it. That is what lets a product manager prototype a feature in 2 to 3 hours instead of writing a spec and waiting for design, and lets sales tailor a deck to a prospect in under an hour instead of 2 to 4 days. I review what reaches customers; internal tools ship without me, and without a sprint's wait for a roadmap slot. Below, three rules beside a Claude Design prototype made from the same system.

    Someone in sales, operations, product or QA asks for a page to create vouchers. The draft arrives with three mistakes: a title in Title Case, a dash in the helper text, and a pale blue button that fails contrast. Three rule checks fix them one at a time.

    cata-ds-rules.md
    1. Listing pagesFind: search first. The only field in the row.
    2. Listing pagesThe status filter (up to five mutually exclusive statuses, All first) is the segmented pill.
    3. AccessibilitySoft badges use the -text tokens.
    The Voucher Packs prototype, made in Claude Design
  4. The AI skill reads only what the task needs.

    It used to read every rule on every use. Now it reads the core rules and the one topic the task touches, about a quarter of the context, so each prototype starts faster and costs less to make.

    Three tasks in turn: an orders list, page tabs and KPI cards. For each, the skill reads core.md and the one topic file the task needs, and leaves the other files and the full spec unread.

  5. Colours chosen by how easy they are to read.

    The old blue action colour reached 1.9:1 on white. Charcoal reaches 16.1:1.

    Before: cloud blue1.9:1fill against white
    Below the 3:1 minimum for a control against its page
    After: charcoal16.1:1fill against white
    Now the colour of every main action
  6. Motion that feels quick and steady.

    The sidebar used to resize on every frame, redrawing every chart with it. Now it slides, and the charts redraw once at the end. On a 144 Hz display, the 300 ms collapse went from 7 of 43 frames to all 43.

    Before
    After
  7. What one source made possible.

    Eleven rule changes reached the product, the prototypes and the AI tools in 12 days, with nobody redoing them by hand. That speed is what lets product, engineering and sales build on their own, and lets me spend my review time on what customers see.

    For a product manager to get a working prototype from the rules. Before, it didn't happen: a spec, then a wait for design.
    3 hours
    For a sales deck on the design guidelines, tailored to the prospect. It used to take 2 to 4 days.
    1 hour
    Design reviews, and roadmap slots, for an internal tool built on the system. The wait used to be a sprint, about two weeks.
    0
    1. v1.1Each kind of movement gets its own timing.
    2. v1.2Charcoal for actions, gold for the brand only.
    3. v1.2.1Gold gets its own name, and number cards fit any width.
    4. v1.2.2A style that made text invisible is now blocked.
    5. v1.2.3The system moves into one home, and charts may use gold.
    6. v1.2.4Faint text in dark mode becomes readable.
    7. v1.2.5Short numbers follow each merchant's currency.
    8. v1.2.6The currency sign goes in front, and labels pass contrast.
    9. v1.2.7Tap a number card to see the exact amount.
    10. v1.2.8Tap a chart total to see the exact amount.
    11. v1.2.9Two notes corrected to match the code.
    Eleven versions of the design system, shipped between 12 and 23 October 2026.
Key decisions, and why
  • One source. Two files each claimed to be the truth and disagreed. Now one file decides, and everything else is generated from it or reviewed against it.
  • Colour roles. Charcoal is for actions, gold is for the brand only, and light blue is for highlights. Light blue as a button failed the contrast minimum on white.
  • Motion. Each kind of movement has its own timing. A staggered chart redraw made each frame lighter but made the visible lag longer, so I did not adopt it.
  • Money. Amounts follow each merchant’s own currency. Most use euro, Singapore dollar or US dollar, and the browser printed “SGD” or a bare “$”.
  • Touch and contrast. Nothing depends on hovering with a mouse, and faint text must meet a minimum contrast.
  • Two kinds of fix. A design decision gets its own ticket and write-up. Small polish is one line in the release notes.