Communitygithub.com

ComeOnOliver/skillshub

Anleitung zur Erstellung von Next.js-Komponenten unter Verwendung von Server/Client Mustern und bestehenden Komponentenstrukturen.

Was ist skillshub?

Diese Fähigkeit (Skill) bietet umfassende Anleitungen für Entwickler, die mit Next.js 16+ und dem App Router arbeiten. Sie erklärt klar, wann Server-Komponenten (Standard) und wann Client-Komponenten (nur bei Interaktivität) verwendet werden sollten, und zeigt dies anhand konkreter Codebeispiele. Die Anleitung enthält wiederverwendbare Pattern-Vorlagen wie `ProtectedRoute`, `LoadingSpinner`, Formularvalidierung und eine Toast-Benachrichtigung. Darüber hinaus werden bewährte Methoden für Tailwind CSS (Utility-Only, bedingte Klassen mit `cn()`, Dark Mode und responsives Design) sowie Barrierefreiheit nach WCAG 2.1 AA vermittelt. Es werden auch fortgeschrittene Patterns wie Drag & Drop mit `@dnd-kit/core` und ein Undo/Redo-Pattern mit `useReducer` vorgestellt. Die Konventionen für Dateibenennung und die Einhaltung von Projektspezifikationen (Constitution Requirements) sind ebenfalls dokumentiert.

Funktioniert mit~Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/ComeOnOliver/skillshub/tree/HEAD/skills/aiskillstore/marketplace/asmayaseen/frontend-component

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Frontend-Komponenten-Skill

Zweck: Leitfaden zur Erstellung von Next.js-Komponenten unter Verwendung von Server/Client-Mustern und bestehenden Komponentenstrukturen.

Übersicht

Next.js 16+ verwendet standardmäßig den App Router mit Server-Komponenten. Client-Komponenten werden nur verwendet, wenn Interaktivität erforderlich ist (Hooks, Ereignisbehandlungen, Browser-APIs).

Server vs Client-Komponenten

Server-Komponenten (Standard)

Wann verwenden:

  • Seiten und Layouts
  • Statischer Inhalt
  • Datenabruf von der API (wenn möglich)
  • SEO-optimierte Inhalte

Muster:

// Keine "use client" Direktive
import { Metadata } from "next";

export const metadata: Metadata = {
  title: "Seitentitel",
};

export default function PageComponent() {
  return <div>Statischer Inhalt</div>;
}

Beispiel: frontend/app/layout.tsx, frontend/app/page.tsx

Client-Komponenten (bei Bedarf)

Wann verwenden:

  • Interaktive Elemente (Buttons, Formulare, Eingaben)
  • Ereignisbehandlungen (onClick, onChange, usw.)
  • React Hooks (useState, useEffect, useRouter, usw.)
  • Browser-APIs (localStorage, window, document, usw.)
  • Echtzeit-Updates
  • Drag & Drop-Funktionalität

Muster:

"use client"; // MUSS die erste Zeile sein

import { useState, useEffect } from "react";
import { useRouter } from "next/navigation";

interface ComponentProps {
  prop1: string;
  prop2?: number;
}

export default function ComponentName({ prop1, prop2 }: ComponentProps) {
  const router = useRouter();
  const [state, setState] = useState("");

  useEffect(() => {
    // Seiteneffekte
  }, []);

  return <div>{/* Komponenten JSX */}</div>;
}

Beispiel: frontend/components/ProtectedRoute.tsx, frontend/app/signup/page.tsx

Vorlage für Komponentenstruktur

"use client"; // Nur wenn Client-Komponente

/**
 * Komponentenname
 *
 * Kurze Beschreibung, was diese Komponente tut
 */

import { useState, useEffect } from "react";
import { ComponentType } from "@/types";
import { cn } from "@/lib/utils";

interface ComponentProps {
  prop1: string;
  prop2?: number;
  className?: string;
}

export default function ComponentName({ prop1, prop2, className }: ComponentProps) {
  // Zustand
  const [state, setState] = useState("");

  // Effekte
  useEffect(() => {
    // Seiteneffekte
  }, []);

  // Behandlungen
  const handleClick = () => {
    // Behandlungslogik
  };

  // Rendern
  return (
    <div className={cn("base-classes", className)}>
      {/* Komponenteninhalt */}
    </div>
  );
}

