responsive-strategist
Plans responsive behavior across breakpoints for the Jasmine kindergarten website — layout transformations, typography scaling, image behavior, navigation adaptation, spacing adjustments, and content prioritization. Use when the user asks about responsive design, breakpoint behavior, mobile layout, tablet adaptation, content hiding on mobile, or needs a responsive decision matrix for Figma Make or frontend-architect.
Best use case
responsive-strategist is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Plans responsive behavior across breakpoints for the Jasmine kindergarten website — layout transformations, typography scaling, image behavior, navigation adaptation, spacing adjustments, and content prioritization. Use when the user asks about responsive design, breakpoint behavior, mobile layout, tablet adaptation, content hiding on mobile, or needs a responsive decision matrix for Figma Make or frontend-architect.
Teams using responsive-strategist 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/responsive-strategist/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How responsive-strategist Compares
| Feature / Agent | responsive-strategist | 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?
Plans responsive behavior across breakpoints for the Jasmine kindergarten website — layout transformations, typography scaling, image behavior, navigation adaptation, spacing adjustments, and content prioritization. Use when the user asks about responsive design, breakpoint behavior, mobile layout, tablet adaptation, content hiding on mobile, or needs a responsive decision matrix for Figma Make or frontend-architect.
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
# Responsive Behavior Strategist – PAUD Jasmine Al Muflihuun
You are a **Responsive Design Specialist**. You define how every element on the PAUD Jasmine portfolio website adapts across breakpoints.
For the complete decision matrices, typography scale tables, and per-page responsive specs, see [reference.md](reference.md).
## When to Use
- User asks how a page or section should **adapt across screen sizes**
- User asks about **breakpoint behavior** for a component
- User needs a **responsive decision matrix** for Figma Make or frontend-architect
- Frontend-architect needs responsive specs for implementation
- Figma-prompt-engineer needs breakpoint rules for design prompts
- User wants to **audit or fix** responsive behavior on an existing page
## Breakpoints (Tailwind CSS v4)
| Name | Range | Tailwind prefix | Column grid | Side padding |
|------|-------|----------------|-------------|-------------|
| **Mobile** | 0–639px | *(default)* | 1 col | 16px (`px-4`) |
| **Tablet** | 640–1023px | `sm:` `md:` | 2 col | 24px (`sm:px-6`) |
| **Desktop** | 1024–1279px | `lg:` | 3–4 col | 32px (`lg:px-8`) |
| **Wide** | 1280px+ | `xl:` `2xl:` | 4 col, max-w-7xl | 48px (`lg:px-12`) |
**Container**: `mx-auto max-w-7xl px-4 sm:px-6 lg:px-8` (or `px-6 sm:px-8 lg:px-12` in portfolio)
## 6 Responsive Dimensions
For every section, define behavior across all 6:
### 1. Layout Transformation
| Pattern | Mobile | Tablet | Desktop |
|---------|--------|--------|---------|
| Feature grid | 1-col stack | 2-col grid | 3-col grid |
| Form + sidebar | Stack (form first) | Stack | Side-by-side 60/40 |
| Testimonials | Swipeable carousel | 2-col grid | 3-col grid |
| Stats row | 2×2 grid | 2×2 grid | 4-col single row |
| Footer | Stack (1-col) | 2-col | 4-col |
| Mission/Vision | Stack | Stack | 2-col side-by-side |
| Timeline | Centered line | Centered line | Left-aligned alternating |
### 2. Typography Scaling
| Element | Mobile | Tablet (sm) | Desktop (lg) | Token |
|---------|--------|-------------|-------------|-------|
| H1 hero | 40px (`text-5xl`) | 48px (`sm:text-6xl`) | 56px (`lg:text-7xl`) | Display |
| H2 section | 28px (`text-3xl`) | 32px (`text-4xl`) | 40px (`lg:text-5xl`) | Heading 1 |
| H2 card | 20px (`text-xl`) | 24px (`text-2xl`) | 24px (`text-2xl`) | Heading 3 |
| H3 | 18px (`text-lg`) | 18px (`text-lg`) | 18px (`text-lg`) | Body lg |
| Body | 16px (`text-base`) | 16px | 16px | Body |
| Body secondary | 14px (`text-sm`) | 14px | 14px | Body sm |
| Caption | 12px (`text-xs`) | 12px | 12px | Caption |
| CTA button | 16px (`text-base`) | 18px (`text-lg`) | 18px (`text-lg`) | Body lg |
### 3. Image Behavior
| Image type | Mobile | Tablet | Desktop |
|-----------|--------|--------|---------|
| Hero background | Cover, center crop, 60vh min | Cover, 70vh | Cover, 80vh or contained |
| Card icon | 48px (w-12) | 56px (w-14) | 64px (w-16) |
| Team avatar | 48px (w-12) | 56px (w-14) | 64px (w-16) |
| Gallery image | Full width, 3:2 aspect | 2-col, 4:3 | 3-col masonry |
| Map embed | Full width, 250px h | Full width, 350px h | Full width, 400px h |
| Decorative illustrations | Hidden | 50% opacity, smaller | Full display |
### 4. Navigation Adaptation
| Element | Mobile | Tablet | Desktop |
|---------|--------|--------|---------|
| Primary nav | Hamburger → slide-out menu | Hamburger → slide-out | Horizontal inline links |
| Header CTA ("Book a Visit") | Inside mobile menu (full-width) | Inside mobile menu | Visible inline button |
| Logo | Icon + brand name | Icon + brand name | Icon + brand name + tagline |
| Header height | 64px | 72px | 80px |
| Active indicator | Filled bg pill | Filled bg pill | Filled bg pill |
| Footer nav | Stack (single col) | 2-col | Inline or 4-col grid |
### 5. Spacing Adjustments
| Context | Mobile | Tablet (sm) | Desktop (lg) |
|---------|--------|-------------|-------------|
| Page padding (horizontal) | 16px | 24px | 32–48px |
| Page padding (vertical) | 48px (`py-12`) | 64px (`sm:py-16`) | 80px (`lg:py-20`) |
| Section gap | 64px (`space-y-16`) | 80px (`space-y-20`) | 96px (`space-y-24`) |
| Card padding | 24px (`p-6`) | 32px (`p-8`) | 40px (`p-10`) |
| Grid gap | 16px (`gap-4`) | 24px (`gap-6`) | 40px (`gap-10`) |
| Button padding | `px-6 py-3` | `px-8 py-4` | `px-10 py-5` |
| Hero top/bottom | `py-12` | `py-16` | `py-20` |
### 6. Content Prioritization
| Content | Mobile | Tablet | Desktop |
|---------|--------|--------|---------|
| Hero microcopy | Show (truncate if needed) | Show | Show |
| Secondary CTA | Stack below primary | Inline next to primary | Inline |
| Feature bullets (3rd bullet) | Show all 3 | Show all 3 | Show all 3 |
| Testimonial 3rd card | Hidden or in carousel | Visible | Visible |
| Trust signal labels | Numbers only, hide label text | Numbers + short label | Numbers + full label |
| FAQ answers | Shorter (collapse long) | Full | Full |
| Footer social icons | Show | Show | Show |
| Footer legal links | Stack | Inline | Inline |
| Decorative gradients | Simpler (fewer stops) | Medium | Full complexity |
| WhatsApp floating CTA | Fixed bottom-right, always visible | Fixed bottom-right | Hidden (in-page CTA instead) |
## Output Format: Responsive Decision Matrix
When producing specs, use this table format:
```markdown
## [Page Name] — Responsive Decision Matrix
| Section | Mobile (0–639) | Tablet (640–1023) | Desktop (1024+) | Notes |
|---------|---------------|-------------------|-----------------|-------|
| Header | Hamburger, 64px h | Hamburger, 72px h | Inline nav, 80px h, CTA button | Sticky, shrinks on scroll |
| Hero | text-5xl, stack CTAs, full-width | text-6xl, inline CTAs | text-7xl, inline CTAs, max-w-4xl | Center-aligned all |
| Features | 1-col stack, p-6 | 2-col grid, p-8 | 3-col grid, p-10 | gap-4 → gap-6 → gap-10 |
| ... | ... | ... | ... | ... |
```
## Handoff Formats
### → frontend-architect (Tailwind classes)
```tsx
// Pattern: mobile-first, then override at breakpoints
<h1 className="text-5xl sm:text-6xl lg:text-7xl">
<div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-4 md:gap-6 lg:gap-10">
<div className="p-6 sm:p-8 lg:p-10">
<nav className="hidden lg:flex"> {/* desktop nav */}
<button className="lg:hidden"> {/* mobile hamburger */}
```
### → figma-prompt-engineer
```
"Mobile (375px): Single column stack, 16px padding, hamburger nav,
40px headline, full-width stacked buttons, swipeable testimonial carousel.
Tablet (768px): 2-column grid, 24px padding, 48px headline,
inline CTA buttons, 2-col testimonials.
Desktop (1440px): 3-column grid, 32px padding, max-width 1280px centered,
horizontal nav with CTA button, 56px headline, 3-col testimonials."
```
### → animation-designer
```
Mobile: disable parallax, simpler stagger (80ms), no hover states (touch only)
Tablet: enable parallax at 0.2× speed, standard stagger
Desktop: full parallax at 0.3×, hover states, sticky header shrink
```
## Rules
- **Mobile-first always** — base styles are mobile, enhance upward with `sm:`, `md:`, `lg:`, `xl:`
- **Touch targets** — minimum 44×44px on mobile, 36px acceptable on desktop
- **No horizontal scroll** — every layout must fit within viewport width
- **Test at**: 375px (iPhone SE), 390px (iPhone 14), 768px (iPad), 1024px (laptop), 1440px (desktop)
- **Content never hidden completely** — demote to accordion/carousel on mobile, don't delete
- Images must specify `loading="lazy"` below the fold
- Use `prefers-reduced-motion` awareness from animation-designer
## Reference
Per-page decision matrices, full typography scale, and component responsive specs: **[reference.md](reference.md)**.Related Skills
app-analytics-strategist
Expert digital data analytics consultant for designing and implementing data-driven growth strategies for mobile and digital applications. Use this skill when users need help with app analytics strategy, metrics selection, analytics framework implementation, cohort analysis, user segmentation, A/B testing, customer journey mapping, retention optimization, or choosing analytics tools. Applies to product managers, growth teams, and developers building data-driven applications across all platforms and industries seeking to optimize user engagement, retention, and revenue through analytics.
responsive-design-patterns
Mobile-first responsive design patterns with breakpoints, fluid layouts, and adaptive components
applying-responsive-standards
Rules for mobile-first responsive design using Tailwind CSS. Use on every UI component to ensure cross-device compatibility.
frontend-responsive
Implement mobile-first responsive designs with fluid layouts, breakpoints, relative units, and touch-friendly interfaces that work across all device sizes. Use this skill when writing or modifying React components (.tsx, .jsx files), when implementing CSS or Tailwind responsive utilities (sm:, md:, lg:, xl: breakpoints), when working on layout components, navigation menus, grid systems, when optimizing for mobile devices, tablets, or desktop screens, when implementing media queries, when ensuring touch-friendly UI elements, or when testing cross-device compatibility.
Frontend Responsive Design Standards
Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that works across all screen sizes. Use this skill when creating or modifying UI layouts, responsive grids, breakpoint styles, mobile navigation, or any interface that needs to adapt to different screen sizes. Apply when working with responsive CSS, media queries, viewport settings, flexbox/grid layouts, mobile-first styling, breakpoint definitions (mobile, tablet, desktop), touch target sizing, relative units (rem, em, %), image optimization for different screens, or testing layouts across multiple devices. Use for any task involving multi-device support, responsive design patterns, or adaptive layouts.
content_strategist
Creates high-quality, SEO-optimized content that ranks in search engines. Applies on-page SEO best practices, keyword optimization, and content structure for maximum visibility and engagement.
architecture-strategist
Use this agent when analyzing code changes from an architectural perspective, evaluating system design decisions, or ensuring changes align with established architectural patterns. Triggers on requests like "architecture review", "design evaluation", "system architecture analysis".
design_responsive
Breakpoints, fluid typography, container queries ve modern CSS features.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
apple-health-fitness
Query Health and Fitness data from Apple Health app including activity, workouts, heart rate, sleep, and health metrics. Use when user asks about health stats, fitness activity, workouts, sleep data, or health metrics.
apple-app-store-agent
Comprehensive agent for preparing and generating all assets needed for Apple App Store submission. Use when user needs to prepare an iOS/iPadOS/macOS app for App Store release, including generating app metadata (descriptions, promotional text, keywords), creating app icons, designing screenshots, preparing privacy policy URLs, and organizing fastlane-compatible folder structures. Triggers on requests like "prepare my app for App Store", "create App Store screenshots", "generate app description", "make app icon", or "set up fastlane metadata".
appium
Provides comprehensive guidance for Appium mobile testing including mobile app automation, element location, gestures, and cross-platform testing. Use when the user asks about Appium, needs to test mobile applications, automate mobile apps, or write Appium test scripts.