Frontend Component Skill

Implement Next.js server and client components with App Router and Tailwind conventions.

2|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/NaimalArain13/Hackathon-II_The-Evolution-of-Todo --skill frontend-component-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Frontend Component Skill
Source: https://github.com/NaimalArain13/Hackathon-II_The-Evolution-of-Todo/tree/main/.claude/skills/frontend-component
Command: npx skills add https://github.com/NaimalArain13/Hackathon-II_The-Evolution-of-Todo --skill frontend-component-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured guide for building Next.js components that correctly balance server and client rendering patterns, standardizing workflows and reducing boilerplate in modern React apps.

Core Features & Use Cases

  • Server Components by default for static content, data fetching, and SEO-friendly pages.
  • Client Components for interactivity, hooks, and browser APIs, with clear patterns for when to opt-in.
  • Reusable component patterns (e.g., ProtectedRoute, LoadingSpinner, Form Handling, Toast notifications) and guidance on code structure, accessibility, and Tailwind usage.
  • Use Case: Build a dashboard with server-rendered pages and interactive widgets using client components where needed, while maintaining consistent styling and accessibility.

Quick Start

Review existing frontend patterns in frontend/app and frontend/components, then implement new components following this skill's guidance.

Frequently Asked Questions about Frontend Component Skill

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

FAQPage Schema
How do I structure Next.js App Router components using server and client patterns?

Next.js App Router components should default to Server Components for static content and data fetching, opting into Client Components only for interactivity, hooks, and browser APIs. This approach accelerates UI development while maintaining SEO and performance.

When should I use client components instead of server components in Next.js?

Use client components in Next.js when you need interactivity, React hooks, or browser APIs. Server components should be the default for static content, data fetching, and SEO-friendly pages, opting into client components selectively to preserve performance.

What's the best way to handle conditional Tailwind classes in React components?

The best way to handle conditional Tailwind classes in React components is by using a cn utility. This pattern enforces consistent styling conventions and simplifies conditional class application across server and client components.

How do I implement accessible forms and notifications in a Next.js dashboard?

Implement accessible Next.js dashboard forms and notifications by using semantic HTML and TypeScript alongside reusable component patterns like form handling and toast notifications. This ensures consistent accessibility standards across server and client components.

Does this Next.js component pattern require TypeScript and Tailwind?

Yes, these Next.js component patterns enforce TypeScript usage and Tailwind styling conventions. This standardization reduces boilerplate and ensures consistent code structure, accessibility, and type safety across server and client components.

What reusable component patterns are recommended for Next.js App Router development?

Recommended Next.js App Router patterns include ProtectedRoute, LoadingSpinner, form handling, and toast notifications. These reusable patterns standardize workflows, reduce boilerplate, and ensure consistent accessibility and styling across server and client components.