design-guide

Centralizes Sprint UI design guidelines for consistent frontend components.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/gancim/sprint --skill design-guide-gancim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-guide
Source: https://github.com/gancim/sprint/tree/main/.claude/skills/design-guide
Command: npx skills add https://github.com/gancim/sprint --skill design-guide-gancim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design tokens, typography, status/priority systems, composition patterns, and the /design-guide showcase page. Always use this skill alongside the frontend-design skill (for visual quality) and the web-design-guidelines skill (for web best practices).

Core Features & Use Cases

  • Design tokens, typography, status/priority systems
  • Composition patterns and a /design-guide showcase page
  • Guidance for creating/updating UI components, tokens, and documentation

Quick Start

Use design-guide when starting any UI component work to align with tokens, patterns, and conventions.

Frequently Asked Questions about design-guide

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

FAQPage Schema
How do I maintain consistent frontend design when creating new UI components?

Maintain consistent frontend design by centralizing UI guidelines, design tokens, and typography rules. Apply these standardized patterns when creating new UI components, updating existing designs, or documenting status and priority systems across your application.

What are design tokens and how do they standardize UI styling?

Design tokens are centralized variables that store UI styling decisions like typography and status systems. They standardize UI styling by providing a single source of truth, ensuring visual consistency across all frontend components and pages during development.

How do I document UI composition patterns for a frontend design system?

Document UI composition patterns by creating a living design-guide showcase page. This page serves as a reference for component creation, design tokens, typography rules, and status systems, providing links to assets and ensuring frontend conventions are accessible.

When do I need a design system guide for frontend component work?

You need a design system guide when starting any UI component work, adding pages, or modifying frontend features. It is required to align new and existing components with established design tokens, typography conventions, and composition patterns.

Does this design system guide work alongside general web design guidelines?

Yes, this design system guide works alongside general web design guidelines. It should be used together with frontend visual quality skills and web best practices skills to ensure both consistent UI language and standard web conventions are met.

What's the best way to update existing frontend designs without breaking visual consistency?

The best way to update existing designs is applying centralized design tokens and typography rules before modifying components. Using a living design-guide page as reference ensures all updates adhere to established status, priority, and composition patterns without breaking visual consistency.