Skip to content
Design system

Pay once. Works with React and PHP, and with Claude Code, Cursor, Codex, Gemini CLI and Copilot.

146ComponentsIn React and in PHP
48ScreensBuilt and ready to copy
80IconsAnd 33 brand marks
3LanguagesEnglish, Italian and Spanish

Everything a product is made of

This shop is one of them: every page of Stokefy, its cart and its checkout included, is built with OS.

A website

A landing page, pricing, a journal, careers and help: the pages a company needs, ready for its words.

A company’s pricing page built on OS, three plans side by side

An app

A home of numbers, lists that filter, sort and select, records and settings, in a shell that holds still while the work scrolls.

An app’s list of companies built on OS, in dark, with filters and a stage for each

A shop

A catalogue, a product page, a cart and a checkout, with the cards your buyers pay with.

A shop’s checkout built on OS: the contact, the delivery and the order beside them

A way in

Sign in, sign up, a code from an app and a lost password, one step to a screen.

A sign-in screen built on OS, in dark

Documentation

Guides, a cookbook and a changelog for your own product, with a column of contents that follows the reading.

A product’s documentation built on OS: a cookbook of examples to filter

A page builder

The blocks a page is made of and the editor that arranges them, so a page is made without writing it.

The page builder: the blocks of a page in a column, and the page beside them

Ready for your AI coding tools.

Claude Code, Gemini CLI, Cursor, Codex and Copilot read the rules OS comes with before they write a line, so what they build is OS, not a guess at it.

AGENTS.md
# Building with OS

## Six rules

1. Use the component OS has for the job.
2. Say what the screen is first, then use OS's screen for it.
3. Ask for decisions, never numbers.
4. Arrange with Stack, Row and Grid.
5. Never restyle a component from outside.
6. Run npx os-check-screens before the build.
Terminal
npx os-check-screens src

os-check-screens: 92 files read under src
OK    every screen opens once, no sheet in a card,
      no strip over a sheet, fields a block apart

The rules where the tools look

AGENTS.md, CLAUDE.md and GEMINI.md for your project: which screen for which page, which prop for which decision, and what never to write by hand.

A live connection

npx os-mcp lets Claude Code, Cursor or Gemini CLI look a component up while it writes, from the version you installed, with nothing to host.

Every component in plain text

A page for each component, with what it is for, its props, their types and defaults, and its PHP signature, all indexed in llms.txt.

One vocabulary

Tone is the purpose, fill is how loud, size is which height, on every component, so what a tool learns on one is right on the next.

A check it can run

os-check-screens reads your screens and stops on the first that breaks a rule: a table in a card, two heads, a record in a drawer.

Every prop and every token in the documentation is read from the code as it builds, so it never describes something that is not there.

Two renderers. One markup.

Every component is a React component and a PHP function, and both write the same HTML. A site on shared hosting and an app in the cloud come out as one product.

React
import { Button } from '@stokefy/os'

<Button tone="brand" size="large">Get started</Button>
PHP
use function Stokefy\OS\button;

echo button('Get started', tone: 'brand', size: 'large');

A component for every part of a product.

Shelved by what the reader is doing: pressing, filling in, browsing, reading a number, finding the way. Every one is a React component and a PHP function of the same name.

Actions

You press it, and something happens. Button, Context menu, Copy button, Link, Menu, Provider button, Share, Theme toggle.

Navigation

It takes the reader somewhere else. Breadcrumb, Contents, Language switcher, Logo, Pagination, Prev and next, Sidebar, Site menu, Tab bar, Tabs.

Shells

The frame a product stands in, once. App shell, Auth shell, Builder shell, Mobile shell, Site shell.

Structure

The bars and heads a page is built round. Footer, Header, Page head, Section head.

Forms

You put a value in, and it comes back out. Checkbox, Code field, Color picker, Combobox, Date field, Drop zone, Editor, Field group, Inline edit, Input field, Password field, Password rules, Phone field, Radio, Range, Search, Segmented control, Select, Switch, Tag field, Textarea.

Views

Many of something, to browse. Agenda, Board, Calendar, Files, Filter bar, List, Log, Notifications, Roadmap, Selection bar, Table, Time bars, Timeline, Toolbar.

Data

A value: a number, a trend, a change, a moment. Area chart, Bar chart, Change, Chart, Dot chart, Heatmap, Line chart, Moment, Pie chart, Radar chart, Radial chart.

Overlays

It comes over the page, and goes away again. Bottom sheet, Cookie banner, Dialog, Drawer, Popover, Toast, Tooltip.

Cards

One of something, as a card. Blog card, Card, Credential card, Event card, File card, Project card.

Content

One of something, set on the page. Accordion, Ad slot, Avatar, Badge, Carousel, Collapsible, Description list, Divider, Emblem, Features, Gallery, Hero, Highlight, How it works, Image, Kbd, Logo cloud, Palette, Pricing, Prose, Skeleton, Snippet, Sortable, Stat, Team, Testimonial, Ticker, Truncated text.

Feedback

What the system is doing. Alert, Feedback, Progress, Spinner, State, Steps.

Chat

A conversation, message by message. Chat.

Builder

