‹ 首页

frontend-development

@avibebuilder · 收录于 1 周前

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.

适合你,如果你需要处理 React/Next.js 前端页面或组件的构建、调试与优化

/ 下载安装
frontend-development.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add avibebuilder/claude-prime/frontend-development
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- avibebuilder/claude-prime/frontend-development
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify avibebuilder/claude-prime/frontend-development
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
106GitHub stars
~1.1K最小装载
~3.9K含声明引用
~7.7K文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 80bcfa4

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

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。