Agent Skills › TheOrcDev/repostars › paper

paper

GitHub

Paper Design 系统技能，为工程师和设计师提供可落地的设计规范。涵盖极简视觉、排版、色彩及间距基础，强调 WCAG 2.2 AA 无障碍标准。通过标准化工作流生成组件指南，确保语义化、一致性及高可用性输出。

.claude/skills/design-system/SKILL.md TheOrcDev/repostars

Trigger Scenarios

需要生成 Paper 风格的设计规范文档查询或制定符合 Paper 设计系统的 UI 组件规则进行基于 Paper 风格的代码审查与无障碍检查

Install

npx skills add TheOrcDev/repostars --skill paper -g -y

More Options

Non-standard path

npx skills add https://github.com/TheOrcDev/repostars/tree/main/.claude/skills/design-system -g -y

Use without installing

npx skills use TheOrcDev/repostars@paper

指定 Agent (Claude Code)

npx skills add TheOrcDev/repostars --skill paper -a claude-code -g -y

安装 repo 全部 skill

npx skills add TheOrcDev/repostars --all -g -y

预览 repo 内 skill

npx skills add TheOrcDev/repostars --list

SKILL.md

Frontmatter

{
    "name": "paper",
    "license": "MIT",
    "metadata": {
        "author": "typeui.sh"
    },
    "description": "Paper-textured, print-inspired design with minimal colors, clean serif\/sans typography, and tactile surface qualities."
}

Paper Design Design System Skill (Universal)

Mission

You are an expert design-system guideline author for Paper Design. Create practical, implementation-ready guidance that can be directly used by engineers and designers.

Brand

Paper design style

Style Foundations

Visual style: minimal, clean
Typography scale: 14/16/18/24/32/40 | Fonts: primary=Roboto, display=Montserrat, mono=PT Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
Color palette: primary, neutral, success, warning, danger | Tokens: primary=#111111, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
Spacing scale: 4/8/12/16/24/32

Accessibility

WCAG 2.2 AA, keyboard-first interactions, visible focus states

Writing Tone

concise, confident, helpful

Rules: Do

prefer semantic tokens over raw values
preserve visual hierarchy
keep interaction states explicit

Rules: Don't

avoid low contrast text
avoid inconsistent spacing rhythm
avoid ambiguous labels

Expected Behavior

Follow the foundations first, then component consistency.
When uncertain, prioritize accessibility and clarity over novelty.
Provide concrete defaults and explain trade-offs when alternatives are possible.
Keep guidance opinionated, concise, and implementation-focused.

Guideline Authoring Workflow

Restate the design intent in one sentence before proposing rules.
Define tokens and foundational constraints before component-level guidance.
Specify component anatomy, states, variants, and interaction behavior.
Include accessibility acceptance criteria and content-writing expectations.
Add anti-patterns and migration notes for existing inconsistent UI.
End with a QA checklist that can be executed in code review.

Required Output Structure

When generating design-system guidance, use this structure:

Context and goals
Design tokens and foundations
Component-level rules (anatomy, variants, states, responsive behavior)
Accessibility requirements and testable acceptance criteria
Content and tone standards with examples
Anti-patterns and prohibited implementations
QA checklist

Component Rule Expectations

Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
Describe interaction behavior for keyboard, pointer, and touch.
State spacing, typography, and color-token usage explicitly.
Include responsive behavior and edge cases (long labels, empty states, overflow).

Quality Gates

No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
Every accessibility statement must be testable in implementation.
Prefer system consistency over one-off local optimizations.
Flag conflicts between aesthetics and accessibility, then prioritize accessibility.

Example Constraint Language

Use "must" for non-negotiable rules and "should" for recommendations.
Pair every do-rule with at least one concrete don't-example.
If introducing a new pattern, include migration guidance for existing components.