elementary

Standardizes token-based styling for React-based frameworks and static sites with themed components.

2|2|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/million-views/skills --skill elementary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elementary
Source: https://github.com/million-views/skills/tree/main/elementary
Command: npx skills add https://github.com/million-views/skills --skill elementary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Elementary design system standardizes design tokens and theme-driven values to ensure consistent UI across projects and teams.

Core Features & Use Cases

  • Layer 1 Token Naming System: semantic tokens that remain stable across themes.
  • Layer 2 Theme Implementations: Polished and Sketch variants with light/dark support
  • Layer 3 Component Classes: pre-built patterns in assets that adapt to tokens across themes

Quick Start

Install the Elementary assets to your project and import the polished theme and components CSS to start theming.

Frequently Asked Questions about elementary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize design tokens for consistent UI theming across multiple projects?

Standardizing design tokens uses a three-layer system separating semantic tokens, theme implementations, and component classes to ensure consistent UI across projects. This approach enables theme switching while reusing the same underlying token structure.

What are semantic design tokens and how do they work with layer separation?

Semantic design tokens are stable naming references that remain consistent across different themes. They work through layer separation: Layer 1 defines tokens, Layer 2 implements themes like light and dark, and Layer 3 applies tokens to component classes.

Can I use CSS variables for design tokens in React-based frameworks and static sites?

CSS variables for design tokens are fully supported in React-based frameworks and static sites. The system applies themeable CSS variables across both environments, allowing theme switching between polished and sketch themes.

How do I set up a token-based design system with light and dark theme switching?

Setting up a token-based design system involves installing the asset files and importing the polished theme CSS along with component styles. This enables immediate light and dark theme switching using the pre-built theme implementations.

Does this design token system work for both polished production UI and sketch themes?

The design token system explicitly supports switching between polished production UI and sketch themes. Both theme variants are built on the same semantic tokens, ensuring component classes adapt correctly across either visual style.

What's the best way to maintain consistent web design when switching between different UI themes?

The best way to maintain consistent web design across UI themes is binding component classes to semantic tokens rather than hard-coded values. This ensures visual consistency automatically updates whenever themes change.