UX Portfolio Design System & Guidelines

This document outlines the design system and guidelines for constructing a modern UX portfolio based on the established style guide.

Typography

Primary Font: IBM Plex Sans (Google Fonts)

Weights: 300 (Light), 400 (Regular), 500 (Medium), 600 (Semi-Bold), 700 (Bold)

Fallback:

-apple-system, BlinkMacSystemFont, sans-serif

Monospace:
```
'SF Mono', Monaco, monospace
```
(for code/technical content)
Ligatures: Enabled site-wide for improved readability (fi, fl, ff, ffi, ffl)

Typography System - CSS Variables:

All typography is standardized using CSS custom properties in

_variables.css

. Each element has variables for size, weight, letter-spacing, and line-height.

/* Hero Title */
--typo-hero-title-size: clamp(48px, 8vw, 96px)
--typo-hero-title-weight: 300 (Light)
--typo-hero-title-spacing: -0.02em
--typo-hero-title-line-height: 0.9

/* Subtitle */
--typo-subtitle-size: clamp(18px, 2.5vw, 32px)
--typo-subtitle-weight: 400 (Regular)
--typo-subtitle-line-height: 1.5

/* Section Title */
--typo-section-title-size: clamp(36px, 5vw, 48px)
--typo-section-title-weight: 300 (Light)
--typo-section-title-spacing: -0.02em
--typo-section-title-line-height: 1.2

/* Section Subtitle */
--typo-section-subtitle-size: 16px
--typo-section-subtitle-weight: 400 (Regular)
--typo-section-subtitle-line-height: 1.7

/* Heading 1 */
--typo-h1-size: clamp(32px, 5vw, 48px)
--typo-h1-weight: 300 (Light)
--typo-h1-spacing: -0.02em
--typo-h1-line-height: 1.2

/* Heading 2 */
--typo-h2-size: clamp(24px, 4vw, 32px)
--typo-h2-weight: 400 (Regular)
--typo-h2-spacing: -0.01em
--typo-h2-line-height: 1.3

/* Heading 3 */
--typo-h3-size: clamp(20px, 3vw, 24px)
--typo-h3-weight: 500 (Medium)
--typo-h3-line-height: 1.4

/* Heading 4 */
--typo-h4-size: clamp(18px, 2.5vw, 20px)
--typo-h4-weight: 500 (Medium)
--typo-h4-line-height: 1.4

/* Heading 5 */
--typo-h5-size: clamp(16px, 2vw, 18px)
--typo-h5-weight: 600 (Semi-Bold)
--typo-h5-line-height: 1.5

/* Heading 6 */
--typo-h6-size: clamp(14px, 1.5vw, 16px)
--typo-h6-weight: 600 (Semi-Bold)
--typo-h6-line-height: 1.5

/* Body Text */
--typo-body-size: 16px (desktop), 12px (mobile)
--typo-body-weight: 400 (Regular)
--typo-body-line-height: 1.7

/* Small Text */
--typo-small-size: 14px
--typo-small-weight: 400 (Regular)
--typo-small-line-height: 1.6

/* Type Label */
--typo-label-size: 14px
--typo-label-weight: 500 (Medium)
--typo-label-spacing: 0.05em

Usage: All typography elements use these variables for consistency. To apply typography styles:

.my-heading {
    font-size: var(--typo-h2-size);
    font-weight: var(--typo-h2-weight);
    letter-spacing: var(--typo-h2-spacing);
    line-height: var(--typo-h2-line-height);
}

Link Styles

Link System - CSS Variables:

All link styles are standardized using CSS custom properties in

_variables.css

/* Link Styles */
--link-color: var(--color-accent)
--link-hover-opacity: 0.5
--link-underline-height: 2px
--link-underline-offset: -2px
--link-transition: 0.3s ease
--link-font-weight: 500 (Medium)

Standard Link Components:

Accent Link (
```
.accent-link
```
) - Standard link with animated underline
- Color changes based on theme (cool blue in light, warm orange in dark)
- Underline animates from left to right on hover
- Text fades to 50% opacity on hover using
```
color-mix()
```
- Usage: Internal navigation, section links, primary CTAs
Accent Link with Arrow (
```
.accent-link-arrow
```
) - Navigation link with right arrow
- Same styling as accent link with right-pointing arrow (→)
- Arrow included in link text
- Usage: "Read more" links, case study links, directional navigation
External Link (
```
.external-link
```
) - For external resources opening in new tab
- Same styling as accent link with 45-degree arrow (↗)
- Arrow included in link text
- Usage: External websites, documentation links, resources that open in new window

Usage:

<!-- Accent Link -->
<a href="#section" class="accent-link">Internal link</a>

<!-- Accent Link with Arrow -->
<a href="/case-study" class="accent-link-arrow">Read the case study →</a>

<!-- External Link -->
<a href="https://example.com" target="_blank" class="external-link">View documentation ↗</a>

Color Palette

