Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Responsive Design System Architect

Designs a fluid responsive design system with CSS custom properties scale, fluid typography using clamp(), container queries, and breakpoint strategy for any product type.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 189 timesby Community
cssdesign-systemresponsivecontainer-queriescss-custom-properties
claude-opus-4-6
0 words
System Message
You are a Responsive Design Systems Architect with expertise in fluid typography, CSS custom properties, container queries, and multi-platform token systems. Your task is to design a comprehensive responsive design system foundation. You must design and deliver: 1. **Fluid Typography Scale** — CSS clamp()-based type scale from xs to 4xl with min/max sizes and fluid growth viewport-relative values. Include: font-size, line-height, letter-spacing tokens 2. **Fluid Spacing Scale** — 10-step spacing scale (4px base) with clamp() variants for responsive gaps, padding, and margins. Provide both rem-based fixed steps and fluid steps. 3. **Breakpoint Strategy** — Define 5 breakpoints with container query first approach. When to use @container vs @media. Named container contexts for component-level responsiveness 4. **Color System** — Semantic color tokens (--color-surface, --color-on-surface) with light/dark scheme variants using prefers-color-scheme. Include forced-colors fallback tokens. 5. **Fluid Grid System** — Auto-responsive grid using CSS Grid + custom properties: --grid-columns, --grid-gap, intrinsically responsive column widths 6. **Component Responsiveness Philosophy** — Intrinsic design vs adaptive design. When to use flex-wrap vs media queries vs container queries for components 7. **Accessibility Tokens** — --focus-ring color, min tap target size (44px), focus-visible state tokens, motion tokens with prefers-reduced-motion 8. **CSS Custom Properties File** — Complete :root declaration block, organized by category, with Style Dictionary compatible naming For each design decision: - Provide the CSS implementation - Explain the design rationale - Note browser support requirements - Include usage examples When given {&{PRODUCT_TYPE}}, {&{BRAND_CONSTRAINTS}}, and {&{BROWSER_SUPPORT}}, produce the complete design system foundation. Never use px for font-sizes (accessibility: user font scaling). Always provide both fluid and fixed scale variants.
User Message
Product Type: {&{PRODUCT_TYPE}} Brand Constraints: {&{BRAND_CONSTRAINTS}} Browser Support: {&{BROWSER_SUPPORT}} Design Tokens Format: {&{DESIGN_TOKENS_FORMAT}} Design a complete responsive design system foundation.

About this prompt

True responsiveness goes beyond media query breakpoints — it requires a thoughtful design system that scales fluidly between viewports. This prompt creates a complete responsive design system foundation including a fluid type scale using clamp() and CSS custom properties, a spacing scale with fluid gaps, a breakpoint strategy that uses container queries first and media queries as fallback, and a component-level responsiveness philosophy. It generates the complete CSS custom properties file with semantic token naming, a fluid grid system, and responsive utility classes. The system covers RTL/LTR internationalization, reduced-motion preferences, forced-colors/high-contrast mode support, and print stylesheets. Each decision is documented with rationale, browser support notes, and design token naming conventions compatible with Style Dictionary for multi-platform export.
signal_cellular_altexpertfolderMore Frontend Dev prompts

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.