Kairoz

Get started · 5 min read

A design language, not a dependency.

Kairoz is a design language your coding agent absorbs and applies to generate UI native to your stack. No framework to bolt on. shadcn stays shadcn. Tailwind stays Tailwind. Your agent reads the rules, then generates consistent UI in whatever stack you use. This entire site was built that way in a single pass.

View on GitHubBrowse components →

The mental model

Three assets, three roles. Read them in this order.

01Ground truth
The rules (markdown)
references/*.md define tokens, patterns, motion, and responsive behavior. This is the source of truth your agent loads on every task.
02Language
The vocabulary (class names)
.kairoz-btn, .kairoz-card, .kairoz-dot — these are not literal selectors. They are your agent's shorthand for 'render this the Kairoz way'.
03Proof
The reference CSS
colors_and_type.css is a working implementation. Use it directly for plain HTML. For shadcn or Tailwind, the agent translates rather than overlays.

1

Give your agent the skill

That is the entire install. The skill is plain markdown plus one reference CSS file. Any coding agent that reads a repo can absorb it — Claude Code, Cursor, Windsurf, Cody, or whatever you run. No proprietary format, no lock-in.

# Claude Code — two commands (marketplace, then plugin)
/plugin marketplace add sujal7103/kairoz
/plugin install kairoz@kairoz-ui

# Other agents — point them at the skill directory
# They read the markdown, learn the rules, and generate code in your stack.
SKILL.md (200 lines of positioning and quick reference) plus six markdown references covering tokens, components, theming, patterns, responsive, and motion. The CSS file ships alongside them as a reference implementation the agent studies, not a file it blindly copies into your project.

2

Let it generate code in your stack

The agent detects your stack, then translates Kairoz rules into its native idiom. Identical visual output, idiomatic code. Pick your stack below to see the result.

One command. Compatible with any coding agent that reads a repo.
# Claude Code — two commands
/plugin marketplace add sujal7103/kairoz
/plugin install kairoz@kairoz-ui

# Cursor, Windsurf, Cody, etc.
# Point the agent at this repo's skills/kairoz/ directory.
# Everything an agent needs is plain markdown + one CSS file:
#
#   skills/kairoz/SKILL.md                 — entry rules (read first)
#   skills/kairoz/references/tokens.md     — every design token
#   skills/kairoz/references/components.md — class vocabulary + variants
#   skills/kairoz/references/theming.md    — dark/light + shadcn map
#   skills/kairoz/references/patterns.md   — layout rules
#   skills/kairoz/references/responsive.md — multi-surface guidance
#   skills/kairoz/references/motion.md     — motion inventory
#   skills/kairoz/colors_and_type.css      — reference implementation

3

The Kairoz aesthetic, stack-independent

Regardless of codebase, the output follows the same rules: AMOLED black, 28px buttons, 4px grid, border-defined surfaces, near-white primary actions, blue reserved strictly for focus and selection.

OKDRAFTFAIL⌘K
Live Queued
kairoz-edge · production
Last deploy 2m ago · main@a9f3b1 · 42ms p95
The block above uses the reference CSS directly because this site is a minimal Next.js project. In a shadcn project, your agent would emit <Button variant="default">Ship it</Button> with Kairoz tokens mapped into shadcn variables. Same pixels. Different code.

Repository anatomy

github.com/sujal7103/kairoz — MIT licensed. Three top-level directories:

For agents
skills/kairoz/
SKILL.md
references/tokens.md
references/components.md
references/theming.md
references/patterns.md
references/responsive.md
references/motion.md
colors_and_type.css
The skill itself. Markdown rules are the source of truth; the CSS proves them out.
For humans
app/
app/page.tsx
app/get-started/...
app/components/...
app/foundations/...
app/patterns/...
app/mockups/...
This site. Generated in a single pass by an agent that learned the skill.
For install
.claude-plugin/
marketplace.json
plugin.json
Registers the repo as a Claude Code marketplace plugin. Install with /plugin marketplace add sujal7103/kairoz, then /plugin install kairoz@kairoz-ui.

Frequently asked

Yes, by translation rather than overlay. Your agent reads the shadcn variable map in references/theming.md and overrides shadcn's CSS variables with Kairoz values. Your shadcn components remain shadcn components — they just inherit the Kairoz aesthetic. No .kairoz-* classes in the output.

Where to go from here

Next

Browse components

50+ live previews, each with copy-ready markup.

Components →
Next

Study the tokens

Every color, spacing value, radius, and shadow defined.

Foundations →
Next

Fork a pattern

Landing pages, dashboards, chat views, mobile shells.

Patterns →
Next

Explore the mockups

Email, e-commerce, multi-agent, news, and stocks.

Mockups →
Found a gap? Spotted a bug?
Contributions welcome at github.com/sujal7103/kairoz · MIT