frontend-developer
Skill9 starsChanged 9 months agoMITView on GitHub
Frontend development expert: React, Vue, Angular, Svelte, CSS/Tailwind, responsive design, accessibility (a11y), performance optimization, state management, component architecture, and browser APIs. Use when: (1) building UI components or pages, (2) implementing responsive layouts, (3) optimizing Core Web Vitals or bundle size, (4) fixing CSS/layout issues, (5) adding client-side interactivity or animations, (6) reviewing frontend code for accessibility or performance. NOT for: backend API logic, database operations, or infrastructure.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- amanuelmamo7/Skillstheir own version, first seen Nov 7, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 6, 2026
- iberi22/skillstheir own version, first seen Oct 15, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Ghosteken/agent-harnesstheir own version, first seen Oct 1, 2026
- romanveselovski/agents-frontend-rulestheir own version, first seen Sep 15, 2026
Used with
Projects with it also use ai-agents-architect, nextjs-best-practices and 2 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.
xfstudioSkillai-agents-architect
Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool use, function calling.
Also in 3 projects that use this
xenitV1Skillnextjs-best-practices
Next.js App Router principles. Server Components, data fetching, routing patterns.
Also in 3 projects that use this
xenitV1Skilltailwind-patterns
Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- Vinix24/vnx-orchestration★ 63same name
- jshsakura/awesome-opencode-skills★ 30same name
- Fandry96/k3-agentic-skills★ 27same name
- xfstudio/skills★ 9same name
- nicolasestrem/antigravity-gemini-skills★ 8same name
- BenjaminG/ai-skills★ 4same name
- marttp/my_agent_skills_I_use★ 4same name
- ai4brands-design/claude-skills★ 2same name
- Ghosteken/agent-harness★ 2same name
- liuchiawei/agent-skills★ 2same name
8 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 repository14 other files it gives its agents.
- ai-ml-engineerSkill
- backend-developerSkill
- cloud-architectSkill
- code-reviewerSkill
- database-administratorSkill
- data-engineerSkill
- devops-engineerSkill
- fullstack-developerSkill
- mobile-developerSkill
- qa-test-engineerSkill
- security-engineerSkill
- senior-java-developerSkill
- system-architectSkill
- tech-leadSkill
The file
Files
Frontend Developer
Expert guidance for building modern, accessible, performant user interfaces.
Core Competencies
1. Component Architecture
Design reusable, composable components following these principles:
Single Responsibility: One component = one purpose
Composition over Inheritance: Compose small components into larger ones
Props Down, Events Up: Unidirectional data flow
Controlled vs Uncontrolled: Know when to use each patternReact Pattern
// Compound component pattern for flexible APIs
function Select({ children, value, onChange }) {
return (
<SelectContext.Provider value={{ value, onChange }}>
<div role="listbox">{children}</div>
</SelectContext.Provider>
);
}
Select.Option = function Option({ value, children }) {
const ctx = useContext(SelectContext);
return (
<div role="option" aria-selected={ctx.value === value}
onClick={() => ctx.onChange(value)}>
{children}
</div>
);
};Vue Pattern
<!-- Composable + slot pattern -->
<template>
<div class="data-table">
<slot name="header" :columns="columns" />
<slot name="row" v-for="row in data" :row="row" :key="row.id" />
<slot name="empty" v-if="!data.length">No data</slot>
</div>
</template>2. State Management Decision Tree
Local UI state (toggle, form input) → useState / ref
Shared between siblings → lift state to parent
App-wide (auth, theme, locale) → Context / Pinia / Redux
Server data (API responses) → TanStack Query / SWR
URL state (filters, pagination) → URL search params
Complex async flows → Zustand / Redux + middleware3. CSS & Layout Strategy
Layout system: CSS Grid (2D) + Flexbox (1D)
Spacing: Use design tokens (--space-1, --space-2, ...)
Typography: Fluid type scale with clamp()
Colors: CSS custom properties + prefers-color-scheme
Responsive: Mobile-first, breakpoint tokens
Animation: prefer-reduced-motion, GPU-composited transformsResponsive Breakpoints
/* Mobile-first approach */
:root {
--bp-sm: 640px;
--bp-md: 768px;
--bp-lg: 1024px;
--bp-xl: 1280px;
}
.container {
width: 100%;
padding-inline: var(--space-4);
}
@media (min-width: 768px) {
.container { max-width: 720px; margin-inline: auto; }
}
@media (min-width: 1024px) {
.container { max-width: 960px; }
}4. Performance Checklist
| Metric | Target | How to Achieve |
| LCP | < 2.5s | Optimize critical rendering path, preload hero image |
| FID/INP | < 200ms | Code-split, defer non-critical JS, use startTransition |
| CLS | < 0.1 | Set explicit dimensions on images/embeds, font-display: swap |
| Bundle Size | < 200KB gzip | Tree-shaking, dynamic imports, analyze with bundler plugin |
| TTI | < 3.5s | Lazy load below-fold, prefetch routes |
Code Splitting Pattern
// Route-level splitting
const Dashboard = lazy(() => import('./pages/Dashboard'));
const Settings = lazy(() => import('./pages/Settings'));
// Component-level splitting
const HeavyChart = lazy(() => import('./components/HeavyChart'));5. Accessibility (a11y) Standards
WCAG 2.1 AA minimum:
- Semantic HTML first (button, nav, main, article)
- ARIA only when native semantics insufficient
- Keyboard navigation: all interactive elements focusable
- Color contrast: 4.5:1 text, 3:1 large text/UI
- Focus indicators: visible, high contrast
- Screen reader: meaningful alt text, aria-labels
- Forms: label + input association, error announcementsTesting a11y
# Automated
npx axe-core/cli http://localhost:3000
npx pa11y http://localhost:3000
# In code
import { axe } from 'jest-axe';
expect(await axe(container)).toHaveNoViolations();6. Build & Tooling
| Tool | Use Case |
| Vite | Dev server + build (fast HMR, ESM-native) |
| Turbopack/webpack | Large monorepo builds |
| ESLint + Prettier | Code quality + formatting |
| Storybook | Component development + visual testing |
| Playwright | E2E browser testing |
| Lighthouse CI | Performance regression in CI |
Quick Commands
# Dev server
npm run dev # Start Vite dev server
npx storybook dev # Start Storybook
# Build & analyze
npm run build # Production build
npx vite-bundle-visualizer # Bundle size analysis
# Testing
npx vitest # Unit tests (watch mode)
npx playwright test # E2E tests
npx lighthouse http://localhost:3000 --view # Performance audit
# Code quality
npx eslint . --fix # Lint + autofix
npx tsc --noEmit # Type check onlyWorkflow
1. Design review → understand specs, breakpoints, interactions
2. Component tree → map UI into component hierarchy
3. Build atoms → small reusable primitives first
4. Compose pages → assemble atoms into features
5. Accessibility pass → keyboard, screen reader, contrast
6. Performance audit → Lighthouse, bundle analysis
7. Cross-browser test → Chrome, Firefox, Safari, mobileReferences
- Framework patterns: See references/framework-patterns.md
- CSS recipes: See references/css-recipes.md
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.

