skillshare-ui-website-style

Standardize design tokens and components across UI and website frontends.

302|22|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/JetBrains/skills --skill skillshare-ui-website-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillshare-ui-website-style
Source: https://github.com/JetBrains/skills/tree/main/ui-website-style
Command: npx skills add https://github.com/JetBrains/skills --skill skillshare-ui-website-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skillshare UI/Website design system standardizes visuals and interaction patterns across both the dashboard UI (ui/) and the public website (website/), reducing drift and speeding up development.

Core Features & Use Cases

  • Shared design tokens for color, typography, spacing, borders, and radii across ui/ and website/.
  • Reusable component guidelines and API expectations to ensure cohesive patterns and accessible experiences.
  • Guidance for two distinct design contexts (UI dashboard and marketing website) with a clear handoff between designers and engineers.

Quick Start

Apply the Skillshare design system to a UI page or website component to enforce consistency.

Frequently Asked Questions about skillshare-ui-website-style

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

FAQPage Schema
How do I standardize design tokens across a UI dashboard and marketing website?

You can standardize design tokens across a UI dashboard and marketing website by applying a unified design system that shares color, typography, spacing, and border tokens across both frontend projects to reduce visual drift.

What is the best way to enforce accessibility and visual consistency in frontend components?

The best way to enforce accessibility and visual consistency is by using reusable component guidelines and API expectations governed by a shared design system, ensuring cohesive patterns across UI pages and website components.

How do I validate design system usage in ui/ and website/ directories?

You validate design system usage in ui/ and website/ directories by requiring explicit front-matter metadata, token references, and companion STYLE_GUIDE guidelines to ensure correct implementation.

Do I need a STYLE_GUIDE to apply design system tokens to my website components?

Yes, you need a companion STYLE_GUIDE to apply design system tokens, as it provides the validation guidelines required to ensure correct token governance and usage across your website components.

Can I use this design system for both marketing website pages and internal UI tools?

Yes, you can use this design system for both marketing website pages and internal UI tools, as it specifically provides guidance for two distinct design contexts with a clear handoff between designers and engineers.

Why does my frontend UI experience visual drift between the dashboard and the website?

Your frontend UI experiences visual drift between the dashboard and website when shared design tokens for typography, spacing, and radii are not standardized across both project directories.