design-guide

Align Paperclip frontend UI components with the established design system.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of inconsistent, non-conforming Paperclip frontend components that break the app's professional dense, keyboard-first, dark-themed control plane design, eliminating rework and ensuring all UI work aligns with established conventions.

Core Features & Use Cases

  • Complete Design System Rules: Covers all core conventions including design tokens (colors, typography, radius), status/priority systems, component hierarchy, and layout structure for Paperclip's UI.
  • Component Development Guidance: Provides clear rules for when to create new reusable components, how to follow composition patterns like entity rows and metric card grids, and how to avoid common styling mistakes.
  • Use Case: When adding a new agent management dashboard page, use this Skill to ensure all status badges, priority icons, and property panels match the existing design language, and update the /design-guide showcase page with the new components as required.

Quick Start

Use the design-guide skill to build a new reusable status filter component for the issues page that follows Paperclip's component hierarchy and composition patterns.

Frequently Asked Questions about design-guide

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

FAQPage Schema
How do I ensure new React components match an existing dark-themed design system?

To ensure new React components match an existing dark-themed design system, apply established design tokens, component hierarchy rules, and composition patterns. This enforces visual consistency and eliminates rework across frontend interfaces.

What are design tokens and how do they work in a component hierarchy?

Design tokens in a component hierarchy are centralized styling variables for colors, typography, and radius. They work by providing a single source of truth, ensuring UI components maintain consistent visual language across the application.

When should I create new reusable UI components for my frontend?

Create new reusable UI components when existing elements cannot satisfy specific layout requirements without breaking conventions. Follow established composition patterns, such as entity rows and metric card grids, to avoid styling mistakes and maintain structure.

Does this design system guidance work for keyboard-first control plane layouts?

Yes, this design system guidance works for keyboard-first control plane layouts. It provides specific conventions for dense, dark-themed interfaces, ensuring all new UI components and page features adhere to the established professional control plane design.

How do I update a design showcase page after adding new UI components?

Update a design showcase page by integrating the newly created frontend components into the established display structure. This ensures all team members can review the visual elements and verify adherence to the application's design tokens and hierarchy.