design_responsive
Breakpoints, fluid typography, container queries ve modern CSS features.
Best use case
design_responsive is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Breakpoints, fluid typography, container queries ve modern CSS features.
Teams using design_responsive should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design_responsive/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design_responsive Compares
| Feature / Agent | design_responsive | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Breakpoints, fluid typography, container queries ve modern CSS features.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 📱 Design Responsive
> Responsive tasarım ve modern CSS özellikleri.
---
## 📐 1. Breakpoints
### Standard
```
Mobile: 0 - 639px
Tablet SM: 640 - 767px
Tablet: 768 - 1023px
Desktop: 1024 - 1439px
Wide: 1440px+
```
### Tailwind Mapping
```
sm: 640px
md: 768px
lg: 1024px
xl: 1280px
2xl: 1536px
```
---
## 🔤 2. Fluid Typography
```css
:root {
--fluid-sm: clamp(0.875rem, 0.8rem + 0.35vw, 1rem);
--fluid-base: clamp(1rem, 0.9rem + 0.5vw, 1.125rem);
--fluid-lg: clamp(1.25rem, 1rem + 1vw, 1.5rem);
--fluid-xl: clamp(1.5rem, 1.2rem + 1.5vw, 2rem);
--fluid-2xl: clamp(2rem, 1.5rem + 2.5vw, 3rem);
}
```
---
## 📦 3. Container System
| Device | Max-Width | Padding |
|--------|-----------|---------|
| Mobile | 100% | 16px |
| Tablet | 768px | 24px |
| Desktop | 1200px | 32px |
| Wide | 1440px | 48px |
---
## 🎯 4. Container Queries
```css
.card-container {
container-type: inline-size;
}
@container (min-width: 400px) {
.card-content {
display: grid;
grid-template-columns: 1fr 2fr;
}
}
```
---
## ⚙️ 5. User Preferences
```css
/* Dark mode */
@media (prefers-color-scheme: dark) { }
/* Reduced motion */
@media (prefers-reduced-motion: reduce) {
* { animation-duration: 0.01ms !important; }
}
/* High contrast */
@media (prefers-contrast: high) { }
```
---
## 📋 6. Grid Columns
| Device | Columns | Gutter |
|--------|---------|--------|
| Mobile | 4 | 16px |
| Tablet | 8 | 16px |
| Desktop | 12 | 24px |
---
## 🔄 Workflow
> **Kaynak:** [MDN - Container Queries](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Containment/Container_Queries) & [Utopia - Fluid Responsive Design](https://utopia.fyi/)
### Aşama 1: Viewport & Layout Strategy
- [ ] **Mobile First**: Tasarımı en küçük ekran boyutundan başlayarak kurgula.
- [ ] **Breakpoints Selection**: Cihaz bazlı değil, içerik bazlı (Content-driven) kırılma noktaları belirle.
- [ ] **Fluid Scaling**: Typography ve spacing için `clamp()` fonksiyonlarını hesapla ve entegre et.
### Aşama 2: Modern CSS Implementation
- [ ] **Container Queries**: Komponentlerin içindeki bulundukları alana göre (Viewport değil) şekil almasını sağla.
- [ ] **Grid/Flex Optimization**: Kompleks layout'lar için `CSS Grid` (Area naming) ve `Flexbox` (Gap) kullan.
- [ ] **Image Optimization**: `srcset` ve `aspect-ratio` kullanarak görsel yüklemelerini ve düzenini optimize et.
### Aşama 3: Performance & Accessibility Audit
- [ ] **Lighthouse Check**: Core Web Vitals (LCP/CLS) metriklerini mobil için optimize et.
- [ ] **Interaction Check**: Dokunmatik (Touch) alanların yeterli boyutta (min 44x44px) olduğunu doğrula.
- [ ] **User Preferences**: `prefers-color-scheme` ve `prefers-reduced-motion` desteğini test et.
### Kontrol Noktaları
| Aşama | Doğrulama |
|-------|-----------|
| 1 | Tasarım 320px (iPhone SE) ve 2560px (Ultra-wide) arasında sorunsuz mu? |
| 2 | Horizontal scroll oluşuyor mu? (Overflow kontrolü) |
| 3 | Font boyutları her viewport'ta okunabilir mi? |
---
*Design Responsive v1.5 - With Workflow*Related Skills
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
frontend-design
Create distinctive, bold UI designs that avoid generic AI aesthetics. This skill should be used when users want frontend components with strong visual identity, creative typography, intentional color palettes, and production-grade animations - specifically to avoid the bland, safe, homogeneous "AI slop" that plagues most generated interfaces.
figma-design
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
faion-ui-designer
UI design: wireframes, prototypes, design systems, visual design.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
detect-design
Design system detection with drift findings and evidence blocks. Use when auditing design system consistency.
design
Design consistency and visual styling for the Svelte client UI. Use when creating or modifying visual elements, colors, typography, buttons, inputs, or cards.
Design Undo/Redo Systems
CREATE comprehensive undo/redo systems with Command Pattern. Design state management for complex applications with canvas interactions, multiple stores, and user actions. Use when building new undo/redo functionality from scratch.
design-system
design system with Tailwind v4.0, accessibility patterns, and project-specific UI/UX rules. Use for all KKOOKK frontend development.
design-system-starter
Create and evolve design systems with design tokens, component architecture, accessibility guidelines, and documentation templates. Ensures consistent, scalable, and accessible UI across products.
design-system-guard
Validate UI screens against Lucid Labs design system rules. Use after implementing UI components to verify adherence to brand colors, typography, layout patterns, and service board logic.
design-strategy
Strategic alignment of design initiatives with business goals using the TRACES framework. Use when (1) aligning design projects with corporate strategy, (2) identifying and mitigating external threats (Technical Debt, Regulatory, Audience, Competition, Economic, Substitute Technology), (3) assessing design maturity/capability, (4) structuring design teams for specific outcomes, (5) managing designer career growth, or (6) communicating design value (ROI, ESG, business outcomes) to senior leadership.