The blocks of a page, and the editor that arranges them. Block fields, Block list, Block picker, Block preview, Media picker, Theme fields.

Ecommerce

What a shop sells, and how it is chosen. Product card, Star rating, Variant picker.

Site

The pages a site is made of, ready for its words. Block page, Blog index, Blog article, Product listing, Product page, Cart, Checkout, Order summary, Contact, Docs page, Legal, Error screen.

Auth

The way in, one step to a screen. Sign in, Sign up, Forgot password, One-time code, Set password, Two-factor setup, Confirm password, Wizard.

Admin

The screens behind the door. Dashboard, Admin list, Admin form, User list, User form, Inbox, Capture, Studio.

Account

What a person keeps about themselves. Settings, Security, Email.

Decisions, not numbers.

Every colour, distance, height and corner in OS is a token with a name. A component asks for the decision, and the mode the product is in answers with the number.

The Typography page of the documentation OS comes with: the type scale, level by level, with its classesThe Typography page of the documentation OS comes with: the type scale, level by level, with its classes

Colour

Roles named for where a thing sits, a surface, a line, an ink, never for a component, and each one worked out in light and in dark.

Typography

One class for each level of text, from the largest heading to the smallest label. The class says what the text is, and the surface decides how large it comes out.

Rhythm

The distances a layout reaches for by name. A component never writes a distance of its own.

Tiers

The heights every control stands on, so a button, a field and a strip asked for the same one line up without anybody measuring.

Roundness

One ramp of corners, and how round the whole product is, chosen once, from square to pill.

Layout

Stack, Row and Grid, with named gaps. Each arrangement has one spelling, and there are no utility classes to learn.

Light and dark, from one colour.

Give OS your brand colour and your typefaces. It works out every surface, line and ink from them, in both themes, at a contrast every reader can read.

One company site built on OS, its left half in light and its right half in dark

At home on a phone.

Each component measures the room it is given, not the window, so a screen works the same on a phone, in a panel and in a drawer.

Three screens built on OS on a phone: a company site, a dashboard in dark and a person’s record

Running in three steps.

From the zip to the first screen, and your AI tool building with it.

  1. React or PHP

    Install the package

    Copy it into your project and install it from the file, or point Composer at its PHP folder.

  2. Once

    Import it, then build

    One stylesheet at the root of the app, then the components where you use them.

  3. One copy

    Hand your AI tool the rules

    Three files from the zip into your project, and Claude Code, Cursor or Gemini CLI build with OS from the first prompt.

Terminal
# 1. Install the package
npm install ./vendor/stokefy-os-1.5.1.tgz

# 2. Import it, then build
import '@stokefy/os/css'
import { Button } from '@stokefy/os'

<Button tone="brand">Get started</Button>

# 3. Hand your AI tool the rules
cp ai/AGENTS.md ai/CLAUDE.md ai/GEMINI.md your-project/

What is in the box

React components

Every component with its types, for React 18 and later.

PHP functions

The same components for PHP 8.1 and later, and a small script that gives them their behaviour.

One stylesheet

The tokens, the modes and every component in one file, with no utility classes to learn.

Icons and marks

The interface icons, and the marks of the networks, services and cards a site shows.

Words, translated

Everything a component says on its own, in English, Italian and Spanish.

The source to change and build again, the documentation as a site you open on your own machine, and every screen as code.

Rules for AI tools

AGENTS.md, CLAUDE.md and GEMINI.md for your project, a page for every component, and a live connection over MCP.

A check for your screens

One command that reads your screens and names what breaks the rules, to run before every build.

Pay once.

Start free with Core, then take the whole system for one person or a team of up to ten. Every update after is yours.

Core

For any project, to start with.
Free
  • 61 components, in React and in PHP
  • The stylesheet, the tokens and the modes
  • The rules for your AI tools
  • Your own projects and your clients’

Team

For up to ten people in one company.
$599once
Everything in Personal, and:
  • Ten people at once
  • Places that move when somebody leaves or joins
  • The company’s projects and its clients’

Pay once, by card.

Every plan, side by side
FeatureCorePersonalTeam
What it holds
Components, in React and in PHP61146146
Screens ready to copyNot included4848
Page sections: hero, features, pricing and moreNot includedIncludedIncluded
Shells, tables, boards and chartsNot includedIncludedIncluded
The page builderNot includedIncludedIncluded
Brand marksNot included3333
Interface iconsLucide’sOS’s ownOS’s own
The source, to change and buildIncludedIncludedIncluded
The documentation, in the zipNot includedIncludedIncluded
For AI coding tools
AGENTS.md, CLAUDE.md and GEMINI.mdIncludedIncludedIncluded
A page for every componentIncludedIncludedIncluded
The live connection over MCPIncludedIncludedIncluded
The screen checkIncludedIncludedIncluded
License
PeopleAnyoneOneUp to ten
Your projects and your clients’IncludedIncludedIncluded
Every update afterIncludedIncludedIncluded
Places that move between peopleNot includedNot includedIncluded

Questions

Every update, dated.

What each release since OS went on sale changed. Your downloads always hold the latest.

Build your next product on OS.

Pay once: $199 for one person, $599 for a team of up to ten. React and PHP, the source, the documentation and the rules for your AI tools.

Type something to search.