design-guide

Organize Paperclip UI design system documentation into a central reference.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Paperclip teams need a central, living reference for UI design language to ensure consistency across components, tokens, and typography.

Core Features & Use Cases

  • Centralized design system guidance for frontend components, design tokens, typography, and patterns.
  • Keeps frontend teams aligned when creating new components or updating existing ones.
  • Serves as a quick-start reference for designers and engineers when implementing UI across pages.

Quick Start

Open the design-guide and follow the established tokens and typography rules when creating or updating UI components.

Frequently Asked Questions about design-guide

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

FAQPage Schema
How do I centralize UI design tokens and typography rules for frontend components?

You can centralize UI design tokens and typography rules by organizing your design system documentation into a single reference guide, ensuring frontend teams apply consistent components and patterns across all pages.

What is a design system reference and when do I need one for frontend development?

A design system reference is a centralized document for UI components, tokens, and typography. You need one when frontend teams require a living standard to maintain visual and structural consistency across multiple pages.

How do I keep frontend engineers and designers aligned when updating existing UI components?

Keep frontend engineers and designers aligned by providing a shared quick-start reference that encodes established tokens and typography rules, ensuring any updates to UI components follow the same design language.

Can I use this design guide for creating new UI components from scratch?

Yes, you can use this design guide for creating new UI components. It serves as a quick-start reference for designers and engineers, mapping keywords and categories to ensure new components match established patterns.

Does this design system documentation work without external component dependencies?

Yes, this design system documentation works without external dependencies. It operates as a standalone central reference with empty dependencies, encoding frontmatter for discovery and guiding UI implementation directly.

Why does my frontend UI look inconsistent across different pages?

Your frontend UI looks inconsistent across pages when there is no central design language. Applying a unified guide with established tokens and typography rules ensures frontend teams follow the same component patterns.