
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-rulesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 62 |
|---|---|
| repo stars | ★ 36 |
| Last updated | July 14, 2026 |
| Repository | oimiragieo/agent-studio ↗ |
What it does
Helps with design & ui/ux tasks.
Files
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-Pattern | Why It Fails | Correct Approach |
|---|---|---|
| Desktop-first CSS with mobile overrides | Mobile overrides fight specificity; cascade order breaks; maintenance burden grows | Write base styles for mobile, then use sm: md: lg: prefixes to scale up |
| Touch targets smaller than 44px | iOS/Android guidelines violated; WCAG 2.5.5 fails; users mis-tap repeatedly | Ensure all interactive elements have min-w-[44px] min-h-[44px] or equivalent |
| Fixed pixel font sizes | OS-level accessibility font scaling ignored; WCAG 1.4.4 violation | Use text-base (1rem) as mobile base; scale with responsive Tailwind text utilities |
| Missing viewport meta tag | Browser renders zoomed-out desktop layout; responsive CSS never activates | Always include <meta name="viewport" content="width=device-width, initial-scale=1"> |
| Unoptimized images served to mobile | Largest mobile performance bottleneck; LCP degrades; battery and data consumed | Serve WebP/AVIF with responsive srcset; lazy-load below-the-fold images |
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.mdAfter completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
Invoke the mobile-first-design-rules skill and follow it exactly as presented to you
'use strict';
/**
* Post-execute hook for mobile-first-design-rules
* Auto-generated by enterprise-bundle-scaffolder
*
* Records metrics after skill execution.
*/
function postExecute(_context) {
// Record execution metrics
return { ok: true, skill: 'mobile-first-design-rules' };
}
module.exports = { postExecute };
'use strict';
/**
* Pre-execute hook for mobile-first-design-rules
* Auto-generated by enterprise-bundle-scaffolder
*
* Validates inputs before skill execution.
*/
function preExecute(context) {
// Validate skill invocation context
if (!context || typeof context !== 'object') {
return { allow: true, message: 'mobile-first-design-rules: no context to validate' };
}
return { allow: true };
}
module.exports = { preExecute };
---
description: Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
globs: **/*.{tsx,jsx}
---
- 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.Research Requirements
- Use Exa first for current best practices.
- Use WebFetch/arXiv fallback when Exa is insufficient.
- Capture constraints and map them to hooks/rules/schemas/workflows.
mobile-first-design-rules Rules
Purpose
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
Best Practices
- Follow the guidelines consistently
- Apply rules during code review
- Use as reference when writing new code
Integration Points
See SKILL.md for complete documentation.
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "mobile-first-design-rulesInput",
"description": "Input schema for Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.",
"type": "object",
"additionalProperties": true,
"properties": {
"target": {
"type": "string",
"description": "Target file or path for the skill to operate on"
},
"options": {
"type": "object",
"description": "Additional options for skill execution",
"additionalProperties": true
}
}
}
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "mobile-first-design-rulesOutput",
"type": "object",
"additionalProperties": true,
"properties": {
"ok": {
"type": "boolean"
},
"summary": {
"type": "string"
}
}
}
#!/usr/bin/env node
/**
* mobile-first-design-rules - Rule-based Skill
* Converted from: mobile-first-design-rules.mdc
*/
const fs = require('fs');
const path = require('path');
// Parse arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
if (args[i].startsWith('--')) {
const key = args[i].slice(2);
const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
options[key] = value;
}
}
if (options.help) {
console.log(`
mobile-first-design-rules - Code Guidelines Skill
Usage:
node main.cjs --check <file> Check a file against guidelines
node main.cjs --list List all guidelines
node main.cjs --help Show this help
Description:
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
`);
process.exit(0);
}
if (options.list) {
console.log('Guidelines for mobile-first-design-rules:');
console.log('See SKILL.md for full guidelines');
process.exit(0);
}
console.log('mobile-first-design-rules skill loaded. Use with Claude for code review.');
mobile-first-design-rules Implementation Template
Goal
- Define target outcome and acceptance criteria.
TDD
1. Red 2. Green 3. Refactor
Verification
- lint
- format
- targeted tests