Loading...
Loading...
Found 106 Skills
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work through a flood of blocking-prerender / instant validation errors, run the `cache-components-instant-false` codemod, or decide between opting routes out with `export const instant = false` and fixing them in place.
Gouvernance d'URL multi-scopes (produits/activités) pour sites modernes, avec canonisation serveur, SEO/crawl, migrations safe, et implémentation Next.js App Router. À utiliser quand tu conçois, refactors, ou migres des routes/URLs (pages publiques/privées/techniques) pour garder un pattern stable, scalable et testable.
Zustand v5 state management for Next.js 16 App Router. Use when implementing global state, stores, persist, hydration, or client-side state in Client Components.
Next.js 15 App Router patterns: Server Components, Server Actions, data fetching, middleware. Trigger: When building Next.js apps, working with app router, server/client components, or API routes.
Expert guide for Next.js 14+ App Router projects. Use when building features, routing, server/client components, forms, layouts, or debugging Next.js-specific issues.
Guide for Next.js App Router dynamic routes and pathname parameters. Use when building pages that depend on URL segments (IDs, slugs, nested paths), accessing the `params` prop, or fetching resources by identifier. Helps avoid over-nesting by defaulting to the simplest route structure (e.g., `app/[id]` instead of `app/products/[id]` unless the URL calls for it).
This skill should be used when the user asks about "Server Components", "Client Components", "'use client' directive", "when to use server vs client", "RSC patterns", "component composition", "data fetching in components", or needs guidance on React Server Components architecture in Next.js.
Refatore apps ou sites setoriais de qualquer tecnologia de origem para o padrão do repositório Elinsa. Use ao migrar projetos externos, legados, protótipos, HTML/CSS/JS puro, jQuery, Vue, Angular, React/Vite, PHP, Laravel, WordPress, templates server-side, sistemas de almoxarifado, formulários de pedidos ou ferramentas internas para Node 26+, pnpm, Next.js 16+ App Router, React Server Components, Tailwind 4+, Biome, shadcn/radix no preset Elinsa, React Hook Form, Zod, Better Auth e Drizzle ORM com PostgreSQL. Use também quando o projeto não tiver Git/versionamento, vier de ZIP/pasta local ou tiver sido criado em Lovable/no-code/AI builder: primeiro transforme em repositório GitHub revisável, depois migre para submissão à TI e futura integração como rotas, páginas, APIs ou componentes.
Refactor Next.js code to improve maintainability, readability, and adherence to App Router best practices. Identifies and fixes God Components, prop drilling, inappropriate 'use client' usage, outdated Pages Router patterns, missing Suspense boundaries, incorrect caching strategies, and useEffect data fetching anti-patterns. Applies modern Next.js 15 patterns including Server Components, Client Components, Server Actions, streaming with Suspense, proper caching strategies, Container-Presentational pattern, layout composition, parallel routes, and intercepting routes.
Debug Next.js issues systematically. Use when encountering SSR errors, hydration mismatches like "Text content did not match", routing issues with App Router or Pages Router, build failures, dynamic import problems, API route errors, middleware issues, caching and revalidation problems, or performance bottlenecks. Covers both Pages Router and App Router architectures.