Discover tools frontend skills, compare source repositories and read the instructions for each workflow.
Design and build reusable, composable UI components with single responsibility, clear interfaces, and proper encapsulation. Use this skill when creating or editing React components, Vue components, Svelte compo...
Implement responsive designs using mobile-first development, fluid layouts, standard breakpoints, and relative units to ensure optimal viewing across all device sizes. Use this skill when creating layouts, impl...
This skill provides best practices for using Shadcn Vue components in the fitness app. Use when working with UI components, forms, dialogs, or implementing component patterns.
Expo framework for React Native development with EAS Build, managed workflow, and OTA updates
Next.js 14+ App Router, Server Components, and full-stack React development patterns
Vue.js and Nuxt development patterns and best practices
React Native mobile development with core components, navigation, and platform-specific patterns
React, Next.js, and TypeScript development patterns and best practices
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 avoid...
Svelte frontend development for this Wails app. Use when building UI components, styling, working with Wails bindings, or implementing frontend features. Covers component patterns, CSS architecture, Elite Dange...
Common Next.js anti-patterns: useEffect misuse (data fetch, browser detect), useState for server data, Pages Router patterns, serial await, over-using 'use client'.
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
Next.js App Router (13+). Migrating from Pages, file conventions (layout, page, loading, error), routing patterns, metadata, generateStaticParams.
Server Component navigation: for links, redirect() for conditional redirects. NO 'use client' needed for static links or server redirects.
Fetch data using URL parameter. Create app/[id]/page.tsx, await params to get ID, fetch API, render. Server Component (no 'use client').
Advanced Next.js routing: Route Handlers (API routes), Server Actions ('use server'), Parallel Routes (@slot), Intercepting Routes ((.)), Error Boundaries, Draft Mode, Suspense streaming.
Server vs Client Components in Next.js App Router. Server is default (async, cookies, headers, searchParams). Client needs 'use client' (hooks, events, browser APIs).
Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
useSearchParams hook in Next.js. REQUIRES 'use client' + Suspense wrapper. Read URL query params: .get(), .getAll(), .has(). Update via router.push().
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Trigge...
Vercel's Web Interface Guidelines for accessibility, performance, and UX best practices. Use when reviewing or writing frontend code to check for accessibility issues, focus states, form patterns, animation bes...
Create distinctive, production-grade frontend interfaces with high design quality. WHEN: Building landing pages, dashboards, web components, beautifying UI, creating polished designs, avoiding generic AI aesthe...
Tailwind CSS utility classes for layout, spacing, typography, responsive design, and dark mode. WHEN: Styling with Tailwind classes, implementing flex/grid layouts, responsive breakpoints, dark mode variants, a...
ApexCharts integration for Vue 3 using vue3-apexcharts for data visualization. WHEN: Creating charts in Vue 3 (line, bar, pie, donut, radar, heatmap), building dashboards, real-time chart updates, integrating A...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.