design

Enforce a cohesive Tailwind-based design system across Svelte client components.

1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/vigneshksaithal/sudoku --skill design-vigneshksaithal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/vigneshksaithal/sudoku/tree/main/.agents/skills/design
Command: npx skills add https://github.com/vigneshksaithal/sudoku --skill design-vigneshksaithal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual drift in the Svelte client UI leads to inconsistent user experiences and increased cognitive load. This Skill defines a shared design system to ensure cohesive visuals, spacing, and typography across components.

Core Features & Use Cases

  • Establish visual primitives: color tokens, typography scales, spacing rules, and component tokens to maintain consistency.
  • Tailwind-based implementation: mandates Tailwind utility classes, no custom CSS blocks, and predictable styling.
  • Review & modify UI: used during design reviews and when creating or updating elements like buttons, inputs, and cards to align with the design system.

Quick Start

Apply the design system to the Svelte UI by auditing components and updating styles to match the guidelines.

Frequently Asked Questions about design

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

FAQPage Schema
How do I fix design drift and inconsistent UI components in Svelte?

Fix design drift in Svelte by applying a shared design system that enforces cohesive colors, typography scales, and spacing rules. This ensures consistent visual primitives and predictable styling across all UI components.

Can I use custom CSS blocks with Tailwind for UI components?

No, custom CSS blocks are not used with Tailwind for UI components. The design system mandates Tailwind utility classes exclusively to ensure predictable styling, mobile-first sizing, and a modular, code-friendly approach.

What's the best way to ensure accessibility when building buttons and inputs?

Ensure accessibility for buttons and inputs by applying a design system that enforces accessibility considerations alongside consistent color tokens and typography. This approach standardizes component visuals while maintaining strict accessibility compliance.

How do I establish visual primitives like color tokens for consistent UI?

Establish visual primitives like color tokens by defining a shared design system that includes typography scales and spacing rules. This creates a cohesive foundation for maintaining consistent UI across Svelte components.

Does this UI design approach support mobile-first sizing?

Yes, this UI design approach supports mobile-first sizing. The design system enforces Tailwind-based implementation with mobile-first sizing rules and a modular, code-friendly approach to ensure components render correctly across all devices.

How do I review and update cards and surfaces to align with a design system?

Review and update cards and surfaces by auditing existing components and updating their styles to match design system guidelines. This aligns colors, typography, and spacing with established Tailwind utility classes.