Spezifische Komponentenmuster

1. ProtectedRoute-Muster

Aus: frontend/components/ProtectedRoute.tsx

"use client";

import { useEffect, useState } from "react";
import { useRouter } from "next/navigation";
import { isAuthenticated } from "@/lib/auth";
import LoadingSpinner from "./LoadingSpinner";

interface ProtectedRouteProps {
  children: React.ReactNode;
}

export default function ProtectedRoute({ children }: ProtectedRouteProps) {
  const router = useRouter();
  const [isAuthorized, setIsAuthorized] = useState(false);
  const [isChecking, setIsChecking] = useState(true);

  useEffect(() => {
    async function checkAuth() {
      try {
        const authenticated = await isAuthenticated();

        if (!authenticated) {
          const currentPath = window.location.pathname;
          if (currentPath !== "/signin") {
            sessionStorage.setItem("redirectAfterLogin", currentPath);
          }
          router.push("/signin");
        } else {
          setIsAuthorized(true);
        }
      } catch (error) {
        console.error("Authentifizierungsprüfung fehlgeschlagen:", error);
        router.push("/signin");
      } finally {
        setIsChecking(false);
      }
    }

    checkAuth();
  }, [router]);

  if (isChecking) {
    return (
      <div className="min-h-screen flex items-center justify-center">
        <LoadingSpinner size="large" />
      </div>
    );
  }

  if (!isAuthorized) {
    return null;
  }

  return <>{children}</>;
}

Muster:

  • Authentifizierung beim Mounten prüfen
  • Lade-Spinner während der Prüfung anzeigen
  • Zielseite in sessionStorage speichern
  • Bei nicht authentifiziert zu /signin umleiten
  • Kinder nur rendern, wenn autorisiert

2. LoadingSpinner-Muster

Aus: frontend/components/LoadingSpinner.tsx

interface LoadingSpinnerProps {
  size?: "small" | "medium" | "large";
  color?: string;
  label?: string;
}

export default function LoadingSpinner({
  size = "medium",
  color = "blue",
  label = "Lädt...",
}: LoadingSpinnerProps) {
  const sizeClasses = {
    small: "w-4 h-4 border-2",
    medium: "w-8 h-8 border-3",
    large: "w-12 h-12 border-4",
  };

  const colorClasses = {
    blue: "border-blue-600 border-t-transparent",
    gray: "border-gray-600 border-t-transparent",
    white: "border-white border-t-transparent",
  };

  const spinnerClass = `${sizeClasses[size]} ${
    colorClasses[color as keyof typeof colorClasses] || colorClasses.blue
  } rounded-full animate-spin`;

  return (
    <div
      className="flex items-center justify-center"
      role="status"
      aria-label={label}
      aria-live="polite"
    >
      <div className={spinnerClass}></div>
      <span className="sr-only">{label}</span>
    </div>
  );
}

Muster:

  • Mehrere Größen (small, medium, large)
  • Mehrere Farben (blue, gray, white)
  • Barrierefreiheitsbezeichnungen (role="status", aria-label, aria-live)
  • Screenreader-Text mit sr-only-Klasse

3. Formularbehandlungsmuster

Aus: frontend/app/signup/page.tsx

"use client";

import { useState } from "react";
import { useRouter } from "next/navigation";
import { api } from "@/lib/api";
import { isValidEmail, getPasswordStrength } from "@/lib/utils";

