neon
Skill0 starsChanged 2 months agoMITView on GitHub
Electric neon glow effects with high-contrast color pairings for bold, attention-grabbing interfaces.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- dafto1/skillstheir own version, first seen Nov 15, 2026
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- x77jh8gvrn-alt/staqd-skillstheir own version, first seen Oct 20, 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
Used with
Projects with it also use neon-auth, neon-postgres-branches and 3 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
- +2 more from jaakla
Other versions16 projects use a version of this.
Word for word · 1
- bergside/awesome-design-skills★ 2.9k100% same
Edited · 0
None found.
Wrote their own version · 15
- xai-org/plugin-marketplace★ 333same name
- neondatabase/agent-skills★ 113same name
- jaakla/openmapstack★ 78same name
- jaakla/openmapstack-skills★ 78same 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
- dafto1/skills★ 1same 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 repository81 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agenticSkill
- antSkill
- artisticSkill
- basicSkill
- bentoSkill
- boldSkill
- brandkitSkill
- brutalismSkill
- cafeSkill
- claudeSkill
- claymorphismSkill
- cleanSkill
- codexSkill
- colorfulSkill
- contemporarySkill
- corporateSkill
- cosmicSkill
- creativeSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- ditheredSkill
- doodleSkill
- dramaticSkill
- editorialSkill
- enterpriseSkill
- expressiveSkill
- fantasySkill
- fictionSkill
- flatSkill
- friendlySkill
- full-output-enforcementSkill
- futuristicSkill
- geometricSkill
- glassmorphismSkill
- gpt-tasteSkill
- gradientSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- immersiveSkill
- impeccableSkill
- industrial-brutalist-uiSkill
- levelsSkill
- lingoSkill
- materialSkill
- matrixSkill
- minimalist-uiSkill
- minimalSkill
- modernSkill
- monoSkill
- neobrutalismSkill
- neumorphismSkill
- pacmanSkill
- paperSkill
- perspectiveSkill
- powerSkill
- premiumSkill
- professionalSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 15 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
- Distinctive: line 33
prefer semantic tokens over raw values
- Distinctive: line 35
keep interaction states explicit
- Distinctive: line 38
avoid low contrast text
- Distinctive: line 39
avoid inconsistent spacing rhythm
- Distinctive: line 43
Follow the foundations first, then component consistency.
- Distinctive: line 44
When uncertain, prioritize accessibility and clarity over novelty.
- Distinctive: line 46
Keep guidance opinionated, concise, and implementation-focused.
- Distinctive: line 53
Add anti-patterns and migration notes for existing inconsistent UI.
- Distinctive: line 57
When generating design-system guidance, use this structure:
- Distinctive: line 73
No rule should depend on ambiguous adjectives alone.
- Distinctive: line 74
Every accessibility statement must be testable in implementation.
- Distinctive: line 75
Prefer system consistency over one-off local optimizations.
- Distinctive: line 79
Use "must" for non-negotiable rules and "should" for recommendations.
- Distinctive: line 81
If introducing a new pattern, include migration guidance for existing components.
“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
<!-- 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
- 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.
<!-- TYPEUI_SH_MANAGED_END -->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.

