frontend-ui

Build frontend UIs with HTML5, CSS3, and Tailwind CSS following accessibility and performance best practices. Use when creating responsive layouts, styling with Tailwind CSS, implementing accessible f

SKILL.md

GitHub

Frontend/UI Development

Purpose: Production-ready frontend development standards for HTML, CSS, Tailwind CSS, and responsive design. Audience: Frontend engineers building web interfaces with modern HTML/CSS and utility-first frameworks. Standard: Follows github/awesome-copilot frontend development patterns.


When to Use This Skill

  • Building responsive web layouts with HTML5 and CSS3
  • Styling with Tailwind CSS utility classes
  • Implementing accessible web forms
  • Optimizing frontend loading performance
  • Creating common UI layout patterns

Prerequisites

  • HTML5 and CSS3 fundamentals
  • Node.js installed for Tailwind CSS build tools

Quick Reference

Need Solution Pattern
Responsive layout Mobile-first with Tailwind flex md:grid grid-cols-3
Semantic HTML Use proper elements <nav>, <main>, <article>
Accessibility ARIA labels + keyboard nav aria-label="Close menu"
Color contrast WCAG AA minimum (4.5:1) Use color tools for validation
Typography Tailwind text utilities text-base md:text-lg
Spacing Consistent Tailwind scale p-4 md:p-6 lg:p-8

HTML5 Semantic Elements

<!-- [PASS] GOOD: Semantic HTML structure -->
<!DOCTYPE html>
<html lang="en">
<head>
 <meta charset="UTF-8">
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
 <title>Page Title</title>
</head>
<body>
 <!-- Navigation -->
 <nav class="bg-white shadow-md">
 <ul class="flex space-x-4">
 <li><a href="#home">Home</a></li>
 <li><a href="#about">About</a></li>
 </ul>
 </nav>

 <!-- Main content -->
 <main class="container mx-auto px-4 py-8">
 <article class="prose lg:prose-xl">
 <h1>Article Title</h1>
 <p>Content goes here...</p>
 </article>
 
 <aside class="mt-8">
 <h2>Related Content</h2>
 </aside>
 </main>

 <!-- Footer -->
 <footer class="bg-gray-800 text-white p-6">
 <p>&copy; 2026 Company Name</p>
 </footer>
</body>
</html>

<!-- [FAIL] BAD: Non-semantic divs -->
<div class="nav">
 <div class="nav-item">Home</div>
</div>
<div class="content">
 <div class="post">...</div>
</div>

Common Pitfalls

Issue Problem Solution
Non-semantic HTML Using <div> for everything Use <nav>, <main>, <article>, <section>
Missing alt text Images without descriptions Always add descriptive alt attributes
Poor contrast Text hard to read Use WCAG AA contrast ratio (4.5:1)
No focus states Keyboard users can't navigate Add visible focus indicators
Fixed widths Not responsive Use relative units and Tailwind breakpoints
Inline styles Hard to maintain Use Tailwind utilities or CSS classes

Resources


See Also: Skills.md - AGENTS.md

Last Updated: January 27, 2026

Troubleshooting

Issue Solution
Tailwind classes not applying Check purge/content config in tailwind.config.js includes your template files
Accessibility audit failures Add ARIA labels, ensure color contrast ratio >= 4.5:1, test keyboard navigation
Layout breaks on mobile Use mobile-first responsive design, test with browser dev tools responsive mode

References