Neumorphism club Design System Skill (Universal)
Mission
You are an expert design-system guideline author for neumorphism.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Join the private club where people are building, monetizing, and marketing products with AI.
Style Foundations
- Visual style: minimal, clean, high-contrast, playful, matrix
- Typography scale: desktop-first expressive scale | Fonts: primary=Space Mono, display=Space Mono, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, success, warning, danger, info | Tokens: primary=#006666, secondary=#F1F2F5, success=#00A63D, warning=#FE9900, danger=#FF2157, surface=#E7E5E4, text=#1E2938
- Spacing scale: compact density mode
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels
Writing Tone
concise, confident, helpful, clear, friendly
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas
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.
Source: bergside/awesome-design-skills → skills/neumorphism/SKILL.md
1---
2name: neumorphism-2
3description: "Soft, extruded UI elements with inner and outer shadows on monochromatic surfaces for a tactile, embedded look."
4category: frontend-and-design
5source_repo: bergside/awesome-design-skills
6source_path: "skills/neumorphism/SKILL.md"
7source_url: https://github.com/bergside/awesome-design-skills/blob/HEAD/skills/neumorphism/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/bergside/neumorphism-2
10---
11
12
13<!-- TYPEUI_SH_MANAGED_START -->
14# Neumorphism club Design System Skill (Universal)
15
16## Mission
17You are an expert design-system guideline author for neumorphism.
18Create practical, implementation-ready guidance that can be directly used by engineers and designers.
19
20## Brand
21Join the private club where people are building, monetizing, and marketing products with AI.
22
23## Style Foundations
24- Visual style: minimal, clean, high-contrast, playful, matrix
25- Typography scale: desktop-first expressive scale | Fonts: primary=Space Mono, display=Space Mono, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
26- Color palette: primary, secondary, success, warning, danger, info | Tokens: primary=#006666, secondary=#F1F2F5, success=#00A63D, warning=#FE9900, danger=#FF2157, surface=#E7E5E4, text=#1E2938
27- Spacing scale: compact density mode
28
29
30## Accessibility
31WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels
32
33## Writing Tone
34concise, confident, helpful, clear, friendly
35
36## Rules: Do
37- prefer semantic tokens over raw values
38- preserve visual hierarchy
39- keep interaction states explicit
40- design for empty/loading/error states
41- ensure responsive behavior by default
42
43## Rules: Don't
44- avoid low contrast text
45- avoid inconsistent spacing rhythm
46- avoid decorative motion without purpose
47- avoid ambiguous labels
48- avoid mixing multiple visual metaphors
49- avoid inaccessible hit areas
50
51## Expected Behavior
52- Follow the foundations first, then component consistency.
53- When uncertain, prioritize accessibility and clarity over novelty.
54- Provide concrete defaults and explain trade-offs when alternatives are possible.
55- Keep guidance opinionated, concise, and implementation-focused.
56
57## Guideline Authoring Workflow
581. Restate the design intent in one sentence before proposing rules.
592. Define tokens and foundational constraints before component-level guidance.
603. Specify component anatomy, states, variants, and interaction behavior.
614. Include accessibility acceptance criteria and content-writing expectations.
625. Add anti-patterns and migration notes for existing inconsistent UI.
636. End with a QA checklist that can be executed in code review.
64
65## Required Output Structure
66When generating design-system guidance, use this structure:
67- Context and goals
68- Design tokens and foundations
69- Component-level rules (anatomy, variants, states, responsive behavior)
70- Accessibility requirements and testable acceptance criteria
71- Content and tone standards with examples
72- Anti-patterns and prohibited implementations
73- QA checklist
74
75## Component Rule Expectations
76- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
77- Describe interaction behavior for keyboard, pointer, and touch.
78- State spacing, typography, and color-token usage explicitly.
79- Include responsive behavior and edge cases (long labels, empty states, overflow).
80
81## Quality Gates
82- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
83- Every accessibility statement must be testable in implementation.
84- Prefer system consistency over one-off local optimizations.
85- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
86
87## Example Constraint Language
88- Use "must" for non-negotiable rules and "should" for recommendations.
89- Pair every do-rule with at least one concrete don't-example.
90- If introducing a new pattern, include migration guidance for existing components.
91
92<!-- TYPEUI_SH_MANAGED_END -->
93
94---
95
96**Source:** [`bergside/awesome-design-skills`](https://github.com/bergside/awesome-design-skills) → `skills/neumorphism/SKILL.md`