Skip to main content
skill CX Codex

generic-fullstack-ux-designer — Claude Code skill: what it does

generic-fullstack-ux-designer is a Claude Code skill that guides UX design for Next.js and NestJS apps, covering loading states, optimistic UI, forms, and SSR quirks.

MIT 153 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill generic-fullstack-ux-designer -a claude-code
Open on GitHub

What generic-fullstack-ux-designer does

This skill equips an agent with interface design standards tailored for client-server architectures. It provides concrete patterns for Server-Side Rendering, such as hydration-safe skeleton loaders, client-server component boundaries, and progressive form enhancement.

The rules structure network feedback strictly by response duration. Requests under 100ms require no visual indicator, 100ms to 1s trigger subtle spinners, 1s to 5s rely on skeletons, and tasks beyond 5s need progress bars. Optimistic UI is restricted to low-risk actions like likes or comments; destructive tasks such as item deletion or payment processing require verified confirmations.

What it helps with

  • prevent React hydration mismatches during server-side rendering
  • structure loading indicators based on measured API response time
  • implement optimistic UI updates with automatic rollback on failure
  • map client-to-server validation flows for multi-step forms

Example prompts for the agent

  • Design an optimistic update flow for a post reaction with rollback handling
  • Review our Next.js authentication flow and protected route redirect logic
  • What loading pattern should we display for file uploads exceeding five seconds?

How to install generic-fullstack-ux-designer

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill generic-fullstack-ux-designer -a claude-code

2Manually: put the files in place

~/.claude/skills/generic-fullstack-ux-designer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/generic-fullstack-ux-designer/

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

Questions about generic-fullstack-ux-designer

How do I install generic-fullstack-ux-designer in Claude Code?

Run npx skills add travisjneuman/.claude --skill generic-fullstack-ux-designer -a claude-code in your terminal.

What does generic-fullstack-ux-designer do?

It injects full-stack UX patterns into the coding agent, focusing on Next.js/NestJS conventions, SSR, loading states, and error recovery.

When does this skill avoid optimistic UI?

It advises against optimistic updates on destructive actions such as deleting records or critical flows like payments, where backend confirmation is mandatory.

Source text

SKILL.md · MIT
---
name: generic-fullstack-ux-designer
description: Professional UI/UX design expertise for full-stack applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design reviews.
---

# Fullstack UX Designer

Professional UX expertise for Next.js/NestJS full-stack applications.

**Extends:** [Generic UX Designer](../generic-ux-designer/SKILL.md) - Read base skill for design thinking process, research methods, interaction patterns, and critique framework.

## Full-Stack UX Considerations

### Server-Side Rendering UX

| Scenario          | UX Pattern                                       |
| ----------------- | ------------------------------------------------ |
| Initial page load | Hydration-safe skeleton screens                  |
| Data fetching     | Server components for static, client for dynamic |
| Authentication    | Protected routes with redirect UX                |
| Form submission   | Progressive enhancement                          |

### Hydration-Safe Patterns

```tsx
// ✓ Avoid hydration mismatch
function Timestamp({ date }: { date: Date }) {
  const [formatted, setFormatted] = useState("");

  useEffect(() => {
    setFormatted(date.toLocaleString()); // Client-side only
  }, [date]);

  return <span>{formatted || "Loading..."}</span>;
}
```

## API Loading & Error States

### Loading State Hierarchy

| Duration   | Pattern         | Example      |
| ---------- | --------------- | ------------ |
| < 100ms    | No indicator    | Button click |
| 100ms - 1s | Subtle spinner  | Form submit  |
| 1s - 5s    | Skeleton screen | Page fetch   |
| > 5s       | Progress bar    | File upload  |

### Error State Design

```
API Error → Parse Error → User-Friendly Message → Recovery Action
```

| Error Type       | User Message           | Recovery          |
| ---------------- | ---------------------- | ----------------- |
| 400 Validation   | Show field errors      | Fix and retry     |
| 401 Unauthorized | "Please log in"        | Redirect to login |
| 404 Not Found    | "Item not found"       | Navigate back     |
| 500 Server Error | "Something went wrong" | Retry button      |

## Optimistic UI Pattern

