Nagisa Ikeda

Nara Labs · Design Engineering

Ai-Native Design System

A design system built for humans and AI agents to design, code, document, and ship products faster.

Role

Product Designer · Design Engineer · Founder

Context

Nara Labs

Timeline

Ongoing

Stack

Figma · React · Next.js · Tailwind · TypeScript · Cursor · Claude Code · OpenAI

TL;DR

Modern design systems should do more than keep interfaces visually consistent. They should help AI generate better code.

I built this system as a shared language between designers, engineers, and AI agents. Every component is tokenized, documented, reusable, and optimized for AI-assisted development.

The goal is to move from idea to production in hours instead of days.

The problem

Traditional design systems were built for human handoff. But modern product teams increasingly build with AI coding assistants.

Most design systems still have:

  • Inconsistent documentation
  • Missing implementation details
  • Duplicated components
  • Disconnected Figma and code
  • Poor token management
  • No AI-readable specifications

AI can only generate high-quality interfaces if the design system itself is structured, reusable, and machine-readable.

Design systems are becoming AI infrastructure

A modern design system is no longer just a UI library. It is an operating layer that helps humans and AI agents design, build, and maintain products together.

The better the system, the better AI can generate consistent, production-ready interfaces.

Design principles

AI-readable

Every component includes clear usage rules, props, states, and implementation guidance.

Single source of truth

Design tokens, components, and code map to the same system.

Code-first

Design decisions translate directly into reusable React components.

Composable

Components are built as primitives, patterns, and templates rather than one-off screens.

Agent-friendly

The system is optimized for Cursor, Claude Code, OpenAI, and future coding agents.

System architecture

  1. Design Tokens
  2. Primitive Components
  3. Composite Components
  4. Product Patterns
  5. Templates
  6. Shipped Products

Each layer builds on the previous one. Changing a token updates the entire product surface, while reusable patterns allow new AI products to be created faster without redesigning the same foundations.

AI-native workflow

Problem framing
AI-assisted user flows
Component selection
Cursor implementation
Claude Code review
Human refinement
Production deployment

The workflow reduces repetitive production work while keeping product judgment, interaction quality, and final taste under human control.

Component system

AI-native design system overview

Core UI

  • Buttons
  • Inputs
  • Cards
  • Modals
  • Tabs
  • Tables
  • Forms

AI Product Components

  • Prompt Inputs
  • Streaming Responses
  • Agent Status
  • Memory Cards
  • Tool Calls
  • File Upload
  • Knowledge Search
  • Voice Controls

Product Patterns

  • Dashboards
  • Chat Interfaces
  • Command Palettes
  • Workflow Timelines
  • Research Panels
  • Onboarding Flows

Toolkit

Models

  • OpenAI
  • Claude
  • Gemini
  • Qwen
  • MiniMax
  • DeepSeek

Engineering

  • TypeScript
  • React
  • Next.js
  • Python
  • FastAPI
  • Convex
  • Vercel

AI Systems

  • Agents
  • MCP
  • RAG
  • Memory
  • Vector Databases
  • Vapi
  • LiveKit
  • Evals

Workflow

  • Cursor
  • Claude Code
  • GitHub
  • Figma

Products built with this system

The system allowed multiple AI products to share consistent visual language, interaction patterns, and engineering foundations without starting from zero each time.

What I built

I designed and built the foundation for an AI-native product system that supports both human creativity and AI-assisted implementation.

  • Visual language
  • Design tokens
  • Reusable React components
  • AI-specific interaction patterns
  • Prompt and agent UI components
  • Documentation structure
  • Cursor implementation workflows
  • Portfolio and Nara Labs product surfaces

Lessons learned

01

Design systems are no longer static UI kits; they are product infrastructure.

02

AI-generated interfaces are only as good as the systems they are grounded in.

03

The most valuable design work is often deciding what should become reusable.

04

The future of design engineering is not handoff. It is co-building with AI.

Outcome

Result

A reusable AI-native design system powering Nara Labs projects and my personal portfolio.

Impact

  • Faster prototyping
  • More consistent AI product interfaces
  • Reduced design duplication
  • Better design-to-code alignment
  • Stronger foundation for future products

Related work

Back to Design Work