design-system

Generates three-layer design tokens, component specifications, and brand-compliant HTML slide decks.

2|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/sathishssj3/NexVR-Engine --skill design-system-sathishssj3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/sathishssj3/NexVR-Engine/tree/main/.agents/skills/design-system
Command: npx skills add https://github.com/sathishssj3/NexVR-Engine --skill design-system-sathishssj3

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Maintaining visual consistency across components and presentations is difficult when colors, spacing, and typography are hardcoded. This Skill establishes a single source of truth for design tokens and automates the creation of token-compliant components and slide decks. ## Core Features & Use Cases - Three-Layer Token Architecture: Generates CSS variables from a JSON config using primitive, semantic, and component layers, with dark-mode support and Tailwind config output. - Component Specifications: Provides detailed specs for buttons, inputs, cards, badges, alerts, dialogs, and tables including variants, sizes, and states. - Slide Generation: Builds brand-compliant HTML pitch decks with Chart.js charts, BM25 slide search, contextual layout decisions, and token compliance validation. - Use Case: A designer needs a 10-slide investor pitch that matches brand guidelines. The Skill queries decision CSVs for layout, typography, and color logic, generates the HTML deck using design tokens, and validates it for hardcoded values. ## Quick Start Ask the AI to generate design tokens from the starter JSON config and then create a brand-compliant pitch deck using the slide generation scripts.

Frequently Asked Questions about design-system

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

FAQPage Schema
How do I generate CSS variables from a design tokens JSON file?▼

Run the generate-tokens.cjs script with your JSON config: node scripts/generate-tokens.cjs --config tokens.json -o tokens.css. It resolves token references across primitive, semantic, and component layers and outputs CSS custom properties, with an optional Tailwind format.

What is a three-layer design token architecture?▼

It structures tokens as primitive raw values, semantic purpose aliases, and component-specific tokens. For example, a primitive blue-600 hex value feeds a semantic primary color, which feeds a button background token, enabling theme switching at the semantic layer.

How to create brand-compliant HTML slides with design tokens?▼

Use the slide generation scripts which query decision CSVs for layout, typography, and color logic, then output HTML importing design-tokens.css. All slides must use var() token references and Chart.js for charts, then pass validation with the token validator.

Does the token validator catch hardcoded colors in HTML files?▼

Yes, html-token-validator.py scans HTML assets for hex, rgb, rgba, and hsl values plus hardcoded fonts outside script blocks. It allows brand-color rgba values for transparency and external font or image URLs, reporting errors per file with a summary.

Can I use these design tokens with Tailwind CSS?▼

Yes, generate-tokens.cjs supports a --format tailwind option that outputs a color config mapping semantic tokens to CSS variables. You add the generated object to tailwind.config.ts under theme.extend.colors.

Why does slide validation fail even when I use brand colors?▼

Validation fails when hex or font values are hardcoded in style blocks or inline styles instead of var() token references. Even correct brand values must be referenced through tokens like var(--color-primary) so theme changes propagate automatically.