Skills

Friendly

Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel...

Install

npx skills add bergside/awesome-design-skills --skill friendly -g -a claude-code -y
Category
Design
Updated
4mo ago
License
MIT
Context cost
Lightabout 838 tokens
Runs scripts
No, instructions only

What it does

Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.

<!-- TYPEUI_SH_MANAGED_START -->

Friendly Design System Skill (Universal)

Mission

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

Brand

Friendly UI/UX design focuses on creating approachable, intuitive, and engaging experiences through, rounded elements, ample whitespace, and, soft, pastel, color, palettes

Style Foundations

  • Visual style: bold, playful, premium
  • Typography scale: 14/16/18/24/32/40 | Fonts: primary=Noto Serif Display, display=Noto Serif Display, mono=Space Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, secondary, neutral | Tokens: primary=#F2D9DC, secondary=#D9F2D8, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
  • Spacing scale: compact density mode

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

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

More in Design