Ship the tokens

Start with one stylesheet. Vendor the generated tree when you want every artifact in source control.

Fastest path

Quick start

Paste the generated output into a stylesheet. In your app stylesheet, @import it before Tailwind so the Tailwind v4 theme mappings can consume the tokens.

@import './etesie.css';
@import 'tailwindcss';

Source-controlled

Vendored tree

These are the exact files Etesie publishes. Download any one now. The tokens and styles form the portable design-system/ folder; the agent skill goes in your agents' skill folders at the repository root.

README.mddesign-system/README.md

1,763 bytes

index.cssdesign-system/index.css

137 bytes

tokens.cssdesign-system/tokens.css

139,519 bytes

tailwind.cssdesign-system/tailwind.css

152,888 bytes

components.cssdesign-system/components.css

127,568 bytes

material-shapes.jsondesign-system/material-shapes.json

209,083 bytes

theme.jsondesign-system/theme.json

1,090,155 bytes

tokens.jsondesign-system/tokens.json

1,216,417 bytes

SKILL.md.agents/skills/et-material-design/SKILL.md

4,657 bytes

SKILL.md.claude/skills/et-material-design/SKILL.md

4,657 bytes

When the system evolves

Keep it synced

GitHub PR publishing lives in Themes: version a publish, review the diff, and keep generated files aligned with the recipe.

CLI fast startComing soon

npx jsrepo add @etesie/default