Primary Colors:

Primary:
```
#0f0f0f
```
(darker than neutral 900)
Secondary:
```
#525252
```
Tertiary:
```
#737373
```

Accent Colors (Temperature-based theming):

Accent Light:
```
#15B5FF
```
(cool blue for light mode)
Accent Dark:
```
#ea580c
```
(warm orange for dark mode)

Color Theory & Theming Strategy:

The accent color system employs temperature-based theming to optimize visual comfort and hierarchy across both light and dark modes. This approach is grounded in color psychology and perceptual contrast principles:

Cool Accents for Light Mode:

Cool blue (
```
#15B5FF
```
) provides strong chromatic contrast against warm white backgrounds
Blue's shorter wavelength creates visual "recession," preventing eye strain on bright screens
Psychologically associated with trust, clarity, and professionalism—ideal for light mode's clean aesthetic
Lower perceptual weight prevents overwhelming the neutral palette

Warm Accents for Dark Mode:

Warm orange (
```
#ea580c
```
) creates vibrant contrast against cool dark backgrounds without harsh glare
Longer wavelength colors feel more comfortable in low-light environments
Orange's energetic, approachable quality balances dark mode's serious tone
Higher luminance value maintains accessibility while feeling intentional rather than harsh

This complementary temperature approach ensures:

Consistent perceptual impact across themes (neither accent feels "louder")
Reduced eye fatigue through wavelength distribution
Clear visual hierarchy that adapts to ambient lighting contexts
Semantic reinforcement: cool = clarity/focus (light), warm = energy/emphasis (dark)

By inverting color temperature relative to the background, each theme maintains optimal legibility, emotional resonance, and visual balance.

Neutral Scale:

White:
```
#ffffff
```
Neutral 50:
```
#fafafa
```
Neutral 100:
```
#f5f5f5
```
Neutral 200:
```
#e5e5e5
```
Neutral 300:
```
#d4d4d4
```
Neutral 400:
```
#a3a3a3
```
Neutral 500:
```
#737373
```
Neutral 600:
```
#525252
```
Neutral 700:
```
#404040
```
Neutral 800:
```
#262626
```
Neutral 900:
```
#171717
```

Layout & Spacing

Container:

Max-width: 1200px
Width: 100% (liquid until max-width)
Padding: 120px 60px (desktop), 80px 24px (mobile)

Modular Spacing Scale:

xs: 4px, sm: 8px, md: 16px, lg: 24px, xl: 48px, xxl: 80px

Spacing Utilities:

Available margin utilities (replace inline styles with these):

```
.m-0
```
- margin: 0
```
.mb-3
```
- margin-bottom: 12px
```
.mb-4
```
- margin-bottom: 16px
```
.mb-6
```
- margin-bottom: 24px
```
.mb-8
```
- margin-bottom: 32px
```
.mb-12
```
- margin-bottom: 48px
```
.mb-30
```
- margin-bottom: 120px
```
.mt-6
```
- margin-top: 24px
```
.mt-8
```
- margin-top: 32px
```
.mt-12
```
- margin-top: 48px

Layout Utilities:

Flexbox utilities (replace inline flex styles with these):

```
.flex-center
```
- Centers content horizontally with flexbox
```
.flex-column-gap-6
```
- Vertical flex column with 24px gap, left-aligned
```
.flex-wrap-gap-6
```
- Horizontal flex with 24px gap and wrapping

Grid System:

CSS Grid with
```
.grid
```
,
```
.grid-cols-{n}
```
,
```
.col-span-{n}
```
Responsive breakpoints: 768px (tablet), 1024px (desktop)
Gap options:
```
.gap-1
```
(4px) to
```
.gap-16
```
(64px)

Interactive Elements & Effects

Glassmorphism Design Language:

Buttons: Semi-transparent backgrounds with backdrop blur
Cards: Subtle transparency with enhanced shadows
Theme toggle: Circular glass effect with blur
No borders in dark mode for cleaner aesthetic

Transitions & Animations:

Standard:
```
transition: all 0.3s ease
```
Fast:
```
transition: all 0.15s ease
```
Slow:
```
transition: all 0.5s ease
```
Smooth cubic-bezier:
```
cubic-bezier(0.4, 0, 0.2, 1)
```

Hover States:

```
.hover-lift
```
: translateY(-2px) with enhanced shadow
```
.hover-scale
```
: scale(1.02)
```
.hover-fade
```
: opacity(0.8)

Theme System

Light Mode:

Background:
```
#ffffff
```
Text:
```
#1a1a1a
```
Accent: Cool blue
```
#2563eb
```

Dark Mode:

Background:
```
#0a0a0a
```
Text:
```
#e0e0e0
```
Accent: Warm orange
```
#ea580c
```
Enhanced contrast with deeper shadows

Theme Toggle:

32pxx32px top-right fixed position

Icons:

/assets/icons/moon-outlined.svg

(light mode),