export default function SignupPage() {
  const router = useRouter();
  const [formData, setFormData] = useState({
    name: "",
    email: "",
    password: "",
  });
  const [errors, setErrors] = useState<Record<string, string>>({});
  const [isLoading, setIsLoading] = useState(false);
  const [apiError, setApiError] = useState("");

  const validateForm = (): boolean => {
    const newErrors: Record<string, string> = {};

    if (!formData.name.trim()) {
      newErrors.name = "Name ist erforderlich";
    }

    if (!formData.email.trim()) {
      newErrors.email = "E-Mail ist erforderlich";
    } else if (!isValidEmail(formData.email)) {
      newErrors.email = "Bitte geben Sie eine gültige E-Mail-Adresse ein";
    }

    // Weitere Validierung...

    setErrors(newErrors);
    return Object.keys(newErrors).length === 0;
  };

  const handleSubmit = async (e: React.FormEvent) => {
    e.preventDefault();
    setApiError("");

    if (!validateForm()) {
      return;
    }

    setIsLoading(true);

    try {
      const response = await api.signup(formData);
      if (response.success) {
        router.push("/dashboard");
      } else {
        setApiError(response.message || "Registrierung fehlgeschlagen");
      }
    } catch (error: any) {
      setApiError(error.message || "Ein Fehler ist aufgetreten");
    } finally {
      setIsLoading(false);
    }
  };

  const handleChange = (e: React.ChangeEvent<HTMLInputElement>) => {
    const { name, value } = e.target;
    setFormData((prev) => ({ ...prev, [name]: value }));
    // Fehler für dieses Feld löschen, wenn der Benutzer zu tippen beginnt
    if (errors[name]) {
      setErrors((prev) => ({ ...prev, [name]: "" }));
    }
  };

  return (
    <form onSubmit={handleSubmit}>
      {/* Formularfelder */}
    </form>
  );
}

Muster:

  • Getrennter Zustand für Formulardaten, Fehler, Ladezustand, API-Fehler
  • Validierungsfunktion, die einen Boolean zurückgibt
  • Fehler bei Eingabeänderung löschen
  • Ladezustand während der Übermittlung
  • Try-catch zur Fehlerbehandlung
  • Bei Erfolg umleiten

4. ToastNotification-Muster

Aus: frontend/components/ToastNotification.tsx

"use client";

import { useEffect, useState } from "react";
import { ToastMessage, ToastType } from "@/types";

export function useToast() {
  const [toasts, setToasts] = useState<ToastMessage[]>([]);

  const showToast = (type: ToastType, message: string, duration?: number) => {
    const id = `toast-${Date.now()}-${Math.random()}`;
    const newToast: ToastMessage = {
      id,
      type,
      message,
      duration,
    };
    setToasts((prev) => [...prev, newToast]);
  };

  const dismissToast = (id: string) => {
    setToasts((prev) => prev.filter((toast) => toast.id !== id));
  };

  return {
    toasts,
    showToast,
    dismissToast,
    success: (message: string, duration?: number) => showToast("success", message, duration),
    error: (message: string, duration?: number) => showToast("error", message, duration),
    // ...
  };
}

Muster:

  • Eigener Hook für Toast-Verwaltung
  • Automatisches Ausblenden mit Dauer
  • Mehrere Toasts stapeln
  • Hilfsmethoden (success, error, warning, info)

Tailwind CSS Muster

1. Nur Utility-Klassen

<div className="flex items-center justify-center gap-4 p-6 bg-white rounded-lg shadow-md">

Muster: Tailwind Utility-Klassen verwenden, keine Inline-Stile

2. Bedingte Klassen mit cn()-Hilfsprogramm

import { cn } from "@/lib/utils";

<div className={cn(
  "base-classes",
  condition && "conditional-classes",
  className // Überschreibung durch Prop erlauben
)}>

Muster: cn() von @/lib/utils für bedingte Klassen verwenden

3. Dark Mode Unterstützung

<div className="bg-white dark:bg-gray-800 text-gray-900 dark:text-white">

Muster: dark:-Präfix für Dark Mode-Stile verwenden

4. Responsives Design

<div className="w-full sm:w-1/2 md:w-1/3 lg:w-1/4">

Muster: Breakpoint-Präfixe (sm:, md:, lg:, xl:) verwenden

Barrierefreiheitsmuster (WCAG 2.1 AA)

1. ARIA-Bezeichnungen

<button aria-label="Dialog schließen">×</button>
<div role="status" aria-live="polite" aria-label="Lädt...">

Muster: Immer aria-label für reine Symbol-Buttons bereitstellen

2. Semantisches HTML

<nav>
  <ul>
    <li><a href="/">Startseite</a></li>
  </ul>
