site-design-system

Plan and audit website design systems using tokens, component contracts, and page templates.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill site-design-system-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-design-system
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/site-design-system
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill site-design-system-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Websites often grow as collections of one-off page fixes, leading to inconsistent colors, spacing, and components that break when real content arrives. This Skill structures website UI as a system of design tokens, component contracts, and page templates so visual decisions stay consistent and maintainable across pages. ## Core Features & Use Cases - Design Token Modeling: Define a compact, semantically named token set covering color, typography, spacing, radius, shadow, layout, and motion, with CSS variable implementation patterns. - Component Contracts: Document reusable components with purpose, variants, states (loading, empty, error, success, disabled), content rules, and accessibility requirements before scaling usage. - Page Hierarchy & Templates: Establish stable page blueprints covering identity, value proposition, primary action, proof, and navigation so page intent is clear within the first screen. - Use Case: When refactoring a marketing site with inconsistent buttons and ad hoc spacing, use this Skill to extract a minimal token vocabulary, write contracts for repeated components, and define reusable page layouts instead of patching individual pages. ## Quick Start Use the site-design-system skill to audit my landing page and propose a token set and component contracts for the repeated UI patterns.

Frequently Asked Questions about site-design-system

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

FAQPage Schema
How do I create a design token system for a website?

Start with a compact token set covering color, typography, spacing, radius, shadow, layout widths, and motion. Name tokens by purpose rather than appearance, such as --color-action-primary instead of raw values, and use semantic tokens in components so the system can evolve without rewriting CSS.

How to document reusable UI components before scaling them?

Write a component contract defining purpose, semantic structure, variants, states, content rules, responsive behavior, and accessibility requirements. A component without a state model covering loading, empty, error, and success cases is not production-ready.

What is the difference between base tokens and semantic tokens?

Base tokens hold raw values like --color-blue-600 or --space-16, while semantic tokens like --color-action-primary express intent. Components should reference semantic tokens so themes or brands can change without rewriting component CSS.

When should I split a component into separate components?

Split when variants solve different jobs, markup diverges significantly, content models are incompatible, or accessibility behavior differs enough to need a separate contract. Do not split over minor styling differences, which are usually variant or token concerns.

Should I fix page-specific CSS or update the design system first?

Prefer fixing system primitives before patching page-specific CSS. If the same fix appears on multiple pages, it belongs in tokens or component contracts; only truly one-off fixes that cannot be generalized should stay local to a page.