Frontend Responsive Design Standards

# Frontend Responsive Design Standards

**Rule:** Mobile-first development with consistent breakpoints, fluid layouts, relative units, and touch-friendly targets.

## When to use this skill

- When creating or modifying layouts that need to work on mobile, tablet, and desktop
- When implementing mobile-first design patterns starting with mobile layout
- When writing media queries or breakpoint-specific styles
- When using flexible units (rem, em, %) instead of fixed pixels for scalability
- When implementing fluid layouts with percentage-based widths or flexbox/grid
- When ensuring touch targets meet minimum size requirements (44x44px) for mobile
- When optimizing images and assets for different screen sizes and mobile networks
- When testing UI across multiple device sizes and breakpoints
- When maintaining readable typography across all screen sizes
- When prioritizing content display on smaller screens through layout decisions
- When using responsive design utilities in CSS frameworks (Tailwind, Bootstrap responsive classes)

This Skill provides Codex with specific guidance on how to adhere to coding standards as they relate to how it should handle frontend responsive.

## Mobile-First Development - Mandatory

**Always start with mobile layout, then enhance for larger screens.**

Bad (desktop-first):
```css
.container {
  width: 1200px;
  display: grid;
  grid-template-columns: repeat(4, 1fr);
}

@media (max-width: 768px) {
  .container {
    width: 100%;
    grid-template-columns: 1fr;
  }
}
```

Good (mobile-first):
```css
.container {
  width: 100%;
  display: grid;
  grid-template-columns: 1fr;
}

@media (min-width: 768px) {
  .container {
    grid-template-columns: repeat(2, 1fr);
  }
}

@media (min-width: 1024px) {
  .container {
    max-width: 1200px;
    grid-template-columns: repeat(4, 1fr);
  }
}
```

**Why mobile-first:**
- Forces content prioritization
- Better performance on mobile (no overriding)
- Progressive enhancement over graceful degradation

## Standard Breakpoints

**Identify and use project breakpoints consistently:**

Common breakpoint systems:

Tailwind:
```
sm: 640px   (small tablets)
md: 768px   (tablets)
lg: 1024px  (laptops)
xl: 1280px  (desktops)
2xl: 1536px (large desktops)
```

Bootstrap:
```
sm: 576px
md: 768px
lg: 992px
xl: 1200px
xxl: 1400px
```

**Check existing codebase for breakpoint definitions before creating new ones.**

Usage (Tailwind):
```jsx
<div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-4">
```

Usage (CSS):
```css
@media (min-width: 768px) { }
@media (min-width: 1024px) { }
```

**Never use arbitrary breakpoints like 850px or 1150px unless explicitly required.**

## Fluid Layouts

**Use flexible containers that adapt to screen size:**

Bad (fixed widths):
```css
.container { width: 1200px; }
.sidebar { width: 300px; }
.content { width: 900px; }
```

Good (fluid):
```css
.container {
  width: 100%;
  max-width: 1200px;
  padding: 0 1rem;
}

.layout {
  display: grid;
  grid-template-columns: 1fr;
}

@media (min-width: 1024px) {
  .layout {
    grid-template-columns: 300px 1fr;
  }
}
```

**Patterns for fluid layouts:**
- Flexbox: `flex: 1`, `flex-grow`, `flex-shrink`
- Grid: `1fr`, `