</nav>

Muster: Semantische HTML-Elemente (nav, main, section, article, usw.) verwenden

3. Tastaturnavigation

<button
  onClick={handleClick}
  onKeyDown={(e) => {
    if (e.key === "Enter" || e.key === " ") {
      handleClick();
    }
  }}
>

Muster: Tastaturzugänglichkeit für alle interaktiven Elemente sicherstellen

4. Screenreader-Text

<span className="sr-only">Inhalt wird geladen</span>

Muster: sr-only-Klasse für Screenreader-Text verwenden

5. Fokusverwaltung

<input
  autoFocus
  className="focus:outline-none focus:ring-2 focus:ring-blue-500"
/>

Muster: Immer sichtbare Fokusindikatoren bereitstellen

Dateibenennungskonventionen

  • Seiten: Kebab-Case (z. B. signup.tsx, signin.tsx)
  • Komponenten: PascalCase (z. B. TaskList.tsx, TaskItem.tsx)
  • Layouts: layout.tsx
  • Fehlerseiten: error.tsx, not-found.tsx

Anforderungskonformität

  • FR-033: Next.js 16+ App Router-Struktur ✅
  • FR-034: Server-Komponenten standardmäßig, Client bei Bedarf ✅
  • FR-035: Fehlergrenzen ✅
  • FR-036: WCAG 2.1 AA Konformität ✅
  • FR-037: TypeScript Strict Mode ✅
  • FR-038: Prettier Formatierung ✅
  • FR-039: ESLint Regeln ✅

