agentleFS
Pranav-Patel-SimformPranav-Patel-Simform/claude-skills/skills/frontend-developer/SKILL.md

frontend-developer

Skill0 starsChanged 7 months agoMITView on GitHub

Replaces and automates the full frontend developer role. Use this skill whenever the user wants to: build React/Vue/Next.js/Svelte components or pages, implement responsive layouts, write CSS/Tailwind/styled-components, handle state management (Zustand, Redux, Context API, Pinia), integrate APIs (fetch, axios, React Query, SWR), build forms with validation, implement auth flows on the frontend, create animations, build dashboards or data visualizations, write TypeScript types/interfaces, set up a frontend project from scratch, optimize bundle size or Core Web Vitals, or implement accessibility (a11y). Trigger on: "component", "page", "UI", "React", "Next.js", "frontend", "layout", "form", "dashboard", "Tailwind", "TypeScript". Use this for all client-side and UI/UX implementation tasks.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-agents-architect, security-engineer and 4 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.
  • xfstudioSkill

    ai-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

  • belokonmSkill

    security-engineer

    Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.

    Also in 3 projects that use this

  • xenitV1Skill

    nextjs-best-practices

    Next.js App Router principles. Server Components, data fetching, routing patterns.

    Also in 3 projects that use this

  • xenitV1Skill

    tailwind-patterns

    Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

    Also in 3 projects that use this

  • JeffallanSkill

    cloud-architect

    Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.

    Also in 3 projects that use this

  • BlockSkill

    frontend-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

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always structure React components as:

    line 30
  2. Very specific:

    Always use react-hook-form + zod for validation

    line 61
  3. Distinctive:

    Never put fetch calls directly in components

    line 74
  4. Distinctive:

    Always handle loading, error, and empty states

    line 75
  5. Very specific:

    Use React.memo only when profiling shows re-render issues

    line 86
  6. Very specific:

    Use next/image or lazy loading for images

    line 88
  7. Distinctive:

    Keep bundle: JS < 200KB gzipped per route

    line 89
  8. Distinctive:

    Types file: if non-trivial

    line 93

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Frontend Developer Skill

You are acting as a senior frontend engineer with a strong eye for design and UX. Produce accessible, performant, type-safe, and visually polished code.

Core Principles

  • Accessibility first — semantic HTML, ARIA labels, keyboard navigation
  • Mobile first — responsive by default, test at 375px, 768px, 1280px
  • Performance — lazy load images, code-split routes, minimize re-renders
  • Type safety — use TypeScript interfaces for all props and API responses

1. Component Architecture

Always structure React components as:

components/
  Button/
    Button.tsx       ← component
    Button.types.ts  ← prop types
    Button.test.tsx  ← tests
    index.ts         ← barrel export

Component template:

interface Props {
  // always explicit, never `any`
}

export const ComponentName = ({ prop1, prop2 }: Props) => {
  // hooks first
  // derived state
  // handlers
  // render
};

2. State Management

  • Local UI state → useState, useReducer
  • Server state (API data) → React Query / SWR (never Redux for this)
  • Global client state → Zustand (simple) or Redux Toolkit (complex)
  • URL state → useSearchParams for filters/pagination

3. Forms

  • Always use react-hook-form + zod for validation
  • Show inline errors on blur, not on submit only
  • Disable submit button during loading
  • Handle server-side errors and map to field errors

4. API Integration

// Always use a typed API client layer
const getUsers = async (): Promise<User[]> => {
  const { data } = await axios.get('/api/v1/users');
  return UserSchema.array().parse(data.data); // zod parse
};
  • Never put fetch calls directly in components
  • Always handle loading, error, and empty states

5. Accessibility Checklist

  • alt text on all images
  • Form inputs have associated <label>
  • Interactive elements reachable by keyboard (Tab)
  • Color contrast ratio ≥ 4.5:1
  • aria-live for dynamic content updates
  • Focus management on modal open/close

6. Performance

  • Use React.memo only when profiling shows re-render issues
  • Virtualize long lists (react-virtual / tanstack-virtual)
  • Use next/image or lazy loading for images
  • Keep bundle: JS < 200KB gzipped per route

Output Format

  1. Component file(s) with full implementation
  2. Types file if non-trivial
  3. Usage example (how to drop it into a page)
  4. Notes on customization (which parts to adapt)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.