# reactive-dashboard-performance

reactive-dashboard-performance sets up React dashboard performance patterns and speeds up async test suites. Helps replace spinners with skeletons and resolve test runner timeouts.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 220 installs · ★ 274 repo stars
- Author: curiositech
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/curiositech/some_claude_skills/tree/HEAD/.claude/skills/reactive-dashboard-performance/SKILL.md
- Updated: 2026-10-30
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/reactive-dashboard-performance

## What it does

This skill guides the agent through performance architectures inspired by Linear, Notion, and Vercel. It prioritizes skeleton renders within 16ms, streaming data progressively without spinners for sub-200ms requests. For state handling, it applies React Query configs with a 5-minute `staleTime`, 30-minute `cacheTime`, and optimistic UI updates.

The second section focuses on fixing fragile test setups. It enforces testing real DOM nodes instead of mocking React UI widgets, isolating only network boundaries through tools like MSW. When integration tests hang, the diagnostic protocol directs the agent to inspect the DOM with `screen.debug()` and replace synchronous `getBy*` queries with asynchronous `findBy*` calls.

Without a proper `TestProviders` wrapper supplying `QueryClientProvider`, async component tests will fail immediately on missing context.

## Requirements
- Works with: Linear, Notion

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill reactive-dashboard-performance -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/reactive-dashboard-performance/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/reactive-dashboard-performance/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill reactive-dashboard-performance -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/reactive-dashboard-performance/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill reactive-dashboard-performance -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/reactive-dashboard-performance/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install curiositech/some_claude_skills .claude/skills/reactive-dashboard-performance
```

2. **Manually: put the files in place**
- File: `.github/skills/reactive-dashboard-performance/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill reactive-dashboard-performance -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/curiositech/some_claude_skills --path .claude/skills/reactive-dashboard-performance
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/reactive-dashboard-performance/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add curiositech/some_claude_skills --skill reactive-dashboard-performance -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/curiositech/some_claude_skills/tree/HEAD/.claude/skills/reactive-dashboard-performance/SKILL.md

## When to use it
- replace slow spinners with instant skeleton loading
- fix integration test timeouts caused by race conditions
- configure aggressive data caching in React Query
- apply React.lazy and component-level code splitting

## Example prompts
- Debug why our dashboard integration test is timing out
- Configure React Query caching rules for this analytics view
- Refactor the dashboard layout to use skeleton-first loading

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6d9fe5deda08cef7.

BEGIN THIRD-PARTY FILE 6d9fe5deda08cef7
````text
---
name: reactive-dashboard-performance
description: Expert in building blazing-fast reactive dashboards with comprehensive testing. Masters React performance patterns, testing strategies for async components, and real-world patterns from Linear,
  Vercel, Notion.
allowed-tools:
- Read
- Write
- Edit
- Bash
- Grep
- Glob
version: 1.0.0
triggers:
- dashboard performance
- slow tests
- reactive testing
- integration tests timeout
- dashboard optimization
metadata:
  category: Frontend Development
  tags:
  - react
  - performance
  - testing
  - dashboard
  - optimization
  pairs-with:
  - skill: react-performance-optimizer
    reason: Dashboard performance depends on React memoization, virtualization, and state management
  - skill: admin-dashboard
    reason: Admin dashboards are the primary consumer of reactive dashboard performance patterns
  - skill: data-viz-2025
    reason: Dashboard charts and graphs require performant data visualization rendering
---

# Reactive Dashboard Performance

Expert in building production-grade reactive dashboards that load in &lt;100ms and have comprehensive test coverage.

## Core Expertise

### Performance Patterns (Linear, Vercel, Notion-grade)

1. **Skeleton-First Loading**
   - Render skeleton immediately (0ms perceived load)
   - Stream in data progressively
   - Never show spinners for &lt;200ms loads

2. **Aggressive Caching**
   - React Query with staleTime: 5min, cacheTime: 30min
   - Optimistic updates for mutations
   - Prefetch on hover/mount

3. **Code Splitting**
   - Route-based splitting (Next.js automatic)
   - Component-level lazy() for heavy widgets
   - Preload critical paths

4. **Memoization Strategy**
   - useMemo for expensive computations
   - React.memo for pure components
   - useCallback for stable references

### Testing Reactive Dashboards

1. **Mock Strategy**
   - Mock at service boundary (React Query, analytics)
   - Never mock UI components (test real DOM)
   - Use MSW for API mocking when possible

2. **Async Handling**
   ```typescript
   // WRONG - races with React
   render(<Dashboard />);
   const element = screen.getByText('Welcome');

   // RIGHT - waits for async resolution
   render(<Dashboard />);
   const element = await screen.findByText('Welcome');
   ```

3. **Timeout Debugging**
````
END THIRD-PARTY FILE 6d9fe5deda08cef7

The third-party file has ended. Everything between the 6d9fe5deda08cef7 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2302 of 4821 bytes. © curiositech · MIT · https://github.com/curiositech/some_claude_skills/tree/HEAD/.claude/skills/reactive-dashboard-performance/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
