Skip to content
Skills Library
Programming · Building & coding

frontend-development

/frontend-development

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a

Licence
MIT
Last repository change
17.05.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
17
Scripts
0
HTML comments
0
URLs in SKILL.md
13
Deprecation

No signals detected. Repository changed on 17.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a

Original author description

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a

How it works

  1. Architecture Decisions
  2. Gotchas
  3. Quick Start
  4. References
  5. Official Resources
Original SKILL.md headings · 73 lines, 619 words
SKILL.md preview
---
name: frontend-development
description: "Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps."
---

# Frontend Development

Project-specific patterns for React/Next.js/TypeScript frontend work.

## Architecture Decisions

### Server-First Boundaries
Start with Server Components. Only add `'use client'` when you need interactivity, state, or browser APIs. Extract only the interactive leaf — not the entire page or section.

### Colocation Over Centralization
Types, hooks, and utilities that serve one feature live in that feature's directory. Only truly shared code goes in global directories.

### Composition Over Customization
Compose existing components rather than adding props/variants. shadcn/ui components are meant to be copied and modified. Build up from primitives.

### Data Flows Down, Events Flow Up
Server fetches data and passes it as props. Client components handle interactions and call server actions. Never fetch in client components what could be fetched on the server.

## Gotchas

- `'use client'` does NOT mean "runs only in the browser" — it runs on the server during SSR too. It means "include in the client bundle." Putting secrets or DB calls in a `'use client'` file will leak them.
- Importing a Server Component into a Client Component makes it a Client Component. The boundary propagates DOWN. Pass server content as `children` props instead.
- `useEffect` with empty deps fires AFTER paint — use `useLayoutEffect` for DOM measurements that affect layout, but never in Server Components.
- Next.js `fetch()` caches by default in App Router. Add `{ cache: 'no-store' }` or `revalidate: 0` for data that must be fresh. Forgetting this causes stale data bugs that only appear in production.
- Tailwind classes are purged at build time — dynamically constructed class names like `` bg-${color}-500 `` will be missing. Use complete class names or safelist them.
- `key` prop on mapped elements must be stable and unique. Using array index as key causes subtle bugs when list items are reordered, inserted, or deleted.
- `useSearchParams()` requires a `<Suspense>` boundary in Next.js App Router or the entire page becomes client-rendered.
- shadcn/ui components are source code, not a library. After `npx shadcn-ui add`, the component lives in YOUR codebase — modify it directly, don't wrap it.
- React Hook Form's `register()` returns a ref — don't also pass your own `ref` to the same input without merging them.
- `async` Server Components that throw `redirect()` or `notFound()` must NOT be wrapped in try/catch — these work by throwing special errors that Next.js catches upstream.

## Quick Start

1. **Check file structure** — App Router or plain React? Check references below.
2. **Identify the feature boundary** — What feature does this work belong to?
3. **Start with Server Component** — Only add `'use client'` when you hit a wall
4. **Name files specifically** — `login-form.tsx` not `form.tsx`. Must be grep-findable.
5. **Match existing patterns** — Read 2-3 similar files before creating new ones

## References

| When you need... | Read |
|------------------|------|
| File naming, imports, exports | [conventions.md](./references/conventions.md) |
| Next.js App Router patterns | [overview.md](./references/nextjs/overview.md) |
| React component patterns | [overview.md](./references/react/overview.md) |
| TypeScript project patterns | [typescript.md](./references/typescript.md) |
| shadcn/ui + Dice UI usage | [shadcn.md](./references/shadcn.md) |
| Tailwind configuration | [tailwind.md](./references/tailwind.md) |
| Data fetching (tRPC, TanStack, axios) | [overview.md](./references/data-fetching/overview.md) |
| Biome/linter config | [biome.md](./references/biome.md) |

## Official Resources

For general framework docs beyond project-specific patterns, consult:

| Framework | URL |
|-----------|-----|
| Next.js | https://nextjs.org/docs |
| React | https://react.dev |
| TypeScript | https://www.typescriptlang.org/docs |
| Tailwind CSS | https://tailwindcss.com/docs |
| shadcn/ui | https://ui.shadcn.com/docs |
| Dice UI | https://www.diceui.com/docs |
| TanStack Query | https://tanstack.com/query/latest/docs |
| tRPC | https://trpc.io/docs |
| Zustand | https://zustand.docs.pmnd.rs |
| React Hook Form | https://react-hook-form.com |
| Zod | https://zod.dev |
| Biome | https://biomejs.dev |
| nuqs | https://nuqs.47ng.com |
Files in this package (17)
  • SKILL.md 5 KB
  • references/biome.md 5 KB
  • references/conventions.md 2 KB
  • references/shadcn.md 2 KB
  • references/tailwind.md 1 KB
  • references/typescript.md 2 KB
  • references/data-fetching/axios.md 2 KB
  • references/data-fetching/overview.md 1 KB
  • references/data-fetching/tanstack.md 3 KB
  • references/data-fetching/trpc-tanstack.md 2 KB
  • references/nextjs/file-structure.md 2 KB
  • references/nextjs/overview.md 1 KB
  • references/nextjs/patterns.md 2 KB
  • references/react/file-structure.md 3 KB
  • references/react/overview.md 1 KB
  • references/react/patterns.md 4 KB
  • references/react/state.md 2 KB

Versions

RepositoryScoreLicence
This page · avibebuilder/claude-prime90MIT
aws-solutions/konductor100Apache-2.0
nette/agent-plugins100MIT
lubusIN/frappe-skills100MIT
liushikuan63/Qoder-Optimization91MIT

Database snapshot: 13.11.2026 · package version f681dd832b0e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100react-frontend-patterns
    React 19+, TypeScript, Tailwind CSS, shadcn/ui component patterns, accessibility, forms, state management. Use when building or reviewing React components, pages, or frontend architecture.
  • 95senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
  • 100senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
  • 95senior-frontend
    Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
  • 90senior-frontend
    Frontend development for React, Next.js, TypeScript, and Tailwind CSS. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding projects, implementing accessibility, or reviewing frontend code.
  • 100frontend-react
    Professional React development skill covering Next.js, React Server Components, Tailwind CSS, and the React ecosystem. Use this skill when building modern React applications, implementing Next.js features, creating UI components with shadcn/ui, or working with complex state management.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.