/assets/icons/sun-outlined.svg

(dark mode)

CSS Variable Architecture & Theme Switching

CRITICAL: Understanding Variable Cascading

CSS variables that reference other variables do NOT automatically re-evaluate when the referenced variable changes. This is crucial for theme switching.

Correct Implementation:

/* ❌ INCORRECT - Won't work for theme switching */
:root {
  --color-accent: var(--color-accent-cool);
  --link-color: var(--color-accent); /* This locks to the initial value */
}

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm); /* Only updates accent, NOT link-color */
}

/* ✅ CORRECT - Explicitly override dependent variables */
:root {
  --color-accent: var(--color-accent-cool);
  --link-color: var(--color-accent);
}

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm); /* Must explicitly override */
}

Theme Variable Override Locations:

Variables must be overridden in BOTH locations due to CSS cascade order:

_variables.css

(line ~222) - Base dark theme overrides

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm);
  /* ... other overrides */
}

_utilities.css

(line ~29) - Final dark theme overrides (loads last)

[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm);
  /* ... other overrides */
}

Why Both Locations?

```
_utilities.css
```
loads LAST in the cascade (see main.css import order)
This ensures theme variables have highest specificity
If you only update in
```
_variables.css
```
, hardcoded values elsewhere may override

When Adding New Theme-Aware Colors:

Define base color variable in
```
:root
```
If it references another variable, add it to BOTH dark theme blocks
Use variables instead of hardcoded hex values in components
Test in both light AND dark modes

Example - Adding a New Themed Element:

/* Step 1: Define in :root (_variables.css) */
:root {
  --button-accent: var(--color-accent);
}

/* Step 2: Override in BOTH dark theme blocks */
body[data-theme="dark"] {  /* _variables.css */
  --button-accent: var(--color-accent-warm);
}

[data-theme="dark"] {  /* _utilities.css */
  --button-accent: var(--color-accent-warm);
}

/* Step 3: Use in components */
.my-button {
  background: var(--button-accent); /* ✅ Will switch with theme */
  /* NOT: background: #15B5FF; ❌ Won't switch with theme */
}

Common Pitfalls to Avoid:

❌ Never use hardcoded hex colors in components

Bad:
```
.link { color: #15B5FF; }
```
Good:
```
.link { color: var(--link-color); }
```

❌ Don't use

rgba()

with hardcoded RGB values

Bad:

.element { color: rgba(21, 181, 255, 0.5); }

Good:

.element { color: color-mix(in srgb, var(--link-color) 50%, transparent); }

❌ Don't create theme-specific selectors for colors
- Bad:
```
body[data-theme="dark"] .link { color: #ea580c; }
```
- Good: Use variables that auto-switch:
```
.link { color: var(--link-color); }
```
✅ Always use CSS variables for any color that should respond to theme
- Links, buttons, borders, backgrounds, shadows with color
✅ The lab page (
```
lab.html
```
) is the source of truth
- All colors on the lab page use variables
- Use it as reference when building new components

Component Library

Buttons:

.btn-primary: Dark glass with white text (light), light glass (dark)
.btn-secondary: Light glass with dark text (light), subtle glass (dark)
Border-radius: 50px (pill-shaped)
Padding: 16px 32px

Cards:

.card: Standard card with glass effect
.glass-card: Enhanced glass card with more blur
.interactive-card: Card with hover lift effect
Border-radius: 16-20px
Backdrop-filter: blur(10-20px)

Interactive Text:

.interactive-text: Underline animation on hover
Color: Theme-appropriate accent color
Transition: width 0.3s ease

Lab Page Components:

.wave-slider-container: Centers slider with 120px bottom margin (80px mobile)
.wave-slider: Responsive slider with width: min(500px, 100%)
.interactive-checkbox-label: Checkbox label with 12px gap and left alignment

Portfolio Construction Guidelines

Page Structure:

Header with navigation (glass effect)
Hero section with large typography
Project showcase grid
About section
Contact/footer

Project Cards:

Use
```
.glass-card
```
with hover effects
Include project thumbnails, titles, descriptions
Maintain consistent spacing and alignment
Responsive grid: 1 col (mobile) → 2-3 cols (desktop)

Navigation:

Fixed or sticky header with glass effect
Theme toggle in top-right corner
Smooth scroll to sections
Active state indicators using accent colors

Performance Considerations:

Optimize backdrop-filter usage (can be expensive)
Use CSS transforms for smooth animations
Implement lazy loading for project images
Maintain accessibility with proper contrast ratios

Content Guidelines:

Use sentence case for most text
Maintain consistent voice and tone
Include case studies with problem/solution structure
Showcase diverse project types and skills

Coding Best Practices

Avoid Inline Styles:

NEVER use inline
```
style=""
```
attributes in HTML
Use utility classes from
```
_utilities.css
```
for spacing, layout, and common patterns
Create component classes in
```
_components.css
```
for reusable patterns
Inline styles prevent responsive adjustments and theme switching

