frontend-nextjs

Develop and debug Next.js applications with React, TypeScript, and App Router patterns.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/Lawrence908/chiron --skill frontend-nextjs-lawrence908
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-nextjs
Source: https://github.com/Lawrence908/chiron/tree/main/plugins/dev/skills/frontend-nextjs
Command: npx skills add https://github.com/Lawrence908/chiron --skill frontend-nextjs-lawrence908

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building production Next.js applications involves many decisions—App Router vs Pages Router, server vs client components, caching strategies, and API integration—where mistakes lead to security leaks, poor performance, and broken rendering. This Skill provides a structured workflow and guardrails for creating, maintaining, and debugging Next.js features correctly. ## Core Features & Use Cases - Full-Stack Next.js Development: Implement pages, API routes, server components, layouts, and routing with TypeScript type safety. - Performance & SEO Optimization: Apply SSR, SSG, ISR caching strategies, Next.js Image optimization, code splitting, and metadata configuration. - Backend Integration: Connect to APIs using fetch, SWR, or React Query with proper error boundaries and loading states. - Use Case: You need a page that displays tasks from a FastAPI backend. The Skill generates a server component with typed data fetching, proper cache configuration, and Tailwind styling—plus a client component variant when interactivity is required. ## Quick Start Create a Next.js page that fetches and displays a list of tasks from my FastAPI backend with loading and error states.

Frequently Asked Questions about frontend-nextjs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch data in Next.js App Router server components?▼

Use async server components with the native fetch API directly in the component body. Control caching with options like cache: 'no-store' for dynamic data or revalidate for ISR, avoiding useEffect-based client fetching when server components can handle it.

When should I use client components vs server components in Next.js?▼

Use server components by default for data fetching and static rendering. Add 'use client' only when you need interactivity like useState, useEffect, or event handlers, since client components increase bundle size and lose server-side benefits.

How do I securely call external APIs from a Next.js frontend?▼

Never expose API keys in client components. Create Next.js API routes as a server-side proxy that holds the secrets, then have client components call your internal API route instead of the external service directly.

Why is my Next.js page showing stale data after deployment?▼

Stale data usually comes from aggressive fetch caching. Check your cache and revalidate options—use cache: 'no-store' for always-fresh data, or set a revalidate interval for incremental static regeneration.

Can I mix App Router and Pages Router patterns in one project?▼

Next.js supports both routers simultaneously during migration, but mixing patterns within the same feature causes confusion and bugs. Pick one router per route tree and follow its conventions consistently.