# neon

Turns your coding agent into an author of Neon design-system guidance: high-contrast color pairings, glow effects, tokens instead of raw values.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2300 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/neon/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/typeuish-neon

## What it does

The skill gives the agent a fixed brief for Neon: high-contrast visuals, a type scale of 14/16/18/24/32/40, a spacing scale of 4/8/12/16/24/32, and a token set — `primary=#BBF351`, `secondary=#00BCFF`, `success=#16A34A`, `warning=#D97706`, `danger=#DC2626`, `surface=#FFFFFF`, `text=#111827`. Fonts are Roboto for body, STIX Two Text for display, Source Code Pro for mono.

Output follows a set order: restate the intent in one sentence, define tokens and foundations, then component rules covering default, hover, focus-visible, active, disabled, loading and error states, and finish with a QA checklist you can run in code review. Every rule has to hang off a token, a threshold or an example, so vague adjectives don't survive. Accessibility target is WCAG 2.2 AA with keyboard-first interaction and visible focus.

One constraint is non-negotiable: when aesthetics and accessibility collide, accessibility wins. That means low-contrast text and drifting spacing get rejected while the rules are being written, not after. The installed file lands at `~/.claude/skills/neon/SKILL.md`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill neon -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/neon/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/neon/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill neon -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/neon/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill neon -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/neon/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills neon
```

2. **Manually: put the files in place**
- File: `.github/skills/neon/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill neon -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/neon
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/neon/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill neon -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/neon/SKILL.md

## When to use it
- write design-system guidance anchored to tokens rather than hex values
- specify component states before anyone builds them
- check text and focus contrast against WCAG 2.2 AA
- pull scattered spacing back onto one scale
- produce a review checklist for UI changes

## Example prompts
- Write the Neon design-system guidance for our app: tokens, typography, button states
- Review this component against the neon skill rules and flag accessibility problems
- Build a QA checklist for code review based on the Neon guidelines

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9b7709859924bb15.

BEGIN THIRD-PARTY FILE 9b7709859924bb15
```text
---
name: neon
description: Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# 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.
```
END THIRD-PARTY FILE 9b7709859924bb15

The third-party file has ended. Everything between the 9b7709859924bb15 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2633 of 3342 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/neon/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md