Native HTML and CSS interface components crafted with Master CSS, in the Moonstone / Obsidian material: a zinc pearl in light mode, a matte obsidian in dark mode, lit from above with layered shadows.
- A contract for each component.
button.jsonbesidebutton.csslists its classes, the element each goes on, its states, its public custom properties and one correct example. People and coding agents write to it, andmaster-ui checkreports markup that breaks it. - Native elements first. Components style
<button>,<select>and<input role="switch">, keeping their keyboard, form and accessibility behavior. The few patterns with no native element ship a reference script that only moves attributes. - One stylesheet per component. Rules live in
@layer components.ui, inside thecomponentslayer, and read Master CSS theme tokens, so utilities in markup always win, and so does a rule of your own in@layer components. - The theme is only a theme. A component never writes a color of its own;
themes/paper.cssis a second material built from tokens alone. - Yours when you need it. Retune with tokens, replace the material with a theme, or
master-ui own <name>to take a component's source, with upstream changes still visible.
@import '@master/css';
@import '@master/ui';<button type="button" class="btn btn-primary">Save changes</button>Read the documentation at ui.master.co.
Note
Master UI follows semantic versioning: only a major release removes or renames a public name. A minor or patch release can still change how a component looks, so pin the version and review each upgrade; see Stability.
Master UI’s design guide explains its material, geometry and interaction choices. Master Design covers general design principles. Master UI owns its design language and implements the theme, components, behavior and markup contracts. Master CSS supplies the styling language and compiler; @master/internal-site composes the first-party documentation sites from these components and owns their routing, reading layout and search.
| Path | Contents |
|---|---|
packages/ui |
@master/ui: the CSS source, a contract beside each stylesheet, the behaviors, the checker and the master-ui command |
skills/master-ui |
The skill a coding agent uses in a project that has Master UI: npx skills add master-co/ui --skill master-ui |
site |
Documentation site: Astro, Svelte and @master/internal-site, deployed to Cloudflare Pages. It also publishes llms.txt, every page as Markdown, the contracts and a registry |
Requires Bun 1.4 and Node.js 24 or later.
bun install
bun run dev # documentation site on http://localhost:3300
bun run test # compile every stylesheet, hold it to its contract, run the checker and the behaviors
bun run type-check # Astro, Svelte and TypeScript checks
bun run build # static site in site/outCommits follow the Aronrepo policy in AGENTS.md; the commit hook checks each message.
- Native HTML and CSS: the component stylesheets and their documentation.
- The foundation (current): a contract for every stylesheet, a checker, reference behaviors, a second theme, a build to plain CSS, a registry of source to own, and what a coding agent reads (
llms.txt, a skill). - Refinement: tuning the components and adding to them on that foundation.
React, Svelte and Vue are served without a bindings package. Most components are a class on a native element, the same in any framework. The seventeen patterns that hold state (a combobox, a calendar, a dialog opened from state, a toast queue and the like) have a component in packages/ui/frameworks/<framework>, which a project copies with master-ui add; what it decides stays in @master/ui/behaviors, written once and held to one set of scenarios in packages/ui/tests/frameworks.
The Master UI library, the public skill, and reusable documentation examples are MIT licensed. The website notice covers the site implementation, original prose, and artwork. See the repository license for the full scope.