frontend-component
Create React/Next.js 16 components. Use when building pages, client/server components, forms with useActionState, or UI with shadcn/ui. ALWAYS activate with frontend-design together.
Explorez les skills IA publiés de xmark168 et consultez leurs instructions source.
Skills indexés
12Étoiles des dépôts des skills indexés
60Forks du dépôt
0Moyenne des étoiles par skill indexé
5Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Create React/Next.js 16 components. Use when building pages, client/server components, forms with useActionState, or UI with shadcn/ui. ALWAYS activate with frontend-design together.
Unit tests with Jest + React Testing Library. CRITICAL - Uses Jest (NOT Vitest).
Implement authentication with NextAuth v5. Use when adding login/logout, checking sessions, protecting API routes, server actions, or pages.
Create implementation plans for Next.js features. Use when breaking down user stories into tasks, planning feature implementation, or decomposing complex requirements.
Write integration tests with Jest for API routes and database operations. Use when testing backend logic, API endpoints, or data layer.
Manage client-side state with Zustand. Use when building shopping cart, user preferences, theme toggle, UI state, or any cross-component shared state with localStorage persist.
Create Next.js 16 API Route Handlers. Use when building REST endpoints (GET, POST, PUT, DELETE), implementing CRUD operations, or creating authenticated APIs with Zod validation.
Define TypeScript types, interfaces, and type utilities. Use when creating type definitions, DTOs, API response types, or component props.
Create Prisma schema models with relations and indexes. Use when designing database schemas, adding models, or defining entity relationships.
Create robust, error-proof Prisma seed scripts with comprehensive error handling and validation.
Review code for quality, security, performance, and best practices. Use when reviewing changes before commit, auditing code for issues, or suggesting improvements.
Debug code errors systematically. Use when analyzing error messages, fixing bugs, resolving build/lint errors, or troubleshooting runtime issues.
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é.