Neon
Skill0 starsChanged 5 months agoMITView on GitHub
Use when building or styling a UI in the Neon aesthetic — A dark-mode-first system built on glowing borders, fluorescent accents, and high-contrast cyberpunk energy. For Claude Code, Cursor, and Codex.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- matheus-rib1108/meu-kit-claude-codetheir own version, first seen Oct 17, 2026
- neondatabase/agent-skillstheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- xai-org/plugin-marketplacetheir own version, first seen Oct 13, 2026
- AtharvaK-XD/Bedrocktheir own version, first seen Oct 13, 2026
Used with
Projects with it also use neon-auth, neon-postgres-branches and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jaaklaSkillneon-auth
Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, passkeys, MFA, trusted domains, invalid domain, and @neondatabase/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed Better Auth. A required plugin outside Managed support: self-managed Better Auth on a Neon Function or the existing app host. Also use for auth APIs in @neondatabase/neon-js.
Also in 5 projects that use this
xAISkillneon-postgres-branches
Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch" and "sensitive data testing".
Also in 4 projects that use this
jaaklaSkillneon-ai-gateway
One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include "call an LLM", "add AI to my app", "chat completion", "model routing", "LLM proxy/gateway", "one API for all models", "use Claude/GPT/Gemini", "AI SDK", "Mastra agent", "Neon AI Gateway", and "log/rate-limit AI calls".
Also in 4 projects that use this
bergsideSkillant
Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.
Also in 3 projects that use this
bergsideSkillartistic
High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.
Also in 3 projects that use this
- +2 more from jaakla
- +4 more from bergside
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- bergside/awesome-design-skills★ 2.9ksame name
- xai-org/plugin-marketplace★ 323same name
- neondatabase/agent-skills★ 111same name
- jaakla/openmapstack★ 76same name
- jaakla/openmapstack-skills★ 76same name
- G1Joshi/Agent-Skills★ 15same name
- iyashjayesh/tokenchit★ 14same name
- vercel-labs/hatchery★ 7same name
- AtharvaK-XD/Bedrock★ 3same name
- regisagnikpe2002-ai/omnipay-bj★ 2same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- BentoSkill
- ClaymorphismSkill
- DashboardSkill
- EditorialSkill
- GlassmorphismSkill
- MinimalSkill
- NeobrutalismSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Avoid thin weights, which shimmer and fade on dark backgrounds.
- Distinctive: line 47
Use a 12-column grid on an 8px base unit with moderate density — dashboards can be information-rich, but each panel keeps internal …
- Distinctive: line 71
Keep motion crisp — no soft bounce.
- Distinctive: line 76
Ensure accent-on-dark text and icons clear 4.5:1 — cyan and magenta both pass at these saturations on the near-black base.
- Distinctive: line 77
Never rely on glow alone to signal state.
- Distinctive: line 80
Keep glow bloom subtle enough not to reduce text contrast, and ensure interactive targets meet 44x44px.
- Very specific: line 95
Cursor: add the contents to a .cursor/rules/<name>.mdc file.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Neon
Neon is a dark-mode-first system that turns interfaces into glowing circuitry. Surfaces sit in near-black, and energy comes from luminous cyan and magenta edges, gradient text, and soft colored bloom.
It feels electric, nocturnal, and high-stakes. Reach for Neon when you want an interface to feel like a control panel from a brighter, faster future — gaming and esports, crypto and web3, music and nightlife, and anything that thrives after dark.
Design principles
- Dark always wins. The canvas is near-black; light is something you emit, never a background.
- Glow over shadow. Depth comes from colored box-shadow bloom, not gray drop shadows.
- Two charged accents. Cyan and magenta carry the system; purple bridges them in gradients.
- Restrained luminance. Glow is a spice — apply it to focal elements so everything doesn't scream.
- Technical typography. Mono numerals and tracked-out uppercase labels evoke a HUD.
- Texture sparingly. Faint grids and scanlines add atmosphere without noise.
Color
The base is a deep blue-black (#0A0A12) with surfaces lifting to #13131F and elevated panels to #1A1A2E. Text is a cool near-white (#E8E8FF) with muted lavender-gray (#8B8BA7) for secondary copy.
- Primary accent: electric cyan (
#00E5FF) — main actions, focus, key data. - Secondary accent: hot magenta (
#FF2E97) — highlights, featured states, destructive actions. - Bridge: purple (
#A855F7) — connects the two in gradients and glows. - Borders: a low-contrast
#26263Aby default, switching to a glowing accent on hover or focus.
Because the system is dark-native, "light mode" is intentionally not the home. If a light variant is required, use a charcoal #16161F rather than white, keeping the neon accents intact. Reserve pure saturated glow for interactive and focal elements only — let the near-black field do the resting.
Typography
Headings use a geometric, slightly technical sans with tight tracking for a confident, machined look; the most prominent headlines can carry a cyan-to-magenta gradient fill.
- Headlines: technical sans, 32-72px, -0.01em tracking, weight 600-700.
- Body: clean neutral sans, 16-18px, weight 400, for readability on dark.
- Numerals: monospace face — prices, stats, timers — for an instrument-like feel.
- Micro-labels: uppercase, +0.12em tracking, muted color, 11-13px.
Avoid thin weights, which shimmer and fade on dark backgrounds. Keep to regular (400), medium (500), and bold (700).
Layout & spacing
Use a 12-column grid on an 8px base unit with moderate density — dashboards can be information-rich, but each panel keeps internal breathing room. Container widths cap around 1280px.
Group related controls inside bordered panels with 20-24px internal padding. Let the near-black background show through as negative space between panels rather than filling everything. A faint 1px grid or dot texture at very low opacity can underlay the whole canvas for atmosphere.
Components
- Buttons: primary is a dark fill with a cyan outline and glow; hover intensifies the bloom and brightens the label. Destructive uses magenta glow.
- Inputs: dark surface, 1px
#26263Aborder, with the border and a soft cyan glow appearing on focus. - Cards:
#13131Fsurface, 8px radius, thin border that lights up on hover; featured cards get a persistent accent glow ring. - Navigation: a dark top bar or sidebar with an underline or left-bar glow marking the active item.
- Modals & overlays: centered dark panels with an accent-glow border over a heavily darkened, slightly blurred backdrop.
- Tables: dark rows separated by faint borders, mono numerals, and accent-colored status text instead of filled badges.
- Badges: pill outlines in cyan or magenta with a faint matching glow and uppercase tracked labels.
- Icons: line icons that carry a subtle glow when active or selected.
Motion
Motion is energetic but controlled — synthetic, not organic.
- Glows pulse gently on key metrics (a 2-3s ease-in-out loop at low amplitude).
- Hover states ramp glow intensity over 150ms ease-out; presses snap inward slightly (scale 0.98).
- Gradient text and borders can slowly drift their hue.
- Page transitions use quick 250ms fades with a faint upward slide.
Keep motion crisp — no soft bounce.
Accessibility
- Cool near-white text (
#E8E8FF) on the base (#0A0A12) exceeds 15:1 contrast. - Ensure accent-on-dark text and icons clear 4.5:1 — cyan and magenta both pass at these saturations on the near-black base.
- Never rely on glow alone to signal state; pair it with a border, icon, or label change.
- Focus states use a visible 2px accent ring plus glow, always present and never suppressed.
- Honor
prefers-reduced-motionby disabling pulsing glows and gradient drift, leaving static accents. - Keep glow bloom subtle enough not to reduce text contrast, and ensure interactive targets meet 44x44px.
Meets WCAG 2.2 AA.
Example prompt
Dashboard panel
Build a stats dashboard panel in the Neon style on a near-black background: dark cards with a thin cyan glowing border, large mono numbers, magenta delta indicators, and a subtle grid texture. Make the primary metric pulse with a faint cyan glow.
Install
Drop the folder into your agent's skills directory, or paste this file's contents into your prompt / rules file:
- Claude Code: copy
skills/<name>/SKILL.mdinto.claude/skills/<name>/SKILL.md(project) or~/.claude/skills/(personal). - Cursor: add the contents to a
.cursor/rules/<name>.mdcfile. - Codex / other agents: paste into your
AGENTS.mdor system prompt.
Part of staqd — a library of 67 design-system skills for Claude, Cursor & Codex. This repo holds the 8 free skills; the full library lives at staqd.ai/skills.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

