- Home
- Skills
- Cyangzhou
- 2 Project Yunshu
- Frontend Design System
frontend_design_system_skill
- JavaScript
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill cyangzhou/-2--project-yunshu- --skill frontend_design_system- SKILL.md436 B
Overview
This skill converts UI style requirements into production-grade frontend code, delivering a scalable design system that balances creativity with engineering rigor. It centralizes visual decisions into design tokens, enforces accessibility compliance, and ships ready-to-use components. The default implementation uses React, Tailwind CSS, and shadcn/ui as a pragmatic, developer-friendly stack.
How this skill works
I inspect your visual specifications, map colors, spacing, typography, and interaction patterns into a token system, then generate reusable React components styled with Tailwind utility classes. Components are organized, documented, and wired for theming and accessibility by default. The output includes token definitions, component code, examples, and basic tests to accelerate production adoption.
When to use it
- Creating a new product UI with consistent design language
- Consolidating scattered styles into a single token-driven system
- Migrating legacy CSS to a component-based architecture
- Ensuring accessibility compliance across a component library
- Rapidly prototyping creative UI concepts with production-ready code
Best practices
- Start with a minimal set of tokens (color, spacing, type) and iterate
- Keep components focused and composable to avoid duplication
- Embed accessibility attributes and keyboard behavior in primitives
- Version tokens and components to manage design evolution
- Document usage examples and visual regression tests for each component
Example use cases
- Ship a themeable component library for a multi-brand platform
- Replace ad-hoc CSS with token-driven Tailwind components
- Audit and remediate accessibility issues across UI primitives
- Deliver high-fidelity prototypes that convert to production code
- Implement dark mode and responsive token scales across products
FAQ
The default stack is React + Tailwind CSS + shadcn/ui, but token-first outputs can be adapted to other frameworks.
How are accessibility concerns handled?
Accessibility is baked into primitives: semantic markup, ARIA where needed, focus management, and automated checks in the CI pipeline.