Agent skill

Design Guide

by paperclipai in paperclipai/paperclip

Paperclip UI design system guide for building consistent, reusable frontend components.

MITAuto-check passedFrontend & Design

Install Design Guide

skills CLI
$ npx skills add paperclipai/paperclip --skill design-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install paperclipai/paperclip design-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/design-guide .claude/skills/design-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
design-guide
GitHub stars
99k
Used in
1 other repo
Token cost
~3.1k tokens
SKILL.md length
1,127 words
Files
2 (incl. references)
Skills in repo
60
Repo updated
First seen
Licence
MIT

At a glance

Paperclip UI design system guide for building consistent, reusable frontend components.

  • Works in 12 steps: Design Principles → Tech Stack → Design Tokens → …
  • Creating new UI components
  • SKILL.md covers 1. Design Principles, 2. Tech Stack, 3. Design Tokens and 4. Typography Scale, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Design Guide is an agent skill from paperclipai/paperclip. Paperclip 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…

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/component-index.md`).

It sits in Frontend & Design, covering Design tokens, Design patterns and Typography. The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.

When your agent uses it

  • Creating new UI components
  • Modifying existing ones
  • Features to the frontend
  • Styling UI elements

Example prompts

  • “/design-guide”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Design Principles
  2. Tech Stack
  3. Design Tokens
  4. Typography Scale
  5. Status & Priority Systems
  6. Component Hierarchy
  7. Composition Patterns
  8. Interactive Patterns
  9. Layout System
  10. The /design-guide Page
  11. Component Index
  12. File Conventions

What it can do on your machine

Read from SKILL.md and the folder at commit b9750b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Design Guide loads about 3.1k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 1,127 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~143
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from paperclipai/paperclip at commit b9750b1, republished under its MIT licence (© paperclipai). 1,127 words, ~3,074 tokens.

Download SKILL.mdSave it as .claude/skills/design-guide/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
design-guide
description
Paperclip 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).

Paperclip Design Guide

Paperclip's UI is a professional-grade control plane — dense, keyboard-driven, dark-themed by default. Every pixel earns its place.

Always use with: frontend-design (visual polish) and web-design-guidelines (web best practices).


1. Design Principles

  • Dense but scannable. Maximum information without clicks to reveal. Whitespace separates, not pads.
  • Keyboard-first. Global shortcuts (Cmd+K, C, [, ]). Power users rarely touch the mouse.
  • Contextual, not modal. Inline editing over dialog boxes. Dropdowns over page navigations.
  • Dark theme default. Neutral grays (OKLCH), not pure black. Accent colors for status/priority only. Text is the primary visual element.
  • Component-driven. Prefer reusable components that capture style conventions. Build at the right abstraction — not too granular, not too monolithic.

2. Tech Stack

  • React 19 + TypeScript + Vite
  • Tailwind CSS v4 with CSS variables (OKLCH color space)
  • shadcn/ui (new-york style, neutral base, CSS variables enabled)
  • Radix UI primitives (accessibility, focus management)
  • Lucide React icons (16px nav, 14px inline)
  • class-variance-authority (CVA) for component variants
  • clsx + tailwind-merge via cn() utility

Config: ui/components.json (aliases: @/components, @/components/ui, @/lib, @/hooks)


3. Design Tokens

All tokens defined as CSS variables in ui/src/index.css. Both light and dark themes use OKLCH.

Colors

Use semantic token names, never raw color values:

TokenUsage
--background / --foregroundPage background and primary text
--card / --card-foregroundCard surfaces
--primary / --primary-foregroundPrimary actions, emphasis
--secondary / --secondary-foregroundSecondary surfaces
--muted / --muted-foregroundSubdued text, labels
--accent / --accent-foregroundHover states, active nav items
--destructiveDestructive actions
--borderAll borders
--ringFocus rings
--sidebar-*Sidebar-specific variants
--chart-1 through --chart-5Data visualization
Radius

Single --radius variable (0.625rem) with derived sizes:

  • rounded-sm — small inputs, pills
  • rounded-md — buttons, inputs, small components
  • rounded-lg — cards, dialogs
  • rounded-xl — card containers, large components
  • rounded-full — badges, avatars, status dots
Shadows

Minimal shadows: shadow-xs (outline buttons), shadow-sm (cards). No heavy shadows.


4. Typography Scale

Use these exact patterns — do not invent new ones:

PatternClassesUsage
Page titletext-xl font-boldTop of pages
Section titletext-lg font-semiboldMajor sections
Section headingtext-sm font-semibold text-muted-foreground uppercase tracking-wideSection headers in design guide, sidebar
Card titletext-sm font-medium or text-sm font-semiboldCard headers, list item titles
Bodytext-smDefault body text
Mutedtext-sm text-muted-foregroundDescriptions, secondary text
Tiny labeltext-xs text-muted-foregroundMetadata, timestamps, property labels
Mono identifiertext-xs font-mono text-muted-foregroundIssue keys (PAP-001), CSS vars
Large stattext-2xl font-boldDashboard metric values
Code/logfont-mono text-xsLog output, code snippets

5. Status & Priority Systems

Status Colors (consistent across all entities)

Defined in StatusBadge.tsx and StatusIcon.tsx:

StatusColorEntity types
active, achieved, completed, succeeded, approved, doneGreen shadesAgents, goals, issues, approvals
runningCyanAgents
pausedOrangeAgents
idle, pendingYellowAgents, approvals
failed, error, rejected, blockedRed shadesRuns, agents, approvals, issues
archived, planned, backlog, cancelledNeutral grayVarious
todoBlueIssues
in_progressIndigoIssues
in_reviewVioletIssues
Priority Icons

Defined in PriorityIcon.tsx: critical (red/AlertTriangle), high (orange/ArrowUp), medium (yellow/Minus), low (blue/ArrowDown).

Agent Status Dots

Inline colored dots: running (cyan, animate-pulse), active (green), paused (yellow), error (red), offline (neutral).


6. Component Hierarchy

Three tiers:

  1. shadcn/ui primitives (ui/src/components/ui/) — Button, Card, Input, Badge, Dialog, Tabs, etc. Do not modify these directly; extend via composition.
  2. Custom composites (ui/src/components/) — StatusBadge, EntityRow, MetricCard, etc. These capture Paperclip-specific design language.
  3. Page components (ui/src/pages/) — Compose primitives and composites into full views.

See references/component-index.md for the complete component inventory with usage guidance.

When to Create a New Component

Create a reusable component when:

  • The same visual pattern appears in 2+ places
  • The pattern has interactive behavior (status changing, inline editing)
  • The pattern encodes domain logic (status colors, priority icons)

Do NOT create a component for:

  • One-off layouts specific to a single page
  • Simple className combinations (use Tailwind directly)
  • Thin wrappers that add no semantic value

7. Composition Patterns

These patterns describe how components work together. They may not be their own component, but they must be used consistently across the app.

Entity Row with Status + Priority

The standard list item for issues and similar entities:

tsx
<EntityRow
  leading={<><StatusIcon status="in_progress" /><PriorityIcon priority="high" /></>}
  identifier="PAP-001"
  title="Implement authentication flow"
  subtitle="Assigned to Agent Alpha"
  trailing={<StatusBadge status="in_progress" />}
  onClick={() => {}}
/>

Leading slot always: StatusIcon first, then PriorityIcon. Trailing slot: StatusBadge or timestamp.

Grouped List

Issues grouped by status header + entity rows:

tsx
<div className="flex items-center gap-2 px-4 py-2 bg-muted/50 rounded-t-md">
  <StatusIcon status="in_progress" />
  <span className="text-sm font-medium">In Progress</span>
  <span className="text-xs text-muted-foreground ml-1">2</span>
</div>
<div className="border border-border rounded-b-md">
  <EntityRow ... />
  <EntityRow ... />
</div>
Property Row

Key-value pairs in properties panels:

tsx
<div className="flex items-center justify-between py-1.5">
  <span className="text-xs text-muted-foreground">Status</span>
  <StatusBadge status="active" />
</div>

Label is always text-xs text-muted-foreground, value on the right. Wrap in a container with space-y-1.

Show full SKILL.md (447 more words)Show less
Metric Card Grid

Dashboard metrics in a responsive grid:

tsx
<div className="grid md:grid-cols-2 xl:grid-cols-4 gap-4">
  <MetricCard icon={Bot} value={12} label="Active Agents" description="+3 this week" />
  ...
</div>
Progress Bar (Budget)

Color by threshold: green (<60%), yellow (60-85%), red (>85%):

tsx
<div className="w-full h-2 bg-muted rounded-full overflow-hidden">
  <div className="h-full rounded-full bg-green-400" style={{ width: `${pct}%` }} />
</div>
Comment Thread

Author header (name + timestamp) then body, in bordered cards with space-y-3. Add comment textarea + button below.

Cost Table

Standard <table> with text-xs, header row with bg-accent/20, font-mono for numeric values.

Log Viewer

bg-neutral-950 rounded-lg p-3 font-mono text-xs container. Color lines by level: default (foreground), WARN (yellow-400), ERROR (red-400), SYS (blue-300). Include live indicator dot when streaming.


8. Interactive Patterns

Hover States
  • Entity rows: hover:bg-accent/50
  • Nav items: hover:bg-accent/50 hover:text-accent-foreground
  • Active nav: bg-accent text-accent-foreground
Focus

focus-visible:ring-ring focus-visible:ring-[3px] — standard Tailwind focus-visible ring.

Disabled

disabled:opacity-50 disabled:pointer-events-none

Inline Editing

Use InlineEditor component — click text to edit, Enter saves, Escape cancels.

Popover Selectors

StatusIcon and PriorityIcon use Radix Popover for inline selection. Follow this pattern for any clickable property that opens a picker.


9. Layout System

Three-zone layout defined in Layout.tsx:

┌──────────┬──────────────────────────────┬──────────────────────┐
│ Sidebar  │  Breadcrumb bar              │                      │
│ (w-60)   ├──────────────────────────────┤  Properties panel    │
│          │  Main content (flex-1)       │  (w-80, optional)    │
└──────────┴──────────────────────────────┴──────────────────────┘
  • Sidebar: w-60, collapsible, contains CompanySwitcher + SidebarSections
  • Properties panel: w-80, shown on detail views, hidden on lists
  • Main content: scrollable, flex-1

10. The /design-guide Page

Location: ui/src/pages/DesignGuide.tsx Route: /design-guide

This is the living showcase of every component and pattern in the app. It is the source of truth for how things look.

Rules
  1. When you add a new reusable component, you MUST add it to the design guide page. Show all variants, sizes, and states.
  2. When you modify an existing component's API, update its design guide section.
  3. When you add a new composition pattern, add a section demonstrating it.
  4. Follow the existing structure: <Section title="..."> wrapper with <SubSection> for grouping.
  5. Keep sections ordered logically: foundational (colors, typography) first, then primitives, then composites, then patterns.
Adding a New Section
tsx
<Section title="My New Component">
  <SubSection title="Variants">
    {/* Show all variants */}
  </SubSection>
  <SubSection title="Sizes">
    {/* Show all sizes */}
  </SubSection>
  <SubSection title="States">
    {/* Show interactive/disabled states */}
  </SubSection>
</Section>

11. Component Index

See references/component-index.md for the full component inventory.

When you create a new reusable component:

  1. Add it to the component index reference file
  2. Add it to the /design-guide page
  3. Follow existing naming and file conventions

12. File Conventions

  • shadcn primitives: ui/src/components/ui/{component}.tsx — lowercase, kebab-case
  • Custom components: ui/src/components/{ComponentName}.tsx — PascalCase
  • Pages: ui/src/pages/{PageName}.tsx — PascalCase
  • Utilities: ui/src/lib/{name}.ts
  • Hooks: ui/src/hooks/{useName}.ts
  • API modules: ui/src/api/{entity}.ts
  • Context providers: ui/src/context/{Name}Context.tsx

All components use cn() from @/lib/utils for className merging. All components use CVA for variant definitions when they have multiple visual variants.


13. Common Mistakes to Avoid

  • Using raw hex/rgb colors instead of CSS variable tokens
  • Creating ad-hoc typography styles instead of using the established scale
  • Hardcoding status colors instead of using StatusBadge/StatusIcon
  • Building one-off styled elements when a reusable component exists
  • Adding components without updating the design guide page
  • Using shadow-md or heavier — keep shadows minimal (xs, sm only)
  • Using rounded-2xl or larger — max is rounded-xl (except rounded-full for pills)
  • Forgetting dark mode — always use semantic tokens, never hardcode light/dark values

© paperclipai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .claude/skills/design-guide of paperclipai/paperclip.

  • SKILL.md
  • references/component-index.md

Open the folder on GitHubat commit b9750b1

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in paperclipai/paperclip, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Design Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Design Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Design Guide this skillpaperclipai/paperclip99k1 repos~3.1kAutomated safety check: PassMIT
Design GuideLF-Decentralized-Trust-labs/gitmesh144—~3.1kAutomated safety check: PassApache-2.0
Ijfw DesignFerroxLabs/ijfw212—~2.2kAutomated safety check: PassMIT
Distinctive Frontend Design Builderirahardianto/awesome-agv157—~2.4kAutomated safety check: PassMIT
Frontend Blueprinttech-leads-club/agent-skills7k1 repos~5.3kAutomated safety check: PassCC-BY-4.0
Visual Design Foundationswshobson/agents40k2 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Design Guide

    LF-Decentralized-Trust-labs/gitmesh

    GitMesh Agents UI design system. An agent skill from LF-Decentralized-Trust-labs/gitmesh.

    144 GitHub stars~3.1k tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Ijfw Design

    FerroxLabs/ijfw

    A skill your agent uses when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience'…

    212 GitHub stars~2.2k tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Distinctive Frontend Design Builder

    irahardianto/awesome-agv

    Commits to one bold aesthetic direction, sets up a CSS token system for it, then builds the interface in Vue or plain HTML using those tokens.

    157 GitHub stars~2.4k tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed
  • Frontend Blueprint

    tech-leads-club/agent-skills

    AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code.

    7k GitHub starsUsed in 1 repo~5.3k tokens
    Frontend & DesignAuto-check passed
  • Apply typography, color theory, spacing systems, and iconography principles to create cohesive visual designs.

    40k GitHub starsUsed in 2 repos~1.8k tokens
    Frontend & DesignAuto-check passed
  • Theming Components

    ancoleman/ai-design-components

    Provides design token system and theming framework for consistent, customizable UI styling across all components.

    526 GitHub stars~2.3k tokensUpdated 10 mo ago
    Frontend & DesignAuto-check passed

More from paperclipai/paperclip

All 60 skills in this repo
  • Garden Inbox

    paperclipai/paperclip

    Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.

    99k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    99k GitHub stars~9.6k tokensUpdated today
    Auto-check passed
  • Paperclip

    paperclipai/paperclip

    A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…

    99k GitHub stars~17k tokensUpdated today
    Auto-check passed
  • Paperclip Page

    paperclipai/paperclip

    Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.

    99k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Paperclip Create Agent

    paperclipai/paperclip

    Create new agents in Paperclip with governance-aware hiring.

    99k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Wireframe

    paperclipai/paperclip

    Produce low-fidelity black-and-white UI wireframes as SVGs or viewer pages.

    99k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Questions about Design Guide

What does Design Guide do?

Paperclip UI design system guide for building consistent, reusable frontend components. Design Guide is an agent skill from paperclipai/paperclip. Paperclip UI design system guide for building consistent, reusable frontend components.

When should I use Design Guide?

Design Guide fits situations like: creating new UI components; modifying existing ones; features to the frontend; styling UI elements.

How do I install Design Guide in Claude Code?

Run `npx skills add paperclipai/paperclip --skill design-guide -a claude-code`. Or copy the skill folder (.claude/skills/design-guide in paperclipai/paperclip) into .claude/skills/design-guide in your project. Claude Code loads it when a task matches its description.

How do I install Design Guide in Codex?

Run `npx skills add paperclipai/paperclip --skill design-guide -a codex`. Or copy the skill folder (.claude/skills/design-guide in paperclipai/paperclip) into .agents/skills/design-guide in your project. Codex loads it when a task matches its description.

Can I use Design Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add paperclipai/paperclip --skill design-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-guide, .gemini/skills/design-guide, .github/skills/design-guide and .opencode/skills/design-guide in your project.

What does Design Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Design Guide is instructions for the agent only.

Does Design Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Design Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Design Guide use?

Design Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Design Guide use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Design Guide?

Skills that share tags, products or a category with Design Guide: Design Guide (LF-Decentralized-Trust-labs/gitmesh, 144 stars), Ijfw Design (FerroxLabs/ijfw, 212 stars), Distinctive Frontend Design Builder (irahardianto/awesome-agv, 157 stars) and Frontend Blueprint (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Design Guide?

paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 98,967 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 9, 2026.

Source: paperclipai/paperclip on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.