Loading...
Loading...
Found 799 Skills
Use when building Next.js 16+ apps with React Server Components. Covers App Router, Cache Components (replacing experimental_ppr), streaming SSR, Server Actions, and React 19 patterns for server-first architecture.
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance in monorepos
Best practices for using the Vercel AI SDK in Next.js 15 applications with React Server Components and streaming capabilities.
Next.js 15 App Router patterns. Trigger: When working with Next.js - routing, Server Actions, data fetching.
Complete Development Guide for Tables, Search, and Pagination Features in React/Next.js Projects. Covers core technologies such as race condition handling, search system implementation, pagination systems, infinite scrolling, CRUD synchronization, Intersection Observer API, and state management selection. Key Features: - Handle race condition issues in asynchronous requests - Implement high-performance search and autocomplete features - Build professional-grade pagination systems and caching strategies - Develop smooth infinite scrolling experiences - Ensure data consistency for CRUD operations - Select the most suitable state management solution Applicable Scenarios: - React/Next.js applications requiring search and pagination features - List display and CRUD operations for large datasets - Need for high-performance infinite scrolling or virtualized lists - Facing complex data management issues such as race conditions and state synchronization - Projects needing to select an appropriate state management solution
This skill should be used when the user asks to "write a Next.js app", "follow React best practices", "optimize a Next.js application", "build with the App Router", or needs guidance on modern React and Next.js patterns for 2025.
Use this skill when building user interfaces in a Next.js project that uses shadcn/ui. Triggers include any request to create, update, or refactor React components, pages, forms, dialogs, tables, or layouts. Also use when the user asks about component installation, styling with Tailwind, form validation, toast notifications, or theming. Use this skill whenever the project stack involves shadcn/ui, Tailwind CSS, React Hook Form, Zod, or Sonner.
Frontend PR checklist for React, Next.js, Vue.js, Tailwind CSS, and React Query (F1–F16). Use when user says "frontend review", "review my React/Vue PR", "check my UI code", working in a frontend repo, or when the diff contains .tsx/.vue/.css files. For the full review workflow, use pr-review.
Use when making single-property CSS or Tailwind visual changes in Next.js App Router projects. Presents a floating control widget on the page so the user can tweak the value before it is persisted. Covers atomic style changes, live preview, and cleanup. Triggers on single CSS value or single Tailwind utility class modifications.
[Pragmatic DDD Architecture] Guide for Next.js 16 Proxy (formerly middleware), app router segments, layout composition, i18n URL localization, cookie management, and redirect strategies between public and protected routes. Use when updating proxy.ts, configuring public vs private environments, modifying the [locale] vs /dashboard routing structure, and appending headers.
Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Next.js app.
Patch, extend, or explain DatoCMS front-end integration code inside an existing web project (Next.js App Router, Nuxt, SvelteKit, Astro, plus React/Vue/Svelte component usage). Use for targeted, per-concern work — adding a draft mode endpoint, wiring Preview Links / Visual Editing flows, fixing Content Link overlays, tuning real-time preview updates/subscriptions, setting up cache-tag invalidation/revalidation flows (Next.js revalidateTag or CDN purge by tags), adding robots/sitemap wiring, or hooking up crawler-safe search integration. Also the go-to skill for framework component/hook wiring with react-datocms, vue-datocms, @datocms/svelte, and @datocms/astro: Image/SRCImage/datocms-image, StructuredText, VideoPlayer (React/Vue/Svelte), SEO/meta helpers (renderMetaTags/toHead/Seo), QuerySubscription/QueryListener realtime patterns, ContentLink components, and Site Search (React/Vue). Prefer this skill whenever the user is modifying a live codebase one concern at a time, asking a framework-specific API question, or mixing several front-end concerns in the same patch.