Use CSS Variables:

ALWAYS use CSS variables instead of hardcoded color values
Use
```
var(--color-accent-cool)
```
instead of
```
#15B5FF
```
Use
```
var(--color-accent-warm)
```
instead of
```
#ea580c
```
This ensures proper theme switching and maintains consistency
Reference the complete variable list in
```
_variables.css
```

Responsive Patterns:

Use
```
min()
```
function for responsive sizing:
```
width: min(500px, 100%)
```
Use
```
clamp()
```
for responsive typography (already defined in variables)
Prefer CSS Grid and Flexbox utilities over custom inline styles

Component Reusability:

If a pattern appears more than once, create a reusable class
Document new components in this file for future reference
Keep lab-specific components in a dedicated section of
```
_components.css
```

Implementation Notes

All effects work cross-browser with
```
-webkit-
```
prefixes
Mobile-first responsive approach
Semantic HTML structure for accessibility
Test glass effects on various backgrounds
Ensure sufficient color contrast in both themes
Use
```
prefers-reduced-motion
```
for accessibility

File Organization

/assets/
  /css/                      # Modular CSS architecture
    main.css                 # Main import file
    _variables.css           # CSS custom properties
    _base.css                # Reset & base styles
    _navigation.css          # Header & navigation
    _hero.css                # Hero section
    _particles.css           # Particle system
    _components.css          # Reusable components
    _carousels.css           # Carousel implementations
    _sections.css            # Page sections
    _project-pages.css       # Project detail pages
    _charts.css              # Data visualizations
    _utilities.css           # Helper classes & dark mode
  /js/                       # Interactive features
    main.js                  # Core functionality
    particles.js             # Particle system
    theme.js                 # Theme switching
  /images/                   # Image assets
/data/
  projects.json              # Project data
/work/                       # Case study pages
  design-system.html
  product-suite.html
  ai-strategy.html
  research-strategy.html
/.claude/                    # Claude Code configuration
  /commands/                 # Slash commands
  settings.local.json
index.html                   # Main portfolio page
lab.html                     # Interactive experiments
resume.html                  # Resume page
CLAUDE.md                    # This file - AI context
README.md                    # Public documentation

Technical Architecture

Modular CSS System

The stylesheet is organized as a series of CSS modules imported into

main.css

Variables - CSS custom properties and theme tokens (
```
--container-max-width
```
, colors, fonts)
Base - Reset, foundational styles, text selection
Navigation - Header, menu, theme toggle
Hero - Hero section, back-to-top button
Particles - Particle system and controls
Components - Reusable UI components (buttons, cards)
Carousels - Carousel implementations
Sections - Page sections (projects, about, brands, contact)
Project Pages - Case study layouts
Charts - Data visualizations
Utilities - Helper classes, dark mode, responsive overrides (must load last)

Cache Busting Strategy

CSS and JavaScript files use query parameter versioning for browser cache control:

<link rel="stylesheet" href="assets/css/main.css?v=1760841100">
<script src="assets/js/main.js?v=1760840700"></script>

Update version numbers after CSS/JS changes to force browser refresh.

Container Strategy

Max-width containers prevent content from becoming excessively wide on large displays:

CSS Variable:

--container-max-width: 1200px

(defined in

_variables.css

)

Applied to: Hero content, navigation, sections
Behavior: Content is fluid up to 1200px, then centers with whitespace on sides
Rationale: Maintains readability and prevents "tiny elements spread out" on 4K+ displays

Known Limitations & Best Practices

Viewport Scaling on Large Displays: CSS cannot replicate browser zoom behavior when using

vh

(viewport height) units. Attempts to use

transform: scale()

or CSS

zoom

property will break layouts that depend on viewport units because:

Browser zoom recalculates viewport dimensions before layout
CSS scaling happens after layout (viewport units already computed)
Result: Misaligned or broken
```
vh
```
-based elements

Recommended Approaches for Large Displays:

✅ Max-width containers (current implementation) - Prevents excessive spread
✅ Targeted media queries - Increase specific font sizes at 2K/4K if needed
✅ User-controlled zoom - Let users apply browser zoom themselves
❌ Avoid
```
transform: scale()
```
or
```
zoom
```
property with
```
vh
```
layouts

Future Considerations: If elements feel too small on ultra-high-resolution displays, consider:

Increasing
```
--container-max-width
```
to 1400-1600px
Adding media queries for larger base font sizes at 2560px+ breakpoints
Adjusting specific component sizes (nav, buttons) via targeted media queries

Development Workflow

Slash commands available via

.claude/commands/

```
/quick-commit
```
- Commit changes on current branch
```
/deploy
```
- Commit, merge to main, push both branches
```
/status
```
- Show git status and recent commits

This design system provides a comprehensive foundation for building a modern, professional UX portfolio that stands out with sophisticated glassmorphism effects and intelligent theming.

UX Portfolio Design System & Guidelines

