responsive-design
Skill0 starsChanged 3 days agoMITView on GitHub
Adapt layouts and interactions to available space and input modes without hiding essential content or functionality.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- Above-the-Fold-Studio/designmd-skillstheir own version, first seen Nov 1, 2026
- smiling66652/workbuddy-skill-toolkitstheir own version, first seen Nov 1, 2026
- ryanschue/automated-product-engineertheir own version, first seen Nov 1, 2026
- eumateusalex/Template-OStheir own version, first seen Oct 20, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- itsyasirkhandev/skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use visual-hierarchy, web-component-design and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
launchapp-devSkillvisual-hierarchy
Establish clear visual hierarchy through size, weight, color, spacing, and positioning.
Also in 3 projects that use this
Aver005Skillweb-component-design
Master React, Vue, and Svelte component patterns including CSS-in-JS, composition strategies, and reusable component architecture. Use when building UI component libraries, designing component APIs, or implementing frontend design systems.
Also in 3 projects that use this
CodeWithBehnamSkillaccessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
Also in 3 projects that use this
- CodeWithBehnamSkill
visual-design-foundations
Apply typography, color theory, spacing systems, and iconography principles to create cohesive visual designs. Use when establishing design tokens, building style guides, or improving visual hierarchy and consistency.
Also in 3 projects that use this
wpankSkilldesign-system-patterns
Foundational design system architecture — token hierarchies, theming infrastructure, token pipelines, and governance. Use when creating design tokens, implementing theme switching, setting up Style Dictionary, or establishing multi-brand theming. Triggers on design tokens, theme provider, Style Dictionary, token pipeline, multi-brand theming, CSS custom properties architecture.
Also in 3 projects that use this
rastianSkillinteraction-design
Apply interaction design (IxD) principles and frameworks to product and service design work. Use this skill when designing or evaluating interaction flows, micro-interactions, feedback mechanisms, affordances, mental models, component states, response time, animation and transitions, error recovery, input validation, task flows, or navigation patterns. Core audiences: product designers, UX designers, UI designers, service designers, and interaction designers working on digital products and services. Trigger on: interaction flow, micro-interaction, affordance, feedback design, state design (hover/focus/error/loading/empty), response time, transition, animation, mental model, task flow, user flow, navigation design, interaction spec, handoff annotation, gesture, input validation, error state, loading state, empty state, system feedback, signifier, design review, interaction audit, IxD principles.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- epam/ai-dial-chat★ 501same name
- Mindrally/skills★ 275same name
- sunflowermm/XRK-AGT★ 140same name
- nahid-sparktales/agent-dispatcher★ 59same name
- launchapp-dev/animus-cli★ 39same name
- MiladJoodi/skills★ 24same name
- DigitalExplorers/agent-skills★ 12same name
- wpank/ai★ 11same name
- lotfb86/web-design-skills★ 9same name
- itsyasirkhandev/skills★ 4same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- image-art-directionSkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- saas-dashboardSkill
- security-engineeringSkill
- super-admin-panelSkill
- testing-and-qualitySkill
- unslop-engineSkill
- ux-researchSkill
- visual-designSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 30 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for new or changed web layouts, navigation, tables, dialogs, forms, and other interfaces that must work across viewport sizes.
- Distinctive: line 15
Do not equate responsive design with shrinking desktop content or adding breakpoints without testing actual content and task behavior.
- Distinctive: line 25
Start with content order and priority.
- Distinctive: line 27
Use fluid sizing and existing breakpoints before adding arbitrary device-specific rules.
- Distinctive: line 32
Check menus, dialogs, forms, charts, and long labels, not just the hero.
- Distinctive: line 33
Test keyboard and touch interactions at narrow, medium, and wide widths.
- Distinctive: line 37
Do not remove essential information on small screens without an alternative.
- Distinctive: line 39
Avoid fixed heights for content that can wrap or localize.
- Distinctive: line 41
Ensure zoom and text resizing do not clip controls.
- Distinctive: line 57
Test real content at narrow and wide sizes, zoom, keyboard, touch, overflow, focus order, and all essential actions.
“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Responsive Design
When to use
Use for new or changed web layouts, navigation, tables, dialogs, forms, and other interfaces that must work across viewport sizes.
When not to use
Do not equate responsive design with shrinking desktop content or adding breakpoints without testing actual content and task behavior.
Inputs and assumptions
Identify supported viewport ranges, touch and keyboard use, content variation, existing breakpoints, and browser support.
Workflow
- Start with content order and priority; decide what may wrap, reflow, scroll, collapse, or move.
- Use fluid sizing and existing breakpoints before adding arbitrary device-specific rules.
- Preserve action visibility, readable text, and adequate targets.
- For wide data tables, choose a deliberate strategy such as prioritized columns, horizontal scrolling with cues, or a detail view.
- Check menus, dialogs, forms, charts, and long labels, not just the hero.
- Test keyboard and touch interactions at narrow, medium, and wide widths.
Decision rules
- Do not remove essential information on small screens without an alternative.
- Avoid fixed heights for content that can wrap or localize.
- Focus order must follow the visual and task order.
- Ensure zoom and text resizing do not clip controls.
Example
A dense table may retain a few decision-critical columns on mobile and open the full record in a detail page; hiding arbitrary columns without telling the user is not acceptable.
Common failures
- Horizontal page overflow from fixed widths.
- Desktop-only hover controls.
- Mobile navigation that traps focus or obscures the current location.
Validation
Test real content at narrow and wide sizes, zoom, keyboard, touch, overflow, focus order, and all essential actions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.