Referenzen

  • Spezifikation: specs/002-frontend-todo-app/spec.md - Komponentenspezifikationen
  • Vorhandene Komponenten: frontend/components/*.tsx - Komponentenbeispiele
  • Vorhandene Seiten: frontend/app/*.tsx - Seitenbeispiele

Fortgeschrittene Komponentenmuster

1. Drag & Drop Muster (Phase 7 - T065)

Bibliothek: @dnd-kit/core

"use client";

import { DndContext, closestCenter, KeyboardSensor, PointerSensor, useSensor, useSensors } from "@dnd-kit/core";
import { SortableContext, sortableKeyboardCoordinates, useSortable, verticalListSortingStrategy } from "@dnd-kit/sortable";

export default function SortableTaskList({ tasks, onReorder }: Props) {
  const sensors = useSensors(
    useSensor(PointerSensor),
    useSensor(KeyboardSensor, {
      coordinateGetter: sortableKeyboardCoordinates,
    })
  );

  const handleDragEnd = (event: DragEndEvent) => {
    const { active, over } = event;
    if (over && active.id !== over.id) {
      onReorder(active.id, over.id);
    }
  };

  return (
    <DndContext sensors={sensors} collisionDetection={closestCenter} onDragEnd={handleDragEnd}>
      <SortableContext items={tasks.map(t => t.id)} strategy={verticalListSortingStrategy}>
        {tasks.map(task => (
          <SortableTaskItem key={task.id} task={task} />
        ))}
      </SortableContext>
    </DndContext>
  );
}

Muster: @dnd-kit/core für Drag & Drop verwenden, Neuordnung bei Drag-Ende behandeln

2. Undo/Redo Muster (Phase 7 - T066)

"use client";

import { useReducer } from "react";

interface HistoryState<T> {
  past: T[];
  present: T;
  future: T[];
}

function historyReducer<T>(state: HistoryState<T>, action: { type: string; newPresent?: T }): HistoryState<T> {
  const { past, present, future } = state;

  switch (action.type) {
    case "UNDO":
      if (past.length === 0) return state;
      return {
        past: past.slice(0, past.length - 1),
        present: past[past.length - 1],
        future: [present, ...future],
      };
    case "REDO":
      if (future.length === 0) return state;
      return {
        past: [...past, present],
        present: future[0],
        future: future.slice(1),
      };
    case "SET":
      if (action.newPresent === present) return state;
      return {
        past: [...past, present],
        present: action.newPresent!,
        future: [],
      };
    default:
      return state;
  }
}

export function useHistory<T>(initialPresent: T) {
  const [state, dispatch] = useReducer(historyReducer, {
    past: [],
    present: initialPresent,
    future: [],
  });

  const undo = () => dispatch({ type: "UNDO" });
  const redo = () => dispatch({ type: "REDO" });
  const set = (newPresent: T) => dispatch({ type: "SET", newPresent });

  return { state: state.present, undo, redo, set, canUndo: state.past.length > 0, canRedo: state.future.length > 0 };
}

Muster: useReducer für Verlaufsverwaltung, separate Stacks für Vergangenheit und Zukunft, Bedingungen für Verfügbarkeit von Rückgängig/Wiederholen.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ComeOnOliver/skillshub

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

ComeOnOliver/skillshub

Next.js 16+ 和 Turbopack — 增量打包、文件系统缓存、开发速度,以及何时使用 Turbopack 与 webpack。

ComeOnOliver/skillshub

SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.

ComeOnOliver/skillshub

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.

ComeOnOliver/skillshub

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

ComeOnOliver/skillshub

Next.js 15 애플리케이션을 위한 프론트엔드 개발 가이드라인. React 19, TypeScript, Shadcn/ui, Tailwind CSS를 사용한 모던 패턴. Server Components, Client Components, App Router, 파일 구조, Shadcn/ui 컴포넌트, 성능 최적화, TypeScript 모범 사례 포함. 컴포넌트, 페이지, 기능 생성, 데이터 페칭, 스타일링, 라우팅, 프론트엔드 코드 작업 시 사용.

ComeOnOliver/skillshub

Provides Tamagui patterns for config v4, compiler optimization, styled context, and cross-platform styling. Must use when working with Tamagui projects (tamagui.config.ts, @tamagui imports).

ComeOnOliver/skillshub

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

ComeOnOliver/skillshub

Create high-converting, visually distinctive landing pages. Use when building marketing pages, product launches, SaaS homepages, or any single-page conversion-focused website. Guides section-by-section composition with anti-AI-slop principles.

ComeOnOliver/skillshub

Auto-loaded context for Portfolio Buddy 2 development. Use for ANY task involving: React 19 development, TypeScript, portfolio analysis features, metrics calculations, trading strategy comparison, or working with the Portfolio Buddy 2 codebase. Contains tech stack, known issues, and architectural constraints.

ComeOnOliver/skillshub

Next.js development tooling via MCP. Inspect routes, components, build info, and debug Next.js apps. Use when working on Next.js applications, debugging routing, or inspecting app structure. NOT for general React or non-Next.js projects.

ComeOnOliver/skillshub

Implement UI using Shadcn MCP (atoms/theme) and 21st.dev MCP (complex sections). Use when adding buttons, layouts, or generating landing pages.

ComeOnOliver/skillshub

A conceptual skill for building an API client in Next.js that handles JWT tokens

ComeOnOliver/skillshub

Best practices and patterns for Next.js App Router, Server Actions, and Routing in this project.

ComeOnOliver/skillshub

The Design System, Theme, and UX rules for the Physical AI Hub.

ComeOnOliver/skillshub

Comprehensive frontend development skill for building modern, performant web applications using ReactJS, NextJS, TypeScript, Tailwind CSS. Includes component scaffolding, performance optimization, bundle analysis, and UI best practices. Use when developing frontend features, optimizing performance, implementing UI/UX designs, managing state, or reviewing frontend code.

ComeOnOliver/skillshub

This document captures learnings from fixing keyboard navigation issues when floating components (Select, DropdownMenu, Popover) have CSS open/close animations.

ComeOnOliver/skillshub

Build Next.js 16 applications with correct patterns and distinctive design. Use when creating pages, layouts, dynamic routes, upgrading from Next.js 15, or implementing proxy.ts. Covers breaking changes (async params/searchParams, Turbopack, cacheComponents) and frontend aesthetics. NOT when building non-React or backend-only applications.

ComeOnOliver/skillshub

Comprehensive Framer Motion animation library for React. Covers motion components, variants, gestures, page transitions, and scroll animations. Use when adding animations to React/Next.js applications.

ComeOnOliver/skillshub

Build interfaces that resonate, not just render. This skill enforces bold, intentional

Verwandte Skills