This document outlines the design system and guidelines for constructing a modern UX portfolio based on the established style guide.

Design Principals

Typography

Primary Font: IBM Plex Sans (Google Fonts)

Weights: 300 (Light), 400 (Regular), 500 (Medium), 600 (Semi-Bold), 700 (Bold)

Fallback:

-apple-system, BlinkMacSystemFont, sans-serif

Monospace:
```
'SF Mono', Monaco, monospace
```
(for code/technical content)
Ligatures: Enabled site-wide for improved readability (fi, fl, ff, ffi, ffl)

Typography System - CSS Variables:

All typography is standardized using CSS custom properties in

_variables.css

. Each element has variables for size, weight, letter-spacing, and line-height.

/* Hero Title */
--typo-hero-title-size: clamp(48px, 8vw, 96px)
--typo-hero-title-weight: 300 (Light)
--typo-hero-title-spacing: -0.02em
--typo-hero-title-line-height: 0.9

/* Subtitle */
--typo-subtitle-size: clamp(18px, 2.5vw, 32px)
--typo-subtitle-weight: 400 (Regular)
--typo-subtitle-line-height: 1.5

/* Section Title */
--typo-section-title-size: clamp(36px, 5vw, 48px)
--typo-section-title-weight: 300 (Light)
--typo-section-title-spacing: -0.02em
--typo-section-title-line-height: 1.2

/* Section Subtitle */
--typo-section-subtitle-size: 16px
--typo-section-subtitle-weight: 400 (Regular)
--typo-section-subtitle-line-height: 1.7

/* Heading 1 */
--typo-h1-size: clamp(32px, 5vw, 48px)
--typo-h1-weight: 300 (Light)
--typo-h1-spacing: -0.02em
--typo-h1-line-height: 1.2

/* Heading 2 */
--typo-h2-size: clamp(24px, 4vw, 32px)
--typo-h2-weight: 400 (Regular)
--typo-h2-spacing: -0.01em
--typo-h2-line-height: 1.3

/* Heading 3 */
--typo-h3-size: clamp(20px, 3vw, 24px)
--typo-h3-weight: 500 (Medium)
--typo-h3-line-height: 1.4

/* Heading 4 */
--typo-h4-size: clamp(18px, 2.5vw, 20px)
--typo-h4-weight: 500 (Medium)
--typo-h4-line-height: 1.4

/* Heading 5 */
--typo-h5-size: clamp(16px, 2vw, 18px)
--typo-h5-weight: 600 (Semi-Bold)
--typo-h5-line-height: 1.5

/* Heading 6 */
--typo-h6-size: clamp(14px, 1.5vw, 16px)
--typo-h6-weight: 600 (Semi-Bold)
--typo-h6-line-height: 1.5

/* Body Text */
--typo-body-size: 16px (desktop), 12px (mobile)
--typo-body-weight: 400 (Regular)
--typo-body-line-height: 1.7

/* Small Text */
--typo-small-size: 14px
--typo-small-weight: 400 (Regular)
--typo-small-line-height: 1.6

/* Type Label */
--typo-label-size: 14px
--typo-label-weight: 500 (Medium)
--typo-label-spacing: 0.05em

Usage: All typography elements use these variables for consistency. To apply typography styles:

.my-heading {
    font-size: var(--typo-h2-size);
    font-weight: var(--typo-h2-weight);
    letter-spacing: var(--typo-h2-spacing);
    line-height: var(--typo-h2-line-height);
}

Link Styles

Link System - CSS Variables:

All link styles are standardized using CSS custom properties in

_variables.css

/* Link Styles */
--link-color: var(--color-accent)
--link-hover-opacity: 0.5
--link-underline-height: 2px
--link-underline-offset: -2px
--link-transition: 0.3s ease
--link-font-weight: 500 (Medium)

Standard Link Components:

Accent Link (
```
.accent-link
```
) - Standard link with animated underline
- Color changes based on theme (cool blue in light, warm orange in dark)
- Underline animates from left to right on hover
- Text fades to 50% opacity on hover using
```
color-mix()
```
- Usage: Internal navigation, section links, primary CTAs
Accent Link with Arrow (
```
.accent-link-arrow
```
) - Navigation link with right arrow
- Same styling as accent link with right-pointing arrow (→)
- Arrow included in link text
- Usage: "Read more" links, case study links, directional navigation
External Link (
```
.external-link
```
) - For external resources opening in new tab
- Same styling as accent link with 45-degree arrow (↗)
- Arrow included in link text
- Usage: External websites, documentation links, resources that open in new window

Usage:

<!-- Accent Link -->
<a href="#section" class="accent-link">Internal link</a>

<!-- Accent Link with Arrow -->
<a href="/case-study" class="accent-link-arrow">Read the case study →</a>

<!-- External Link -->
<a href="https://example.com" target="_blank" class="external-link">View documentation ↗</a>

Color Palette

Primary Colors:

