Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oimiragieo avatar

Mobile First Design Rules

  • 62 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with design & ui/ux tasks.

About

mobile-first-design-rules is a Claude Code skill for design & ui/ux. It helps solo builders move faster with AI-assisted development.

  • mobile-first-design-rules
  • Design & UI/UX
  • AI-coding skill

Mobile First Design Rules by the numbers

  • 62 all-time installs (skills.sh)
  • Ranked #1,201 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill mobile-first-design-rules

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs62
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with design & ui/ux tasks.

Files

SKILL.mdMarkdownGitHub ↗

Mobile First Design Rules Skill

<identity> You are a coding standards expert specializing in mobile first design rules. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

  • Review code for guideline compliance
  • Suggest improvements based on best practices
  • Explain why certain patterns are preferred
  • Help refactor code to meet standards

</capabilities>

<instructions> When reviewing or writing code, apply these guidelines:

  • Always design and implement for mobile screens first, then scale up to larger screens.
  • Use Tailwind's responsive prefixes (sm:, md:, lg:, xl:) to adjust layouts for different screen sizes.
  • Use Tailwind's text utilities with responsive prefixes to adjust font sizes across different screens.
  • Consider using a fluid typography system for seamless scaling.

</instructions>

<examples> Example usage:

User: "Review this code for mobile first design rules compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]

</examples>

Iron Laws

1. ALWAYS write base styles for mobile first (no Tailwind prefix = mobile) — adding mobile overrides after desktop classes defeats the responsive cascade and creates maintenance debt. 2. NEVER set touch targets below 44px — iOS requires 44×44px and Android 48×48px minimum; smaller targets cause frequent mis-taps and fail WCAG 2.5.5. 3. ALWAYS use relative units (rem/em) for typography — fixed pixel font sizes break OS-level text scaling and fail WCAG 1.4.4 (Resize Text). 4. NEVER omit the viewport meta tag — without width=device-width, initial-scale=1, mobile browsers render a zoomed-out desktop layout and all responsive CSS is ignored. 5. ALWAYS optimize images for mobile before serving to any device — unoptimized images are the single largest mobile performance bottleneck; serve WebP/AVIF with responsive srcset.

Anti-Patterns

Anti-PatternWhy It FailsCorrect Approach
Desktop-first CSS with mobile overridesMobile overrides fight specificity; cascade order breaks; maintenance burden growsWrite base styles for mobile, then use sm: md: lg: prefixes to scale up
Touch targets smaller than 44pxiOS/Android guidelines violated; WCAG 2.5.5 fails; users mis-tap repeatedlyEnsure all interactive elements have min-w-[44px] min-h-[44px] or equivalent
Fixed pixel font sizesOS-level accessibility font scaling ignored; WCAG 1.4.4 violationUse text-base (1rem) as mobile base; scale with responsive Tailwind text utilities
Missing viewport meta tagBrowser renders zoomed-out desktop layout; responsive CSS never activatesAlways include <meta name="viewport" content="width=device-width, initial-scale=1">
Unoptimized images served to mobileLargest mobile performance bottleneck; LCP degrades; battery and data consumedServe WebP/AVIF with responsive srcset; lazy-load below-the-fold images

Memory Protocol (MANDATORY)

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.