nextjs-anti-patterns
Common Next.js anti-patterns: useEffect misuse (data fetch, browser detect), useState for server data, Pages Router patterns, serial await, over-using 'use client'.
Découvrez les skills Tests et sécurité, comparez leurs dépôts et consultez leurs instructions.
Common Next.js anti-patterns: useEffect misuse (data fetch, browser detect), useState for server data, Pages Router patterns, serial await, over-using 'use client'.
Vercel AI SDK v5: generateText, streamText, useChat, tool calling (use tool() helper + inputSchema), embeddings. v5: sendMessage vs append, message.parts, string models.
Client component onClick/form → Server Action → set cookie. 'use client' calls 'use server' action using cookies() from next/headers.
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
Next.js App Router (13+). Migrating from Pages, file conventions (layout, page, loading, error), routing patterns, metadata, generateStaticParams.
Server Component navigation: for links, redirect() for conditional redirects. NO 'use client' needed for static links or server redirects.
Fetch data using URL parameter. Create app/[id]/page.tsx, await params to get ID, fetch API, render. Server Component (no 'use client').
Next.js dynamic routes with [param] folders. Access via params prop (Server) or useParams() (Client). Next.js 15+: await params. Default to app/[id]/ not app/products/[id]/.
Advanced Next.js routing: Route Handlers (API routes), Server Actions ('use server'), Parallel Routes (@slot), Intercepting Routes ((.)), Error Boundaries, Draft Mode, Suspense streaming.
Server vs Client Components in Next.js App Router. Server is default (async, cookies, headers, searchParams). Client needs 'use client' (hooks, events, browser APIs).
Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
useSearchParams hook in Next.js. REQUIRES 'use client' + Suspense wrapper. Read URL query params: .get(), .getAll(), .has(). Update via router.push().
Error handling with @julian-i/try-error. Wrap throwable code with tryPromise (async) or tryThrow (sync). Forces reflection on error types, handling location, audience, and recovery.
Research topics by verifying actual source content. Use when asked to research or study links and documentation.
Code review with Codex CLI. Use for PR review, diff review, code analysis, or when user says "codexでレビュー", "コードレビュー".
GraphQL development best practices. Use when working with fragments, queries, mutations, or .graphql files.
Git workflow conventions. Use when committing, creating branches, or making pull requests.
Create or update Claude Code skills. Use when user wants to create a new skill, update an existing skill, or needs guidance on skill design.
Browser automation skill. ALWAYS use this for ANY browser-related task including ブラウザテスト, ブラウザ操作, E2Eテスト, page check, localhost, screenshot.
Setup browser testing configuration. Use when setting up test credentials and organization info for E2E testing.
Act as a versatile professional, seamlessly switching between Document Custodian (Signer), Software Programmer, and UX/UI Designer based on the user's task. This skill enables Claude to manage and certify offic...
Example skill providing background knowledge and context
Perform an expert frontend code review directly from a GitHub Pull Request using gh CLI.
A CLI tool that searches inside class and className attributes and matches against each class name individually. Use this instead of grep when searching or replacing class names.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.