Primary:
```
#0f0f0f
```
(darker than neutral 900)
Secondary:
```
#525252
```
Tertiary:
```
#737373
```

Accent Colors (Temperature-based theming):

Accent Light:
```
#15B5FF
```
(cool blue for light mode)
Accent Dark:
```
#ea580c
```
(warm orange for dark mode)

Color Theory & Theming Strategy:

Cool Accents for Light Mode:

Cool blue (
```
#15B5FF
```
) provides strong chromatic contrast against warm white backgrounds
Blue's shorter wavelength creates visual "recession," preventing eye strain on bright screens
Psychologically associated with trust, clarity, and professionalism—ideal for light mode's clean aesthetic
Lower perceptual weight prevents overwhelming the neutral palette

Warm Accents for Dark Mode:

Warm orange (
```
#ea580c
```
) creates vibrant contrast against cool dark backgrounds without harsh glare
Longer wavelength colors feel more comfortable in low-light environments
Orange's energetic, approachable quality balances dark mode's serious tone
Higher luminance value maintains accessibility while feeling intentional rather than harsh

This complementary temperature approach ensures:

Consistent perceptual impact across themes (neither accent feels "louder")
Reduced eye fatigue through wavelength distribution
Clear visual hierarchy that adapts to ambient lighting contexts
Semantic reinforcement: cool = clarity/focus (light), warm = energy/emphasis (dark)

By inverting color temperature relative to the background, each theme maintains optimal legibility, emotional resonance, and visual balance.

Neutral Scale:

White:
```
#ffffff
```
Neutral 50:
```
#fafafa
```
Neutral 100:
```
#f5f5f5
```
Neutral 200:
```
#e5e5e5
```
Neutral 300:
```
#d4d4d4
```
Neutral 400:
```
#a3a3a3
```
Neutral 500:
```
#737373
```
Neutral 600:
```
#525252
```
Neutral 700:
```
#404040
```
Neutral 800:
```
#262626
```
Neutral 900:
```
#171717
```

Layout & Spacing

Container:

Max-width: 1200px
Width: 100% (liquid until max-width)
Padding: 120px 60px (desktop), 80px 24px (mobile)

Modular Spacing Scale:

xs: 4px, sm: 8px, md: 16px, lg: 24px, xl: 48px, xxl: 80px

Spacing Utilities:

Available margin utilities (replace inline styles with these):

```
.m-0
```
- margin: 0
```
.mb-3
```
- margin-bottom: 12px
```
.mb-4
```
- margin-bottom: 16px
```
.mb-6
```
- margin-bottom: 24px
```
.mb-8
```
- margin-bottom: 32px
```
.mb-12
```
- margin-bottom: 48px
```
.mb-30
```
- margin-bottom: 120px
```
.mt-6
```
- margin-top: 24px
```
.mt-8
```
- margin-top: 32px
```
.mt-12
```
- margin-top: 48px

Layout Utilities:

Flexbox utilities (replace inline flex styles with these):

```
.flex-center
```
- Centers content horizontally with flexbox
```
.flex-column-gap-6
```
- Vertical flex column with 24px gap, left-aligned
```
.flex-wrap-gap-6
```
- Horizontal flex with 24px gap and wrapping

Grid System:

CSS Grid with
```
.grid
```
,
```
.grid-cols-{n}
```
,
```
.col-span-{n}
```
Responsive breakpoints: 768px (tablet), 1024px (desktop)
Gap options:
```
.gap-1
```
(4px) to
```
.gap-16
```
(64px)

Interactive Elements & Effects

Glassmorphism Design Language:

Buttons: Semi-transparent backgrounds with backdrop blur
Cards: Subtle transparency with enhanced shadows
Theme toggle: Circular glass effect with blur
No borders in dark mode for cleaner aesthetic

Transitions & Animations:

Standard:
```
transition: all 0.3s ease
```
Fast:
```
transition: all 0.15s ease
```
Slow:
```
transition: all 0.5s ease
```
Smooth cubic-bezier:
```
cubic-bezier(0.4, 0, 0.2, 1)
```

Hover States:

```
.hover-lift
```
: translateY(-2px) with enhanced shadow
```
.hover-scale
```
: scale(1.02)
```
.hover-fade
```
: opacity(0.8)

Theme System

Light Mode:

Background:
```
#ffffff
```
Text:
```
#1a1a1a
```
Accent: Cool blue
```
#2563eb
```

Dark Mode:

Background:
```
#0a0a0a
```
Text:
```
#e0e0e0
```
Accent: Warm orange
```
#ea580c
```
Enhanced contrast with deeper shadows

Theme Toggle:

32pxx32px top-right fixed position

Icons:

/assets/icons/moon-outlined.svg

(light mode),

/assets/icons/sun-outlined.svg

(dark mode)

CSS Variable Architecture & Theme Switching

CRITICAL: Understanding Variable Cascading

