react-vite-guide
React 19 + Vite SPA development guidelines. Use PROACTIVELY when writing, reviewing, or refactoring any React component — even if the user doesn't explicitly ask for best practices. Covers composition patterns (compound components, boolean prop elimination, state lifting, context providers), performance optimization (React.lazy, Suspense, code splitting, useMemo, useCallback, memo, re-render prevention, bundle size reduction), and web interface best practices (accessibility, ARIA, forms, animation, dark mode). Triggers on any work involving useState, useEffect, useRef, useMemo, useCallback, useTransition, useContext, use(), React.lazy, Suspense, SWR, React Router, Vite config, import.meta.env, manualChunks, rollupOptions, Tailwind CSS, CSS Modules, or barrel file imports. Also triggers on performance debugging, re-render issues, bundle analysis, code splitting decisions, component architecture discussions, state management patterns, or new feature development in React + Vite projects.
What this skill does
# React 19 + Vite Guide Comprehensive guidelines for building React 19 SPA applications with Vite. Combines composition patterns, performance optimization, and web interface best practices into a single reference optimized for AI agent workflows. ## Tech Stack - **React 19** — `use()`, ref as prop, React Compiler support - **Vite** — `React.lazy()` + dynamic `import()`, env variables, HMR - **TypeScript** — strict mode recommended - **Pure SPA (CSR)** — no SSR, no hydration concerns ## Capability Index ### 1. Composition Patterns (references/composition-patterns.md) Component architecture and state management patterns for scalable React apps. | Priority | Category | Impact | |----------|----------|--------| | 1 | Component Architecture | HIGH | | 2 | State Management | MEDIUM | | 3 | Implementation Patterns | MEDIUM | | 4 | React 19 APIs | MEDIUM | Key topics: - Boolean prop proliferation vs composition alternatives - Compound components with shared context - State management decoupled from UI via providers - Generic context interfaces (state/actions/meta) - State lifted into providers for sibling access - Explicit component variants vs boolean modes - Children vs render props - React 19: `use()` replaces `useContext()`, ref as regular prop ### 2. Performance Optimization (references/performance-optimization.md) Performance optimization patterns adapted for Vite + React 19 SPA. Next.js-specific patterns removed; Vite equivalents provided. | Priority | Category | Impact | |----------|----------|--------| | 1 | Async Optimization | CRITICAL | | 2 | Bundle Size | CRITICAL | | 3 | Client-Side Data Fetching | MEDIUM-HIGH | | 4 | Re-render Optimization | MEDIUM | | 5 | Rendering Performance | MEDIUM | | 6 | JavaScript Performance | LOW-MEDIUM | | 7 | Advanced Patterns | LOW | Key topics: - `Promise.all()` and dependency-based parallelization - `React.lazy()` + `Suspense` for code splitting (Vite) - Barrel file import cost and direct imports - Hover/focus preloading for perceived speed - SWR for client-side data deduplication - Functional `setState`, lazy state initialization - `useTransition` for non-urgent updates - `content-visibility: auto` for long lists - `useRef` for transient values - Module-level caching patterns ### 3. Web Interface (references/web-interface.md) UI/UX patterns for accessibility, forms, animation, performance, and content quality. | Category | Focus | |----------|-------| | Accessibility | ARIA, semantic HTML, keyboard handlers | | Focus States | `focus-visible`, no bare `outline-none` | | Forms | `autocomplete`, correct `type`, paste allowed | | Animation | `prefers-reduced-motion`, compositor-only props | | Typography | Ellipsis, curly quotes, `tabular-nums` | | Content Handling | Truncation, empty states, long content | | Images | Explicit dimensions, lazy loading | | Performance | Virtualization, no layout reads in render | | Navigation & State | URL reflects state, deep-linkable UI | | Touch & Interaction | `touch-action`, `overscroll-behavior` | | Dark Mode | `color-scheme`, `theme-color` meta | | Locale & i18n | `Intl.DateTimeFormat`, `Intl.NumberFormat` | ### 4. Vite-Specific Patterns (references/vite-specific.md) Vite-specific configuration, conventions, and optimization patterns. Key topics: - Dynamic imports and code splitting with Vite - Environment variables (`import.meta.env`) - Vite plugin ecosystem (React SWC/Babel) - Build optimization (`manualChunks`, `rollupOptions`) - Alias and path resolution - CSS Modules / Tailwind CSS integration
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.