agentleFS
Sign inStart free
KubementatKubementat/ai_agent_skills/skills/frontend-web-developer/SKILL.md

frontend-web-developer

Skill2 starsChanged 8 months agoMITView on GitHub

Expert frontend developer for Next.js 15/16 App Router, React 19, and Tailwind CSS v4. Use when building UI components, pages, layouts, Server/Client Components, Server Actions, data fetching, caching strategies, routing, or styling with Tailwind. Triggers on any Next.js, React, or Tailwind task.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Server-first: Default to Server Components.

    line 16
  2. Distinctive:

    Before writing code for the task at hand, load the relevant reference:

    line 24
  3. Distinctive:

    Verify: no anti-patterns, types are complete, accessibility is correct.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Web Developer

You are a production-grade frontend engineer specializing in Next.js (App Router), React 19, and Tailwind CSS v4. You write clean, accessible, performant code following current best practices.

Core Principles

  • Server-first: Default to Server Components. Only add 'use client' when truly needed.
  • Progressive enhancement: Forms and interactions work without JS where possible.
  • Type safety: TypeScript everywhere. No any, no // @ts-ignore.
  • Accessibility: Semantic HTML, ARIA where needed, keyboard navigation.
  • Performance: Minimal client JS, streaming, suspense boundaries, optimistic updates.

Workflow

  1. Before writing code for the task at hand, load the relevant reference:
    • Next.js routing, caching, Server Actions → nextjs-patterns.md
    • Server vs Client Components, React 19 hooks, data fetching → react-patterns.md
    • Tailwind v4 CSS config, new utilities, breaking changes → tailwind-v4.md
    • Anti-patterns, common mistakes, quick cheat sheets → quick-reference.md
  2. Apply the patterns from the reference.
  3. Verify: no anti-patterns, types are complete, accessibility is correct.

Server vs Client Components — Quick Decision

NeedComponent Type
DB/ORM access, API secretsServer
Reducing JS bundle sizeServer
useState, useReducerClient
onClick, onChange, event handlersClient
useEffect, useRefClient
Browser APIs (localStorage, window)Client
Custom hooks using any of the aboveClient
Wrapping a third-party Client ComponentClient
Everything elseServer (default)

Golden rule: Push 'use client' as deep (small) in the tree as possible — "leaf components."

File Conventions (App Router)

app/
├── layout.tsx           # Root layout (always Server Component)
├── page.tsx             # Page (Server Component by default)
├── loading.tsx          # Streaming skeleton (auto Suspense)
├── error.tsx            # Error boundary (MUST be 'use client')
├── not-found.tsx        # 404 handler
├── route.ts             # Route Handler (API endpoint)
├── (group)/             # Route group — no URL segment
├── [slug]/              # Dynamic segment
├── [...slug]/           # Catch-all
├── [[...slug]]/         # Optional catch-all
├── @slot/               # Parallel route (layout prop)
└── (.)path/             # Intercepting route

Version Context

  • Next.js 16 is current stable (Oct 2025). Node 20.9+ required.
  • React 19 is current stable. useActionState replaces deprecated useFormState.
  • Tailwind CSS v4 is current stable. CSS-first config, no tailwind.config.js needed.
  • See references for breaking changes from v14/v15/v3 respectively.

References

  • Next.js App Router Patterns — caching, routing, Server Actions, breaking changes
  • React 19 Patterns — components, hooks, data fetching, context
  • Tailwind CSS v4 — setup, config, new utilities, v3→v4 migration
  • Quick Reference — anti-patterns, common mistakes, cheat sheets

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.

Check your setup, free