```typescript
// Show immediate feedback, rollback on error
async function toggleLike(postId: string) {
  // 1. Update UI immediately
  setLiked(true);
  setLikeCount((c) => c + 1);

  try {
    // 2. Call API
    await api.like(postId);
  } catch {
    // 3. Rollback on failure
    setLiked(false);
    setLikeCount((c) => c - 1);
    showToast("Failed to like");
  }
}
```

### When to Use Optimistic UI

| Action        | Optimistic? | Why                        |
| ------------- | ----------- | -------------------------- |
| Like/favorite | Yes         | Low risk, common action    |
| Add comment   | Yes         | Can show pending state     |
| Delete item   | No          | Destructive, needs confirm |
| Payment       | No          | Critical, must verify      |
| Form submit   | Maybe       | Depends on complexity      |

## Form Submission UX

### Client → Server Flow

```
User Input → Client Validation → Submit → Server Validation → Response
     ↓              ↓              ↓              ↓              ↓
  Feedback    Inline errors   Loading...   Field errors    Success/Error
```

### Multi-Step Forms

```tsx
// Show progress and allow back navigation
<FormStepper
  steps={["Details", "Payment", "Confirm"]}
  currentStep={step}
  onBack={() => setStep((s) => s - 1)}
/>
```

## Authentication UX

### Login Flow Patterns

| State         | UX                           |
| ------------- | ---------------------------- |
| Loading auth  | Full-page skeleton           |
| Not logged in | Show login form              |
| Logging in    | Disable form, show spinner   |
| Success       | Redirect with toast          |
| Error         | Inline error, keep form data |

### Protected Route Pattern

```tsx
// Redirect unauthenticated users
if (!user && !loading) {
  return <Navigate to="/login" state={{ from: location }} />;
}
```

## Real-Time Updates

| Pattern   | Use Case                              |
| --------- | ------------------------------------- |
| Polling   | Low-frequency updates (notifications) |
| WebSocket | Chat, live collaboration              |
| SSE       | One-way server updates                |

### Presence Indicators

- Online status dots
- "User is typing..." indicators
- Collaborative cursors

## Full-Stack Design Critique

| Aspect           | Questions                        |
| ---------------- | -------------------------------- |
| Loading states   | What shows during API calls?     |
| Error recovery   | Can users recover from errors?   |
| Offline behavior | What happens without network?    |
| Auth transitions | Smooth login/logout experience?  |
| Data freshness   | Is stale data clearly indicated? |

## See Also

- [Generic UX Designer](../generic-ux-designer/SKILL.md) - Base methodology
- [UX Principles](../_shared/UX_PRINCIPLES.md) - Research methods, heuristics
- [Design Patterns](../_shared/DESIGN_PATTERNS.md) - Visual patterns

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Frontend and UI →

From the same set117

The whole set →
seo-analytics-auditor seo-analytics-auditor — a skill that checks meta tags, structured data, analytics scripts and Core Web Vitals on a page. It reads the source HTML and walks through the SEO checklist item by item. CX Codex +1 156installs financial-scenario-planner financial-scenario-planner runs a financial plan through bear, base and bull cases, then adds sensitivity tables, break-even and a runway check. Useful when the assumptions behind a model need testing. CX Codex +1 156installs product-management product-management equips your agent with product strategy frameworks: RICE scoring, roadmap horizons, OKR setups, and PMF validation surveys. CX Codex +1 153installs agent-teams Teaches Claude how to compose agent teams: which tasks split well, how many teammates to spawn, and what goes into each spawn prompt. Active only once teams are enabled. CX Codex +1 153installs fundraising-analyzer The fundraising-analyzer skill breaks down nonprofit fundraising with donor segments, campaign ROI, retention metrics, and trend views. Use it to review results or plan campaigns. CX Codex +1 153installs microservices-architecture The microservices-architecture Claude Code skill guides microservice design, monolith decomposition, and service communication choices. It activates for distributed-system design tasks. CX Codex +1 153installs debug-systematic debug-systematic — a four-phase debugging skill for hard-to-reproduce failures, race conditions, and unexplained behavior. It guides the agent from reproduction to verified fix. CX Codex +1 152installs mobile-cicd mobile-cicd guides CI/CD pipelines for iOS and Android apps using Fastlane, GitHub Actions, EAS Build, and code signing configs. CX Codex +1 152installs

Project sponsors

Companies that keep this analytics open