paper
bergside/awesome-design-skills
Paper-textured, print-inspired design system with minimal colors and clean typography.
What is paper?
Paper is a design-system skill for creating minimal, print-inspired interfaces with tactile surface qualities. Use it when authoring design guidelines, component specifications, and accessibility-first UI systems that prioritize clarity and semantic consistency.
- Generate design-system guidance with defined tokens, component anatomy, and interaction states
- Enforce WCAG 2.2 AA accessibility standards with keyboard-first interactions and visible focus states
- Specify typography scale (14/16/18/24/32/40px) with Roboto, Montserrat, and PT Mono fonts
- Define color palette with semantic tokens (primary, neutral, success, warning, danger)
- Create component rules covering default, hover, focus, active, disabled, loading, and error states
- Document anti-patterns, migration notes, and QA checklists for design consistency
How to install paper
npx skills add https://github.com/bergside/awesome-design-skills --skill paperHow to use paper
- 1.Install the skill using the provided npm command
- 2.Define your design intent and goals for the component or system you're documenting
- 3.Restate the design intent in one sentence before proposing rules
- 4.Define tokens and foundational constraints (typography, color, spacing) before component guidance
- 5.Specify component anatomy, required states (default, hover, focus, active, disabled, loading, error), and interaction behavior
- 6.Include WCAG 2.2 AA accessibility acceptance criteria and testable requirements
- 7.Document content and tone standards with concrete examples
- 8.List anti-patterns and prohibited implementations
Use cases
- Writing design-system documentation for a new product or redesign
- Establishing consistent component specifications across engineering and design teams
- Creating accessibility-compliant UI guidelines with testable acceptance criteria
- Defining responsive behavior and edge-case handling for form inputs, buttons, and navigation
- Authoring content and tone standards aligned with brand voice
- Design system authors and leads
- Product designers building component libraries
- Engineers implementing design specifications
- Design ops and governance roles
- Teams establishing accessibility standards
paper FAQ
Paper includes typography scale (14/16/18/24/32/40px), fonts (Roboto primary, Montserrat display, PT Mono mono), color tokens (primary #111111, secondary #8B5CF6, success #16A34A, warning #D97706, danger #DC2626, surface #FFFFFF, text #111827), and spacing scale (4/8/12/16/24/32px).
Yes, Paper requires WCAG 2.2 AA compliance, keyboard-first interactions, and visible focus states. All guidance must include testable accessibility acceptance criteria.
Paper expects you to define: default, hover, focus-visible, active, disabled, loading, and error states (as relevant to the component), with explicit spacing, typography, and color-token usage for each.
No; Paper prioritizes system consistency over local optimizations. Use semantic tokens first, and document any trade-offs or conflicts between aesthetics and accessibility before introducing alternatives.
Context and goals, design tokens and foundations, component-level rules, accessibility requirements, content and tone standards, anti-patterns, and a QA checklist for code review.
Full instructions (SKILL.md)
Source of truth, from bergside/awesome-design-skills.
name: paper description: Paper-textured, print-inspired design with minimal colors, clean serif/sans typography, and tactile surface qualities. license: MIT metadata: author: typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->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.
Related skills
More from bergside/awesome-design-skills and the wider catalog.
