Skip to main content
skill CX Codex

web-rules — Claude Code skill: what it does, how to install

web-rules enforces 34 strict UX and visual design rules for React 19, Next.js 16 App Router, and Tailwind CSS 4. Keeps components accessible, consistent, and structured around Server Actions.

MIT 173 installs ★ 227 updated 2026-08-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pproenca/dot-skills --skill web-rules -a claude-code
Open on GitHub

What web-rules does

The skill provides an Always/Never rule guide across six categories, pairing incorrect examples with correct snippets. Its baseline requires React 19 Server Components by default, Next.js 16 routing files like layout.tsx and error.tsx, and mutations run via Server Actions instead of data fetching inside useEffect.

The guidelines mandate WCAG AA accessibility, touch targets of at least 44×44 px, and clean dark mode using CSS variables. Styling relies on Tailwind CSS 4 with the 4 pt scale, lucide-react icons at 1.5px stroke, and shadcn/ui primitives, ruling out CSS-in-JS libraries.

On codebases using Pages Router or other CSS systems, the skill causes false flags because it directly demands App Router conventions and @theme directives.

What it helps with

  • audit interface accessibility against WCAG AA standards
  • scaffold layouts and routes in Next.js 16 App Router
  • implement accessible dialogs and focus traps with Radix primitives
  • build forms with Server Actions and optimistic updates

Example prompts for the agent

  • Review this dialog implementation for keyboard traps and WCAG accessibility
  • Build a settings page layout using React 19 and Tailwind CSS 4 with autosave
  • Check our route segment for proper loading.tsx and error.tsx boundaries

How to install web-rules

1Skills CLI (Vercel)

npx skills add pproenca/dot-skills --skill web-rules -a claude-code

2Manually: put the files in place

~/.claude/skills/web-rules/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/web-rules/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about web-rules

How do I install web-rules in Claude Code?

Run npx skills add pproenca/dot-skills --skill web-rules -a claude-code in your terminal.

What stack does web-rules require?

The rules assume React 19, Next.js 16 App Router, Tailwind CSS 4, shadcn/ui primitives, and lucide-react. The stack excludes CSS-in-JS tools like styled-components.

What accessibility standards are enforced?

The guide mandates WCAG AA contrast ratios, minimum 44×44 px touch targets, and full usability at 320 px viewport width without horizontal scrolling.

Source text

SKILL.md · MIT
---
name: web-rules
description: Strict design and UX rules for React 19 + Next.js 16 (App Router) + Tailwind CSS 4. Covers navigation, interaction design, accessibility, user feedback, UX patterns, and visual design. Use when designing, building, or reviewing any user-facing web feature on this stack. Trigger when the user asks to "build a settings page", "add a dialog", "design this form", "review for accessibility", "fix dark mode", or any Next.js App Router / React 19 / Tailwind UI task. Also trigger when the user says output "looks off", "isn't accessible", or "doesn't follow best practices."
---

# React 19 + Next.js 16 + Tailwind CSS Best Practices

Comprehensive strict-rules reference for web apps built on React 19, the Next.js 16 App Router, and Tailwind CSS 4. Contains 34 rules across 6 categories. Each rule is stated as an Always/Never directive with a quantified impact, an incorrect example, and a correct example.

## Stack Contract

All guidance assumes:

- **React 19** with Server Components by default; Client Components only when interactivity is required (`'use client'` at the top)
- **Next.js 16 App Router** with `app/` directory, `layout.tsx`, `page.tsx`, `loading.tsx`, `error.tsx`, `not-found.tsx`, parallel routes, intercepting routes
- **Server Actions** for mutations (`'use server'`) — never `useEffect` for data fetching
- **Tailwind CSS 4** with the `@theme` directive, `dark:` variant, container queries, and the standard 4pt spacing scale
- **lucide-react** as the canonical icon system
- **No CSS-in-JS** (no styled-components, no emotion) — Tailwind utility classes only, with `cn()` from `clsx` + `tailwind-merge` for conditional classes
- **shadcn/ui primitives** (Radix-based) preferred for dialogs, popovers, dropdowns, tooltips, toasts

