ui

Generate accessible React/Next.js UI components with Server Components and Tailwind styling.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill ui-timekast
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/domains/ui
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill ui-timekast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the difficulty of building consistent, accessible React/Next.js UI components quickly without bloated client code or fragile styles.

Core Features & Use Cases

  • Server Components by default: keep interactivity in client components only when you actually need state, effects, or browser APIs.
  • Composition-first UI patterns: build small reusable components and compose them for feature-level UI.
  • Tailwind-first styling + consistent design system: prefer shadcn/ui primitives and Tailwind utility classes for maintainable styling.
  • Accessibility and UX guardrails: enforce focus visibility, ARIA-friendly UI, accessible dialog/toast patterns, and human-readable error messaging.

Use cases: creating feature components in a Next.js App Router app, implementing forms with React Hook Form + Zod, designing interactive tables with predictable client/server state, and adding loading states using Suspense skeletons.

Quick Start

Ask the AI to generate an accessible Next.js App Router UI component using shadcn/ui primitives and Tailwind classes, defaulting to a Server Component and adding 'use client' only where interactivity requires it.

Frequently Asked Questions about ui

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

FAQPage Schema
How do I build accessible React UI components that default to Server Components in Next.js?

Build accessible React forms in Next.js using React Hook Form with Zod schema validation, styling inputs with Tailwind utility classes and shadcn/ui primitives, while enforcing accessible interaction patterns and human-readable error messaging.

Can I use Tailwind and shadcn-ui to create interactive tables with predictable state?

Yes, you can use Tailwind and shadcn-ui to create interactive tables with predictable client and server state. The approach applies composition-first UI patterns to maintain consistent, accessible behavior without fragile styles.

What is the best way to add loading skeletons and Suspense states in a Next.js App Router?

The best way to add loading skeletons in a Next.js App Router is generating Suspense-bound skeleton components using Tailwind-first styling. This maintains visual consistency while waiting for Server Component data to resolve.

Do I need 'use client' for every accessible dialog and toast interaction pattern?

No, you do not need 'use client' for every dialog and toast. You should default to Server Components and only apply 'use client' where interactivity requires state, effects, or browser APIs, while still enforcing ARIA-friendly UI patterns.