frontend-builder — Claude Code skill for React and installation
The frontend-builder skill guides React and Next.js UI work, from component structure to forms and error handling. Use it when starting a web app or deciding how its frontend should be organized.
MIT 134 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill frontend-builder -a claude-codeWhat frontend-builder does
The skill recommends a server-first approach for Next.js, with Server Components as the starting point and client-side interactivity added where needed. It covers component structure, state, data loading, forms, styling, and performance. For single-page apps, it also points to React with Vite.
Its guidance includes Tailwind CSS v4 with shadcn/ui, React Hook Form with Zod, Server Actions, and TanStack Query for client-side caching. It advises keeping state near the components that use it and reserving useEffect for side effects. This skill does not cover backend API design, database schemas, or deployment infrastructure, so it won’t guide those parts of a project.
What it helps with
- choose a starting stack for a React or Next.js app
- split a UI into focused components
- decide where state and data fetching belong
- build a form with schema validation
- handle errors within page sections
Example prompts for the agent
- Plan a Next.js page around Server Components, with client interactivity only where needed.
- Review where this React form should keep its state and how to validate it with Zod.
- Build a page using Tailwind CSS v4 and shadcn/ui, with error boundaries around its feature sections.
How to install frontend-builder
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill frontend-builder -a claude-code2Manually: put the files in place
~/.claude/skills/frontend-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/frontend-builder/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill frontend-builder -a codex2Manually: put the files in place
.agents/skills/frontend-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill frontend-builder -a cursor2Manually: put the files in place
.cursor/skills/frontend-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/frontend-builder2Manually: put the files in place
.github/skills/frontend-builder/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill frontend-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/frontend-builderManually: put the files in place
.devin/skills/frontend-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill frontend-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about frontend-builder
How do I install frontend-builder in Claude Code?
Run npx skills add oakoss/agent-skills --skill frontend-builder -a claude-code. The skill file is at ~/.claude/skills/frontend-builder/SKILL.md.
What does frontend-builder do?
It provides guidance for React and Next.js frontend architecture, including components, state, data fetching, forms, styling, and error handling. It also covers server and client rendering choices.
Can frontend-builder help design backend APIs or database schemas?
No. Its scope is frontend work; it does not cover backend API design, database schemas, or deployment infrastructure.
Source text
SKILL.md · MIT
--- name: frontend-builder description: 'Builds modern React and Next.js frontends. Use when creating web applications, choosing frontend stack, structuring components, implementing UI/UX designs, or setting up project architecture. Use for React, Next.js, Tailwind CSS, shadcn/ui, server components, and component patterns.' license: MIT metadata: author: oakoss version: '1.0' source: 'https://react.dev' --- # Frontend Builder ## Overview Builds maintainable, performant React and Next.js frontends using a server-first architecture. Covers component design, state management, data fetching, forms, styling, and performance optimization. Not for backend API design, database schema, or deployment infrastructure. ## Quick Reference | Pattern | Approach | Key Points | | ---------------- | ----------------------------------------------------------- | ---------------------------------------------------------- | | Framework | Next.js App Router (default), React + Vite (SPAs) | Server-first rendering, file-based routing | | Components | Page, Feature, UI, Layout types | Single responsibility, typed props, composition | | Server vs Client | Server Components default, `'use client'` at leaf nodes | Push interactivity to edges of component tree | | State (local) | `useState`, props, lift to parent | Keep state close to where it is consumed | | State (global) | Context API (theme, auth), Zustand (complex) | Avoid Context for frequently changing values | | Data fetching | Server Components (server), TanStack Query (client) | Server Actions for mutations, `revalidatePath` for cache | | Forms | React Hook Form + Zod, or Server Actions + `useActionState` | Schema validation, optimistic updates with `useOptimistic` | | Styling | Tailwind CSS v4 + shadcn/ui | CSS-first config with `@theme`, OKLCH colors | | Performance | Suspense streaming, code splitting, memoization | `React.lazy()`, `next/dynamic`, selective `memo()` | | Error handling | Error boundaries, `error.tsx` per route | Wrap feature sections, not individual components | ## Common Mistakes | Mistake | Correct Pattern | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | Adding `'use client'` to every component | Default to Server Components; add `'use client'` only for interactivity | | Giant multi-responsibility component | Break into focused sub-components with single purposes | | Placing all state at the top of the component tree | Keep state as close to where it is consumed as possible | | Using `useEffect` to compute derived data | Use `useMemo` for derived values; reserve `useEffect` for side effects | | Missing error boundaries around feature sections | Wrap feature areas with error boundaries to prevent full-page crashes | | Creating API routes for simple mutations | Use Server Actions with `'use server'` for form submissions and mutations | | Passing non-serializable props to Client Components | Props crossing server/client boundary must be serializable (no functions, classes) | | Using `tailwind.config.js` with Tailwind v4 | Use CSS-first configuration with `@theme` directive in CSS file | | Fetching data in Client Components when Server Components suffice | Fetch in Server Components by default; use TanStack Query only when client-side caching is needed | ## Delegation When building frontends, delegate to specialized skills: - `react-patterns` -- React hooks, rendering patterns, and performance optimization - `nextjs` -- Next.js routing, middleware, and deployment configuration - `tanstack-query` -- Client-side data fetching, caching, and mutations - `tanstack-form` -- Complex form handling and field-level validation - `tailwind` -- Tailwind CSS utility patterns and responsive design - `design-system` -- Token hierarchy and component architecture - `performance-optimizer` -- Profiling, bundle analysis, and Core Web Vitals ## References - [Component Architecture](references/component-architecture.md) -- Component types, folder structure, TypeScript patterns, and composition - [Server Components](references/server-components.md) -- Server/client boundary, Server Actions, Suspense streaming, and data flow - [State Management](references/state-management.md) -- useState, Context API, Zustand, and URL state patterns - [Data Fetching](references/data-fetching.md) -- TanStack Query, Server Components data, and cache revalidation - [Forms and Validation](references/forms.md) -- React Hook Form, Zod schemas, Server Actions, and useActionState - [Styling](references/styling.md) -- Tailwind CSS v4, shadcn/ui, CSS-first config, and responsive patterns - [Performance and Errors](references/performance-and-errors.md) -- Memoization, code splitting, Suspense streaming, and error boundaries
© oakoss · MIT · oakoss/agent-skills