Quick start
The shortest path from an empty project to an installed component library. This is the shape of the workflow — each step links to the concept behind it.
#The workflow
- Create a project and choose its targets. A project declares which outputs it produces — React today, with Figma as a design target. See Targets.
- Author your foundations. Define the design tokens — color, spacing, type, radius, motion — that every component and every output will draw from. See Foundations.
- Compose components. Build components from neutral nodes, give them a props contract, and wire interactive behavior. See Components and Behaviors.
- Generate. A generator turns the IR into real code — self-contained React components plus a shared theme. See Generators.
- Release. Assemble the generated library into a versioned package and publish it to your registry. See Release & registry.
- Install and use it in your app, like any other dependency.
#Installing a released library
Consumers don't need Milda — they install the generated package from your registry and import components like any library. Point the package scope at your registry, then install:
bash
# .npmrc — route only your scope to the private registry @your-scope:registry=https://registry.your-company.com # then install the released design system npm install @your-scope/design-system
And use it:
tsx
import { Button } from '@your-scope/design-system'
export function Example() {
return <Button variant="primary">Ship it</Button>
}What's available today
React generation, foundations, targets, and release assembly are built. Hosted registry hosting and team collaboration are on the roadmap; locally, releases publish to a Verdaccio registry. The commands above show the consumer-side shape, which is registry-agnostic.
#Try it without installing anything
The fastest way to get a feel for Milda is right here. The Foundations editor and editor runtime pages embed the real Studio components — interactive, no setup.