Skip to content

A design system for agents to read.

For a platform where agents build a new app for every customer, we designed the component library and wrote the design rules the agents follow.

A chat where the agent searches a founder graph, explains why a team fits, and surfaces one founder with a warm intro
Client
Stealth client
What they build
AI platform where agents build each customer's app
Our work
Component library, Agent-readable guidance
Timeline
August to September 2026

The company

An AI-native intelligence platform in stealth. Customers search, track and act on data through chat, automations and an agent. Each customer gets its own app, built by agents and engineers, and every app pulls from one shared design system. One component change reaches every deployment.

The problem

The product worked, but the experience felt chaotic and the visuals undersold it. The team needed a library that engineers without design training could use to build polished front ends for every customer.

The design system has a new reader. Write it for the agent too.

The work, piece by piece.

01

Chat foundations

People and companies rendered as distinct objects, a standard template for tool calls, and a composer where mentions resolve to real records.

02

A home portal

Draggable widgets for active work and pending actions.

03

Three detail patterns

A side drawer for browsing, an overlay for focused tasks, and a full-page expand.

04

The component library

Forms, tags, data tables, chat bubbles, thinking states, action cards, empty and loading states, toasts, drawers and charts, built in Figma and React.

05

Per-customer theming

The same system re-skins for each customer.

06

Guidance agents can follow

Motion and interaction rules written into each component's docs, so agents building new pages choose the right pattern on their own.

HomeOne box. Three good questions to start.The home screen: a greeting, one prompt box and three suggested questions beside the workspace sidebar
ScoutsDescribe who you want. The agent keeps looking.A scout for robotics founders in New York, listing founders with a tag, a stage and one line on why they fit
RosterEvery founder, stage and warm path in one table.A roster table of founders with stage, thesis, round and partner, and a hover card showing one founder's history
Founder detailOpen a row without losing your place.A side drawer with one founder's details: what they're building, how they were found, and what they're raising

How it went

Four weeks. We polished a few key screens first, then pulled the color, type and spacing standards out of them. The team pulled our frames straight into code through the Figma MCP and was building new screens from the library every day.

What other teams can learn from it.

  • Design systems and motion rules for agents to read
  • A standard template for tool calls
  • One system, themed per customer
Polar's home: one workflow waiting on your input, plus the latest results, beside the persistent sidebarNext · PolarMaking long-running work legible.

Building something like this?

Start a project