2026
itBoat: Marketplace and a Design System for AI Agents
itBoat started as an encyclopedia of yachts and boats. The next step was a marketplace on top of it, and there was nothing to build it on: no design system, no components, and auto layout only in places. I designed the marketplace and built the design system for the whole product, with one requirement beyond consistency: AI agents had to be able to design with it, not only people.
- 15,000+
- Yacht and boat models in the encyclopedia
- 1,200+
- Builders, each with its own page
- 140+
- Categories and types
Product Designer on a two-month, part-time contract in 2026.
context
Every builder, model and type in the encyclopedia has its own page, so each page template is repeated thousands of times. The marketplace would add listings: specific boats for sale, placed by brokers.
What I owned
- Designing the marketplace: the listings page with filters, listing sections inside the encyclopedia, and the model, builder and listing pages
- Building the component library for the whole product, marketplace and encyclopedia
- Structuring the system so AI agents could design new screens and components with it
problem
Two products on the same pages
The marketplace was never going to be a separate site. A listing is one specific boat of a model the encyclopedia already describes, and encyclopedia pages had to show boats for sale. From day one the two would share galleries, specs, cards and page structure.
Building the marketplace on components while the encyclopedia stayed as loose layouts would have meant two versions of every shared part, drifting further apart with every change.
decision
One system for the whole product
The brief was the marketplace, but with this much overlap it made sense to move the encyclopedia onto the same components in the same pass. It made the job bigger up front. In return, every part built for one side was immediately available to the other, and there was one system to maintain instead of two.
system
A system agents can design with
The system had a second audience. The goal was for AI agents to design new screens, and even new components, from it. A designer fills gaps with judgement. An agent does exactly what the file says. So everything a designer would infer had to be made explicit.
Structure, not coordinates
Auto layout on every frame. An agent changes a layout by editing its structure instead of guessing positions.
Only known parts
Every page is assembled from components, with no detached copies. A new page is a new combination of parts the system already has.
Options as properties
States and variations are named component properties. An agent switches a property instead of redrawing an element.
design
Designing the marketplace
The marketplace had to work in two places: as its own section, with a listings page and filters, and inside the encyclopedia, where people are already reading about a model or a builder.
On encyclopedia pages, the marketplace appears as a section of boats for sale from that builder and similar ones, using the same listing cards.
results
- The whole product, encyclopedia and marketplace, is now designed on one component library, built from zero.
- Listing pages and listing sections across the encyclopedia are live on itboat.com.
- By the time my contract ended, the team had started using AI agents to design on top of the system.
reflection
What I learned
Designing for agents means designing for the most literal reader. Every shortcut a person would forgive, a detached instance, a frame without auto layout, a vague layer name, is a place where an agent goes wrong. Building for that reader made the system better for people too.