design-guide

Guides creation of consistent React UI components using Paperclip design tokens and patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building frontend features without a shared design language leads to inconsistent styling, ad-hoc typography, hardcoded colors, and duplicated one-off components. This Skill encodes the Paperclip UI design system so every new component, page, or feature follows the same tokens, typography scale, status colors, and composition patterns. ## Core Features & Use Cases - Design Tokens & Typography: Enforces semantic CSS variables (OKLCH), a fixed typography scale, radius and shadow rules for Tailwind CSS v4 with shadcn/ui. - Component Conventions: Defines the three-tier hierarchy (shadcn primitives, custom composites like StatusBadge and EntityRow, page components) plus rules for when to create reusable components. - Composition Patterns: Provides ready-made patterns for entity rows, grouped lists, property panels, metric cards, progress bars, log viewers, and the mandatory /design-guide showcase page. - Use Case: When adding a new issues list page, use this Skill to compose EntityRow with StatusIcon and PriorityIcon, apply the grouped-list pattern, and register the result on the /design-guide page. ## Quick Start Use the design-guide skill to create a new reusable UI component following the Paperclip design system and add it to the /design-guide page.

Frequently Asked Questions about design-guide

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

FAQPage Schema
How do I create a new UI component in a shadcn/ui design system?

Create reusable components only when a visual pattern appears in two or more places or encodes domain logic like status colors. Place custom components in ui/src/components/ using PascalCase, compose shadcn primitives rather than modifying them, and use CVA for variants with cn() for class merging.

How should I use design tokens with Tailwind CSS v4?

Use semantic CSS variable tokens like --background, --muted-foreground, and --border instead of raw hex or rgb values. Tokens are defined in OKLCH in ui/src/index.css for both light and dark themes, so components adapt automatically without hardcoded colors.

Does this design system support dark mode?

Yes, dark theme is the default and both themes use OKLCH CSS variables. Always reference semantic tokens rather than hardcoding light or dark values so components render correctly in either theme.

When should I not create a new reusable component?

Avoid creating components for one-off page-specific layouts, simple Tailwind className combinations, or thin wrappers with no semantic value. Use Tailwind directly for those cases to prevent abstraction bloat.

Why is my component styling inconsistent with the rest of the app?

Common causes include using raw colors instead of CSS variable tokens, inventing typography outside the established scale, hardcoding status colors instead of StatusBadge, or using shadows heavier than shadow-sm and radii larger than rounded-xl.