CSS variables that reference other variables do NOT automatically re-evaluate when the referenced variable changes. This is crucial for theme switching.

Correct Implementation:

/* ❌ INCORRECT - Won't work for theme switching */
:root {
  --color-accent: var(--color-accent-cool);
  --link-color: var(--color-accent); /* This locks to the initial value */
}

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm); /* Only updates accent, NOT link-color */
}

/* ✅ CORRECT - Explicitly override dependent variables */
:root {
  --color-accent: var(--color-accent-cool);
  --link-color: var(--color-accent);
}

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm); /* Must explicitly override */
}

Theme Variable Override Locations:

Variables must be overridden in BOTH locations due to CSS cascade order:

_variables.css

(line ~222) - Base dark theme overrides

body[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm);
  /* ... other overrides */
}

_utilities.css

(line ~29) - Final dark theme overrides (loads last)

[data-theme="dark"] {
  --color-accent: var(--color-accent-warm);
  --link-color: var(--color-accent-warm);
  /* ... other overrides */
}

Why Both Locations?

```
_utilities.css
```
loads LAST in the cascade (see main.css import order)
This ensures theme variables have highest specificity
If you only update in
```
_variables.css
```
, hardcoded values elsewhere may override

When Adding New Theme-Aware Colors:

Define base color variable in
```
:root
```
If it references another variable, add it to BOTH dark theme blocks
Use variables instead of hardcoded hex values in components
Test in both light AND dark modes

Example - Adding a New Themed Element:

/* Step 1: Define in :root (_variables.css) */
:root {
  --button-accent: var(--color-accent);
}

/* Step 2: Override in BOTH dark theme blocks */
body[data-theme="dark"] {  /* _variables.css */
  --button-accent: var(--color-accent-warm);
}

[data-theme="dark"] {  /* _utilities.css */
  --button-accent: var(--color-accent-warm);
}

/* Step 3: Use in components */
.my-button {
  background: var(--button-accent); /* ✅ Will switch with theme */
  /* NOT: background: #15B5FF; ❌ Won't switch with theme */
}

Common Pitfalls to Avoid:

❌ Never use hardcoded hex colors in components

Bad:
```
.link { color: #15B5FF; }
```
Good:
```
.link { color: var(--link-color); }
```

❌ Don't use

rgba()

with hardcoded RGB values

Bad:

.element { color: rgba(21, 181, 255, 0.5); }

Good:

.element { color: color-mix(in srgb, var(--link-color) 50%, transparent); }

❌ Don't create theme-specific selectors for colors
- Bad:
```
body[data-theme="dark"] .link { color: #ea580c; }
```
- Good: Use variables that auto-switch:
```
.link { color: var(--link-color); }
```
✅ Always use CSS variables for any color that should respond to theme
- Links, buttons, borders, backgrounds, shadows with color
✅ The lab page (
```
lab.html
```
) is the source of truth
- All colors on the lab page use variables
- Use it as reference when building new components

Component Library

Buttons:

.btn-primary: Dark glass with white text (light), light glass (dark)
.btn-secondary: Light glass with dark text (light), subtle glass (dark)
Border-radius: 50px (pill-shaped)
Padding: 16px 32px

Cards:

.card: Standard card with glass effect
.glass-card: Enhanced glass card with more blur
.interactive-card: Card with hover lift effect
Border-radius: 16-20px
Backdrop-filter: blur(10-20px)

Interactive Text:

.interactive-text: Underline animation on hover
Color: Theme-appropriate accent color
Transition: width 0.3s ease

Lab Page Components:

.wave-slider-container: Centers slider with 120px bottom margin (80px mobile)
.wave-slider: Responsive slider with width: min(500px, 100%)
.interactive-checkbox-label: Checkbox label with 12px gap and left alignment

Portfolio Construction Guidelines

Page Structure:

Header with navigation (glass effect)
Hero section with large typography
Project showcase grid
About section
Contact/footer

Project Cards:

Use
```
.glass-card
```
with hover effects
Include project thumbnails, titles, descriptions
Maintain consistent spacing and alignment
Responsive grid: 1 col (mobile) → 2-3 cols (desktop)

Navigation:

Fixed or sticky header with glass effect
Theme toggle in top-right corner
Smooth scroll to sections
Active state indicators using accent colors

Performance Considerations:

Optimize backdrop-filter usage (can be expensive)
Use CSS transforms for smooth animations
Implement lazy loading for project images
Maintain accessibility with proper contrast ratios

Content Guidelines:

Use sentence case for most text
Maintain consistent voice and tone
Include case studies with problem/solution structure
Showcase diverse project types and skills

Coding Best Practices

Avoid Inline Styles:

NEVER use inline
```
style=""
```
attributes in HTML
Use utility classes from
```
_utilities.css
```
for spacing, layout, and common patterns
Create component classes in
```
_components.css
```
for reusable patterns
Inline styles prevent responsive adjustments and theme switching

Use CSS Variables:

