← LeaderboardThe Skill Leaderboard

neon

Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.

Published by bergside ↗bergside/awesome-design-skills

Try your first task

Draft Neon card guidelines

Start a fresh conversation. Replace the highlighted placeholders.

Use the neon skill to draft concise design-system guidance for one interactive card in my interface. Apply the documented Neon typography, colors, and spacing; define the card's anatomy and relevant interaction states; address responsive behavior, long content, and overflow; and include testable WCAG 2.2 AA acceptance criteria. Interface context: [describe the interface and card content]. Interaction: [describe what selecting or activating the card does].

Required inputs

  • Interface context and card content
  • Expected card interaction

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

SKILL.md

name: neondescription: Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.license: MITmetadata:   author: typeui.sh

Neon Design System Skill (Universal)

Mission

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

Brand

Neon high contrast design

Style Foundations

  • Visual style: high-contrast
  • Typography scale: 14/16/18/24/32/40 | Fonts: primary=Roboto, display=STIX Two Text, mono=Source Code Pro | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, secondary | Tokens: primary=#BBF351, secondary=#00BCFF, 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

  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.

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.