zest-component-creation-web

Create Zest design system components with token-based styling and accessibility standards.

3|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/guicheffer/devorch-cli --skill zest-component-creation-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zest-component-creation-web
Source: https://github.com/guicheffer/devorch-cli/tree/main/templates/skills/ui-design-system-web/zest-component-creation
Command: npx skills add https://github.com/guicheffer/devorch-cli --skill zest-component-creation-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new Zest design system components for web applications, ensuring consistency, reusability, and adherence to best practices.

Core Features & Use Cases

  • Component Scaffolding: Provides a structured approach to creating new components within the packages/zest/src/ directory.
  • Token-Based Styling: Emphasizes the use of BoxWithNewTokens and design tokens for styling, promoting theme consistency.
  • Accessibility Focus: Mandates the implementation of semantic HTML, ARIA attributes, and keyboard navigation.
  • Use Case: When a new UI element like a "Notification Banner" is designed in Figma, this Skill guides the developer through creating the necessary TypeScript files (.tsx, types.ts, variants.ts, styles.ts), implementing it with BoxWithNewTokens, and ensuring it's accessible and testable.

Quick Start

Use the zest-component-creation-web skill to create a new Zest component named 'UserProfileCard' following the provided guidelines.

Frequently Asked Questions about zest-component-creation-web

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

FAQPage Schema
How do I create web UI components with token-based styling in React?

To create web UI components with token-based styling in React, use a structured approach that scaffolds TypeScript files like .tsx and styles.ts, applying BoxWithNewTokens to ensure theme consistency and reusability across your design system.

What's the best way to structure a React component for a design system?

The best way to structure a React component for a design system is to separate concerns into distinct TypeScript files: .tsx for logic, types.ts for definitions, variants.ts for variations, and styles.ts for token-based styling.

How do I ensure my TypeScript web components meet accessibility standards?

To ensure TypeScript web components meet accessibility standards, mandate the implementation of semantic HTML, appropriate ARIA attributes, and full keyboard navigation support during the component scaffolding and variant definition process.

Can I use design tokens for styling variants in React UI components?

Yes, you can use design tokens for styling variants in React UI components by leveraging BoxWithNewTokens within your styles.ts file, which promotes theme consistency and supports dynamic variant definition across the application.

What files do I need to scaffold for a new React design system component?

To scaffold a new React design system component, you need to create specific TypeScript files including .tsx for the main component, types.ts for definitions, variants.ts for variations, and styles.ts for token-based styling rules.

Why does my design system component need separate TypeScript files for variants and styles?

Your design system component needs separate TypeScript files for variants and styles to enforce a structured file organization, ensuring that token-based styling and component variations remain reusable, maintainable, and distinct from core logic.