## When to Apply

Reference these rules when:

- Building any user-facing route, layout, or component
- Reviewing PRs for design / UX / accessibility regressions
- Choosing between modality types (dialog vs popover vs full-page)
- Implementing forms with Server Actions and `useFormState` / `useOptimistic`
- Configuring loading and error boundaries
- Designing onboarding, permissions, or settings flows
- Ensuring dark mode, focus management, and keyboard navigation work end-to-end

## Rule Categories by Priority

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | Navigation | CRITICAL | `nav-` |
| 2 | Interaction Design | CRITICAL | `inter-` |
| 3 | Accessibility | CRITICAL | `acc-` |
| 4 | User Feedback | HIGH | `feed-` |
| 5 | UX Patterns | HIGH | `ux-` |
| 6 | Visual Design | HIGH | `vis-` |

## Quick Reference

### 1. Navigation (CRITICAL)

- [`nav-primary`](references/nav-primary.md) - Use top nav (3-7 sections) or sidebar; never hamburger-only on desktop
- [`nav-app-router`](references/nav-app-router.md) - Use App Router layouts, parallel routes, and `<Link>` for all internal navigation
- [`nav-page-actions`](references/nav-page-actions.md) - Place primary actions in the page header; never bury them in scroll

### 2. Interaction Design (CRITICAL)

- [`inter-touch-targets`](references/inter-touch-targets.md) - 44×44 px minimum touch target (WCAG 2.5.5)
- [`inter-pointer-patterns`](references/inter-pointer-patterns.md) - Use standard hover/click/long-press patterns; never invent new ones
- [`inter-microinteractions`](references/inter-microinteractions.md) - Always confirm interaction with visual feedback within 100ms
- [`inter-keyboard-navigation`](references/inter-keyboard-navigation.md) - Every interactive element must be reachable and operable by keyboard
- [`inter-drag-drop`](references/inter-drag-drop.md) - Provide a keyboard-accessible alternative whenever drag is offered
- [`inter-revalidation`](references/inter-revalidation.md) - Use `revalidatePath`/`revalidateTag` after mutations; never rely on client refresh
- [`inter-row-actions`](references/inter-row-actions.md) - Use a single "row action" pattern per list (kebab menu OR hover actions OR swipe)
- [`inter-search`](references/inter-search.md) - Debounce search input by 200-300ms and reflect query in the URL

### 3. Accessibility (CRITICAL)

- [`acc-labels`](references/acc-labels.md) - Every interactive element has an accessible name
- [`acc-text-scaling`](references/acc-text-scaling.md) - All text scales to 200% browser zoom without horizontal scroll
- [`acc-color-contrast`](references/acc-color-contrast.md) - WCAG AA: 4.5:1 body text, 3:1 large/UI
- [`acc-reduce-motion`](references/acc-reduce-motion.md) - Respect `prefers-reduced-motion: reduce`
- [`acc-color-independent`](references/acc-color-independent.md) - Never rely on color alone to convey meaning
- [`acc-focus-management`](references/acc-focus-management.md) - Always render a visible focus ring; trap focus inside modals
- [`acc-relative-units`](references/acc-relative-units.md) - Use `rem` for text and spacing; never fix text size in `px`
- [`acc-responsive-layout`](references/acc-responsive-layout.md) - Every layout works at 320 px width without horizontal scroll

### 4. User Feedback (HIGH)

