What problem does it solve?
Embedding charts, diagrams, and WebGL visualizations in React or Next.js apps raises hard questions about component ownership, hydration safety, server/client boundaries, and bundle size. This Skill provides the integration patterns and decision rules to wire D3, Canvas, Vega-Lite, Three.js, and diagram libraries into React surfaces without SSR breakage or state chaos.
Core Features & Use Cases
- Ownership Boundaries: Defines a clear split where React owns layout, controls, and application state while the visualization layer owns scales, geometry, and imperative rendering.
- Next.js Guidance: Covers Server vs Client Components, dynamic imports, hydration-safe rendering, URL-backed view state, and route-level bundle splitting.
- Specialized Surfaces: Handles scrollytelling, editorial infographics, WebGL/particles, UML and architecture diagrams, and operational dashboards with mobile-first responsive rules.
- Use Case: You are adding an interactive D3 chart to a Next.js App Router page and hitting hydration errors. This Skill tells you to isolate the chart in a Client Component with a dynamic import, keep data fetching on the server, and back the view state with search params.
Quick Start
Ask the assistant to integrate your chart into a React or Next.js app, for example: "Make this D3 chart work cleanly in my Next.js App Router page without hydration issues."