ALWAYS use CSS variables instead of hardcoded color values
Use
```
var(--color-accent-cool)
```
instead of
```
#15B5FF
```
Use
```
var(--color-accent-warm)
```
instead of
```
#ea580c
```
This ensures proper theme switching and maintains consistency
Reference the complete variable list in
```
_variables.css
```

Responsive Patterns:

Use
```
min()
```
function for responsive sizing:
```
width: min(500px, 100%)
```
Use
```
clamp()
```
for responsive typography (already defined in variables)
Prefer CSS Grid and Flexbox utilities over custom inline styles

Component Reusability:

If a pattern appears more than once, create a reusable class
Document new components in this file for future reference
Keep lab-specific components in a dedicated section of
```
_components.css
```

Implementation Notes

All effects work cross-browser with
```
-webkit-
```
prefixes
Mobile-first responsive approach
Semantic HTML structure for accessibility
Test glass effects on various backgrounds
Ensure sufficient color contrast in both themes
Use
```
prefers-reduced-motion
```
for accessibility

File Organization

/assets/
  /css/                      # Modular CSS architecture
    main.css                 # Main import file
    _variables.css           # CSS custom properties
    _base.css                # Reset & base styles
    _navigation.css          # Header & navigation
    _hero.css                # Hero section
    _particles.css           # Particle system
    _components.css          # Reusable components
    _carousels.css           # Carousel implementations
    _sections.css            # Page sections
    _project-pages.css       # Project detail pages
    _charts.css              # Data visualizations
    _utilities.css           # Helper classes & dark mode
  /js/                       # Interactive features
    main.js                  # Core functionality
    particles.js             # Particle system
    theme.js                 # Theme switching
  /images/                   # Image assets
/data/
  projects.json              # Project data
/work/                       # Case study pages
  design-system.html
  product-suite.html
  ai-strategy.html
  research-strategy.html
/.claude/                    # Claude Code configuration
  /commands/                 # Slash commands
  settings.local.json
index.html                   # Main portfolio page
lab.html                     # Interactive experiments
resume.html                  # Resume page
CLAUDE.md                    # This file - AI context
README.md                    # Public documentation

Technical Architecture

Modular CSS System

The stylesheet is organized as a series of CSS modules imported into

main.css

Variables - CSS custom properties and theme tokens (
```
--container-max-width
```
, colors, fonts)
Base - Reset, foundational styles, text selection
Navigation - Header, menu, theme toggle
Hero - Hero section, back-to-top button
Particles - Particle system and controls
Components - Reusable UI components (buttons, cards)
Carousels - Carousel implementations
Sections - Page sections (projects, about, brands, contact)
Project Pages - Case study layouts
Charts - Data visualizations
Utilities - Helper classes, dark mode, responsive overrides (must load last)

Cache Busting Strategy

CSS and JavaScript files use query parameter versioning for browser cache control:

<link rel="stylesheet" href="assets/css/main.css?v=1760841100">
<script src="assets/js/main.js?v=1760840700"></script>

Update version numbers after CSS/JS changes to force browser refresh.

Container Strategy

Max-width containers prevent content from becoming excessively wide on large displays:

CSS Variable:

--container-max-width: 1200px

(defined in

_variables.css

)

Applied to: Hero content, navigation, sections
Behavior: Content is fluid up to 1200px, then centers with whitespace on sides
Rationale: Maintains readability and prevents "tiny elements spread out" on 4K+ displays

Known Limitations & Best Practices

Viewport Scaling on Large Displays: CSS cannot replicate browser zoom behavior when using

vh

(viewport height) units. Attempts to use

transform: scale()

or CSS

zoom

property will break layouts that depend on viewport units because:

Browser zoom recalculates viewport dimensions before layout
CSS scaling happens after layout (viewport units already computed)
Result: Misaligned or broken
```
vh
```
-based elements

Recommended Approaches for Large Displays:

✅ Max-width containers (current implementation) - Prevents excessive spread
✅ Targeted media queries - Increase specific font sizes at 2K/4K if needed
✅ User-controlled zoom - Let users apply browser zoom themselves
❌ Avoid
```
transform: scale()
```
or
```
zoom
```
property with
```
vh
```
layouts

Future Considerations: If elements feel too small on ultra-high-resolution displays, consider:

Increasing
```
--container-max-width
```
to 1400-1600px
Adding media queries for larger base font sizes at 2560px+ breakpoints
Adjusting specific component sizes (nav, buttons) via targeted media queries

Development Workflow

Slash commands available via

.claude/commands/

```
/quick-commit
```
- Commit changes on current branch
```
/deploy
```
- Commit, merge to main, push both branches
```
/status
```
- Show git status and recent commits

This design system provides a comprehensive foundation for building a modern, professional UX portfolio that stands out with sophisticated glassmorphism effects and intelligent theming.

UX Portfolio Design System & Guidelines

Related Skills

Markdown Converter

Nano Banana Pro

1password