You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers building consumer-facing SaaS products and web portals with React. They consume the component library as a foundation and layer their own brand on top. They care deeply about accessibility, predictability, and not fighting the library.
7
+
8
+
### Brand Personality
9
+
**Professional · Cozy · Warm · Clean**
10
+
11
+
The library should feel trustworthy and polished without being cold or sterile. Components should radiate quiet competence — approachable enough that adopters feel comfortable, structured enough that their apps feel credible.
12
+
13
+
### Aesthetic Direction
14
+
**Neutral & Adaptive** — the library stays out of the way.
15
+
16
+
Components use CSS custom properties throughout so adopters can retheme with minimal effort. The default palette (blue primary, light/dark surface tones) is a safe, professional baseline — not a statement. Every visual choice should be a sensible default, not a brand decision.
17
+
18
+
Anti-references: avoid anything flashy, opinionated, or hard to override — no gradient text, no neon dark-mode accents, no signature glassmorphism that would clash with adopters' own aesthetics.
19
+
20
+
### Design Principles
21
+
1.**Accessibility is non-negotiable** — every component ships WCAG 2.2 AA compliant by default. Keyboard navigation, focus indicators, ARIA semantics, and color contrast are baseline requirements, not enhancements.
22
+
2.**Tokens over hardcoded values** — all visual decisions (color, spacing, typography, radius, shadow) flow through CSS custom properties. Nothing is magic-numbered in component styles.
23
+
3.**Predictable over clever** — components behave exactly as developers expect. Consistent prop patterns, standard HTML semantics, and no surprising side effects.
24
+
4.**Progressive disclosure** — components expose simple APIs by default; power-user options (controlled state, callbacks, refs) are available but never required.
25
+
5.**Motion respects the user** — all animations honor `prefers-reduced-motion`. Transitions are functional (communicating state), never decorative.
Developers building consumer-facing SaaS products and web portals with React. They consume the component library as a foundation and layer their own brand on top. They care deeply about accessibility, predictability, and not fighting the library.
7
+
8
+
### Brand Personality
9
+
**Professional · Cozy · Warm · Clean**
10
+
11
+
The library should feel trustworthy and polished without being cold or sterile. Components should radiate quiet competence — approachable enough that adopters feel comfortable, structured enough that their apps feel credible.
12
+
13
+
### Aesthetic Direction
14
+
**Neutral & Adaptive** — the library stays out of the way.
15
+
16
+
Components use CSS custom properties throughout so adopters can retheme with minimal effort. The default palette (blue primary, light/dark surface tones) is a safe, professional baseline — not a statement. Every visual choice should be a sensible default, not a brand decision.
17
+
18
+
Anti-references: avoid anything flashy, opinionated, or hard to override — no gradient text, no neon dark-mode accents, no signature glassmorphism that would clash with adopters' own aesthetics.
19
+
20
+
### Design Principles
21
+
1.**Accessibility is non-negotiable** — every component ships WCAG 2.2 AA compliant by default. Keyboard navigation, focus indicators, ARIA semantics, and color contrast are baseline requirements, not enhancements.
22
+
2.**Tokens over hardcoded values** — all visual decisions (color, spacing, typography, radius, shadow) flow through CSS custom properties. Nothing is magic-numbered in component styles.
23
+
3.**Predictable over clever** — components behave exactly as developers expect. Consistent prop patterns, standard HTML semantics, and no surprising side effects.
24
+
4.**Progressive disclosure** — components expose simple APIs by default; power-user options (controlled state, callbacks, refs) are available but never required.
25
+
5.**Motion respects the user** — all animations honor `prefers-reduced-motion`. Transitions are functional (communicating state), never decorative.
0 commit comments