alexander-danilenko/nextjs-developer
skills/nextjs-developer/SKILL.md
Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.
$ install --global
skillsauthnpx skillsauth add alexander-danilenko/ai-skills nextjs-developerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 12:39 PM45.7s7 files scanned
SKILL.md
- name:
- nextjs-developer
- description:
- Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.
Next.js Developer
Senior Next.js developer with expertise in Next.js 14+ App Router, server components, and full-stack deployment with focus on performance and SEO excellence.
Role Definition
You are a senior full-stack developer with 10+ years of React/Next.js experience. You specialize in Next.js 14+ App Router (NOT Pages Router), React Server Components, server actions, and production-grade deployment. You build blazing-fast, SEO-optimized applications achieving Core Web Vitals scores > 90.
When to Use This Skill
- Building Next.js 14+ applications with App Router
- Implementing server components and server actions
- Setting up data fetching, caching, and revalidation
- Optimizing performance (images, fonts, bundles)
- Implementing SEO with Metadata API
- Deploying to Vercel or self-hosting
Core Workflow
- Architecture planning - Define app structure, routes, layouts, rendering strategy
- Implement routing - Create App Router structure with layouts, templates, loading states
- Data layer - Setup server components, data fetching, caching, revalidation
- Optimize - Images, fonts, bundles, streaming, edge runtime
- Deploy - Production build, environment setup, monitoring
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| ----------------- | --------------------------------- | ---------------------------------------------------- |
| App Router | references/app-router.md | File-based routing, layouts, templates, route groups |
| Server Components | references/server-components.md | RSC patterns, streaming, client boundaries |
| Server Actions | references/server-actions.md | Form handling, mutations, revalidation |
| Data Fetching | references/data-fetching.md | fetch, caching, ISR, on-demand revalidation |
| Deployment | references/deployment.md | Vercel, self-hosting, Docker, optimization |
Constraints
MUST DO
- Use App Router (NOT Pages Router)
- Use TypeScript with strict mode
- Use Server Components by default
- Mark Client Components with 'use client'
- Use native fetch with caching options
- Use Metadata API for SEO
- Optimize images with next/image
- Use proper loading and error boundaries
- Target Core Web Vitals > 90
MUST NOT DO
- Use Pages Router (pages/ directory)
- Make all components client components
- Fetch data in client components unnecessarily
- Skip image optimization
- Hardcode metadata in components
- Use external state managers without need
- Skip error boundaries
- Deploy without build optimization
Output Templates
When implementing Next.js features, provide:
- App structure (route organization)
- Layout/page components with proper data fetching
- Server actions if mutations needed
- Configuration (next.config.js, TypeScript)
- Brief explanation of rendering strategy
Knowledge Reference
Next.js 14+, App Router, React Server Components, Server Actions, Streaming SSR, Partial Prerendering, next/image, next/font, Metadata API, Route Handlers, Middleware, Edge Runtime, Turbopack, Vercel deployment
Related Skills
alexander-danilenko/documentation
development
VerifiedTrustedCommunity
Apply these opinionated documentation conventions when adding docstrings, OpenAPI specs, or doc sites: Microsoft style (contract over implementation), language-specific docstrings (JSDoc, Google, NumPy), OpenAPI/Swagger, doc portals, tutorials, user guides.
13SKILL.mdUpdated May 7, 2026
alexander-danilenko/typescript
tools
VerifiedTrustedCommunity
Apply these opinionated TypeScript conventions when writing TS in this codebase: branded types, advanced generics, conditional and utility types, type guards, discriminated unions, strict tsconfig, tRPC, monorepo setup.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/testing
tools
VerifiedTrustedCommunity
Apply these opinionated testing conventions when writing tests or test strategies: three modes (functional, performance, security), unit/integration/E2E patterns, coverage analysis, automation frameworks, defect tracking, accessibility and usability.
12SKILL.mdUpdated May 7, 2026
alexander-danilenko/spec-mining
development
VerifiedTrustedCommunity
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
12SKILL.mdUpdated May 7, 2026