- [`feed-loading-states`](references/feed-loading-states.md) - Always use `loading.tsx` or `<Suspense>` with a skeleton matching final layout
- [`feed-error-states`](references/feed-error-states.md) - Every route segment has `error.tsx` with a Try-Again action
- [`feed-toasts`](references/feed-toasts.md) - Use toasts only for confirmations of non-blocking actions
- [`feed-success-confirmation`](references/feed-success-confirmation.md) - Confirm every destructive or irreversible action with explicit visible feedback
- [`feed-empty-states`](references/feed-empty-states.md) - Empty states explain why and offer the next action

### 5. UX Patterns (HIGH)

- [`ux-onboarding`](references/ux-onboarding.md) - Onboarding never exceeds 3 screens; always skippable
- [`ux-permissions`](references/ux-permissions.md) - Request browser permissions in-context, not on page load
- [`ux-modality`](references/ux-modality.md) - Choose dialog / popover / full-page by content weight; never stack modals
- [`ux-destructive-confirmation`](references/ux-destructive-confirmation.md) - Destructive actions require a typed confirmation OR an undo window
- [`ux-data-entry`](references/ux-data-entry.md) - Use Server Actions + progressive enhancement; never disable submit while typing
- [`ux-undo`](references/ux-undo.md) - Prefer undo over confirmation for everyday actions
- [`ux-settings`](references/ux-settings.md) - Settings are autosaved on change; never gated behind a Save button

### 6. Visual Design (HIGH)

- [`vis-dark-mode`](references/vis-dark-mode.md) - Use CSS custom properties + `dark:` variant; never hardcode `text-black`/`bg-white`
- [`vis-icon-system`](references/vis-icon-system.md) - Use lucide-react with `1.5px` stroke and `size-4`/`size-5` standard sizes
- [`vis-spacing`](references/vis-spacing.md) - Use the Tailwind 4 pt scale and container queries; never use ad-hoc `px` margins

## How to Use

Read individual reference files for detailed explanations and code examples:

- [Section definitions](references/_sections.md) - Category structure and impact levels
- [Rule template](assets/templates/_template.md) - Template for adding new rules

## Reference Files

| File | Description |
|------|-------------|
| [references/_sections.md](references/_sections.md) | Category definitions and ordering |
| [assets/templates/_template.md](assets/templates/_template.md) | Template for new rules |

© pproenca · MIT · pproenca/dot-skills

Similar skills

All skills for Frontend and UI →

From the same set139

The whole set →
marketplace-pre-member-personalisation marketplace-pre-member-personalisation — a skill for Claude Code, Cursor, Codex, GitHub Copilot, and Gemini CLI that maps the full anonymous-to-paid-member funnel on a two-sided trust marketplace. CX Codex +1 204installs design-review The design-review skill reviews existing UI code and, when needed, the live browser result. It helps rank visual, accessibility, and interaction fixes before a merge. CX Codex +1 180installs react-fetch-cache-patterns react-fetch-cache-patterns — a skill with 48 rules for scalable data fetching and caching in React: request orchestration, backend protection, prefetching, error resilience. CX Codex +1 180installs react-19-component-scaffolder react-19-component-scaffolder scaffolds TypeScript files for React 19 components and related code. Use it to start a page, form, hook, or other common project structure from a template. CX Codex +1 174installs algorithmic-complexity-review The algorithmic-complexity-review skill spots code patterns that drive up runtime or memory use, then classifies their Big-O complexity. Use it when reviewing slow code or refactoring a hot path. CX Codex +1 171installs expo-ios-hig expo-ios-hig is a Claude Code skill with Apple Human Interface Guidelines rules for screens, components, and navigation in Expo and React Native. CX Codex +1 169installs web-taste web-taste — a skill that makes the agent work out who the user is and what they need before it writes any React 19, Next.js 16 and Tailwind CSS. CX Codex +1 169installs typescript-advanced-patterns typescript-advanced-patterns — a TypeScript skill with 40 rules on type-level programming, library API design and deeper use of TS 5.x features. Useful once plain typings stop being enough. CX Codex +1 162installs

Project sponsors

Companies that keep this analytics open