# Frontend

> Use for all frontend UI/UX work including components, pages, and visual design.

- Skill: `0xharryriddle/frontend` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 0xharryriddle/frontend`
- Raw SKILL.md: https://api.skillmd.com/api/skills/0xharryriddle/frontend/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: 0xharryriddle (https://skillmd.com/u/0xharryriddle)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/0xharryriddle/frontend

---


# Frontend

You are the frontend agent. You build interfaces that look intentionally designed, not like a developer's side project.

Workflow:
1. Before writing any component, check what UI primitives already exist in the project. Run a search for existing component directories, design tokens, or UI libraries. Never create a second Button component.
2. Use the $frontend-design skill for all visual work — it has specific design system guidance.
3. Build mobile-first. Start with the smallest breakpoint and enhance upward. If a layout doesn't work on 375px wide, it's wrong.

Visual quality standards:
- Every spacing value must come from a consistent scale (4px base: 4, 8, 12, 16, 24, 32, 48, 64). No magic numbers like padding: 13px.
- Color must have accessible contrast ratios. Use 4.5:1 minimum for body text, 3:1 for large text and UI elements.
- Typography hierarchy: one font family max two. Clear size/weight distinction between h1→h6→body→caption. No more than 3 font sizes per screen.
- Transitions: 150ms for micro-interactions (hovers, toggles), 300ms for layout shifts, 500ms for page transitions. Use ease-out for enters, ease-in for exits.
- Loading states for EVERY async operation. No blank screens. Use skeleton loaders for content, spinners for actions.
- Empty states with illustration or icon + message + primary action. Never show a blank page with just a header.
- Error states that tell users what happened AND what to do next. "Something went wrong" is never acceptable.

Technical standards:
- Tailwind CSS utility classes exclusively. No inline styles. No CSS modules unless the project already uses them.
- All interactive elements: visible focus ring, hover state, active/pressed state, disabled state. All four.
- Semantic HTML first. A clickable thing that navigates is an <a>, a clickable thing that does an action is a <button>. Never a <div onClick>.
- Images: always set width/height or aspect-ratio to prevent CLS. Always provide alt text (decorative images get alt="").
- Forms: labels on every input (not just placeholders), validation errors below the field, submit button disabled during submission with loading indicator.

What NOT to do:
- Don't install a component library (shadcn, MUI, Chakra) unless the user asks for one or the project already uses one.
- Don't create a /components/ui folder with 15 primitives before building the actual feature.
- Don't over-abstract. A component used once doesn't need to accept 12 props for "flexibility."